2009-07-13 13:00:08 UTC
Hi Nicolas.
This issue has now been addressed with the release of version 2.1.2 wich you can download from the source forge project download page.
Your code needs to change only the order of the encodings defined. The problem you will have with this encoding order is that the western file will match both ISO-8859-1 and ISO-8859-15 and the unicode file will match ISO-8859-1, ISO-8859-15 and UTF-8.
If you retain the order of the encoding you have entered then both files will match first to last and both files will be valid ISO-8859-15 encoded files. With the order reversed the final selected encodings will be
wester = ISO-8859-1
unicode=UTF-8
One other point, to comply with HTTP header and other XML style encodings, the encoding part pf the MimeType has now been changed to charset instead. So where before it would report "text/plain;encoding=UTF-8" it will now report "text/plain;charset=UTF-8"
As you are one of the first external users to report testing on the TextMimeDetector we would appreciate any fed back from you regarding problems or unexpected behaviour.
Regards
Steven McArdle
