On Aug 22, 2005, at 5:38 PM, Kalin KOZHUHAROV wrote:
>>> "Gustave T. Stresen-Reuter" <firstname.lastname@example.org> wrote on
>>> 11:33:06 AM:
>>>> Specifically, documents checked into Subversion from the Mac
>>>> in utf-8 No BOM) and then checked out onto Windows end up
>>>> encoded (accented characters display incorrectly). Likewise,
>>>> created on the windows machines, checked into Subversion and then
>>>> checked out onto the Mac end up with "gremlins" (characters that
>>>> display but are definitely a part of the document).
>>>> I've read in several places that documents checked into Subversion
>>>> converted to utf-8, but if that were true, why would we end up with
>>>> this mis-encoded documents? Is it possible that JEdit or some other
>>>> aspect of Windows is messing with the encoding and if so, what
>>>> could it
>>>> possibly be?
>>>> This is somewhat urgent so any help resolving this issue is greatly
>>> Subversion does not do anything to the contents of your files. The
>>> exception being that you can ask Subversion to do stuff with the EOL
>>> characters and/or expand specific keywords.
> Yes, make sure svn:eol-style is "native". If you don't believe
> subversion (then why do you use it :-), make an MD5 sum of the file
> before svn add, after svn add, after commit and after checkout on a
> different platform. All MD5s should be the same. If not, post here
> which are the different ones.
Indeed, it appears to be a problem with Tortoise. Here is the result of
a file checked out using TortoiseSVN and one using the Subversion
Windows command line tool:
Mac: MD5 (index.html) = 45f0f1bc8e0571a025e225dea7f7c353
Win cmd line: MD5 (index-cmd.html) = 45f0f1bc8e0571a025e225dea7f7c353
Win Tortoise: MD5 (index-win.html) = 5384838ac87ceae69925eae16d9e6a7d
Thanks to everyone for your help. Is this a TortoiseSVN configuration
issue or a Windows configuration issue???
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Aug 22 21:34:31 2005