NB> the level 4 kludge should at least be honored while I'm using a NB> multibyte character encoding. No?
If you say so. I still don't understand why a native linux application would require it. Near as I can tell it does nothing which is a *good* thing imho. All the editors I have tried have no issues with UTF-8 characters in a 'linux' terminal enviroment. Beats me why anyone porting an app to Linux should wish to have it any other way. I could say exactly the same about any codepage that is supported by the kernel. The level parameter is useless near as I can tell from this angle, which includes 7-bit ascii codes and supported 8-bit character codepages. However it doesn't hurt anything so if others require it then I don't have any issues with supplying it. I honestly believe my CHRS kludge is up to snuff and I cite the 'Møøse' in the tagline as evidence that it truly works and is not just some bogus claim.
NB> should definitely NOT be showing up as "UTF-8 2"
Agreed. However I still see your UTF-8 characters as UTF-8 characters despite the above.
NB> the Win32 version that Michiel uses
I have yet to see any evidence of it truly working despite it getting the kludge right. Have you?
Life is good, Maurice
... A Møøse once bit my sister ... --- GNU bash, version 4.2.45(2)-release (x86_64-unknown-linux-gnu) * Origin: Pointy Stick Society - Ladysmith BC, Canada (1:153/7001.0)
