btw @chcg :
(a little off topic, but i’ll wrap it as text limit ;-) )
did you or @donho have time to take a closer look at the UCharDet 0.0.6 implementation issue ?
i’ve tested UCharDet 0.0.6 separately and it detects all test samples correctly, and i can’t find out why, nor understand where the (pretty same) code behaves differently, when implemented into notepad++.
(side note, if it might be something to look at: quite a few users reported, that once detected falsely, you can’t hit “encode in utf-8”, as the bullet jumps right back to the language in “character sets” it has been falsely marked with. you can, however, select “convert to utf-8” and the bullet will stay there. i’ve been able to reproduce this every time)