On Mon, Dec 08, 2008 at 03:33:49PM +0100, Carles Pina i Estany wrote: > > Hello, > > On Dec/08/2008, Carles Pina i Estany wrote: > > > I understand that we/I should adapt some scripts using, for example, this > > guideline?: > > http://www.gnu.org/software/automake/manual/gettext/Preparing-Shell-Scripts.html > > > > (I haven't tested now, I think that some years ago I did some tests with > > They use gettext.sh file, in my Debian is in: > /usr/bin/gettext.sh, in package gettext-base . Do you think that this is > the best way? Do we assume that gettext.sh it's there, or we provide > backfail mechanism? (for example I don't think that this file comes with > cygwin...) > > I can translate in two ways: > ---- > echo $(gettext "hello world") > eval_gettext "hello world";echo > ---- > > so, with eval_gettext (comes from gettext.sh) or from gettext binary > straight. > > eval_gettext helps a bit substituing shell variables: > # eval_gettext MSGID > # looks up the translation of MSGID and substitutes shell variables in the > # result. > eval_gettext () { > gettext "$1" | (export PATH `envsubst --variables "$1"`; envsubst > "$1") > } > > But we could do it without gettext.sh > > Which method do you think that we should use? > With failback option?
I have no idea about this, and others in this list didn't reply. I suggest you ask Jordi Mallach (CCed). He's quite knowledgeable about such things and often hangs around here too ;-) -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
