On 02-May-2010 Bram Moolenaar <[email protected]> wrote: > > Ron Aaron wrote: > > > I have recently started editing files with a '.wiki' extension, and > > rather than getting the 'wikipedia' filetype, they pick up the > > 'flexwiki' type. That's not the problem. > > > > The problem is that the 'flexwiki' filetype handler sets "bomb", > > resulting in extra characters at the front of my utf8 files -- this > > has caused problems with other software which reads those files (I > > never have 'bomb' set). > > > > Scanning the ftplugins, it seems 'flexwiki' is the only one which sets > > 'bomb'. Is it an ok thing for it to do? Also, why is "flexwiki" the > > handler, when wikipedia is probably the most widely used wiki? But > > that's a quibble. > > Setting 'bomb' is weird. Unless the filetype requires the file to be > written in utf-8 for the file to be working properly. [...] > As a guard, 'bomb' should only be set when 'encoding' is utf-8. > This applies to 'fileencoding' as well.
I might be totally wrong basing my understanding of BOM and character sets mainly on Wikipedia, but I thought that setting 'bomb' for utf-8 encoded files (which does not pose a risk of misinterpreting the contents due to endianness difference) didn't make much sense. For utf-16 that would be another thing. http://en.wikipedia.org/wiki/Byte-order_mark -- Cheers, Lech -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
