here's an illustration: http://i38.tinypic.com/ilkln6.jpg
Version info:
TortoiseMerge 1.5.3, Build 13783 - 32 Bit , 2008/08/30 20:59:46
libsvn_diff 1.5.2,
apr 1.2.12
apr-utils 1.2.12
---------------------------------------------------------------------
To unsubscribe, e-mail: users-un...@tortoisesvn.tigris.org
For additional commands, e-mail: users...@tortoisesvn.tigris.org
Try a nightly build please:
http://nightlybuilds.tortoisesvn.net/1.5.x/
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
In night build(13872) Working Copy is not converted to UTF8 encoding,
if it was in ANSI.
But, if Working Copy already contained any text in UTF8 w/o BOM, then,
all the following text that is copied using "Use this text block"
feature in TortoiseMerge becomes UTF8 encoded.
Isn't that possible to disable auto-encoding in any option?
On Sep 9, 6:28 pm, Stefan Küng <tortoise...@gmail.com> wrote:
>
> Try a nightly build please:http://nightlybuilds.tortoisesvn.net/1.5.x/
>
> Stefan
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.net
>
> signature.asc
> < 1KViewDownload
Sure, it you have utf8 encoded text, then the file is utf8 encoded.
> Isn't that possible to disable auto-encoding in any option?
No, that's not possible. Sorry.
-----Original Message-----
From: debose [mailto:ex.d...@gmail.com]
Sent: Thursday, September 11, 2008 6:32 AM
To: us...@tortoisesvn.tigris.org
Subject: Re: BUG: TortoiseMerge automatically converts ANSI file to UTF8 w/o BOM
13872 build still incorrectly detects UTF8 encoding.
For example, files containing only ASCII(without locale-dependent
symbols) are still treated as UTF8 CRLF. But in fact they are ANSI
files. The worst is that, after editing these files in
TortoiseMerge(adding any locale-dependent symbol), they will actually
become UTF8, which is not acceptable.
But if TortoiseSVN Team will not confirm that as a bug, I'll try other
diff-tools =)
On Sep 11, 4:53 pm, "Fisher, John" <jfis...@forthrightsolutions.com>
wrote:
> Maybe you should use a separate app like Win Merge or Beyond Compare, since you can configure Tortoise to use them instead of TortoiseMerge. Have you tried that, yet?
>
---------------------------------------------------------------------
I added a registry key to set the default:
HKCU\Software\TortoiseMerge\UseUTF8
(DWORD value)
if set to 1, then TortoiseMerge will default to utf8 when loading files
which only have chars < 127 in it.
This was done in r13918.
Stefan
The code looks different from this description. It appears that it
will use UTF8 in the following conditions:
a) if there is already a UTF8 BOM, or
b) if there are non-ascii chars AND the UseUTF8 key is non-zero.
The UseUTF8 key defaults to 0, so by default there is no conversion.
Is that correct?
Simon
--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
As I said: if the registry key is set to 1 (UseUTF8 is 1, not the
default 0), then an ANSI file which only has chars < 127 is treated as
utf8 (if there are no chars > 127, then the encoding can be either ANSI
or utf8 - it's the same).
But that registry key is of course only used if the automatic encoding
detection isn't able to detect the encoding automatically.
Stefan
debose wrote:On Sep 9, 9:27 pm, Stefan Küng <tortoise...@gmail.com> wrote:Sure, it you have utf8 encoded text, then the file is utf8 encoded.Seems like that build, incorrectly detects UTF8 w/o BOM. F.e. every file that contains ONLY ASCII(plain English, without locale-dependent symbols) is treated in TortoiseMerge as UTF8 CRLF, while in fact it is ANSI. And after editing in TortoiseMerge, it will become UTF8, which is not acceptable for me. =(I added a registry key to set the default: HKCU\Software\TortoiseMerge\UseUTF8 (DWORD value) if set to 1, then TortoiseMerge will default to utf8 when loading files which only have chars < 127 in it. This was done in r13918. Stefan
Well, there is
http://subversion.tigris.org/issues/show_bug.cgi?id=2329
but closed due to "lack of consensus".
I, personally, wonder, why not to include the charset into existing
svn:mime-type property, e.g.
svn:mime-type=text/plain;charset=ISO-8859-9
Have a nice day!
Best regards,
Konstantin Kolinko
On Sep 11, 6:43 pm, Stefan Küng <tortoise...@gmail.com> wrote:
>
> I added a registry key to set the default:
> HKCU\Software\TortoiseMerge\UseUTF8
> (DWORD value)
>
> if set to 1, then TortoiseMerge will default to utf8 when loading files
> which only have chars < 127 in it.
>
> This was done in r13918.
>
> Stefan
---------------------------------------------------------------------
No. A mime type doesn't contain the charset (usually). And TMerge
hasn't linked the libsvn_wc to read properties.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------