Santiago Gala wrote:
Conor MacNeill escribió:
(...)
Just to be clear this is not a Gump issue - I think the problem would appear whenever you try to compile on any platform with a different default encoding.
Yes. For this reason, I'm encouraging people to start using utf-8 as default encoding in any server platform. This brings a whole new set of issues :-( but at least you can represent all Unicode characters, and ASCII maps transparently. This is specially important fot multilingual portals, for instance.
Pardon my ignorance, but can you tell me how to do this? The primary Gump machine is Redhat linux, many of the others are Solaris.
Under redhat, /etc/sysconfig/i18n contains definitions for the locale variables, sourced during system initialization. AFAIK, LC_CTYPE is the one involving numeric/alpha mappings, lower to upper mappings, and byte/character conversion, and LC_COLLATE the one involving character sort order.
export LC_ALL=en_US.UTF-8 in /etc/.profile (or .bash_profile... depending on shell) of the user under which the processes run should map all the variables to the used locale. "locale -a" should give a list of the available locales, which come in packages called locales-xx-version, or locales-version for the base one. If there are processes spawned by, say, an ant task, they will take whatever is in the environment at the moment.
I'm not Solaris Expert, so I can't comment on this.
- Sam Ruby
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Santiago Gala High Sierra Technology, S.L. (http://hisitech.com) http://memojo.com?page=SantiagoGalaBlog
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
