On 2018-05-10, Jean-Marc Lasgouttes wrote:
> Le 05/05/2018 à 23:26, Scott Kostyshak a écrit :
>> The reason for this error, from the R perspective, is detailed by this
>> r-help ML post [1]. The problem is that when LyX exports the .Rnw file
>> (which in turn is used to make the .R file), the .Rnw
On Thu, May 10, 2018 at 11:50:37AM +, Jean-Marc Lasgouttes wrote:
> Le 05/05/2018 à 23:26, Scott Kostyshak a écrit :
> > The reason for this error, from the R perspective, is detailed by this
> > r-help ML post [1]. The problem is that when LyX exports the .Rnw file
> > (which in turn is used t
Le 05/05/2018 à 23:26, Scott Kostyshak a écrit :
The reason for this error, from the R perspective, is detailed by this
r-help ML post [1]. The problem is that when LyX exports the .Rnw file
(which in turn is used to make the .R file), the .Rnw file is created
with encoding "iso-8859-1". I think
On Sun, May 06, 2018 at 07:46:52AM +, Jürgen Spitzmüller wrote:
> No, not automatically. The encoding is marked by the inputenc package
> and the \inputencoding switches.
Ah I see.
> I am not sure what we can do on an "automatic" level here.
OK good to know. I'll leave it alone then.
> You
Am Samstag, den 05.05.2018, 17:26 -0400 schrieb Scott Kostyshak:
> The attached .lyx file contains a knitr chunk. If I export to PDF,
> the
> PDF is created successfully. However, if I export the .R file and run
>
> source('encoding_export_issue.R', echo = TRUE)
>
> I get an error:
>
> Error
The attached .lyx file contains a knitr chunk. If I export to PDF, the
PDF is created successfully. However, if I export the .R file and run
source('encoding_export_issue.R', echo = TRUE)
I get an error:
Error in nchar(dep, "c") : invalid multibyte string, element 1
The reason for this erro
