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

Re: File encoding

From: Ross Boylan <ross_at_biostat.ucsf.edu>
Date: 2007-01-19 20:17:01 CET

On Wed, Jan 17, 2007 at 03:17:01PM -0800, Ross Boylan wrote:
> I have GNU/Linux system with LANG=en_US and another with
> LANG=en_US.UTF-8.
> A program produces some output, which is compared to an expected
> output file (e.g., test1.Rout.save). The latter is kept in
> subversion.
> The output differs between the two systems because of the encoding
> differences.
> Is there anything I can do to make this work more smoothly? In
> particular, it would be nice if the file (which is text) were created
> with the correct encoding by the svn client.
> The docs indicate that the server stores all filenames and logs as
> UTF-8, but files appear to be kept as unmodified binaries. mime-type
> can affect comparisons and eol-style can affect end of lines, but I
> don't see anything dealing with the encoding per se (even if it is
> part of the MIME type, and I'm not sure it is).

The MIME specification provides a charset parameter for text files
that seems to cover the encoding. Given subversion's current
approach, I assume that parameter is ignored, and it might even
confuse the code that decides whether a file is text or binary.


> I know that historically version control systems attempt to be clever
> about their files has often led to problems, but it seems to me
> conversions between encoding schemes are fairly well-defined, and
> would be useful. (Yes, I know some conversions are impossible!).
> Thanks.
> Ross Boylan

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 19 20:17:30 2007

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.