UTF-8/NLS dilemma

[H.Merijn Brand]

On Thu, 23 Nov 2006 09:12:15 +0100, "H.Merijn Brand" wrote:
> > The requirement to handle e.g. multibyte characters can be fulfilled
> > only by assuming LC_CTYPE is correctly set and libc supports the used
> > encoding, or by reimplementing the necessary libc functionality (which
> > is rather impractical, considering that glibc currently supports 240
> > different character encodings).
> 
> It is not only $LANG and/or $LC_ALL. It also depends on the font you chose.
> It is very confusing to have a iso8859-1 xterm with iso-10646-1 font or vise
> versa. Things start to fail.
> 
> Maybe somewhere somehow there should be a check on wide-char enabled tcsh
> running on utf8 enabled xterm with iso10646 (or other utf8 enabled) font.
> 
> I've chosen for the static library approach,

That worked out.

% llldd /pro/bin/tcsh
ldd[01] on /pro/bin/tcsh                  <=
ldd[02] on /usr/lib/hpux64/libsec.so.1    <= /pro/bin/tcsh
ldd[03] on /usr/lib/hpux64/libm.so.1      <= /usr/lib/hpux64/libsec.so.1
ldd[02] on /usr/lib/hpux64/libc.so.1      <= /pro/bin/tcsh
ldd[03] on /usr/lib/hpux64/libdl.so.1     <= /usr/lib/hpux64/libc.so.1
ldd[02] on /usr/lib/hpux64/libm.so.1      <= /pro/bin/tcsh
ldd[02] on /usr/lib/hpux64/libdl.so.1     <= /pro/bin/tcsh
Lib                                  Real path                            Size      Date                Refs
------------------------------------ ------------------------------------ --------- ------------------- ----
/pro/bin/tcsh                        /pro/bin/tcsh                          1180800 2006-11-23 09:44:46    4
/usr/lib/hpux64/libsec.so.1          /usr/lib/hpux64/libsec.so.1             470080 2005-12-07 01:48:42    1
/usr/lib/hpux64/libm.so.1            /usr/lib/hpux64/libm.so.1              2237184 2005-05-18 23:41:14    0
/usr/lib/hpux64/libc.so.1            /usr/lib/hpux64/libc.so.1              4319432 2006-02-14 15:25:00    1
/usr/lib/hpux64/libdl.so.1           /usr/lib/hpux64/libdl.so.1               34736 2006-03-15 22:43:11    0


Now, when setting LC_ALL to univ.utf8, I can enter and use utf8.
/me very happy :)

Problem still with backspace. When using utf8 outside of the iso8859 region,
like L-DOT (ŀ) L-STROKE (ł) and AE-LIGATURE (æ), backspacing over these
erases them, but goes back too much

More specific:

prompt > ŀłæ

After the prompt, I enter AltGr . l AltGr / l AltGr a e
First backspace clears the ae, second clears the l/ third clears the l.
but the I can still enter three more backspaces that clear out the trail of the prompt

-- 
H.Merijn Brand         Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using & porting perl 5.6.2, 5.8.x, 5.9.x   on HP-UX 10.20, 11.00, 11.11,
& 11.23, SuSE 10.0 & 10.1, AIX 4.3 & 5.2, and Cygwin. http://qa.perl.org
http://mirrors.develooper.com/hpux/            http://www.test-smoke.org
                        http://www.goldmark.org/jeff/stupid-disclaimers/