Jump to: navigation, search

Translating Gramps using Weblate

1,880 bytes added, 18:37, 28 June 2021
no edit summary
Translators are advised to read the [ Weblate documentation].
== Creating an account ==
Registration is easy - just click on [ Register].
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.
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"].
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 <code>.po</code> 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 <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.
* Upload the <code>.po</code> file using the "Files -> Upload translation" menu option.
= Testing =
* Download the <code>.mo</code> file using the "Files -> Customize download" menu option. Select a "gettext MO" quick download containing all strings.
* Rename the download to <code></code>
* Locate the translations directory. It will be something like ''/usr/share/locale/{lang}/LC_MESSAGES'', with {lang} being your language.
* Copy the <code></code> file into the translations sirectory after making a backup of the original.

Navigation menu