Bug Report - Characters with accents don't export properly

[Jan Erik Moström]

Trevor Harmon <trevor at vocaro.com> 2005-11-16 19:40:

> Okay, bad example. :) It appears BBEdit either defaults to UTF-8 or  
> has some kind of autodetection mechanism, so you don't even need an  
> encoding tag. But other text editors, such as TextEdit and jEdit,  
> don't have this feature, and they depend on the BOM as a flag to turn  
> on UTF-8 decoding. So even though some editors don't require it, some  
> do; that's why the BOM needs to be there.

I think we agree on the major point:

    The current situation for text files are bad, there are a
    number of encodings there and with a plain text file there is
    no way to *know* what encoding a file uses ... the programmer
    has to guess the encoding or let the user be able to choose
    (but most users don't know what the problem is, they just see
    the garbled text).

    So a text file needs some meta-information about what encoding
    the file contains, so it becomes possible for programs to differ
    between Latin1, MacRoman, WindowLatin1, UTF-8, etc

-- 
Jan Erik Moström, www.mostrom.pp.se