Very cool indeed! :-)
I think this is correct for Brazilian Portuguese; pt_BR
But I am not 100% certain.
One question is the directory layout. Should it be something like
src/en
src/pt_BR
etc?
Should the output be something like
getstarted_en.pdf
getstarted_pt_BR.pdf
I did the following, although I am thinking this might not be a very
good method. I copied the getstart directory of pt_BR into
src/getstart_pt_BR, then added the following lines to build.xml
Index: build.xml
===================================================================
--- build.xml (revision 358619)
+++ build.xml (working copy)
@@ -101,7 +101,14 @@
</target>
<target name="pdf"
depends="init,pdf.getstart,pdf.tools,pdf.devguide,pdf.adminguide,pdf.ref,pdf.tuning"/>
-
+
+ <target name="pdf.getstart_pt_BR" depends="init">
+ <antcall target="pdf.dita">
+ <param name="manual.name" value="getstart_pt_BR"/>
+ <param name="manual.ditamap" value="getstartderby.ditamap"/>
+ </antcall>
+ </target>
+
<target name="pdf.getstart" depends="init">
<antcall target="pdf.dita">
<param name="manual.name" value="getstart"/>
The output was:
out/getstart:
getstartderby.fo getstart-single.html
out/getstart_pt_BR:
getstartderby.fo getstartderby.pdf
I think it best if we tag the language to the end of the file (before
the .html .pdf etc). For example getstartderby_pt_BR.pdf and possibly
put the file in getstart so all languages will be within the getstart.
So the above isn't quite correct from my point of view. I think file
name collisions are highly likely without tagging the language to the
file itself?
I'm a bit uncertain about your question about how to keep everything
synced. I guess svn diffs would be the easiest to keep track of(?)
Also, I think their must be a better method to build different languages
than adding them manually to the build.xml file. I would have to look
into ant a bit to figure that out, unless someone knows a good answer.
scott
Jeff Levitt (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-780?page=comments#action_12361132 ]
Jeff Levitt commented on DERBY-780:
-----------------------------------
While I cant comment on the content (since I can't read Brazilian Portoguese),
I can say that I checked the build of these dita files by substituting them for
the getting started english files and running the derby docs build using ant,
and everything looks great. Thanks Halley for such a great contribution to
Derby!
Since this is the first documentation translating contributed to Derby, I think
a discussion is warranted on how we want these placed in the build. Should
users have a choice to download translated docs or does everything go at once?
Do we have a mirrored nightly build process for the website that produces
nightly translated documentation alongside the English, and if so, how much
work would that entail to set up? Finally, if changes are made to the english
docs, how do we make sure changes are made in the corresponding translated
book, or at least track those changes so a translater can make the changes when
they want to?
Getting Started manual translated into Brazilian Portuguese
-----------------------------------------------------------
Key: DERBY-780
URL: http://issues.apache.org/jira/browse/DERBY-780
Project: Derby
Type: Improvement
Components: Documentation
Versions: 10.1.1.0
Environment: DITA-sourced documentation
Reporter: Halley Pacheco de Oliveira
Attachments: getstart.tgz
DITA files from %DOC_ROOT%/trunk/src/getstart translated into Brazilian Portuguese to be
attached following "Andrew McIntyre" <[EMAIL PROTECTED]> instructions Re: How
do I contribute translation? 11501 and 11503 on derby-dev Digest 13 Dec 2005 23:33:11 -0000
Issue 597
