similar to: writing to file with encodings (PR#2674)

Dear R wizards: I believe some more font encoding info. some of the font encodings work, others do not: IsoLatin1, MacRoman, WinAnsi, and PDFDoc seem fine. AdobeStd, AdobeSym, ISOLatin2, ISOLatin9, and TeXtext seem broken, in that the resulting output file is silently corrupt. The font encoding error does not appear in the postscript device driver, and it works fine. It would be nice if

Hello, Is file("out.txt", open="wt", encoding=ISOLatin1) (resp: MacRoman, WinAnsi) broken/unimplemented ? I am trying: zz <- file("out.txt", open="wt", encoding=ISOLatin1) cat(ASCII,file = zz, sep="\n") close(zz) on R162 for MacOs (carbon). Thanks. -- ------------------------------------------------------------------------------ Jean-Pierre

Hallo, I would like to ask you, for one question. When I export graph to .pdf and I need some czech font, I use a parameter encoding="ISOLatin2.enc" for these special fonts. But exported text is bad. I try ISOLatin1 and MacRoman, but it is some one. I don't know, what Iam doing bad, because in quartz is the graph ok. Sorry....I forget....I have a Mac with Leopard and R ver. 2.6.1.

Hi, after a lengthy but unsuccessfull search I couldn't come up with a solution to the following problem: I would like to have a "comma" instead of a "point" as the decimal point in my graphics, i.e. postscript and pdf files, for I write my thesis in German. My system is: OS: Debian Unstable R-Version: 2.0.1 System locale: de_DE at euro Could someone, please, help

Dear list, Following advice posted to this list a while back by Prof Ripley [1], I have been trying to draw a per mille character [2] in an axis label. This should give the correct character: plot(1:10, ylab = "\u2030") but all I get is '"S'. I'm running linux (FC5) and have fonts installed that have the correct character (viewed in the Gnome character map at least).

Hi there, I've hit a bump in writing postscript files with special characters in the WinAnsi encoding on a windows machine. Here's some sample code: ########################################### postscript(file = "test.eps", encoding="WinAnsi.enc", width = 3, height = 5.5, onefile = TRUE, horizontal=FALSE, family = "sans", title =

CentOS Errata and Security Advisory 2016:2674 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-2674.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 12f569a66c65aedcf6899fdc85fd4a7ece9179735863e8863c3819b03b901faf libgcrypt-1.4.5-12.el6_8.i686.rpm

https://bugzilla.mindrot.org/show_bug.cgi?id=2674 Bug ID: 2674 Summary: [CONFIRMED] channel 4: open failed: administratively prohibited: open failed Product: Portable OpenSSH Version: 7.4p1 Hardware: Other OS: OpenBSD Status: NEW Severity: minor Priority: P5

Concerns: OS Win32 / R 2.5.0 Recently (IIRC not with R < 2.3.0), I had some problems including postscript graphics produced in R into LaTeX with MikTeX [version 2.5.2574]: yap, respectively GhostScript/GSView (versions 8.54/4.7 resp.) threw errors. In fact, I realized this was just the same problem as reported in http://tolstoy.newcastle.edu.au/R/help/06/06/28858.html Apparently, by

We have some small networks with connectivity to the Internet through firewall routers.? The smallest has one Windows 7 system and three Linux systems including both CentOS 6 and CentOS 7 machines.? The Windows 7 systems have full Adobe packages that are updated regularly and are trouble free. On the Linux systems, evince has been our go to product for viewing and printing .pdf documents.? This

Hi all! To add to my previous posting I want to give some more deatils give a more precise I want to print a hyphen to a pdf() or postscript() device. As the documentaion of postscript says ASCII Character 45("-") is mapped to a minus sign (ASCII Character 95) by default. The advice given is to use "\173" for a hyphen. But, the following code produces a curly brace instead

Dear all Can anyone point to a list of valid pdf.options() encodings? I checked ?pdf and ?postscript, but they do not quite answer my questions. I would like to try UTF-8 instead of the default "ISOLatin1.enc" for Sweave plots (I have issues with Greek characters in labels). Thank you Liviu -- Do you know how to read? http://www.alienetworks.com/srtest.cfm Do you know how to write?

I have a little problem, I cannot solve (at least reasonable fast) I use gnu-emacs 21.2.1 with r-1.5.1 on windows 95. In recent versions I changed "process-coding-system-alist" (C-x[REt]p) to "latin-1". Then I was able to plot german "????" etc(rgui does make this correct). With the new R version this does not work any more. I tried to use some other codings systems

Hello, Can anybody tell me how stream titles, which are non-ASCII, are sent? For example, at ShoutCast.com, there are Asian and European streams that send encoded strings. However, I can't see how to detect what type of encoding they are using. e.g. UTF8, ISOLatin1, etc. If I could work out the encoding, then I can display the names properly. Any differences between how IceCast and

This only happens on platforms with a faulty implementation of realloc(). Some C libraries do not allow realloc() to be called with a NULL pointer to resize. The assignment ISOLatin1 <- 0:255 in Rprofile then causes a core dump. The attached set of 4 patches should be very safe to use and fix the problem. --please do not edit the information below-- Version: platform = i386-pc-sco3.2v4.2

Hi I just can''t seem to figure this out. I know that PDF doesn''t support UTF-8 so I''m trying to use Iconv to convert the string from UTF-8 to MacRoman (or anything that will work). This doesn''t seem to be working though. Is there a better/ correct way to do this? The sting is stored as UTF-8 in MySQL and displays properly on the web (<?xml

Hello, I'm trying to use the package ttda, wich is involved in text analysis, for my own data about answers in a company survey. I've installed it, as well as ispell, but when trying to use an example: > zz <- file("stupid.txt", "w") # build a data file > cat("{comment - stupid data file} \n" , file = zz) > cat("<uci=1>

With R 2.3.1 on Windows, I've noticed that it defaults to the "WinAsci.enc" encoding, which throws up an error when viewed with the default install of GhostScript/GSView (versions 8.51/4.7 respectively). I didn't have this problem prior to upgrading to 2.3.1 as I can view all my old PS graphs and they don't have the WinAsci encoding. I've got around this problem by

Hello, I posted 2 weeks ago this problem and it is currently not working. First thanks a lot for all the hints and helps. In the attached file I have added (hopefully) all informations. To summarize: I want to setup a print server, which allows the user to download the necessary files for new printers. Installed are (on top of suse 7.1) samba 2.2.6_pre2 and cups 1.1.15_1. Installed the printers,

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