Bug Report - Characters with accents don't export properly

[Jan Erik Moström]

Trevor Harmon <trevor at vocaro.com> 2005-11-17 09:59:

> Yes, but getting back to the original point, you had suggested it's  
> okay for OmniOutliner not to include a BOM because it causes problems  
> in some text editors. This is not the case for modern (i.e. Unicode- 
> aware) text editors, so OO *should* be including a BOM when exporting  
> to UTF-8 text. It's a bug in OO, not merely a bad state of affairs  
> with regard to legacy text encodings.

I was trying to avoid commenting this ... the discussion have been long
enough ;-)

Once again I'm no expert of unicode, but from what I understand there is no
*requirement* that you use a BOM but it's a very good idea to use some kind
of meta information to indicate what encoding is used. If this is true, we
could argue if it's a bug or not.

Personally, I try to avoid BOMs since they cause problems when I use certain
tools that doesn't understand anything else than character streams.

Actually, the only time I use BOMs is when I want to write a "one-time"
python script and include characters like å, ä, ö. Python is able to detect
UTF-8 and use the proper encoding ... but if I'm writing something that I
expect to use for a longer time I use a special markup of the source file
just to get a text file without BOM.

I would probably use BOMs if all tools I used would understand them, but they
don't. (or even better, all programs would assume UTF8 as default)


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