Step 5: Build the PDF and commit your work

To put your configuration to the test, build a PDF in your language, e.g.:

gradlew docbookPdf --docId=qsg15-ru --language=ru

Inspect the result carefully. If you find any “### #### ##” spots in the document, the location may give you a clue as to what went wrong:

If they are in the titles, you probably forgot to override the title.font.family in fo-params.txt and/or to add the bold or bold-italic variations in fop-userconfig.xml.
If they occur in some places in the body text, you may have forgotten to replace the monospace.font.family.
If the document mostly consists of “#”s but the titles are OK, chances are that you didn't supply a body.font.family (this should make you feel really silly!)
If the pound signs are in isolated places, maybe you have to override the Symbol and/or Dingbat families after all.

Comparing your PDF to the English original may also help to find the cause of the problem. And of course, there's always the firebird-docs list.

Once everything works fine, add and commit the following to git:

The config/xx language subdirectory (if it's not in git yet).
The fo-params.txt file in that subdirectory.
Any .xml metrics files in that subdirectory.
The fop-userconfig.xml file in that subdirectory.

If you don't have git write access, ask a subproject member to commit your work for you, or fork the firebird-documentation project, commit your changes on a branch and submit a pull request on GitHub.