From dwinsemius at comcast.net  Fri Apr 27 03:51:36 2018
From: dwinsemius at comcast.net (David Winsemius)
Date: Thu, 26 Apr 2018 18:51:36 -0700
Subject: [Rd] embeded R application on Windows prints broken character.
In-Reply-To: <34362763-1753-45cf-b627-c4e8a42e93eb@Spark>
References: <34362763-1753-45cf-b627-c4e8a42e93eb@Spark>
Message-ID: <8B9F15E6-F7BD-49F0-89BC-E64C8C36A42C@comcast.net>


> On Apr 26, 2018, at 4:25 PM, Randy Lai <randy.cs.lai at gmail.com> wrote:
> 
> The issue was reported to me for https://github.com/randy3k/rtichoke/issues/50
> which is a python program which embeds R and provides a interface to R.
> 
> With R 3.5, for reason which i don't understand, when I typed `"a"` in the console
> STDOUT got `"\x02\xff\xfea\x03\xff\xfe"` with the extra escaped characters.
> 
> I notice that `\x02\xff\xfe` and `\x03\xff\xfe` are encoding related byte marks.
> A clear solution is to filter the escaped characters, but I want to understand what
> changes are causing it happens. It didn?t happen for R 3.4.

The maintainer (randy3k, oh that's you) of that python package has apparently fixed it:

https://github.com/randy3k/rtichoke/commit/4e29747c47f03381b319665943e290f17fd7914f



> Randy
> 
> 	[[alternative HTML version deleted]]
> 
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

David Winsemius
Alameda, CA, USA

'Any technology distinguishable from magic is insufficiently advanced.'   -Gehm's Corollary to Clarke's Third Law



[Rd] embeded R application on Windows prints broken character.
David Winsemius