A while back on vim_dev, there was a suggestion for TOhtml to use the 'fencoding' of the source buffer for the HTML encoding of the generated file.
This thread discusses it, and I eventually included an initial beta version that does exactly this: http://groups.google.com/group/vim_dev/browse_thread/thread/c41f797237e46f45 Also included is detection of the proper 'fileencoding' from the user-specified HTML encoding, if given. I have not received any feedback on the initial release, but I have acted on my musings and created a second beta version that removes specific encodings from the automatic detection, which are not supported on all 5 major browsers, according to http://wiki.whatwg.org/wiki/Web_Encodings. Please try it out and send me any comments! See attached patch against the current latest Vim (Mercurial changeset fae782ef63dd), or go to http://code.google.com/p/vim-2html-test/downloads/list for the fully patched files. Most users should not notice any differences, unless they had specific encoding-related problems in the past, in which case hopefully the updates solve more problems than they create. One thing in particular I'd like to know, is it worthwhile to provide platform-specific code, that adds additional encodings based on your system? For example, Windows users might like windows-1252 detected automatically by default. Is there a good way to figure out what the supported encodings are for a given system? Maybe, code like this would be better as a separately distributed plugin, since most users can probably just use UTF-8 with no problems. -- 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
2html_v7b2_fenc.patch
Description: Binary data
