Konstantin Kolinko wrote:
> 2008/9/12 Craig McQueen <mcqueen-c_at_edsrd1.yzk.co.jp>:
>
>> Stefan Küng wrote:
>>
>> debose wrote:
>>
>>
>> On Sep 9, 9:27 pm, Stefan Küng <tortoise..._at_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
>>
>>
>> This situation begs for an svn property to store the file's character
>> encoding -- in a similar way to svn:mime-type stores the MIME type. I've
>> done a web search and found discussion about svn:charset.
>> This seems like a great idea -- is it likely to become mainstream?
>>
>> Regards,
>> Craig McQueen
>>
>>
>
> 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
>
>
If we set the charset in the svn:mime-type, will TSVN use it instead of
auto-detecting?
BTW auto-detecting character encoding sounds like amazing magic.
Craig
Received on 2008-09-15 02:55:40 CEST