Start Poedit and select the appropriate project and language you want to work on, this will open the Poedit with the appropriate. Activate updated translation at your server ¶ mo files after you made source code changes. The last step will create a PULL REQUEST which can be reviewed and then approved by a developer. Go to the correct file position which, in case for French is:ĭrag the updated files into the Upload form, and write a title/description of the changesĬlick on “Create a new branch for this commit…” and then click on the green button. Push translations to the repository ¶įor sharing our updates, we must upload the files to GeoNode’s GitHub repository. The ‘.mo’ file can be overwritten if necessary. Poedit will ask where to write the “.mo” file to, by default, this is the same folder as the edited ‘.po’ resides in. Go to the Catalog menu and choose the Update from POT File sub menu. Compiling the translation means to create a binary “.mo” file out of the edited “.po” file. Follow the instructions below to update your custom translation file to include an up to date list of strings to translate: Open existing translation file (another-wordpress-classifieds-plugin-deDE.po, for example) using Poedit.
All you have to do is clicking the ‘Save’ button from the top menu.Īs a last step we compile the file. Saving translations ¶Īs soon as the translation is complete, it must be saved and compiled. In case this button is checked, the phrase will be marked as ‘fuzzy’ and ignored in GeoNode. When clicking on one, it can be translated through the bottom panel.ĭuring translation pay special attention to the button saying ‘needs work’. This is not necessarily an error, just a warning asking the user to double check.įollowing to marked phrases, ‘Poedit’ will show untranslated sentences. ‘Poedit’ will place translations which may require additional consideration on top of the list.Ī warning mark means that the interpretation might be not entirely consistent with the original phrase. Next click on ‘Validate Translations’ from the ‘Catalogue’ menu: Poedit’s interface should look similar to the one shown in the picture below: Identifying translation issues ¶įrom the ‘poedit’ menu ‘View’, make sure that ‘Entries with Errors first’ is checked: Make a copy of the file before starting the translation so that you can revert in case of errors.Īfter installing ‘poedit’, you should be able to double click on the ‘.po’ file to open it.
#Poedit update from code install
Next, to download the language file, we need to install an OpenSource Editor called “poedit” for editing from: Translation process ¶ Download the translation File ¶Īll language files live in a specific subfolder called after their iso code within the locale folder.įor example, for French, the main translation file called django.po can be downloaded from here.
#Poedit update from code full
If you’d like to know more about how all of this works you’ll find a full description at the Django Docs.įollowing will concentrate on what is needed for edit existing or contribute a new translation.
#Poedit update from code software
Activate updated translation at your serverīehind the scenes, GeoNode is using a software called GNU gettext further text-based translation files (django.po and djangojs.po) for translating content.