Is the patch able to be upstreamed?
I can explain how the patch works from the point of the source codes.
Thanks,
fujiwara
(07/22/09 18:50), Takao Fujiwara-san wrote:
> I revised the patch.
> "shift-jisx0213", "euc-jisx0213" and "euc-jp-ms" are moved from
&g
I revised the patch.
"shift-jisx0213", "euc-jisx0213" and "euc-jp-ms" are moved from
enc_alias_table[] to enc_canon_table[].
Thanks,
fujiwara
(07/22/09 00:20), Takao Fujiwara-san wrote:
> (07/21/09 19:09), Tony Mechelynck-san wrote:
>> On 21/07/09 10:04,
(07/21/09 19:09), Tony Mechelynck-san wrote:
> On 21/07/09 10:04, Takao Fujiwara wrote:
>> (07/21/09 16:34), Tony Mechelynck-san wrote:
>>> Mine could, obviously, and without any patching.
>>
>> Your suggestion doesn't work on none UTF-8 in my env.
>>
&g
(07/21/09 16:34), Tony Mechelynck-san wrote:
> Mine could, obviously, and without any patching.
Your suggestion doesn't work on none UTF-8 in my env.
1. Launch your terminal on ja_JP.WINDOWS-31J
% iconv -f eucJP -t WINDOWS-31j pkdfmt.txt > pkdfmt-win31j.txt
% vim
:view ++enc=windows-31j pkdfmt-
(07/20/09 20:49), Tony Mechelynck-san wrote:
> Won't Vim +iconv accept any charset known by your installed version of
> iconv, even charsets not compiled into Vim? You can list them (at least
I'm not sure if I understand 'Vim +iconv' exactly however 'vim --version' shows
'+iconv' in my env.
% e
(07/21/09 04:09), Bram Moolenaar-san wrote:
> I'm not worried about performance. I do want to avoid that we add
> things in here that might cause a problem for someone.
OK, I see. I also think it's nice to review my patch here.
>
> I invite everybody to make comments. Anything that looks like
(07/19/09 05:25), Bram Moolenaar-san wrote:
> Can you please explain for each entry why it should be added?
+{"ms932", IDX_CP932},
MS932 is added in glibc/iconvdata/gconv-modules
+{"windows-31j",IDX_CP932},
WINDOWS-31J is added in glibc/iconvdata/gconv-modules
WINDOWS-31J
Hi,
I'd like to update the charsets of vim.
I'm attaching the patch.
Thanks,
fujiwara
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~-