[fossil-users] annotate/blame for UTF-16 files.

2014-03-07 Thread Jan Nijtmans
People might notice that it is now possible to get annotation information on committed UTF-16 files. For example: http://fossil-scm.org/index.html/praise?checkin=46459fd922filename=test/utf16le.txt And ... in case you wonder what changes were white-space only, you can click the Ignore Whitespace

Re: [fossil-users] annotate/blame for UTF-16 files.

2014-03-07 Thread Richard Hipp
On Fri, Mar 7, 2014 at 10:39 AM, Jan Nijtmans jan.nijtm...@gmail.comwrote: People might notice that it is now possible to get annotation information on committed UTF-16 files. For example: http://fossil-scm.org/index.html/praise?checkin=46459fd922filename=test/utf16le.txt And ... in

Re: [fossil-users] annotate/blame for UTF-16 files.

2014-03-07 Thread Ramon Ribó
Some points: 1- Would it be possible to write the list of analyzed ancestors after the line origins list? (most useful information first) 2- Would it be possible to have option ignore whitespace activated by defaut? 3- Would it be possible to make the ignore whitespace more persistent between

Re: [fossil-users] annotate/blame for UTF-16 files.

2014-03-07 Thread Jan Nijtmans
2014-03-07 16:48 GMT+01:00 Richard Hipp d...@sqlite.org: Jan, when you made your edit to the test/utf16le.txt file, you also converted the file to UTF-8. It's reall cool that annotate and diff can now show differences between UTF-8 and UTF-16LE files. But at the same time, we also do need