Re: utf8 and solaris

Rich, thanks for your thoughts.
I do have the locale en_US.UTF-8 and tcsh support them good on linux and AIX. When it comes to solaris though I see it behave strange. Well as a program even a smal sample like the below can dump octal values for "$".

#!/usr/bin/tcsh -f
set verbose
setenv LC_CTYPE "en_US.UTF-8"
echo $$
exit

Could be a tcsh thing..

Thanks
Balaji

Rich Felker wrote:

On Sat, Nov 18, 2006 at 07:43:54PM +0530, Balaji.Ramdoss wrote:

Folks, well this is not on linux. I have an issue in Sun Solaris box 
where octal values gets displayed instead of symbols like "^","|" as 
\136, \075.
This happens if I set my LC_CTYPE to en_US.UTF-8 locale and I have the 
"set verbose" on.
The OS/hardware is
SunOS irvhomer 5.9 Generic_118558-23 sun4u sparc SUNW,Ultra-250
and the tcsh is
tcsh 6.14.00 (Astron) 2005-03-25 (sparc-sun-solaris) options 
wide,nls,dl,al,kan,rh,color,filec

Will really appreciate if someone has any possible work around to this 
solaris/tcsh bug ?


1. Does your version of Solaris actually have a locale named
   en_US.UTF-8? If not you need to figure out how to create it.

2. What program is displaying octal codes, etc.? If it's tcsh the
   problem is most likely just that tcsh sucks. :) As far as I know it
   doesn't support UTF-8. You might be able to get it to display the
   characters with the same options that make 8bit encodings work, but
   I suspect it will be hard to interactively edit the commandline.

Rich


--
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/linux-utf8/

Confidentiality Statement:

This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by return email.