On Wed, 18 Jun 2008, björn wrote:
> 2008/6/18 Christian J. Robinson <[EMAIL PROTECTED]>:
>> Did the user install from the vimball, or from the zip file? If
>> the former, have them re-install from the zip file. Vimball is
>> just plain broken (sorry Charles Campbell), and won't preserve file
>> encodings at both the creation and the extraction stages of a .vba
>> (among other problems such as no binary file support, etc.).
>
> I personally used the zip file. Its not really a problem with the
> files in the archive, but how menus are represented ones they've
> been loaded into memory. In other words, the problem is with MacVim
> and not with the HTML plugin. :-)
Well, for this plugin I've been saving 'encoding' and changing it to
"latin1" before I define the menus, then restoring the 'encoding'
option. Changing it to use ":scriptencoding latin1" as Tony
Mechelynck suggested elsewhere in the thread doesn't really seem to
work right.
Dealing with encoding issues is not something I'm well versed in, so I
could be going about this the wrong way, but what I do now is the
result of trial and error with people reporting problems.
- Christian
--
"It only takes 20 years for a liberal to become a conservative without
changing a single idea." -- Robert Anton Wilson
Christian J. Robinson <[EMAIL PROTECTED]> -- http://infynity.spodzone.com/
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
