This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: warning: internationalized messages should not contain the '\v' escape sequence


On 18/01/20 7:39 pm, Румен Петров wrote:
>> which means that character is necessary in this place and should
>> be preserved by translators.  What kind of warning can you see?
> 
> Please see mail subject, i.e. warning: internationalized messages should
> not contain the '\v' escape sequence.

I see this too when I do a msgmerge.

>> Is it OK if we just ignore the warning?
> 
> :) Warning is warning. Question when warning is supposed to block a
> process is out of scope to this thread.
> 
> 
> Let me quite gettext manual (see url above):
> ...
> Another example is the ‘argp’ convention to use a single ‘\v’ (vertical
> tab) control character to delimit two sections inside a string. This is
> flawed. Some translators may convert it to a simple newline, some to
> blank lines. With some PO file editors it may not be easy to even enter
> a vertical tab control character. So, you cannot be sure that the
> translation will contain a ‘\v’ character, at the corresponding
> position. The solution is, again, to let the translator translate two
> separate strings and combine at run-time the two translated strings with
> the ‘\v’ required by the convention.
> ...
> 

This should be easy enough to fix in gencat.c once glibc master opens up
in February.

Siddhesh


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]