ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 28049] - sql task not able to import "windows UTF-8"
Date Mon, 05 Apr 2004 12:42:44 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28049>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28049

sql task not able to import "windows UTF-8"





------- Additional Comments From bodewig@apache.org  2004-04-05 12:42 -------
This is an issue for so many other classes in Ant that any local fix for the
sql task would be wrong.

Sun's own docs don't talk about a BOM for utf-8, so it's pretty likely they'll not
support it properly.  Even the unicode FAQ you link to says "Note that some
recipients of UTF-8 encoded data do not expect a BOM." and says it wouldn't make
any difference for the endianess of the stream.  So Notepad is allowed to do that,
but it's useless and dangerous.  Obviously Java clients are in the "do not expect
a BOM" department.

I'm not really sure what to do here.  Your patch should probably only apply if
requested or native encoding is UTF-8 and it should be farmed out into a helper
class so that othere tasks can reuse it.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message