From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: gettext in scripts
Date: Sat, 10 Mar 2012 23:25:13 +0100 [thread overview]
Message-ID: <4F5BD4C9.4010708@gmail.com> (raw)
In-Reply-To: <4F35B480.9020402@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
On 11.02.2012 01:21, Andreas Born wrote:
> I think for common use cases it would be enough to add additionally to
> the already implemented locale_dir=$dir1 a second environment variable
> like additional_locale_dir=$dir2. That would overcome the problem of
> reloading all directories/ comparing lists. It offers less
> flexibility, but a too long list of files to search would probably
> have a negative performance penalty anyway.
I think everyone reached this consensus. Additionally it makes it
similar to bash with TEXTDOMAIN variable. So the use is
secondary_locale_dir=<my .mo directory>
echo $"Text to translate"
Because I discovered an important bug in gettext (inability to disable
it or change locale_dir) it needed a restructure and squeezing this was
trivial. Given gettext importance I did so.
However currently there is no "printf" in grub and it would be too big
for freeze exception. Lack of printf puts limits to localisation.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
prev parent reply other threads:[~2012-03-10 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 22:54 gettext in scripts Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-11 0:21 ` Andreas Born
2012-03-10 22:25 ` 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=4F5BD4C9.4010708@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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 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.