On Tue, Oct 30, 2001 at 12:30:34PM -0500, Dom Lachowicz wrote: > One cannot make the assumption that the files on disk are written in the > same locale that you're running under.
There's no other assumption you can make. There are hundreds of encodings out there, and the only way Abiword can know what my prefered encoding is by asking me - i.e. the locale. > Hell, you might've gotten them from > someone who wrote it in iso-8859-1 (god forbid anyone use that locale any > more...). God forbid anyone use ISO-8859-3, or KOI8-R, or EUC-JP, or ... Dealing with multiple encodings on the same disk has always been the problem of the user. > AbiWord will assume ASCII text by default, just like it always has, No one's arguing the interpretation of octets 00-7F. But what do you do when an octet > 7F appears? > If you want Abi to read encoded text > via some mechanism and Abi *can't* auto-detect the encoding, then use the > encoded-text dialog and specify the encoding manually. As I said in my reply, I tried that. It work once, and then it doesn't work anymore. If I start up Abiword, go to file, open, change the selector to Encoded Text, select the file, select UTF-8, the abiword opens the file up with garbage. Again, there are two bugs here. If you won't fix the first one, please realize that I can't open up a UTF-8 file by using the encoded-text dialog, either. -- David Starner - [EMAIL PROTECTED] Pointless website: http://dvdeug.dhis.org "I saw a daemon stare into my face, and an angel touch my breast; each one softly calls my name . . . the daemon scares me less." - "Disciple", Stuart Davis - Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
