[ http://issues.apache.org/jira/browse/TORQUE-49?page=all ]
Thomas Fischer resolved TORQUE-49.
----------------------------------
Fix Version/s: 3.2.1
Resolution: Fixed
Fixed this by using the encoding in the header of the xml file as encofding
when parsing the xml file.
The behaviour is very difficult to test. In the test project, the schema.xml
files get copied and filtered before they are used, which may mess up the
encoding. Then, most editors seem to cache whether a file is utf-8 or
iso-8859-1, and they tend to recognize the encoding header of an xml file, so
it is very difficult to predict the encoding they use to save the file.
> Encoding will not be used in insert-sql if it is used in generation task
> ------------------------------------------------------------------------
>
> Key: TORQUE-49
> URL: http://issues.apache.org/jira/browse/TORQUE-49
> Project: Torque
> Issue Type: Bug
> Components: Generator
> Affects Versions: 3.2
> Reporter: Thoralf Rickert
> Assigned To: Thomas Fischer
> Priority: Trivial
> Fix For: 3.2.1
>
>
> My schema.xml is encoded in UTF-8 and torque generates a SQL file in UTF-8.
> But when I run "insert-sql" the TorqueSQLExec task decodes the file with the
> system encoding because it doesn't know that the SQL file was encoded in
> UTF-8.
> My current solution is to set the attribute encoding="UTF-8" in the
> "torque-sql-exec" task call in my build-torque.xml.
> But I think torque should know the encoding of the files that it generates.
> It could be set (for example) in the sqldb.map file or by using special
> filename extension like .utf8.sql
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
