DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23568>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23568 native2ascii task malfunction with property in encoding attribute ------- Additional Comments From [EMAIL PROTECTED] 2003-10-06 15:26 ------- When I sent this I was thinking about property name... so I tried "encoding". I really don't know, what is involved in this task, because I had found few of behaviours: - "ISO-8859-2" written directly - works when I have no locales set (in linux) - "ISO-8859-2" directly - does not work - destination file is also Latin 2 - on account where I have set sk_SK locales - "ISO8859_2" (canonical name for java.io) works perfectly on both (Well I know, that this canonical form should be used, but native2ascii is accepting both and the form of java.nio.* (ISO-8859-2) is closer to ISO name, so I like it. :-)) I iterated to "ISO8859_2" without property, but I'm not happy, that it does not work like Sun's tool. file.encoding was really a bad name for property and like I said... it works in different ways on different system (maybe unix locales was involved). \ufffd was produced only with this property name. Property evaluation is no problem actually. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
