[ 
https://issues.apache.org/jira/browse/DERBY-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Knut Anders Hatlen updated DERBY-4999:
--------------------------------------

    Attachment: encoding.diff

The problem seems to be caused by the copy and move ant tasks that take a 
filterset or a filterchain. If no encoding is specified in the build script, 
ant assumes the files are encoded using the platform's default encoding when it 
does the filtering. This causes the UTF-8 BOMs to be garbled when the files are 
copied in a non-UTF-8 locale.

The attached patch specifies UTF-8 encoding for the copy and move tasks that do 
filtering, which makes it build again in my environment.

As a side effect, this also seems to fix the garbling of non-ascii characters 
that we saw even before the build started failing. So now I'm able to build the 
Japanese manuals in the C locale and get output that looks Japanese to me (the 
question marks are gone).

> Docs build fails under C locale
> -------------------------------
>
>                 Key: DERBY-4999
>                 URL: https://issues.apache.org/jira/browse/DERBY-4999
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.8.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: antoutput.log.gz, encoding.diff
>
>
> The Hudson job that builds the documentation sometimes fails. See these 
> threads on derby-dev:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/201101.mbox/%3C129452085.1211295467008379.JavaMail.hudson@aegis%3E
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/201102.mbox/%3C1799570032.14811296675968251.JavaMail.hudson@aegis%3E
> The failure happens when processing the Brazilian Portuguese translation of 
> the reference manual.
> I'm able to reproduce the failure by building the pt_BR.html ant target with 
> locale set to C. It builds fine if the locale is en_US.UTF-8.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to