Subject: bug#1654: 23.0.60; auto encoding detection
(detect-coding-region) not working
Kenichi Handa <handa@xxxxxxxx> writes:
> In article <87k56bu0uu.fsf@xxxxxxxxxxx>, Chong Yidong <cyd@xxxxxxxxxxxxxxxxx>
>> Hi Handa-san,
>> Could you take a look at bug#1654? Thanks.
>> The auto encoding detection can not detect the correct encoding (for
>> example, for the two files attached). And neither the
>> detect-coding-region function works (after M-x find-file-literally)
> At least detect_coding_region works correctly for
> test_gbk.txt. But, it doesn't work for test_big5.txt by the
> same reason as above.
Yes, the gbk issue is confirmed solved in the CVS
(after coding.c rev1.413)
But for the big5, in the list returned by
"(detect_coding_region (region-beginning) (region-end))",
there is not big5. I do understand that gbk and big5's sequences might
not be easy to distinguish, but in this case, both encodings are
compatible to the input literal text, so both should be in the returned list. Am
I right? Can you check with this?
BTW, is that any hook that I can put after the coding detection? I might
want to write a small lisp to distinguish BIG5 and GBK (by char statistics,
I re-attached the test_big5.txt file here.
Description: Text document
> Kenichi Hand...