From: "Румен Петров" <transl@roumenpetrov.info>
To: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: warning: internationalized messages should not contain the '\v' escape sequence
Date: Sat, 18 Jan 2020 16:09:25 +0200 [thread overview]
Message-ID: <bee6334e-b7fa-e24f-e86c-198d55a47a26@roumenpetrov.info> (raw)
In-Reply-To: <928503646.1039073.1579042453618@poczta.nazwa.pl>
Rafal Luzynski wrote:
> 12.01.2020 12:59 Румен Петров <transl@roumenpetrov.info> wrote:
>> During the check of 2.30.9000 translation I note again above warning. In
>> Bulgarian tab is it is translated as new line.
>>
>> Please could you update original text to be gettext compliant.
>
> According to the documentation it is:
>
> "A descriptive string about this program; if it contains a
> vertical tab character (\v), the part after it will be
> printed *following* the options"
Hmm interesting, I cannot see in
https://www.gnu.org/software/gettext/manual/gettext.html .
>
> 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.
> 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.
...
>
> Regards,
>
> Rafal
>
Regards,
Roumen Petrov
next prev parent reply other threads:[~2020-01-18 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 11:59 warning: internationalized messages should not contain the '\v' escape sequence Румен Петров
2020-01-14 22:54 ` Rafal Luzynski
2020-01-18 14:09 ` Румен Петров [this message]
2020-01-19 5:05 ` Siddhesh Poyarekar
2020-01-20 18:10 ` Joseph Myers
2020-01-21 4:21 ` Siddhesh Poyarekar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bee6334e-b7fa-e24f-e86c-198d55a47a26@roumenpetrov.info \
--to=transl@roumenpetrov.info \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).