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 :help
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 locale is defined by
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
represented internally
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 HTML
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?
It's a
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 in MacVim.
(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
conversion is
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 of that script
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
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 file
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 I can't
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 by the fact
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 messages at the time
13 matches
Mail list logo
