After a guide has been translated on Zanata, the language team has to make a thorough review of all the messages in order to correct and finally approve them. Zanata is a tremendous tool both for translating and reviewing, nevertheless, it is sometime difficult to deal with some aspects such as punctuation, verb tenses, and so on, without viewing both the original and the translated messages in context. Depending on whether the message is an image caption, or a list item, or the content of a message box,or includes a internal link (section, chapter, figure,…) as part of the sentence itself, translation may vary a bit?
Moreover, the presence of numerous tags, sometimes nested, make the visual aspect a bit far from the rendered text, and thus doesn't facilitate detection of erroneous punctuation or spacing.
All this is why, having the guide in the form of a translated finalized book may be a precious help for reviewers. This page explains how to build it.
The tools used to build the Fedora Guides is Publican. Install it with:
su -c 'dnf install publican publican-doc publican-fedora'
Before using Publican, you should at least set the user's defaults which are: firstname, surname, email, formats, lang, langs. Please refer to the relevant page the Publican User's Gude in /usr/share/doc/publican-doc/en-US/index.html (Chapter 2.).
Normally using the three commands that follow should be enough for the needs of this tutorial:
echo 'firstname: "André"' >>~/.publican.cfg echo 'surname: "Dupneu"' >>~/.publican.cfg echo 'email: "email@example.com"' >>~/.publican.cfg
Of course, replace the personal data with you own.
Getting the Original Folders and Files
Normally, you can create a book with publican using the
publican create command.
This command creates a directory structure which is described in the publican manual. Here is this structure:
- en-US (directory)
- images (directory)
The Chapter.xml file is a template for creating chapter files. Chapter files contain the content that make up a book.
In our situation, we do not need to create the book as it has already been created by the author. In fact, we can get the above directory structure, including the chapters that have been added by the author from the [https://pagure.io/] site.
Change to the directory where you want to download the files. Then run:
git clone -b <BRANCH> https://pagure.io/<PROJECT_NAME>
where <BRANCH> is the name of the project branch and <PROJECT_NAME> the name of the project.
For example to get the release-notes files for F24, run:
git clone -b f24 https://pagure.io/release-notes
Building the Original Guide (occasional situation)
It may happen that a book, proposed for translation on Zanata is not yet available on the docs.fedoraproject.org site. As such a guide is also of great help for translators during the translation process, one may want to build it. To do so, use the following command :
$ publican build --formats=html,html-single,pdf --langs=en-US
Preparing the translation files
- Open a terminal and change to the root directory of the guide. The one that contains the directory structure presented above.
- As a standard user, use the following command:
$ publican trans_drop
With this command, Publican creates a new subdirectory, named trans_drop/. The trans_drop/ subdirectory contains a snapshot of the source files of the document. When the trans_drop/ directory is present in a documentation project, Publican uses its content as the basis for the commands documented later in this procedure.
- Generate portable object template (POT) files from the XML files, using the following command:
$ publican update_pot
If this is the first time that POT files have been created for this document, Publican creates a new subdirectory, named pot. The pot subdirectory holds a POT file for each XML file in the document. If Publican has created POT files for this document previously, Publican updates the existing POT files to reflect any changes in the XML since the POT files were last updated.
- Generate portable object (PO) files from the POT files to begin translation into a particular language:
$ publican update_po --langs=language_code
If this is the first time that PO files have been created for a particular language, Publican creates a new subdirectory, named with the language code that you specified with the --langs= option. This subdirectory holds a PO file for each POT file in pot subdirectory, plus a Revision_History.xml file that tracks the history of this particular translation.
Replace the .po files in the <language-code> directory with the translated ones
- Go to the Zanata, log in, and open your project/branch/language page. Select your language and download the po files using the Downlad All (zip) link shown in the following picture:
- Extract the archive
- Copy/paste the po files from the archive to replace the original ones.
Your are now ready to build your translated book.
Building the Translated Book
To build the book use the following command:
$ publican build --formats=html,pdf --langs=fr
Of course, replace the language code (here fr) with your one and add – or remove – formats you want.
Normally if everything goes well – but real life is not that easy —, the resulting books should be placed in a tmp subdirectory.
If you plan to have a book to see the messages in context in order to approve them, you may still have some fuzzy messages let in the po files. Unfortunately, this makes the build process crash. Fortunately, Publican gives information about where the trouble occurred, e.g.:
Fusionner fr/After_Installation.po >> trans_drop/After_Installation.xml -> tmp/fr/xml_tmp//After_Installation.xml AVERTISSEMENT : message approximatif dans le fichier PO. 45: "Both of these tools will allow you to configure user-specific s...
Here the message is in French and it means: WARNING: Fuzzy message in the po file.
In such case, edit the po file and remove all the #fuzzy lines you find in After_Installation.po. Save your file and use the building command again.
If you don't plan to publish content online, another solution is to add --showfuzzy in you build command.
Bad XML source files
In some cases, you may get this kind of message:
DTD Validation failed for '/home/jaaf/Documents/install-guide-625e08c186c09c1abce89f3f0bf37c37563c7880/tmp/fr/xml/Installation_Guide.xml': Booting_the_Installation.xml:105: validity error : Element keycombo content does not follow the DTD, expecting (keycap | keycombo | keysym | mousebutton)+, got (keycap CDATA keycap)
Normally it should not happen but life is different. In this case, correct the fault as you can. For example, just remove the troublesome <keycombo> tag.
Note : Even if Pelican tell you to look in Booting_the_Installation.xml, you'll probably have to fix your error in Booting_the_Installation.po.
After that, if you had to change the xml files, you should rerun the update_pot and update_po commands above. Then rerun the build command.
In some cases, you may get this kind of message:
mismatched tag at line 6, column 185, byte 422: %BOOK_ENTITIES; ]> <para>Une partition Ã©tendue peut contenir plusieurs partitions (maintenant appelÃ©es <firstterm>partitions logiques</firstterm> par opposition aux quatre firstterm>partitions primaires</firstterm> vues prÃ©cÃ©demment). Chacune de ces partitions logique est prÃ©cÃ©dÃ©e d'un secteur (appelÃ© Extended Boot Record (<acronym>EBR</acronym>) utilisÃ© Ã la maniÃ¨re d'un MBR, Ã la diffÃ©rence que deux entrÃ©es de partition seulement sont utilisÃ©es. l'une qui pointe sur la partition logique elle-mÃªme, l'autre qui pointe sur l'EBRÂ de la partition logique suivante. Les partitions sont ainsi chaÃ®nÃ©es et leur nombre n'est plus limitÃ© que par la capacitÃ© du disque lui-mÃªme et par l'Ã©tendue adressable. </para> ========================================================================================================================================================================================^
In this case, one < is missing from string, correct the fault.
Some characters are rendered by a # in the pdf file
Some times, it appears that some characters are not correctly rendered in the pdf but are replaced with a #. It is probably due to the fact that the builder cannot find a fallback font that provides the wrongly rendered character. For example, with the French language, the narrow-no-break space normally necessary before a high punctuation (; ! ? ) was rendered by a #. Just adding the following lines at the end of /usr/share/publican/xsl/pdf.xsl solved the trouble:
<xsl:param name="title.font.family"> <xsl:text>FreeSans,Liberation Sans,sans-serif</xsl:text> </xsl:param> <xsl:param name="body.font.family"> <xsl:text>FreeSans,Liberation Sans,sans-serif</xsl:text> </xsl:param> <xsl:param name="monospace.font.family"> <xsl:text>Liberation Mono,monospace</xsl:text> </xsl:param> <xsl:param name="sans.font.family"> <xsl:text>FreeSans,Liberation Sans,sans-serif</xsl:text> </xsl:param>
For more information, please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1344078
No images in the pdf file
After having built you pdf with publican, from the root directory of the document, please run the following commands:
cd tmp/<language code>/xml
cp /usr/share/publican/fop/fop.xconf ./
fop -c fop.xconf -fo <document name>.fo -pdf ../pdf/<document name>.pdf
For more information, please see https://bugzilla.redhat.com/show_bug.cgi?id=1290423