Re: Issue 520 in tortoisesvn: TortoiseMerge fails to detect utf-16 without BOM

On 20.07.2013 19:43, Oto BREZINA wrote:
> On 20. júla 2013 19:03, tortoisesvn_at_googlecode.com wrote:
>> Status: Started
>> Owner: tortoisesvn
>> Labels: Type-Defect Priority-Medium Milestone-1.8.1
>>
>> New issue 520 by tortoisesvn: TortoiseMerge fails to detect utf-16 without
>> BOM
>> http://code.google.com/p/tortoisesvn/issues/detail?id=520
>>
>> Files that are encoded in utf-16 but do not have a BOM are treated as ASCII
>> or UTF8 in TortoiseMerge.
>> The encoding detection logic only check the BOM.
>>
>> We have to improve that detection logic so that utf-16 files are detected
>> correctly even if they don't have a BOM.
>>
> Note for 1.9: All detection are fain but will never be a 100%, thats
> true especialy for short file, where there is not enough data for
> reliable statiscs analyse. So there should be way to load file in
> prespecified by user in load or other menu.

Already there:
double click on the status bar at the bottom where the encoding of the
file is shown.

> I had some ideas about this, but as it is started I'll not try to
> implement those.
> It was based on odd/even positioning of 0 bytes. In addition to new
> lines, and spaces.

Curious: why newlines and spaces to detect the encoding?

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3060926
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].