Child pages
  • as a translator
Skip to end of metadata
Go to start of metadata

In this example, my user name is "translator", my basic language is German and I am translating into English. Basically, as a translator I want to be able to:

  • quickly and comfortable edit the values of the language keys
  • filter, sort and find keys to translate
  • change my configuration
  • download my own work and
  • browse the ready to use files before.
To achieve this, my oTranCe administrator set up the rights as you can see in this screenshot below:

Let us go through every single point of the navigation visible for translators as we already did in the tutorial for guest users of oTranCe.

The Dashboard

When logging into the system with this rights the first screen you will see is the dashboard that shows up all available languages and the status of their translations in absolute and in relative numbers. You can see also the user names of the translators working on their language.

Configuration

Here, you can adjust several personal configurations as are:

  • Interface language
  • Default entries per page in tab "Translations"
  • Your reference language(s): usually this is the language you choose as your native language, I'd choose German in my case. The language you can edit has to be set by your administrator.
  • Change your password here.
  • Enter your personal credentials if you have access to the VCS where oTranCe shall export the language files. Leave it empty if you don't know what it is.

 

Translations

Now it becomes interesting as this is your main working space. Entering this page you will get something like shown in this screenshot:

As you can see, you have several possibilities here to filter and to search for keys and values, the language files (file templates) and to find untranslated keys in the language you want to translate. Of course, you can limit the entries per page and can switch between the pages.

In the table, you will find the file template, the language key and the translation into several languages listed. As a translator, you will not be able to edit file templates and language keys.

In this screen shot, I already filtered by untranslated keys for English. You now have two choices: either edit inline the table by clicking on the pen besides your untranslated value - then you shall see something similar to this screen:

Save your work and open the next value untranslated value in the row by clicking on the pen. Or click on the word untranslated to get to the form view:

You can now browse to the next untranslated file with the blue arrow button, your value will be saved automatically.

Downloads

On this page you can download the whole language pack including all languages for use with the installation of your translated application. The downloads shall be available in several different formats such as *.zip or *.tar.gz. Download one of this packages, unpack it and upload it to the proper path for language files of your application.

Please note: Before you can download the packages, the download packages have to be built by hitting the Button "Build download package" in the Export tab.

File browser

The file browser lets you have a look at the files before you download them.

Export

In this section, you can prepare the download packages. There's no need for building new download packages if all download packages are shown with a green hook (if they are up-to-date). But most likely, you will see a red minus instead on some place as you probably have been working on translations before.

Once the download packages have been build, you will also see a button "Export to VCS". If you don't know what it is, do not press it or ask your administrator. You will not provoke any damage if you hit it anyway (smile)

Log and Statistics

The Log and the Statistics function is more or less just for information: get numbers about who changed how many values or filter the log by user, language and action.

 

 

  • No labels