On 6/9/07, Quentin Mathé <[EMAIL PROTECTED]> wrote: > Le 9 juin 07 à 18:49, Yen-Ju Chen a écrit : > > > I found PuTTY has codes to convert common western encoding to Unicode > > and spit out the incomplete one. > > It is very convenient for terminal emulator because like StepChat, > > it may not always receive a complete glyph. > > It is under MIT license, so I probably will use it. > > > > Quentin, could you do me a favor ? > > Sure. > > > I need to know how OSX handles terminal encoding. > > I assume you use French version, which is iso8859-1 encoding ? > > I do use French version, but Terminal default encoding is set to UTF-8. > > > I need to know what's the output of 'locale' command. > > LANG= > LC_COLLATE="C" > LC_CTYPE="C" > LC_MESSAGES="C" > LC_MONETARY="C" > LC_NUMERIC="C" > LC_TIME="C" > LC_ALL="C"
It is interesting that LC_CTYPE is 'C', which means it treats all character as C encoding (ASCII ?). > > > And what is your default C string encoding [NSString > > defaultCStringEncoding]. > > NSMacOSRomanStringEncoding > And all Cocoa (and probably Carbon) applicaions treats characters as Roman. Then I wonder how Unix command, like 'more' and 'vi', see the characters. It also raises the question what is the encoding of the file system (filename). Is it UTF8 (compatible with ASCII) or MacOSRoman ? A quick way to see is changing line 416 in TXTextView.m to difference encoding and see. It is where it decides how to convert characters into NSString. Yen-Ju > Hope it helps, > Quentin. > _______________________________________________ > Etoile-discuss mailing list > [email protected] > https://mail.gna.org/listinfo/etoile-discuss > _______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
