cc: [email protected] [email protected]
[email protected]
Subject: Re: Re: [ast-developers] Re: [ast-users] Write up on how to localize
shell scripts - Second Try
--------
I'm not sure how to handle scripts because $"string" is not part of
POSIX, but for ksh builtin commands it is IMO *required* that they
behave like external commands and recognize if NLSPATH is changed
like:
builtin cat
NLSPATH=/path/path2/wc1.cat:$NLSPATH cat thisfileisnothere
NLSPATH=/path/path2/wc2.cat:$NLSPATH cat thisfileisnothere
cat called in the 2nd line should use /path/path2/wc1.cat as message
catalog and cat in the 3rd line should use /path/path2/wc2.cat as
message catalog, assuming the ksh builtins should conform to POSIX.
Chris
--
^---^
(@)v(@) Chris Pickett
| / IT consultant
===m==m=== [email protected]
ksh93 handles $"..." when compiling the script similar to the way
that aliases are handled.
David Korn
[email protected]
_______________________________________________
ast-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-users
