cc: [email protected] [email protected] [email protected] [email protected] Subject: Re: Re: Re: Re: [ast-developers] Re: [ast-users] Write up on how to localize shell scripts - Second Try --------
> 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 > > I have looked at this further. Currently, shcomp replaces I18N message strings at compilation. However, shcomp -n does not replace them at compile time. When the compiled script or function is read in, they are replaced at that time. However, there is a one line bug in ksh93t and in the current beta for ksh93u which causes a core dump when trying to run a script compiled with shcomp -n. The next ksh93u beta will have a fix for this and we are considering putting out an update to ksh93t+ for this as well. However, if you run a script and change the locale inside a compound command, whether compiled or not, the error messages will be from the locale known at the time the compound command is read. This is similar to the behavior of aliases. Changing this behavior would require a lot of changes, and unless I can be convinced that this is important enough, it is not likely to change. I am also considering making shcomp, without -n, generate what shcomp -n generates, but I am concerned that compiled scripts will be attemtped to be run with a ksh without the core dump fix. David Korn [email protected] _______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
