[ 
http://issues.apache.org/jira/browse/DERBY-2186?page=comments#action_12459097 ] 
            
Andrew McIntyre commented on DERBY-2186:
----------------------------------------

And I take it back, there is corruption in the files of the multi-page HTML 
from my nightly doc build. I don't get the same corruption when building on my 
Mac. I will investigate and see if I can determine the source of the problem on 
my build machine. I don't see any errors reported during the build for the 
Japanese Getting Started manual.

I could have sworn that the getstart-single.html also appeared corrupt earlier 
in my browser, but now it doesn't appear to be the case.

As for configuring FOP to use Japanese fonts for the PDF, it should be 
possible, see:

http://www.javaranch.com/journal/200409/CreatingMultipleLanguagePDFusingApacheFOP.html

for a step-by-step tutorial. Integrating the extra arguments for FOP into the 
DITA build process may not be easy, but it should be possible.

> Publicate Japanese translation of "Getting Started with Derby" on the web
> -------------------------------------------------------------------------
>
>                 Key: DERBY-2186
>                 URL: http://issues.apache.org/jira/browse/DERBY-2186
>             Project: Derby
>          Issue Type: New Feature
>          Components: Web Site
>         Environment: http://db.apache.org/derby/manuals/index.html
>            Reporter: Tomohito Nakayama
>         Attachments: DERBY-2188.patch, ja_JP.tar.gz
>
>
> I found Japanese translated manual at 
> http://db.apache.org/derby/docs/dev/ja_JP/getstart/ and
> http://db.apache.org/derby/docs/dev/ja_JP/getstart/getstart-single.html 
> already.
> However, characters in former is broken and they are not publicated at the 
> manual page.

-- 
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

        

Reply via email to