[ksh93-integration-discuss] Re: Some comments/questions about ksh93_20060831...

[Dr. Werner Fink]

On Tue, Sep 12, 2006 at 11:44:58PM +0200, Roland Mainz wrote:
> Glenn Fowler wrote:
> [snip]
> > > > Ok... thanks! :-)
> > > > ... but note that I hit the problem with LANG=en_US.UTF-8 and
> > > > LC_ALL=en_US.UTF-8 - that's a multibyte locale while "de" is usually a
> > > > link to "de_DE.ISO8859-1" or "de_DE.ISO8859-15" (which are both
> > > > single-byte locales in both Solaris and Linux) ... ;-(
> > 
> > > this is where I have a disconnect with utf8 vs 8bit vs 7bit locales
> > > you set LC_ALL to utf8 for a ksh
> > > you mouse snarf the 8bit german chars above and paste into ksh edit mode
> > > how does the edit sw know that the snarfed text is 3 8bit chars
> > > and not some utf8 encoding?
> > 
> > here's the promised repost
> 
> Sorry for the late reply to your original posting... currently I am a
> little bit slow getting all the emails answered... ;-(
> 
> > my original question may have been ill-posed, so I'll rephrase:
> > 
> > Roland, when you switched to a utf-8 locale, exactly what
> > sequence of events lead to the problem? I'm mainly interested
> > in the source of the <o-umlaut><a-umlaut><u-umlaut> that
> > ended up in the ksh read buffer
> 
> That was my laptop's keyboard (the normal german keyboard layout) in
> KDE's "konsole" terminal emulator running SuSE 10.0 (SuSE Linux uses
> en_US.UTF-8 as default locale if you select "English" as the default
> system language and AFAIK all other languages now use *.UTF-8 locales,
> too (maybe Werner Fink knows when the switch to *.UTF-8 locales occured
> in SuSE Linux)).

We switched over to UTF-8 since SuSE Linux 9.3.


           Werner

-- 
  "Having a smoking section in a restaurant is like having
          a peeing section in a swimming pool." -- Edward Burr