From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: "Mario Blättermann" <mario.blaettermann@gmail.com>
Cc: The development of GRUB 2 <grub-devel@gnu.org>, yurchor@ukr.net
Subject: Re: Unclear gettextized strings
Date: Tue, 21 Feb 2012 17:27:08 +0100 [thread overview]
Message-ID: <4F43C5DC.7040303@gmail.com> (raw)
In-Reply-To: <4F2ECE45.5000201@gmail.com>
On 05.02.2012 19:45, Mario Blättermann wrote:
> Am 05.02.2012 19:23, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
>> We use the word "key" several times to refer to the key that you
>> press but the same word also means a key in catalog and both Yuri and
>> Mario understood messages like "unknown key" in the second sense.
>> I've rephrased those somehow, now it should be clear.
> I've translated "key" in sense of an "encryption key" and not a
> keyboard key, which could be wrong in some (or almost all?) cases.
> Besides your recent source code changes, you should add some
> translator comments and send the updated pot file to the TP Robot.
I both agree and disagree. I agree that some of the strings are too
short. But I also think that in most cases one should make the string
themselves clearer.
Also please don't do manual line-breaking in .po since GRUB already
handles it and takes the real screen width into account.
I've submitted the new tgz. It contains also .po which is fixed a bit. I
hope that TP robot will pick those de.po and uk.po
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
prev parent reply other threads:[~2012-02-21 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 18:23 Unclear gettextized strings Vladimir 'φ-coder/phcoder' Serbinenko
[not found] ` <4F2ECE45.5000201@gmail.com>
2012-02-21 16:27 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F43C5DC.7040303@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
--cc=mario.blaettermann@gmail.com \
--cc=yurchor@ukr.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.