Purpose

GetPaid is built with internationalization (i18n) to allow for translations of the interface in different languages. Depending on a Plone site's settings, the translations will display based on the user's browser settings. This document is designed to help those desiring to make (or update) a translation of the GetPaid interface into another language to do so.

Prerequisities

• How to update language files - Plone translation files
• You will need to have the ability to commit your translated files to the product (either directly, if you have commit rights to the product, or with the help of someone who does). To get commit access to GetPaid, send an email via www.plonegetpaid.com/contact requesting access. If you already have a file and need it added to the product, you can send it to the getpaid-dev mailing list.
• You will need some kind of editor to edit the .po file
• GetPaid is implemented in 2 main products (PloneGetPaid and getpaid.core), and thus has two separate areas where translations are created/maintained: PloneGetPaid/i18n/ (two files) and getpaid.core/src/getpaid/core/locales/ (one file per language, in the language's folder).
  

Step by step

Making a new translation

For translating to a new language, translate each of the fields in the .po file to the language corresponding to the file (see more below). In order to get the .po file into the product, it needs to be committed to the product.

Updating a translation

GetPaid continues in development, and thus new items that need translation will be created as new parts of the interface are added. Please be sure to update the appropriate .po files located at PloneGetPaid/i18n/ and getpaid.core/src/getpaid/core/locales/ .

Further information

•  How to update language files - Plone translation files