On Fri, 20 Jun 2008, Tony Mechelynck wrote:
> ":scriptencoding" must be in the script itself. It acts from the next
> line to the next ":scriptencoding" command or to the end of the script,
> whichever comes sooner, and doesn't apply to other scripts sourced from
> within that range.
>
> From ":h
On 20/06/08 03:02, Ben Schmidt wrote:
[...]
>> Have you got any suggestions how to deal with scripts that fail to set
>> :scriptencoding?
>
> The only think I can think of that would be worth doing would be to
> check that when Vim converts a script that uses :scriptencoding, it uses
> ++bad=drop
Tony Mechelynck wrote:
> On 20/06/08 02:02, Ben Schmidt wrote:
>>> Can you tell me exactly in which script (of which date) you find that
>>> misbehaving menu statement (use ":verbose menu" followed by the menu
>>> name to see where it was set), so I can check the mod-date mentioned at
>>> the top
>>> (From your previous post I found out that e.g. gui_mch_draw_string()
>>> will pass strings in the encoding specified by 'enc', thus I can look
>>> at output_conv to determine if I need to convert the string to utf-8
>>> before drawing it. However, I cannot use the same method to decide if
>>>
On 20/06/08 02:41, Ben Schmidt wrote:
>> Well, for this plugin I've been saving 'encoding' and changing it to
>> "latin1" before I define the menus, then restoring the 'encoding'
>> option.
>
> That is a Bad Thing to do. It will almost certainly result in invalid
> menus on many systems, as it is
> Well, for this plugin I've been saving 'encoding' and changing it to
> "latin1" before I define the menus, then restoring the 'encoding'
> option.
That is a Bad Thing to do. It will almost certainly result in invalid
menus on many systems, as it is in MacVim. As documented at :help
'encoding'
On 20/06/08 02:02, Ben Schmidt wrote:
>> Can you tell me exactly in which script (of which date) you find that
>> misbehaving menu statement (use ":verbose menu" followed by the menu
>> name to see where it was set), so I can check the mod-date mentioned at
>> the top of that script on my system?
> Can you tell me exactly in which script (of which date) you find that
> misbehaving menu statement (use ":verbose menu" followed by the menu
> name to see where it was set), so I can check the mod-date mentioned at
> the top of that script on my system?
It's a third party plugin, Tony (the H
On 19/06/08 21:46, björn wrote:
[...]
> Bram, thanks for the answer.
>
> This presents a problem with scripts that do not use :scriptencoding
> like the HTML plugin. It (I'm only using it as an example since its
> the only problem I'm aware of) defines menu items whose titles contain
> characters
2008/6/19 Bram Moolenaar <[EMAIL PROTECTED]>:
>
> Bjorn Winckler wrote:
>
>> 2008/6/18 Tony Mechelynck <[EMAIL PROTECTED]>:
>> >
>> > On 18/06/08 12:03, bj=F6rn wrote:
>> >> 2008/6/18 Tony Mechelynck<[EMAIL PROTECTED]>:
>> >>> 'encoding' set to UTF-8 means the contents of _files being edited_ are
Bjorn Winckler wrote:
> 2008/6/18 Tony Mechelynck <[EMAIL PROTECTED]>:
> >
> > On 18/06/08 12:03, bj=F6rn wrote:
> >> 2008/6/18 Tony Mechelynck<[EMAIL PROTECTED]>:
> >>> 'encoding' set to UTF-8 means the contents of _files being edited_ are
> >>> represented internally as UTF-8. IIUC, the menu l
2008/6/18 Tony Mechelynck <[EMAIL PROTECTED]>:
>
> On 18/06/08 12:03, björn wrote:
>> 2008/6/18 Tony Mechelynck<[EMAIL PROTECTED]>:
>>> 'encoding' set to UTF-8 means the contents of _files being edited_ are
>>> represented internally as UTF-8. IIUC, the menu locale is defined by
>>> ":language mes
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
>>
On 18/06/08 12:03, björn wrote:
> 2008/6/18 Tony Mechelynck<[EMAIL PROTECTED]>:
>> 'encoding' set to UTF-8 means the contents of _files being edited_ are
>> represented internally as UTF-8. IIUC, the menu locale is defined by
>> ":language messages" at the time the menu script is sourced:
>
> Than
2008/6/18 Christian J. Robinson <[EMAIL PROTECTED]>:
> On Wed, 18 Jun 2008, björn wrote:
>
>> A user reported problems using the HTML plugin
>> (http://www.vim.org/scripts/script.php?script_id=453) with MacVim on
>> the vim_mac list. I looked into this problem and found out that it
>> was caused
2008/6/18 Tony Mechelynck <[EMAIL PROTECTED]>:
>
> 'encoding' set to UTF-8 means the contents of _files being edited_ are
> represented internally as UTF-8. IIUC, the menu locale is defined by
> ":language messages" at the time the menu script is sourced:
Thanks for clarifying that. So now that
On Wed, 18 Jun 2008, björn wrote:
> A user reported problems using the HTML plugin
> (http://www.vim.org/scripts/script.php?script_id=453) with MacVim on
> the vim_mac list. I looked into this problem and found out that it
> was caused by the fact that menus in this plugin are defined in a file
>
On 18/06/08 11:13, björn wrote:
> Hi,
>
> A user reported problems using the HTML plugin
> (http://www.vim.org/scripts/script.php?script_id=453) with MacVim on
> the vim_mac list. I looked into this problem and found out that it
> was caused by the fact that menus in this plugin are defined in a
Hi,
A user reported problems using the HTML plugin
(http://www.vim.org/scripts/script.php?script_id=453) with MacVim on
the vim_mac list. I looked into this problem and found out that it
was caused by the fact that menus in this plugin are defined in a file
whose filetype is latin-1 but some cha
19 matches
Mail list logo
