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=23919>. 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=23919 [PATCH] nightly build and ant 1.6 not buildable with jdk 1.2.2 ------- Additional Comments From [EMAIL PROTECTED] 2003-10-21 20:22 ------- Hi, on the last issue mentioned I wrote a separate bug report as it also fails for the IBM JDK. Its bug id 23920. Regarding the encoding ISO-8859-1 cannot contain all Unicode characters, but contains only a subset. A subset of this and many other encodings is US-ASCII, which seems to match with the rest of the codebase. Why should code set ISO 8859-1 be selected to develop with, as said taking only a subset would match many encodings, while also ISO 8859-1 is a subset of the entire Unicode space. Chooosing character set 8859-1 is choosing an obsolete character set (it has been superseded by 8859-15 at least in western europe afaik) which makes it harder to develop for people that normally use an other encoding (while working with a lot of different encodings, certainly the entire ISO 8859 series, KOI8-R various ms-dos codepages and UTF-8 work as long as everyone uses the common ASCII subset) Furthermore the transition to the UTF-8 encoding, which allows all unicode characters is ruled out by using ISO 8859-1. Therefore imho choosing ISO 8859-1 isn't going to make developing on ant easier for a lot of people, and will even make it more difficult to go to the only Unicode encoding variant we currently comply with (UTF-8) if we wanted to support all unicode characters in the ant source. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
