public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: R does not handle package non-ASCII DESCRIPTION files properly
Date: Tue, 5 May 2020 08:55:14 -0600	[thread overview]
Message-ID: <fd307010-3db0-9845-f217-5ae40c519b46@SystematicSw.ab.ca> (raw)
In-Reply-To: <f60e7c3282f47182b29911874f4b2853@mhoenicka.de>

On 2020-05-05 02:47, Markus Hoenicka wrote:
> Am 2020-04-30 22:17, schrieb Marco Atzeri via Cygwin:
>> Am 30.04.2020 um 17:28 schrieb Markus Hoenicka:
>>> I've contacted the processx package maintainer on a problem reported here
>>> previously (see https://cygwin.com/pipermail/cygwin/2020-April/244667.html).
>>> He suggested to try the github version but that triggered a different type of
>>> error which does not seem to be package-specific.
>>>
>>> 1st try: build from a local copy of the github package sources with default
>>> locale settings on a German Windows 10 system
>>>
>>>> install.packages("/cygdrive/c/Temp/processx-master",repos=NULL,type="source")

>>> Installing package into ‘/usr/lib/R/site-library’
>>> (as ‘lib’ is unspecified)
>>> * installing *source* package ‘processx’ ...
>>> ** using staged installation
>>> Error : Invalid DESCRIPTION file
>>>
>>> Authors@R field gives no person with maintainer role, valid email
>>> address and non-empty name.
>>>
>>> See section 'The DESCRIPTION file' in the 'Writing R Extensions'
>>> manual.
>>>
>>> ERROR: installing package DESCRIPTION failed for package ‘processx’
>>> * removing ‘/usr/lib/R/site-library/processx’
>>> Warning message:
>>> In install.packages("/cygdrive/c/Temp/processx-master", repos = NULL,  :
>>>    installation of package ‘/cygdrive/c/Temp/processx-master’ had non-zero
>>> exit status

>> Noted. I will look on both the two issues but it could take a bit.
>> I never looked at the build process of R packages in such details

> kind of "while you're at it": I've noticed one additional problem with non-ASCII
> characters. This may or may not be related to the problem reported above.
> Several packages throw an error during installation, in my case questionr,
> readr, pls, and vegan. The output of the latter is shown here:
> 
> installing to /usr/lib/R/site-library/00LOCK-vegan/00new/vegan/libs
> ** R
> ** data
> ** inst
> ** byte-compile and prepare package for lazy loading
> ** help
> *** installing help indices
> Error in Rd_info(db[[i]]) :
>   missing/empty \title field in
> '/tmp/RtmprL23H1/R.INSTALLffe51949f2e2/vegan/man/sipoo.Rd'
> Rd files must have a non-empty \title.
> See chapter 'Writing R documentation' in manual 'Writing R Extensions'.
> * removing ‘/usr/lib/R/site-library/vegan’
> 
> The file in question (man/sipoo.Rd) starts like this:
> 
> \encoding{UTF-8}
> \name{sipoo}
> \alias{sipoo}
> \alias{sipoo.map}
> \docType{data}
> \title{ Birds in the Archipelago of Sipoo (Sibbo and Borgå)}
> 
> Please note that the encoding is set to UTF-8 explicitely. Nonetheless, the a
> with overring in "Borgå" seems to mess up the title, which makes R think the
> \title field is missing. Changing the å to a circumvents this problem. I've also
> noticed that non-ASCII characters outside the title field do not hurt at all.

Add "Encoding: UTF-8" to the package DESCRIPTION file and remove from .Rd files,
as documented near the bottom of the section:

https://cran.r-project.org/doc/manuals/R-exts.html#The-DESCRIPTION-file

referenced by:

https://stackoverflow.com/questions/18080303/rd-files-with-different-encoding

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

  reply	other threads:[~2020-05-05 14:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 15:28 Markus Hoenicka
2020-04-30 20:17 ` Marco Atzeri
2020-05-01 10:44   ` Marco Atzeri
2020-05-04 11:20     ` Markus Hoenicka
2020-05-05  8:47   ` Markus Hoenicka
2020-05-05 14:55     ` Brian Inglis [this message]
2020-05-05 16:25       ` Marco Atzeri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fd307010-3db0-9845-f217-5ae40c519b46@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).