On Tue, 12 May 2009, Chris Leick wrote:

Prof Brian Ripley schrieb:
On Mon, 11 May 2009, Dirk Eddelbuettel wrote:
On 11 May 2009 at 14:17, Prof Brian Ripley wrote:
| Unfortunately a bug in the Debian bugs system means that messages that
| are forwarded get corrupted, and it seems most non-ASCII characters
| are replaced by spaces (at least in this group of non-bug reports).
| It isn't my end: there is an equally corrupt copy on the web page,
| after the original.
|
| I didn't notice until testing the result, so it was a major
| inconvenience. I've had to extract the inline info from the web pages
| and do it all again.

I did mention the web page in my email stilll included below. The webpage
contains a clear copy of the attachment which is why I mentioned it.

It also contains a corrupt copy.

I've seen, that the copy is correct:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526875
Are you sure, that you are using UTF-8?

Yes, I am using UTF-8, but my browser uses the setting on the HTML page which is UYT-8. Scroll on down to the (second) copy prefixed by |, which has the u-umlaut replaced by space (and so on). It was that copy that was forwarded.


| Please have the courtesy to use the R documented
| procedures on any future occasion: I've never had anything like this
| difficulty with any other contributed translation.

It is not clear whether you are talking to me or to Chris? .

Chris.

Sorry, I've translated many Debian-Pakages and I've found "vr" on the Debian Website. Is there any difference between "R documented procedures" and other translations?

R is a separate project from Debian: translation procedures are in its manuals and on developer.r-project.org.

Greetings,
Chris


--
Brian D. Ripley,                  [email protected]
Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
University of Oxford,             Tel:  +44 1865 272861 (self)
1 South Parks Road,                     +44 1865 272866 (PA)
Oxford OX1 3TG, UK                Fax:  +44 1865 272595



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to