Oops, I committed a blunder with pasting. The patch part contains my
'showbreak' characters.
Please see that attached patch. Sorry about the inconvenience.
2017-02-11 10:37 GMT+09:00 Kazunobu Kuriyama <[email protected]>:
> Forgot to note :)
>
> How about the following patch for recap.py, so that the script works for
> Unix variants as well as Windows?
>
> 99,100c99,100
> < infile = "%s\%s" % (dirpath, filename)
> < otfile = "%s\%s" % (re.sub('^lang', 'output', dirpath),
> filena<<<<me)
> ---
> > infile = os.path.join(dirpath, filename)
> > otfile = os.path.join(re.sub('^lang', 'output',
> dirpath), file<<<<name)
>
> 2017-02-11 7:49 GMT+09:00 Kazunobu Kuriyama <[email protected]>:
>
>> Hi Zhenhuan
>>
>> 2017-02-11 5:24 GMT+09:00 Keny Hu <[email protected]>:
>>
>>> Hi Kazunobu
>>>
>>> I think that is an issue caused by PowerShell always trying to output
>>> utf-16. The characters look fine in GitHub client.
>>>
>>
>> TIL :)
>>
>>
>>>
>>> Attached here is the diff file covering only menu.vim and synmenu.vim.
>>> The attached Python script should be able to parse all utf-8 language
>>> scripts under runtime/lang.
>>>
>>> Please let me know if it works this time.
>>>
>>
>> LGTM. Thanks.
>>
>>
>>>
>>> Zhenhuan
>>>
>>
>> - Kazunobu
>>
>>>
>>> On Fri, Feb 10, 2017 at 11:19 AM, Kazunobu Kuriyama <
>>> [email protected]> wrote:
>>>
>>>> 2017-02-10 14:54 GMT+09:00 Zhen-Huan Hu <[email protected]>:
>>>>
>>>>> So here we go...
>>>>>
>>>>> This patch also updates the English part of all language translation
>>>>> scripts under runtime/lang, along with two additional changes made in the
>>>>> synmenu.vim. I manually verified the Chinese translation script and
>>>>> everything seems fine. I did not however touch any syntax menu items in
>>>>> this patch (because I really have no idea what most of them actually are).
>>>>> It seems no language translation script translated syntax menu either.
>>>>>
>>>>
>>>> Unfortunately, I couldn't seem to apply your patch (DOS format,
>>>> UTF16-LE encoding) to my Vim repo on OS X even after I, hoping any luck,
>>>> converted it into UNIX format, UTF-8 encoding.
>>>>
>>>> I also tried git-apply(1) but had no luck, either.
>>>>
>>>> The files in runtime/lang/ are encoded in various ways. I'm not sure
>>>> if patch(1) can work with such a single patch file that consists of
>>>> multiple diff parts each of which may be encoded differently from the
>>>> others.
>>>>
>>>> So, as Bram suggested in the last paragraph of his message, it should
>>>> be easier and safer to begin with a few changes, making sure they cause no
>>>> problem, and then going on to add another set of changes, without handling
>>>> multiple encodings simultaneously to avoid possible troubles.
>>>>
>>>> - Kazunobu
>>>>
>>>>
>>>>> I also attached here the Python script I used to sync the changes to
>>>>> the language files. Please run it in the runtime folder. It should parse
>>>>> all .vim files under the runtime/lang folder and save the new files in
>>>>> runtime/output.
>>>>>
>>>>> --
>>>>> --
>>>>> You received this message from the "vim_dev" maillist.
>>>>> Do not top-post! Type your reply below the text you are replying to.
>>>>> For more information, visit http://www.vim.org/maillist.php
>>>>>
>>>>> ---
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "vim_dev" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to [email protected].
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>> --
>>>> --
>>>> You received this message from the "vim_dev" maillist.
>>>> Do not top-post! Type your reply below the text you are replying to.
>>>> For more information, visit http://www.vim.org/maillist.php
>>>>
>>>> ---
>>>> You received this message because you are subscribed to a topic in the
>>>> Google Groups "vim_dev" group.
>>>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>>>> pic/vim_dev/wZhgIZcFGr4/unsubscribe.
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> [email protected].
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>>> --
>>> You received this message from the "vim_dev" maillist.
>>> Do not top-post! Type your reply below the text you are replying to.
>>> For more information, visit http://www.vim.org/maillist.php
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "vim_dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
99,100c99,100
< infile = "%s\%s" % (dirpath, filename)
< otfile = "%s\%s" % (re.sub('^lang', 'output', dirpath),
filename)
---
> infile = os.path.join(dirpath, filename)
> otfile = os.path.join(re.sub('^lang', 'output', dirpath),
> filename)
