[ 
https://issues.apache.org/jira/browse/DERBY-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601073#comment-13601073
 ] 

Rick Hillegas commented on DERBY-6106:
--------------------------------------

Thanks for digging into that, Knut. I have looked inside the bin distributions 
for 10.2, 10.3, and 10.4. The 10.2 and 10.3 distributions don't have Japanese 
docs. They don't have Portuguese docs either. I do see Japanese and Portuguese 
docs inside the 10.4 bin distribution. And those docs seems to be encoded 
properly. That is, they display correctly in my browser. Here's a revised plan:

1') The documentation tab of the website should be updated so that the Japanese 
variants only appear under the 10.4 manuals. The Portuguese variants will only 
appear under the 10.2 manuals.
                
> Remove the outdated Japanese and Portuguese docs
> ------------------------------------------------
>
>                 Key: DERBY-6106
>                 URL: https://issues.apache.org/jira/browse/DERBY-6106
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools, Documentation, Web Site
>            Reporter: Rick Hillegas
>         Attachments: derby-6106-01-aa-dontBuildJapaneseAndBrazilianDocs.diff
>
>
> This is a task to track the removal of the outdated Japanese and Portuguese 
> doc variants, as discussed on this email thread: 
> http://apache-database.10148.n7.nabble.com/removing-the-Japanese-and-Portuguese-variants-of-our-user-docs-td126520.html
>  The following actions should be taken:
> 1) The documentation tab of the website should be updated so that the 
> Japanese and Portuguese variants only appear under the 10.2 manuals.
> 2) The release procs should be updated to not include these stale docs in 
> future Derby releases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to