From murdoch.duncan at gmail.com  Fri Dec 12 12:01:22 2014
From: murdoch.duncan at gmail.com (Duncan Murdoch)
Date: Fri, 12 Dec 2014 06:01:22 -0500
Subject: [Rd] SUGGESTION: Force install.packages() to use ASCII encoding
 when parse():ing code?
In-Reply-To: <s3s4mt11bb5.fsf@slagelg.uio.no>
References: <CAFDcVCSgxuDLTLQQFg8w2m_e2CB7sn7zdRdQHjGqJc0wbueEtg@mail.gmail.com>	<5489E6AE.9060002@gmail.com>
	<s3s4mt11bb5.fsf@slagelg.uio.no>
Message-ID: <548ACB02.5050906@gmail.com>

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?

I agree that CRAN probably shouldn't accept packages like that, at least
for exported symbols:  packages there should run anywhere.  But I
suspect that the majority of R packages are for private use, and will
never be sent to CRAN.  Do you know any reason that non-ASCII names
would be dangerous for those?

Duncan Murdoch



[Rd] SUGGESTION: Force install.packages() to use ASCII encoding when parse():ing code?
Duncan Murdoch