On Wed, 28 Jul 2010 15:16:48 +0200 I. Szczesniak wrote:
> IMO both LC_MESSAGES and NLSPATH are required to be dynamic, if we
> still assume that the localisation of a shell function and shell built
> in commands like cut, paste should be able to behave like an external
> command. As example:
> ----------------------------------------
> unset LC_ALL LANG LC_MESSAGES
> function printhello
> {
> print $"hello"
> }
> LC_MESSAGES=fr_FR.utf-8 printhello
> LC_MESSAGES=C printhello
> LC_MESSAGES=ja_JP.utf-8 printhello
> ----------------------------------------
and this is the case in ksh+ast
with the exception that NLSPATH changes will not affect
message catalogs already located by the current process
e.g., for
NLSPATH=foo
LC_MESSAGES=fr_FR.utf-8 printhello
LC_MESSAGES=C printhello
NLSPATH=bar
LC_MESSAGES=fr_FR.utf-8 printhello
LC_MESSAGES=ja_JP.utf-8 printhello
the second printhello will use the same message catalog as the first
even if the NLSPATH change would have located a different catalog
but the last printhello will check NLSPATH=bar for its catalog
_______________________________________________
ast-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-users
