[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nano-devel] RFC: some strings with problems

From: Mike Frysinger
Subject: Re: [Nano-devel] RFC: some strings with problems
Date: Tue, 8 Mar 2016 12:16:42 -0500

On 08 Mar 2016 18:02, Benno Schulenberg wrote:
> The messages with capitals in them were inherited from Pico.
> But I propose to remove the space before the question mark,
> and to use a semicolon instead of a comma where appropriate.
> See the first attached patch.

we should omit the space before punctuation.

> Looking through the Croatian PO file, I noticed that one of
> the messages that is put up on the statusbar is too long --
> 81 characters, when on an 80-column terminal only 76 positions
> are available for the message (the other 4 being taken up by
> the brackets and spaces: "[  ]").
> To see if there are more strings that are too long, I did this:
> msgmerge --no-wrap /dev/null po/nano.pot >blank.pot
> grep "^msgid " blank.pot | sed 's/msgid "//' | sed 's/"$//' |
>     while read line; do echo "$(echo $line | wc -c)  $line"; done |
>     grep -v "^. " | sort | less
> Luckily, it is the only line that is too long (the corresponding
> plural message will be even one character longer):
> 81  Read %lu line (Converted from DOS and Mac format - Warning: No write 
> permission)
> The second patch shortens this string.

i think having "warning" is more clear, but i won't lose sleep over it

Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]