Rights and Roles, Translator Name Placeholders and Easy Deleting Languages

During the last week, we have been working really hard. In this blog post we want to inform you about the latest news of our development:

Assing language to translator in oTranCeAssigning translators in language administration
While managing the languages in oTranCe, it is possible to assign a translator to it. Of course, this user has to be entered before. There is a full text search and a pagination for systems with many translators now. Clicking on the translator’s name, access to the language is granted without page re-loading. You’ll get response immediately via icons.

Placeholders for languages and names in header
From now on it is possible to export translator names and assigned languages in the header or the footer of your language file. The following values are possible: {LANG_NAME}, {LOCALE} and {TRANSLATOR_NAMES}.

As an example:
// {LANG_NAME} is maintained by {TRANSLATOR_NAMES}

will become this in output:
// Deutsch is maintained by joachim.bosch, admin, dsb

New right and role options for every user
All new options for rights and roles for existing or newly registered users will be de-activated by default and must be activated explicitely.

  • User is allowed to delete users
    Does what it says: A user with this right will be able to delete another user. The translations made by the deleted user is not concerned.
  • User is allowed to delete languages
    If this option is checked, the user is allowed to delete languages. All log files for this language will be cleared. All other assigned users for this language will lose their rights to hit it.

Deleting file templates will also delete keys and translations
Deleting a file template will cause the deletion of all assigned language keys as well as translations. Optionally they can be assigned to other file templates entered before.

Status “unassigned” has been deleted
Until this change it was possible to set the status of a language constant to “unassigned”. From now on, a language constant must be assigned to a template file to avoid database rubbish.

Keeping your database clean
All deletion actions (except of deleting language keys) will automatically provoke a defragmentation and optimization of the database on a file system level.

Optimizing the usability (OTC-79)
On the start page, now a click on to the language or the locale directly leads to a list of untranslated keys.

Export untranslated language keys with no value or with the fall back language (OTC-83)
This option in Admin -> Project defines if a missing translation of a language key shall be exported with either the value of the fall back language or with no value. This behaviour might become important for projects using unit tests and selenium tests.

Leave a Reply

Your email address will not be published. Required fields are marked *