PKP uses a different tool for translating documentation called GitLocalize, which is compatible with markdown files, integrated with GitHub, and designed for translating longer pieces of text - and so better suited for translating documentation than Weblate. This chapter explains how to use GitLocalize, find documentation to translate, translate documentation, and maintain translations.
You can translate documentation directly in GitHub without using GitLocalize and the section “Translate without GitLocalize” explains how to do that, but we still recommend reading this chapter to understand how documentation translation works as a whole.
PKP creates and maintains many different guides on using, administering, and developing PKP software applications, as well as other guides about scholarly publishing. Our published documentation can be found in the PKP Docs Hub.
Documentation is coordinated, created, and maintained by the Documentation Interest Group, as well as other PKP staff and community members. We are always improving documentation - from creating new guides to updating documentation as the software and its features change.
All of our documentation is created and updated in the pkp-docs GitHub repository in markdown files and rendered into web pages in the Docs Hub using a tool called Jekyll. You do not need to have any knowledge of these tools to translate documentation.
Most of our documentation is created in English and then translated into other languages, but original documentation in other languages is welcome. If you would like to create and update documentation or are just interested in learning more about how documentation works, check out our Guidelines for Contributing to PKP Documentation or contact us at firstname.lastname@example.org.
Documentation translation is integrated with PKP software translation, and the workflow is similar. Translation of PKP software and documentation is done by PKP software users around the world. Translators can translate one guide or many.
PKP has a Translation Coordinator who coordinates translators and translations and approves and merges translations.
Larger language groups have a Language Moderator who coordinates translators and translations in that language and reports to the Translation Coordinator. The smaller language groups are coordinated directly by the Translation Coordinator.
Anyone with fluency in multiple languages and some understanding of the software and scholarly publishing context is welcome to contribute to translation. We especially appreciate translators who can commit to maintaining a translation over the long term. If you have multilingual fluency but no experience with our software, please use the documentation resources noted above to learn about our software before you start translating. Additional resources are noted below under Choose the Right Words.
If you’re interested in being a Language Moderator for a particular language, please contact email@example.com. Language Moderators are required to make a minimum 2-year commitment to moderating the language. Language moderators should have excellent translation skills and knowledge of PKP software, as they are responsible for reviewing and approving translations. They should also have a relationship with and understanding of the user community for the language, so they can effectively coordinate and recruit translators.
To get started translating PKP software documentation, you can follow the instructions in this guide. If you have questions you can contact the Translation Coordinator or your Language Moderator. You can also talk to other PKP translators and ask questions in the PKP Community Forum.
To use GitLocalize for translation, you need to have a GitHub account and be logged in. If you do not already have an account, register on GitHub.
Once you are logged into GitHub, go to the PKP Docs GitLocalize site. You will need to give GitLocalize access to your GitHub account.
On the homepage, you will see a list of languages.
Click on the language that you want to translate into. In this example, it is Portuguese.
On the language page you will see a list of documents, and beside each document name, the percentage of the document that has been translated. The next step is to decide which document to translate.
Consider the following when choosing a document to translate.
Is there one document that would be more useful to other PKP software users who speak your language than others? If so, you may want to translate that document first.
You can ask the language moderator for your language if they know of any documentation needs or priorities for your language group. You can also inquire with regional user groups.
Think about how much time you can commit to this current translation project. Once you begin a translation project, it is best to finish it within one or two weeks.
Documents vary in size. A few documents, like Learning OJS, have more than 10 chapters and some chapters are quite long. However, most documents have approximately 5 chapters that are 1-3 pages each.
Translation is done in chapter files and paragraphs, so you can choose to only translate a chapter or even only a few paragraphs in a chapter. You may find a document that is mostly translated and only needs a small part of it translated. However, if there is an entirely un-translated document, it is best if you can commit to translating the whole document or at least a thematic section of it. The translation will not be published until the entire document (all files/chapters) have been translated.
You can open each document to see how long it is and what parts of it need to be translated. When you first open the document, you will see the “en” folder and an index file.
Click the en folder to see all of the chapter files in the document.
Then open a chapter folder to see how long the chapter is and what parts need to be translated.
In this example you can see that the guide has not been translated yet.
In this example the guide has been translated.
If there is a document that is completely or mostly untranslated, you can also open it in the Docs Hub to see how long it is and what content it contains.
Once you decide on a project, you can start translating.
In GitLocalize, go to the folder for the language that you are translating into. Find the guide that you want to translate and open it.
Click the en folder to see all of the chapter files in the document. You will also need to translate the Index file in the main folder.
The chapter files will be listed in alphabetical order. Start by translating the SUMMARY.md file. After that you can translate the files in any order you want, but it might be easier for you to translate the files in their logical order. If so, you can open the guide in the Docs Hub to see what order the chapters are in and follow that order.
Starting with the SUMMARY.md file, open the file. You will see a split-view editor, with the original text on the left. GitLocalize breaks the files down into translatable segments, automatically links the translation with the version in the source language, highlighting the sections that are missing translations.
If you click the text on the right, a text-editing box will appear with the original text in it. You can replace this text with translated text. Click Submit as you finish each part.
You can also use the machine translation tool to get machine translation assistance.
If you click the Machine Translate button below the text box, GitLocalize’s machine translation tool will enter a suggested translation into the text box, which you can then edit.
Or if you click the Machine Translate button on the top right of the page, machine translations will be entered in all of the text boxes that have not already been translated. This will take a few seconds. You can then edit them manually.
You may find that the machine translator will skip some sections, which you will have to translate manually or use an external machine translation tool.
You will have to click Submit below each piece of text to confirm that the translation is complete.
When translating software documentation, it’s important to use terminology that is consistent with the software application and is commonly understood by users. There are a number of ways you can check this:
You will see screenshots as you are translating, but you can ignore them. PKP is developing an automatic process to generate screenshots for translations.
When you have finished translating the chapter and clicked Submit below each piece of text, the next step is to request a review of the translation to the language moderator.
Click the Create Review Request button on the top left. This will open a form where you can leave comments about your translation. Note anything you were unsure about that you want the moderator to check in particular. Include any other comments that are relevant.
Then click Submit.
Now you will see a page where you can commit the changes, but you cannot actually take an action here unless you are a Moderator, so you are finished.
After the review has been completed and your translation merged, you will receive an email notification. The moderator may have questions or suggestions for your translation, in which case you will also receive an email notification.
Now you can translate another chapter! Click the language link to go back to the language folder and follow the steps above again, creating a new review request as you finish each chapter.
After you complete a translation of a document, it is ideal if you can continue to maintain the translation as the document is changed and updated. Documents are updated when the software changes or when improvements and additions to the document are made.
Once you translate a document, any time there is an update to that document it will get sent to GitLocalize and you will receive a notification of the update at the email address associated with your GitHub account.
You can also visit GitLocalize to see if there have been updates that need to be translated, even if you did not do the original translation. If a document shows a percentage un-translated, there is probably an update that needs to be translated.
If the document shows a status of “Conflict,” like in the example below, it probably means the document was translated outside of GitLocalize and so the relationships between the original text and translated text have not been defined. See the section below on “Update a Document Translated Outside of GitLocalize” for further information.
Usually updates will consist of small changes, such as a change to a paragraph, a new paragraph or section, and/or updated screenshots. Sometimes changes will be larger, like a new chapter or substantial changes to the text and/or screenshots. Usually if a document changes substantially, the DIG will release a new version of it and maintain the old version.
To update the translation, open the guide and find the chapter that needs to be updated, which will not be 100% translated.
On the right you will see text in the document’s original language that needs to be translated.
Translate that text, using machine translation tools as desired, and click Submit below the section when finished.
Click Create Review Request when you have finished translating the updates.
Some PKP documents were translated before GitLocalize was adopted. These translations have been moved into GitLocalize but the translated segments of text need to be manually connected to the original segments of text. Until the segments are connected, the document will show as having “conflicts.”
To update these translations you can follow the instructions above. Please note that because these documents were translated in the past, there may be a number of significant changes and new segments that need to be translated.
In addition to updating the translation, you will need to connect any segment tinted red to its original segment. This includes screenshots.
Do this for the rest of the red segments on the page.
If a document has already been translated but you think the translation needs to be improved, you can edit an existing translation.
Follow the instructions above under Start Translating. The translated text will appear on the right.
You can edit any section that needs improvement and click Submit as you finish the section.
When you are finished, follow the instructions under Create Review Request.
If you do not want to use GitLocalize to translate PKP documentation, your other option is to translate the markdown files, maintaining markdown formatting, and submit your translation directly in the pkp-docs repository in GitHub. Please note, this method is less preferred because the translation will need to be pulled into GitLocalize and the Translation Coordinator or a future translator will have to manually associate each translated segment of text with the original text.
To understand how documents in pkp-docs are structured and how to create and edit documents, read the Guidelines for Contributing to PKP Documentation.
You can look at the structure of an already translated document, such as Learning OJS, to see how a GitHub-based translation will work.
If you are a Language Moderator and a new translation in that language is completed in GitLocalize, you will receive a notification by email that there is a new translation to review.
Go to the PKP Docs GitLocalize site. You will be automatically logged in if you are logged in to GitHub.
Go to the Review Request tab to see the open review request.
Click on the review request to open it. The Conversation tab will show any comments the translator made. Go to the second Translated Texts tab to view the translation.
If you want to suggest changes to the translator or ask a question, reply in the Conversation tab. If you are happy with the translation, you can go back to the Conversation tab and click Send Pull Request. You will be asked to enter a Title and Description for your pull request. The title should include the name of the file or files that are included in the translation pull request and the language that they were translated into. For example, “French translation of Learning OJS - Website Settings.” The Description can be the same or you can add further information as needed.
This will send a pull request to the pkp-docs GitHub repository, to be merged. You will receive an email notification once it is merged. The translation will be available in the Docs Hub the next time the website is built, which could be in a few days or a week.
There is a bug in GitLocalize that will sometimes display a link to “Create Review Request” after you have gone through all of the above steps and there is nothing new to review. If you encounter this, please ignore it.