$
publican trans_drop
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.
$
publican update_pot
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.
Remove unused XML files
$
publican print_unused
command to generate a list of XML files that are not used in your document.
$
publican update_po --langs=language_code
$
publican update_po --langs=hi-IN,pt-BR,ru-RU,zh-CN
--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. When created for the first time, the Revision_History.xml
file records the date on which the PO files for this translation were created, and the version of the source language XML (taken from the source language's Revision_History.xml
file) on which this translation is therefore based.
Revision_History.xml
file to record the date on which the PO files for this translation were refreshed, and the version of the source language XML on which the revision is based. You can update existing PO files in every subdirectory with the --langs=all
option:
$
publican update_po --langs=all
Remove unused POT files
pot
directory, whether the POT file is based on a corresponding XML file that is used in the document or not, or whether a corresponding XML file even exists. If you transform POT files for unused or deleted XML files into PO files, you waste the time and effort of volunteer translators, and waste money if you are paying for translations.
publican add_revision
command to describe your changes or corrections. Publican updates the Revision_History.xml
file for you.
publican trans_drop
, publican update_pot
, and publican update_po
commands as described earlier in this procedure instead.
$
publican build --formats=html,html-single,pdf --langs=is-IS,nb-NO
$
publican package --lang=is-IS
--langs=all
option, but note that you must package each language individually. Refer to Section 4.7, “Building a document” for more information on building a document, and Section 4.8, “Packaging a document” on packaging a document.
$translation/Author_Group.xml
and add a valid DocBook authorgroup. The translator can add their details to this file and Publican will append it to $source_lang/Author_Group.xml
when the book is build. This allows authors to finalize the original text without needing to know who will translate the book.
<glossentry>
elements into a book's glossary; and <primary>
, <secondary>
, and <tertiary>
<indexterm>
elements into a book's index. Entries are sorted automatically, and although this system works well for languages written with an alphabet, abugida, or syllabic script, languages written with logograms sort less well.
sortas
attribute to the XML element. For example, to ensure that the Japanese word 暗号化 sorts correctly in an index, specify:
#. Tag: indexterm #, no-c-format msgid "<primary>encryption</primary>" msgstr "<primary sortas="あんごうか">暗号化</primary>"
#. Tag: glossentry #, no-c-format msgid "<glossterm>encryption</glossterm>" msgstr "<glossterm sortas="あんごうか">暗号化</glossterm>"