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

Re: Bug report: UTF-8 encoded files merge issue

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2005-12-30 08:44:54 CET

Simon Large wrote:
> Kalin KOZHUHAROV wrote:
>> By default TortoiseMerge (still) does not support UTF-8 or any other
>> encoding. The only supported encoding is the default of your OS
>> (depends on the OS language).
> It *does* support UTF-8, but it requires a proper BOM at start of file,
> otherwise it cannot be sure what the encoding is. I think Stefan has
> just improved the auto-recognition so it will find UTF-8 with no BOM
> more easily now.

Yes, it now checks the whole file for UTF8 sequences and only loads the
files as UTF8 if there are
- no chars that are illegal in UTF8
- at least one UTF8 sequence is found

> Stefan, how hard would it be to add a menu to allow the user to specify
> the encoding to use? Default would be 'Auto' as it is now, but the user
> could override that if needed.

There's a little problem with that: the files are *loaded* in a specific
encoding. So it you want to switch the encoding, the files would have to
be reloaded (and so you would loose all your modifications).

I'd rather have someone else implement this feature, because I can't
really test this fully. I mean, even if e.g. Shift-JIS chars would be
shown correctly on my machine, I couldn't tell if it's correct because I
just can't read those.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Dec 30 08:45:13 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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