I may well be toadally out to luntch here (if so please excuse the added
noise) but perhaps the following may be of some help or relevance.
In a package that I wrote, I wanted to include the ß symbol in *.Rda
file. After a lot of thrashing about (and seeking advice from younger
and wiser h
On Wed, 19 Jun 2019 at 19:03, Charith Karunarathna
wrote:
>
> Hi,
>
> I got the following NOTES after submitting my R package to CRAN for the first
> time.
>
> "
> Flavor: r-devel-windows-ix86+x86_64
> Check: use of SHLIB_OPENMP_*FLAGS in Makefiles, Result: NOTE
> src/Makevars.win: SHLIB_OPEN
Hi Charith,
On 19 June 2019 at 16:41, Charith Karunarathna wrote:
| I got the following NOTES after submitting my R package to CRAN for the first
time.
| "
| Flavor: r-devel-windows-ix86+x86_64
| Check: use of SHLIB_OPENMP_*FLAGS in Makefiles, Result: NOTE
| src/Makevars.win: SHLIB_OPENMP_C
Hi,
I got the following NOTES after submitting my R package to CRAN for the first
time.
"
Flavor: r-devel-windows-ix86+x86_64
Check: use of SHLIB_OPENMP_*FLAGS in Makefiles, Result: NOTE
src/Makevars.win: SHLIB_OPENMP_CXXFLAGS is included in PKG_CXXFLAGS but not
in PKG_LIBS
src/M
Section 1.2 of 'Writing R Extensions' says
Another example is when a package installs support files that are required at
run time, and their location is substituted into an R data structure at
installation time. The names of the top-level library directory (i.e.,
specifiable via the ‘-l’ argume
On Wed, 19 Jun 2019 at 16:47, mark padgham wrote:
>
> Yeah, but that would require completely rewriting the C code to accept a
> variable for something that is used hundreds of times as a simple macro.
> (Most of that C code is an old library bundled with the package, so not
> my work in that rega
Yeah, but that would require completely rewriting the C code to accept a
variable for something that is used hundreds of times as a simple macro.
(Most of that C code is an old library bundled with the package, so not
my work in that regard.) It would still be enormously easier to robustly
provide
What do you mean by
"call an external text file"
? Text files are data... do you want to open it and read it? Are you familiar
with the system.file() function?
On June 19, 2019 5:45:51 AM CDT, mark padgham wrote:
>Dear All,
>
>I'm developing a package which primarily relies on C code that its
Dear All,
I'm developing a package which primarily relies on C code that itself
has to call an external text file representing a dictionary or lookup
table. The location of this file is defined in a C macro, the file
itself packaged in "./inst/dict/" and so currently called as
"#define mylocation
Sorry, I failed to clarify that the link to ltnews.pdf was the point of my
message. In some ways it is definitive from the LaTeX team.
My understanding is that option 'mathletters' is not the default in ucs, since
it produces math Greek and Hebrew letters also in text mode.
Georgi Boshnakov
On 18/06/2019 17:10, Georgi Boshnakov wrote:
Since April 2018 'utf8' is the default input encoding in LaTeX, see
http://anorien.csc.warwick.ac.uk/mirrors/CTAN/macros/latex/doc/ltnews.pdf and
they added some symbols in December.
Interesting ... but still not sufficient. I have a fairly recent la
11 matches
Mail list logo
