similar to: R-devel news: non-ASCII character strings in packages

Since R 2.5.0 it has been possible to declare the encodings of character strings (at the level of individual elements of a character vector). As a reminder, here is the announcement in NEWS o R now attempts to keep track of character strings which are known to be in Latin-1 or UTF-8 and print or plot them appropriately in other locales. This is primarily intended to make it possible

You seem confused about Latin-1: those characters are not in Latin-1. (MicroSoft code pages are a proprietary encoding, some code pages such as CP1252 being extensions to Latin-1.) You have not given the 'at a minimum information' asked for in the posting guide so we have no way to reproduce this, and without showing us the output on your system, we have no idea what you saw. [As a

The report on R_help about problems loading package irr (in a UTF-8 locale, it seemed) prompted me to look a little deeper. There are quite a few packages with Latin-1 chars in their .R files, and a couple in UTF-8. Apart from non-ASCII chars in comments, this is a problem as the code concerned cannot be represented in some locales R runs in (for example Japanese on Windows). It happens

Thanks, That fixed the problem. Jarek -----Original Message----- From: ripley at stats.ox.ac.uk [mailto:ripley at stats.ox.ac.uk] Sent: Friday, July 15, 2005 11:11 AM To: Tuszynski, Jaroslaw W. Cc: r-devel at stat.math.ethz.ch Subject: Re: [R] Passing character strings from C code to R Reading the posting guide would have shown you that R-help was quite inappropriate, so I have moved this to

This pre-announcement is being sent for information to both R-help and BioC. Please use R-devel at r-project.org for any follow-up discussion. ----------------------------------------------------------------------- We are about at the end of a several-week process of adding support for non-Latin character sets and non-Western-European languages to R. - For Linux users, R works in the UTF-8

This pre-announcement is being sent for information to both R-help and BioC. Please use R-devel at r-project.org for any follow-up discussion. ----------------------------------------------------------------------- We are about at the end of a several-week process of adding support for non-Latin character sets and non-Western-European languages to R. - For Linux users, R works in the UTF-8

> From: Peter Dalgaard BSA <p.dalgaard at biostat.ku.dk> > Date: 28 Sep 2000 13:58:22 +0200 > > Peter Dalgaard BSA <p.dalgaard at biostat.ku.dk> writes: > > > I think Occam/Ockham himself wrote in Latin. By my failing memory, the > > quote is > > > > "Entia non runt multiplicanda praeter necessitam" > > > > give or take

Has anyone ever successfully used Fortran character strings with R? ?Foreign says R C Fortran integer int * integer .... character char ** [compiler dependent] Character strings are passed as C arrays of character strings to Fortran: the first string may be usable if its length is passed

Following the report of Henrik Bengtsson which was traced by Duncan Murdoch to a bug in the regexp code from glibc-2.3.3 in R, I have updated the code in R-devel to -2.3.5. This had that bug fixed and about 700 other changes, most of which seem to be bug fixes. My tests on Linux (including of all CRAN packages) have detected no differences (but then I was not able to reproduce Henrik's

Quite a few packages have used this construct to launch a device, but it has several flaws. It's not clear in most cases that a package really needs to launch a new device (R will do so if needed), but 2.7.0 provides a function dev.new() to do so. (If you really need this in a GPL-ed package that must run in R < 2.7.0, consider copying dev.new.) You cannot assume any arguments for

It looks like no one tested the beta of 2.1.0 for Windows in an East Asian or cyrillic locale. In most cases example() will fail there. If this is likely to affect you, please use R-patched instead. We really do need help from the users in the beta-test period, especially in languages not used by the core team. (Even the Chinese translator does not himself use R in Chinese.) So the beta

We now have the integrated 32/64-bit installer for R-devel available from http://cran.r-project.org/bin/windows/base/rdevel.html , and binary builds of almost all the CRAN packages from CRAN or CRAN extras (and BioC 2.7 has a fairly complete 32/64-bit repository). There is also a win-builder service available for R-devel. These are built with different toolchains from R 2.11.x, using gcc

This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --27464147-159404577-1190380210=:1425 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8BIT Please do read the documentation, which says The 'rbind' data frame method first drops all zero-column

and so you will probably need to (cd src/extra/zlib; make distclean) ./configure after updating the sources, as some files have been removed that appear as dependencies. -- Brian D. Ripley, ripley@stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road,

We are planning to phase in some major changes to the R build process on Windows shortly, so expect problems and temporary unavailability of binary builds of R and of packages, and if you are building from sources, check out the latest version of the R-admin manual (in the sources) for the current state. The planned changes are - to move the 32-bit builds to MinGW's recent release of gcc

> Date: Tue, 7 Nov 2000 17:34:37 +0000 (GMT) > From: Jonathan Myles <mylesj at icrf.icnet.uk> > > I've now got a colleague at MRC-BSU to compress it, and email it as an > attachment to my UNIX machine, where I uncompressed it and then ftp'ed > it in ascii format to my laptop. So it doesn't seem to be an ascii/bin > issue ... Is it possible to get a binary

Your error message was >> d <- sqlFetch(channel, District) > Error in odbcTableExists(channel, sqtable) : > object "District" not found and as you had not defined an object 'District' in that session, it seems perfectly plain. If you want to refer to table "District" you have to give a character string (with quotes), not the name of an R

R-devel has new versions of the X11(), png() and jpeg() devices on Unix-alikes. The intention is that these are used identically to the previous versions (which remain available) but will produce higher-quality output with more features. Pros: Antialiasing of text and lines (can be turned off) but no blurring of fills. Buffering of the X11 display and fast repainting from a backing image.

Hello dear useRs and wizaRds, I am currently developing a package that will enable to use administrative map of Poland in R plots. Among other things I wanted to include region names in proper Polish language so that they can be used in creating graphics etc. I am working on Windows and when I build the package it is complaining about non-ASCII characters R code files. I was wondering what would

There seems to be a problem in print.default with some ISO-latin1 characters (the chars AFTER ASCII in western Europe...) if they appear in strings. (no problem if they are part of a function comment, see below). Some of the characters lead to 4 character Hex-codes being printed instead: "û" ## ^u prints as "0xFB" If you use the funny characters in comments of functions,