I fully agree with Irek here. Compiled shell scripts should be NLS-aware. Users expect no less than that. At the very least, if this is truly the case, text needs to be added to the shcomp man page to warn people about this serious restriction.
- Finnbarr > Date: Wed, 28 Jul 2010 23:13:21 +0200 > Subject: Re: Re: Re: [ast-developers] Re: [ast-users] Write up on how to > localize shell scripts - Second Try > From: [email protected] > To: [email protected] > CC: [email protected]; [email protected]; > [email protected] > > On Wed, Jul 28, 2010 at 10:20 PM, David Korn <[email protected]> wrote: > > cc: [email protected] [email protected] > > [email protected] [email protected] > > Subject: Re: Re: Re: [ast-developers] Re: [ast-users] Write up on how to > > localize shell scripts - Second Try > > -------- > > > >> Are $"..." strings handled the same as normal "..." literals when the > >> script is compiled or is there a difference? > >> > >> > > > > They are replaced by the locale specific string and treated just > > as if the were "..." strings after substitution. > > Do you say the replacement of strings happen at the time shcomp > compiles the literals? This IMO defeats the purpose of localisation > and forces anyone who uses shcomp compiled shell scripts to use > /bin/gettext again to localise compiled shell scripts. > > Irek > _______________________________________________ > ast-developers mailing list > [email protected] > https://mailman.research.att.com/mailman/listinfo/ast-developers
_______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
