public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] i18n project
Date: Tue, 20 Jun 2006 17:35:29 -0400	[thread overview]
Message-ID: <200606201735.29905.vapier@gentoo.org> (raw)
In-Reply-To: <20060619201621.1ed5b579@pingviinilohhari>

[-- Attachment #1: Type: text/plain, Size: 728 bytes --]

On Monday 19 June 2006 13:16, Flammie Pirinen wrote:
> 2006-06-19, Jan Kundrát sanoi, jotta:
> > Paul de Vrieze wrote:
> > > What about messages output by ebuilds? Are they also going to be
> > > translated? In that case, how?
> >
> > There's no way to provide localized output of einfo/... calls from
> > ebuild that I'm aware of. Suggestions are welcome :)
>
> Is there a reason why calling gettext from einfo() etc. or extracting
> messages from tree using e.g. xgettext wouldn’t work?

this would make it impossible to translate strings when einfo is given 
user-based variables (die "econf $* failed")

just use bash's system for translating strings:
echo $"hihihihi"
einfo $"PLEASE TO READ ME"
-mike

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2006-06-20 21:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09 23:37 [gentoo-dev] [RFC] i18n project Diego 'Flameeyes' Pettenò
2006-06-10 13:11 ` Jan Kundrát
2006-06-11  0:16   ` Marius Mauch
2006-06-11  8:25     ` Peter Volkov (pva)
2006-06-11 11:08     ` Jan Kundrát
2006-06-19 15:12       ` Paul de Vrieze
2006-06-19 16:39         ` Jan Kundrát
2006-06-19 17:16           ` Flammie Pirinen
2006-06-20 21:35             ` Mike Frysinger [this message]
2006-06-11  7:57   ` Peter Volkov (pva)
2006-06-11 11:17     ` Jan Kundrát
2006-06-11  8:37   ` Nguyễn Thái Ngọc Duy
2006-06-11 11:20     ` Jan Kundrát
2006-06-12  6:43 ` Flammie Pirinen

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=200606201735.29905.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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