From b.h.mevik at usit.uio.no  Fri Dec 12 15:35:00 2014
From: b.h.mevik at usit.uio.no (=?utf-8?Q?Bj=C3=B8rn-Helge_Mevik?=)
Date: Fri, 12 Dec 2014 15:35:00 +0100
Subject: [Rd] SUGGESTION: Force install.packages() to use ASCII encoding
	when parse():ing code?
In-Reply-To: <548ACB02.5050906@gmail.com> (Duncan Murdoch's message of "Fri,
	12 Dec 2014 06:01:22 -0500")
References: <CAFDcVCSgxuDLTLQQFg8w2m_e2CB7sn7zdRdQHjGqJc0wbueEtg@mail.gmail.com>
	<5489E6AE.9060002@gmail.com> <s3s4mt11bb5.fsf@slagelg.uio.no>
	<548ACB02.5050906@gmail.com>
Message-ID: <s3s7fxxym0b.fsf@slagelg.uio.no>

Duncan Murdoch <murdoch.duncan at gmail.com> writes:

> On 12/12/2014, 4:12 AM, Bj?rn-Helge Mevik wrote:
>> Duncan Murdoch <murdoch.duncan at gmail.com> writes:
>> 
>>> users of other languages may want to have messages and variable names
>>> in their native language, and ASCII might not be enough for that.
>> 
>> Allowing for messages in non-ASCII encodings would probably be a good
>> idea, but I think allowing non-ASCII variable names is dangerous.
>
> Dangerous in what way?

Perhaps "dangerous" is a little too strong, but it opens up
possibilities for problems with sharing code or running it on other
systems.  Also, judging by the many files I've seen (and created myself
:) with a mixture of iso8859-1 and utf8, or with "double-encoded" utf8,
it is surprisingly easy to make encoding mistakes when editing or
processing files.  And as Jan Kim wrote, you could get things that look
similar but are different.

-- 
Regards,
Bj?rn-Helge Mevik



[Rd] SUGGESTION: Force install.packages() to use ASCII encoding when parse():ing code?
=?utf-8?Q?Bj=C3=B8rn-Helge_Mevik?=