Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Echoing of 8-bit-characters broken after 4.3.2?
- X-seq: zsh-workers 26647
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: Echoing of 8-bit-characters broken after 4.3.2?
- Date: Sat, 28 Feb 2009 15:01:31 -0800
- Cc: Wolfgang Hukriede <whukriede@xxxxxxxxxxxxxx>
- In-reply-to: <200902282349.55759.arvidjaar@xxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <2493fbfb0902281231t3b5d61b0g5a7898635fc1c9fc@xxxxxxxxxxxxxx> <200902282349.55759.arvidjaar@xxxxxxxxx>
} > True, but setting LANG to "is_IS.ISO8859-1" once and then setting it
} > to anything else seems to do the trick as well:
} > > export LANG=is_IS.ISO8859-1
} > > date
} >
} > lau 28 feb 2009 21:17:50 CET
} >
} > > export LANG=nada
} > > date
} >
} > Sat Feb 28 21:24:36 CET 2009
} >
} > Eight-bit-chars still work.
}
} setlocale() failed so old value (is_IS.ISO8859-1) remains in effect.
In more detail, what's happening is that the variable is no longer in
the environment, so it's not inherited by "date", even though zsh is
still using the previous local.
However, the deeper problem is that is_IS.ISO8859-1 is probably the
wrong value in the first place. I found it by tab-completing thus:
zsh% LANG=IS<TAB>
but on a closer look there are a whole lot of possible alternatives.
I'm guessing that perhaps one of de_AT.iso88591 or de_DE.iso88591 is
more correct, but you should look through the list yourself.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author