May I add some observation to this discution? The better way to use BOM is when you know your target. I work in a MacBook which has UTF-8 as default. When I'm working with Objective-C that will be compiled using LLVM there is no problem using BOM (which is a good thing since the encoding can be easily recognized). But when I'm working with Java, doing something for the Android platform, I use ISO-8859-1 because the Google guys had defined the 'encoding' argument of the 'javac' compiler as 'ASCII' in an ANT XML somewhere.
I known, also, that PHP doesn't handle BOM well. So I decided to work with PHP also in ISO-8859-1. But, my e-mails are all HTML formated using UTF-8 with BOM (edited on VIM), always seen in Firefox, Safari or Chrome with no problems. I believe that the problem with major browsers is in respect with user configuration. You can left the browser discover the character set of a page or configure it to use one based in the assumption that you are in an occidental country (or another part of the world). This causes no problems if you don't open pages from another countries. In the current days, is preferable if you let the browser handle the encoding it self. Regards. -- You received this message from the "vim_use" 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
