From |uc@r @end|ng |rom |edor@project@org  Mon Feb 18 17:42:40 2019
From: |uc@r @end|ng |rom |edor@project@org (=?UTF-8?Q?I=C3=B1aki_Ucar?=)
Date: Mon, 18 Feb 2019 17:42:40 +0100
Subject: [Rd] Encoding issues
In-Reply-To: <CABtg=K=dS=1geaahi=s7R2hd1ad=h-ez-CafFj5NV_O+kiDL3A@mail.gmail.com>
References: <CALEXWq344mKov29L4VrNvGrOWg-uOxiXXwjNajpmwkLv+ZvPYg@mail.gmail.com>
 <CABtg=K=dS=1geaahi=s7R2hd1ad=h-ez-CafFj5NV_O+kiDL3A@mail.gmail.com>
Message-ID: <CALEXWq1nDwk39dz=sOBbpn+XXJSayCMviRjEH55OHYLSoAVpCg@mail.gmail.com>

On Mon, 18 Feb 2019 at 17:27, G?bor Cs?rdi <csardi.gabor at gmail.com> wrote:
>
> From "Writing R Extensions":
>
> "Only ASCII characters (and the control characters tab, formfeed, LF
> and CR) should be used in code files."
>
> So I am afraid you cannot use ?m.

Thanks, G?bor, I missed that bit. Then, is an .Rd file considered a
"code file"? Our surprise comes from the fact that the quoted version
works fine in a test file, but not in an example. Anyway, if they
cause such a documented trouble, it seems that the safest option is to
avoid its use in the first place.

I?aki



[Rd] Encoding issues
=?UTF-8?Q?I=C3=B1aki_Ucar?=