Difference between revisions of "Translating Gramps using Weblate"

From Gramps
Jump to: navigation, search
(Offline translation)
Line 42: Line 42:
  
 
* Use [http://gtranslator.sourceforge.net GTtranslator] (GNOME, windows), [http://i18n.kde.org/tools/ KBabel] (KDE), [http://userbase.kde.org/Lokalize Lokalize] (KDE, windows), Emacs po-mode, [http://virtaal.translatehouse.org Virtaal] (GNU/Linux, Mac, windows), [http://www.poedit.net/ poedit] (GNU/Linux, OSX, windows), or any similar tool designed for translating <code>.po</code> files. If you do not like any of these tools, you can use any text editor to translate messages. If using vim, properly setting the "langmap" option will significantly speed up your work.
 
* Use [http://gtranslator.sourceforge.net GTtranslator] (GNOME, windows), [http://i18n.kde.org/tools/ KBabel] (KDE), [http://userbase.kde.org/Lokalize Lokalize] (KDE, windows), Emacs po-mode, [http://virtaal.translatehouse.org Virtaal] (GNU/Linux, Mac, windows), [http://www.poedit.net/ poedit] (GNU/Linux, OSX, windows), or any similar tool designed for translating <code>.po</code> files. If you do not like any of these tools, you can use any text editor to translate messages. If using vim, properly setting the "langmap" option will significantly speed up your work.
 +
 +
* If possible, when you are finished translating, go to '''File -> Save as...''' to generate a <code>.mo</code> file to syntax check your work. Under poedit, there is an option to always compile a <code>.mo</code> file when saving changes by clicking '''File -> Preferences''' and on the '''Editor tab''' check the '''Automatically compile ''.mo'' file on save box'''. A dialog will warn you if there is a syntax error in your <code>.po</code> file. Lokalize and GTranslator also provide a syntax check when saving. Please enable this feature to avoid errors in the compilation process.
  
 
* Upload the <code>.po</code> file using the '''Files -> Upload translation''' menu option.
 
* Upload the <code>.po</code> file using the '''Files -> Upload translation''' menu option.

Revision as of 18:55, 28 June 2021

As of Gramps 5.2.x, Hosted Weblate for translations.

Translators are advised to read the Weblate documentation.

Creating an account

Registration is easy - just click on Register.

The E-mail and Full name fields are used to credit your contributions.

You need to be signed in to translate, otherwise you can only make suggestions.

Starting a new translation

If your language is not currently translated, you can request that it be added. Navigate to the "gramps" component and select the Tools -> Start new translation menu option.

Select your language, and then click the "Request new translation" button. Further details can be found in the documentation.

A request will be sent to the administrator.

Workflow

Any authenticated user can edit translations. Changes are automatically submitted as a pull request to the Gramps GitHub repository. This can take 24 hours since Weblate attempts to group changes from the same author in a process called "lazy commits".

Some translators have been designated as reviewers. A list of reviewers can be found on the Translators Portal page.

A reviewer an approve translations. After a translation has been approved, it can only be changed by a reviewer or administrator, although any user can still make suggestions.

Bulk edit

It is possible to bulk edit translations. This can be useful if a reviewer wants to approve all translations that they have previously translated and are happy with.

The bulk edit toll can be found under the Tools -> Bulk edit menu option. This may not be available to all users.

Offline translation

Some translators prefer to work offline. In this case, downloading and uploading translations provides an option for a translator to use their favourite translation software.

  • Download the .po file using the Files -> Download translation menu option.
  • Use GTtranslator (GNOME, windows), KBabel (KDE), Lokalize (KDE, windows), Emacs po-mode, Virtaal (GNU/Linux, Mac, windows), poedit (GNU/Linux, OSX, windows), or any similar tool designed for translating .po files. If you do not like any of these tools, you can use any text editor to translate messages. If using vim, properly setting the "langmap" option will significantly speed up your work.
  • If possible, when you are finished translating, go to File -> Save as... to generate a .mo file to syntax check your work. Under poedit, there is an option to always compile a .mo file when saving changes by clicking File -> Preferences and on the Editor tab check the Automatically compile .mo file on save box. A dialog will warn you if there is a syntax error in your .po file. Lokalize and GTranslator also provide a syntax check when saving. Please enable this feature to avoid errors in the compilation process.
  • Upload the .po file using the Files -> Upload translation menu option.

Testing

  • Download the .mo file using the Files -> Customize download menu option. Select a "gettext MO" quick download containing all strings.
  • Rename the download to gramps.mo
  • Locate the translations directory. It will be something like /usr/share/locale/{lang}/LC_MESSAGES, with {lang} being your language.
  • Copy the gramps.mo file into the translations sirectory after making a backup of the original.