[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Windows Codepage: Problem SOLVED

From: Paul Maier <svn-user_at_web.de>
Date: Wed, 3 Nov 2010 06:28:30 +0100

Hi David, Bert, Alexey and everybody,

now it WORKS!! Thank you for your advises. 8-))

To solve my encoding problem, I had to:
- upgrade to cygwin 1.7
- set LC_ALL=de_DE.CP1252 (for Cygwin)
- chcp 1252 (for Windows)
- use a True-Type font (Lucida Console)

=> Now Windows, Dos console, Cygwin and svn can talk with each
   other with all German umlaut characters and such.


> -----Ursprüngliche Nachricht-----
> Von: David Huang [mailto:khym_at_azeotrope.org]
> Gesendet: Montag, 1. November 2010 04:23
> An: users_at_subversion.apache.org
> Betreff: Re: Feature request: Support of Windows Codepage 850
> On Oct 31, 2010, at 1:35 PM, Paul Maier wrote:
> > Hi there!
> >
> > All output, that comes from the svn internationalization,
> shows correctly
> > on both codepages, 850 and 1252. E. g. error messages or
> "svn help ci". Good.
> > (Font in use is Lucida Console.)
> >
> > This shows, that it *is* possible for svn, to produce
> correct output on both
> > codepages, 850 and 1252.
> >
> > But output that comes from file data ("svn cat file") only
> prints correct with
> > Codepage 1252. Seems, that this output goes through a
> different piece of code,
> > that is not able to adjust to the Codepage in use.
> svn cat just outputs the file that's in the repository... if
> your file happens to be a a CP1252-encoded text file, but
> your console expects CP850, I don't think you should expect
> it to display properly. And how would svn even know that the
> file is a CP1252-encoded text file? While it does keep track
> of the MIME type, it doesn't keep track of charset
> encoding... perhaps I have a Chinese BIG5-encoded file in my
> repo; if SVN assumed it was CP1252 and tried to do a
> 1252->850 conversion on it, it'd corrupt the file.
> I think svn cat just needs to output the exact bytes of the
> file, rather than trying to do any conversion. If you want to
> do charset conversion, you could probably just pipe the
> output through iconv (available in Cygwin). E.g., svn cat
> filename | iconv -f cp1252 -t cp850
> > (I have to use Codepage 850, because Cygwin needs it.)
> I haven't tried it myself, but my understanding is that
> Cygwin 1.7 honors the locale environment variables. Perhaps
> try "set LC_CTYPE=de_DE.CP1252" or perhaps one of the other
> locale variables (LANG? LC_ALL?)=
Received on 2010-11-03 06:29:15 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.