better support for UTF-16 in qdiff, qannotate, qcat

Bug #416645 reported by Alexander Belchenko
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
QBzr
Confirmed
Medium
Unassigned

Bug Description

Philippe Lhoste wrote in bzr ML:
-------------------------------------------------------
I was puzzled because I had a simple .reg file (exported by regedit) which I hacked to add support for a new source code extension (icon, editor/compiler, etc.), and Bazaar was seeing it as binary although my editor shown only CR and LF control chars...

The Bazaar User Reference mentions (casually) that binary status is guessed by content (I suppose looking for some control chars at first bytes, as usual).

When I opened the file with a hex editor, I saw the reason: it is an UTF-16 file with Bom (0xFF 0xFE).

It is annoying because I cannot do diffs (it says just "Binary files ... differ and qdiff shows nothing -- at least I can do an external diff), cats are strange (letters are double spaced -- qcat shows a hex view), etc.
-----------------------------------------------------

So I think we could handle UTF-16 better in QBzr and provide autodetection of such files by BOM markers.

Changed in qbzr:
importance: Undecided → Wishlist
status: New → Confirmed
Changed in qbzr:
importance: Wishlist → Medium
Revision history for this message
Xavier Hourcade (xaho) wrote :

Applies to qbzr-0.21.4-1.fc16.x86_64

With large files, UI may completely stall/hang.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.