[...]
I traced the code again and again but nothing special happened. You
called string_convert and pass 0 as the length of the string, so in
string_convert_ext you calculates the length of the string with
STRLEN, then call iconv_string, last iconv. There is nothing wrong
with the length anywhere.
On 8/13/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
[removed the Vim maillist, this is development only]
Edward L. Fox wrote:
> On 8/12/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
> > [...]
> > You may have uncovered a bug that went unnoticed so far. Please try to
> > discover what causes
[removed the Vim maillist, this is development only]
Edward L. Fox wrote:
> On 8/12/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
> > [...]
> > You may have uncovered a bug that went unnoticed so far. Please try to
> > discover what causes this problem. I can't guess why the last character
> >
On 8/13/06, A.J.Mechelynck <[EMAIL PROTECTED]> wrote:
[...]
Edward had it on Windows. From ":help encoding-values" I gather that
"Chinese" and "prc" are alias to cp936 / euc-cn. Maybe gbk and gb18030
can be added to the "family"?
I'm using Debian Etch. But I had a look at the Windoze system and
Bram Moolenaar wrote:
Tony Mechelynck wrote:
Bram Moolenaar wrote:
Edward L. Fox wrote:
[...]
The menu.vim file should never change 'encoding'. It should load menus
that are appropriate for the current 'encoding' and language.
But gvim doesn't support an encoding named 'gbk'. If the system
Tony Mechelynck wrote:
> Bram Moolenaar wrote:
> > Edward L. Fox wrote:
> [...]
> >>> The menu.vim file should never change 'encoding'. It should load menus
> >>> that are appropriate for the current 'encoding' and language.
> >> But gvim doesn't support an encoding named 'gbk'. If the system
>
Edward L. Fox wrote:
> On 8/12/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
> > [...]
> > > But gvim doesn't support an encoding named 'gbk'. If the system
> > > encoding is 'gbk', the menu and toolbar get malformed.
> >
> > What do you mean by "system encoding"? How does Vim see this?
>
> I m
Hi Bram,
On 8/12/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
[...]
You may have uncovered a bug that went unnoticed so far. Please try to
discover what causes this problem. I can't guess why the last character
is messed up, looks strange.
I think I solved the problem! That was caused by ic
On 8/12/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
[...]
> But gvim doesn't support an encoding named 'gbk'. If the system
> encoding is 'gbk', the menu and toolbar get malformed.
What do you mean by "system encoding"? How does Vim see this?
I meant the $LANG variable.
GBK is right an ali
Bram Moolenaar wrote:
Edward L. Fox wrote:
[...]
The menu.vim file should never change 'encoding'. It should load menus
that are appropriate for the current 'encoding' and language.
But gvim doesn't support an encoding named 'gbk'. If the system
encoding is 'gbk', the menu and toolbar get mal
Edward L. Fox wrote:
> Sorry for sending this mail for the second time because my previous
> mail with attachment was rejected by the mail daemon. :-(
>
> On 8/11/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
> >
> > [...]
> >
> > The menu.vim file should never change 'encoding'. It should load
Hi vimmers,
Sorry for sending this mail for the second time because my previous
mail with attachment was rejected by the mail daemon. :-(
On 8/11/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
[...]
The menu.vim file should never change 'encoding'. It should load menus
that are appropriate fo
12 matches
Mail list logo
