On 21 May 2005 at 16:05, Peter Dalgaard wrote:
| Dirk Eddelbuettel <[EMAIL PROTECTED]> writes:
|
| > | INTERNATIONALIZATION
| > |
| > | o Unix-alike versions of R can now be used in UTF-8 and other
| > | multi-byte locales on suitably equipped OSes if configured
| > | with option --enable-mbcs (which is the default). [The
| > | changes to font handling in the X11 module are based on the
| > | Japanization patches of Eiji Nakama.]
| > |
| > | so I build debs with this option explicitly enabled, but it made no
| > | difference.
| >
| > Did you find anything out when talking to the amd64 folks? I am CCing this
| > to Peter who is very knowledgeable about amd64 as well -- Peter, the amd64
| > package should be built with exactly the same parameters as the other ten or
| > eleven arches, in particular as the 64 bit hppa and ia64.
| >
| > Any idea what may go astray here? Is there a relation to the r-bugs post of
| > png() failing under amd64 ?
|
| I think I've seen this work OK on amd64 (certainly with R running on
| amd64, but my X server is usually on a 32 bit system). My guess would
| be that something in the FontSet setup is messsed up on the system in
| question, but I can't remember how this all fits together. Debugging
| with a breakpoint in R_XLoadQueryFontSet() could be informative. The
| XLC_LOCALE file for the locale factors in somewhere.
Fair point -- Ryan could you check if your fontconfig differs from what, say,
the Ubuntu amd64 livecd sets up? Maybe it is your font configuration rather
than R? Comments?
Dirk
--
Statistics: The (futile) attempt to offer certainty about uncertainty.
-- Roger Koenker, 'Dictionary of Received Ideas of Statistics'
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]