Re: Gump and Unicode
I once had the same problem with the JMeter sources, tried to add that encoding attribute to the java task, and it didn't help. It was helping on my platform, but not on Gump. I never learned why. If you attempt it here, I'll be interested to know if it works. Salut, Jordi. En/na Conor MacNeill ha escrit: On Thu, 12 Jun 2003 01:05 am, Brian Ewins wrote: Use the unicode escapes rather than the character literals in the code? You won't get DoubleMetaphone.java to compile unless you pass the encoding flag to javac. The two letters appear to be \u00C7, \u00D1 - capital C with a cedilla and capital N with a tilde? Putting case '\u00C7': case '\u00D1': in the appropriate places should fix things. Or add the encoding attribute to the javac task. The file may remain more readable that way, at least on some platforms. I'm not sure if that is possible from a Maven generated build file. 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. Conor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump and Unicode
Tim, I looked at the code in codec. It is obvious that GUMP error would occur the same as Jakarta-Jetspeed and other projects experienced once. (Also, in my Japanese environment, it is garbled character) This means that we Japanese can not build codec. (Default codepage is different) ... Needless to say, I failed. Please change the Ntilde etc. to \u*** style. (just use native2ascii in your env) Sincerely, -- Tetsuya ([EMAIL PROTECTED]) - On 11 Jun 2003 09:37:59 -0500 (Subject: Gump and Unicode) Tim O'Brien [EMAIL PROTECTED] wrote: commons-codec fails to compile in Gump because it contains an Ntilde among other characters used in languages other than English. Any ideas? - Tetsuya Kitahata -- Terra-International, Inc. E-mail: [EMAIL PROTECTED] : [EMAIL PROTECTED] http://www.terra-intl.com/ (Apache Jakarta Translation, Japanese) http://jakarta.terra-intl.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump and Unicode
Sam Ruby escribió: 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]
RE: Gump and Unicode
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 I'm not Solaris Expert, so I can't comment on this. My installs of Solaris 2.6 and 8 support the en_US.UTF-8 locale, so I suspect the process is the same. (although I haven't tested) NOTICE This e-mail and any attachments are confidential and may contain copyright material of Macquarie Bank or third parties. If you are not the intended recipient of this email you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. Macquarie Bank does not guarantee the integrity of any emails or any attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Macquarie Bank. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump and Unicode
Tim O'Brien escribió: commons-codec fails to compile in Gump because it contains an Ntilde among other characters used in languages other than English. Any ideas? I seem to recall that java source code is supposed to be written in unicode, but I could be wrong. The '\u' convention is ASCII and should be safe, instead of using 8/16 bit characters in code. If the original files are right, but gump's version is not, something bad is happening in the cvs commit/checkout encoding/decoding or gump processing pipes. Difficult to track, and potentially nasty problems ensured. Regards, and good luck - 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]
Re: Gump and Unicode
Santiago Gala escribió: Tim O'Brien escribió: commons-codec fails to compile in Gump because it contains an Ntilde among other characters used in languages other than English. Any ideas? I seem to recall that java source code is supposed to be written in unicode, but I could be wrong. The '\u' convention is ASCII and should be safe, instead of using 8/16 bit characters in code. http://mail.python.org/pipermail/string-sig/1999-January/001117.html gives some light. -- 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]
Re: Gump and Unicode
Use the unicode escapes rather than the character literals in the code? You won't get DoubleMetaphone.java to compile unless you pass the encoding flag to javac. The two letters appear to be \u00C7, \u00D1 - capital C with a cedilla and capital N with a tilde? Putting case '\u00C7': case '\u00D1': in the appropriate places should fix things. Tim O'Brien wrote: commons-codec fails to compile in Gump because it contains an Ntilde among other characters used in languages other than English. Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Privacy and Confidentiality Notice The information contained in this E-Mail message is intended only for the person or persons to whom it is addressed. Such information is confidential and privileged and no mistake in transmission is intended to waive or compromise such privilege. If you have received it in error, please destroy it and notify us on the telephone number printed above. If you do not receive complete and legible copies, please telephone us immediately. Any opinions expressed herein including attachments are those of the author only. i-documentsystems Ltd. does not accept responsibility for the accuracy or completeness of the information provided or for any changes to this Email, however made, after it was sent. (Please note that it is your responsibility to scan this message for viruses). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump and Unicode
On Thu, 12 Jun 2003 01:05 am, Brian Ewins wrote: Use the unicode escapes rather than the character literals in the code? You won't get DoubleMetaphone.java to compile unless you pass the encoding flag to javac. The two letters appear to be \u00C7, \u00D1 - capital C with a cedilla and capital N with a tilde? Putting case '\u00C7': case '\u00D1': in the appropriate places should fix things. Or add the encoding attribute to the javac task. The file may remain more readable that way, at least on some platforms. I'm not sure if that is possible from a Maven generated build file. 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. Conor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump and Unicode
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. Conor -- 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]
