From ripley at stats.ox.ac.uk  Thu Oct 12 09:18:59 2006
From: ripley at stats.ox.ac.uk (Prof Brian Ripley)
Date: Thu, 12 Oct 2006 08:18:59 +0100 (BST)
Subject: [Rd] Bug in 2.4.0 Windows menu setup (PR#9277)
In-Reply-To: <4526954A.7050509@stats.uwo.ca>
References: <20061005025158.19A9C20804@slim.kubism.ku.dk>
	<dc41e1260610050506i3b65913ifca644ebd0b690e4@mail.gmail.com>
	<4525075D.4040102@stats.uwo.ca> <452693D4.2010905@cimr.cam.ac.uk>
	<4526954A.7050509@stats.uwo.ca>
Message-ID: <Pine.LNX.4.64.0610091258200.24252@gannet.stats.ox.ac.uk>

On Fri, 6 Oct 2006, Duncan Murdoch wrote:

> On 10/6/2006 1:35 PM, Hin-Tak Leung wrote:
>> Duncan Murdoch wrote:
>>> On 2006-10-5 8:06, Ei-ji Nakama wrote:
>>>> I do not understand Chinese, but recognize kanji.
>>>> RGui-zh_CN.po is written in utf-8, but charset=CP936 wrote.
>>>>
>>>>   perl -p -i -e 's#charset=CP936#charset=utf-8#' RGui-zh_CN.po
>>>>   msgfmt -o RGui.mo RGui-zh_CN.po
>>>
>>> Thanks!!  That does fix the error, at least on my system.  I'll commit
>>> the change to R-devel and R-patched.
>>
>> Hmm, I do understand Chinese, and I can confirm that the content
>> of RGui-zh_CN.po in R 2.4 is in utf-8 rather than CP936.
>>
>> I can also confirm that CP950(big5) for RGui-zh_TW.po is correct, and
>> CP932(shift-JIS) for  RGui-ja.po is also correct. (so you'll need to
>> find some korean to verify CP949 for RGui-ko.po).
>>
>> However, the fix is slightly "asymmetric". Out of ru, zh_CN, zh_TW,
>> ja, ko, only ru in R-2.4.0/po/*.po is in localised encoding,
>> (the others 4 in UTF-8), whereas RGui-*.po, after the fix, all
>> are in localised encoding except RGui-zh_CN.po .
>>
>> I would propose correcting the encoding of the *content*, rather
>> than the charset tag, so that Rgui-* all uses localised ones (CP932,
>> CP936, CP949, CP950). That should be better for older windows...

That was the intention, but the translator marked it incorrectly, and it 
appeared to be valid CP936 so not picked up by me.

> I did try that, but iconv didn't want to convert the file from UTF-8 to
> CP936.  I've no idea why not.
>
> In any case, those files only need to be readable by the translation
> teams, not by end-users, so I don't think the asymmetry matters:  if a
> translator finds it easy to work in UTF-8 that's fine for R, as long as
> it is correctly recorded.

Not really: the file does need to be convertible to the target encoding, 
and on Windows that is e.g. CP936.  That is why we have the RGui files in 
the native encoding: for all the other files we prefer UTF-8 or Latin-1.

I need to sort out with the translator a valid CP936 version of that file: 
it contains a character that is not in CP936.

-- 
Brian D. Ripley,                  ripley at stats.ox.ac.uk
Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
University of Oxford,             Tel:  +44 1865 272861 (self)
1 South Parks Road,                     +44 1865 272866 (PA)
Oxford OX1 3TG, UK                Fax:  +44 1865 272595




[Rd] Bug in 2.4.0 Windows menu setup (PR#9277)
Prof Brian Ripley