Translating Field Desktop
The German Archaeological Institute’s (DAI) software for the documentation of field research is currently managed by the development team in English and German. All other languages are managed by the community. This page explains the why and how of translating the application (user interface and configuration) into a new language or participating in the translation effort for one of the already available languages.
Field Desktop is the main desktop (MacOS, Windows and Linux) application for collecting data. Any new version release requires the user interface to be translated immediately. Therefore a structured process is required to enable the community to participate. The following steps are to be taken if a private person or an organization wants to be involved.
The translations are managed with Weblate. Please consult the documentation for any questions on specific functionality like the statistics. This wiki focuses on the practical translation of Field Desktop and its components. The DAI manages the translations for Field Desktop in a publicly visible Weblate project. If you click on the project you will see many components with a visual representation of the translation status.
All the components besides the manual (see below) are listed here.
The components of the software are:
The components of the configuration are:
Additionally the Sample data can be translated as well. The glossary can be used to ensure consistency of translations across components.
To get the right to translate into a certain language, registration is required. If you have any questions about the registration process feel free to contact the development team, but there is nothing out of the ordinary here.
After successful registration, you will be sent a confirmation link. Follow the link to confirm your registration and login to your account.
Next, create an issue in the Field Desktop repository. Please tell us your Weblate username and which languages you want to translate into, see screenshot. Use the label "translation" as shown below.
One of the admins will add you to the groups as quickly as possible so you can start.
If you want to become an admin for the language, mention this in the issue as well. Admins will be able to review the translations and be responsible for responding when a new version of Field Desktop is released.
Pick the language that you are translating (if you have more than one and pick an option to start with. The navigation options all have an explainatory pop up text, that appears when you hover over the icon.
Under "Strings status" you can see the unfinished strings, and strings marked for edit. If you click on "Untranslated strings" you will see all untranslated strings in this specific language. Clicking on "Browse" lets you look through the strings, "Translate" brings you into translation-mode and "Zen" changes into zenmode. In Zenmode you see all items that are to be displayed in one list that can be scrolled through without switching the page. This mode is also useful for translating (see below).
The most important parts of the application are the User interface, the Application window and the Application initialization. The Core Configuration should also be translated, but will not grow with every version.
When there are new terms added to the application window, they will show up on the top. When you click on "Translate" all the terms will appear in a new window.
At the top of the page, the options display 1/50 strings in this section (see screenshots), besides that are the option to go to the beginning, back and to the next string or to the last one. Besides the basic navigation options at the top of the page, there is a search bar. Besides typing in a word to search for (which is searched within the translation, the key and also the language translated from) you have a lot of options here to filter the strings with, like string:needs-editing shows all strings that were flagged with "needs editing". The results of a search are shown and can be navigated through. If no results are available, a message will appear that no strings were found.
In the translation window (note the top-right option to create a permalink to this item) the first part in the example (see screenshot) displays the german translation of the key, which is displayed at the top right. Besides the German there is a button to copy the string to the clipboard and right beside it one that clones the string into the translation (English in the example).
Right below the translation of the language you are translating into is displayed, every translation can be flagged with "Needs editing". They are automatically flagged as needing editing, when the original (German) string has changed or it has been lagged manually.
Different characters and control signs can be added directly to the translation with the options being displayed right above the translation. Below the strings, you have the option to skip the string or to save the translation and continue.
#Todo: add glossary terms
The manual is currently available here. It is not managed by Weblate and has to be translated separately at the moment. If you are interested in offering a translation don't hesitate to contact the team!
Please feel free to point out any problems with the English or German translations and create an issue to make the development team aware of any mistakes.