Re: problems with 4.3.4 and Tru64

[Peter Stephenson <pws@xxxxxxx>]

Timo Aaltonen <tjaalton@xxxxxxxxx> wrote:
> 'unset LANG' doesn't seem to help, and setopt doesn't show multibyte
> even if I try to load it. So it somehow fails to load, apparently?

It occurs to me this may simply be confusion because if multibyte is
on by default, it doesn't show up with "setopt" because that shows options
changed from the default.  Try also "setopt kshoptionprint".  Then you
should be able to see the state of multibyte with a further "setopt".  It
should now show up as "nomultibyte off", i.e. no change from the default
state of multibyte on.

(If that's not the problem: check that

#define MULTIBYTE_SUPPORT 1

is present in config.h.  If that's the case, multibyte support should be
compiled into the main shell and turned on by default.  Does "setopt
multibyte" give an error?  I presume it doesn't, but if it does, it may be
the wrong version of the shell.)

If that's all it is, and multibyte mode is on, see if something brutal does
the trick:

(unset LANG; unset -m 'LC_*'; export LC_ALL=fi_FI.UTF-8; zsh -f)

-- 
Peter Stephenson <pws@xxxxxxx>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


To access the latest news from CSR copy this link into a web browser:  http://www.csr.com/email_sig.php

To get further information regarding CSR, please visit our Investor Relations page at http://ir.csr.com/csr/about/overview