whoops! wrote that before my brain woke up. SciTE *is* your editor of course.
I work with a translator and often deal with Cyrillic text so I made utf-8 my default and never use anything else. I use these settings on WinXP: code.page=65001 character.set=utf8 LC_CTYPE=en_AU.UTF-8 Darren, you don't have "character.set=utf8" Is that why you have a problem? For me, SciTE writes the BOM on every new file it creates. It has no problem with the BOM being there, does not display it. Also there's no problem reading/writing such files with codecs in Python 2.5, when i use utf_8_sig encoding. Would like to switch to Linux some day - does SciTE have some problem with utf-8 on Linux? Regarding your other points about utf8 / 8bit, take a look at http://en.wikipedia.org/wiki/UTF-8#Description It's an excellent article. -jh Jim Hill wrote: > Darren Cook wrote: >> I'm editing UTF-8 files on linux and got bitten by the unexpected BOM >> character being inserted at the front of the file. > > (preface my comments with "to the best of my limited knowledge" ;) > > The BOM character is not unexpected. > SciTE is doing the right thing. > > An application that is unicode-aware should deal with the BOM > transparently and not show it in an edit window. > > In what way does what bite you? > Is it your editor application that needs fixing? > > A side note: > in python 2.5 there is a new encoding called utf_8_sig. > codecs now writes a BOM when you create a file with this encoding. > (with the old utf_8 encoding it did not write a BOM, > you had to do it yourself) > > - jh Send instant messages to your online friends http://au.messenger.yahoo.com _______________________________________________ Scite-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scite-interest
