I am using 3.13 and noticed that SpecialPropertySet now uses hard coded ASCII charset when it creates a new String out of byte[]. This change was introduced in September by revision 1700677.
It broke some of my test cases (where a POT file has non-ASCII characters in doc properties - see attached). Aren't we better off without this change (hence use system's default charset)? Or, better yet, why not allow user to provide the charset and default to ASCII if not provided? I can create a bug and patch if there's agreement on either. Azfar
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
