[g11n-ko-discuss] Re: [i18n-discuss] [Fwd: Re: ksh93 i18n problems on Solaris ? / was:Re: [ksh93-integration-discuss] comments on ksh93 migration plan]

[Roland Mainz]

Ienup Sung wrote:
> I just built the ksh93 as Roland instructed and uploaded the binaries at
> the following location:
> 
>         http://www.opensolaris.org/os/community/int_localization/tmp/

Thanks! :-)

> The binaries have been built with Solaris 10 and SOS10 C compiler and so
> they should work for S10 and SX releases. There is also readme.txt file that
> people can take a look at to see some more info on how to extract and what to
> test.
> 
> I also briefly tested the ksh with en_US.UTF-8 locale and found the result
> a bit of mixed bag. I was able to input most of

What do you mean with "most of" ? Were there any failures with
characters in these languages?

> CJK, Arabic, Greek, Cyrillic
> characters and also view all Unicode characters (for that, by doing
> "more /usr/pub/UTF-8") but I wasn't able to input some accented characters
> such as ä, ç, and so on.

Which terminal emulator did you use ? The Gnome terminal ? Does it work
with other terminal emulators (e.g. "dtterm" or KDE's "konsole") ?
How does normal Solaris ksh behave for such characters (or bash3) ?
BTW: Did you enable "emacs" or "vi" editing mode (e.g. % set -o emacs #)
before entering the chars ?

> I was, however, able to input Å,, Å?, and so on.

Weired. Any idea what is going wrong here (except the list of "usual
suspects" listed above) ?

> (The attached script file shows the test log that I did. The same for i386
> version of ksh too.)
> 
> I did "ldd ksh" after the build and it showed the following by the way:

BTW: You build the 64bit version on SPARC... did you get the same issues
with accented characters when you run the 32bit version ?

>         system% ldd arch/sol10.sun4/bin/ksh
>          libm.so.2 =>     /lib/64/libm.so.2
>          libsecdb.so.1 =>         /lib/64/libsecdb.so.1
>          libc.so.1 =>     /lib/64/libc.so.1
>          libnsl.so.1 =>   /lib/64/libnsl.so.1
>          libcmd.so.1 =>   /lib/64/libcmd.so.1
>          libmp.so.2 =>    /lib/64/libmp.so.2
>          libmd5.so.1 =>   /lib/64/libmd5.so.1
>          libscf.so.1 =>   /lib/64/libscf.so.1
>          libdoor.so.1 =>  /lib/64/libdoor.so.1
>          libuutil.so.1 =>         /lib/64/libuutil.so.1
>          /platform/SUNW,Sun-Blade-1000/lib/sparcv9/libc_psr.so.1
>          /platform/SUNW,Sun-Blade-1000/lib/sparcv9/libmd5_psr.so.1
> 
> And I also noticed that you've src/lib/libcmd/cat.c patched.

That's the builtin version of /bin/cat ...

> Would I also
> need to add -Bstatic before linking with the -lcmd?

The libcmd issue is slightly different. ksh93 has it's libcmd and
Solaris has it's own libcmd.
- For "buildksh93.ksh" I am simply linking libcmd.a (due lack of a
shared library this should work (or not... I really didn't check this
but I think you're right with the -Bstatic thing... ;-/ ) - and for the
non-shared version of ksh93 (e.g. without seperate libast, libdll,
libshell etc. libraries) it works definately as this is the normal way
how the kornshell.com people build it).
- For OS/Net I have a merged version of libcmd which contains both
versions (see
http://mail.opensolaris.org/pipermail/ksh93-integration-discuss/2006-March/000172.html).
IMO it's IMO better to ship the non-shared version for testing purposes
which does not depend on all the other libraries...

BTW: Does Sun have any automated i18n test scripts for shells ?

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz at nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 7950090
 (;O/ \/ \O;)