SignAgent Manage Fields, Visuals, Fonts, Colours, and TranslationsManage Translations: Set up Translation Fields

Manage Translations: Set up Translation Fields

Once you've set up your languages, you should make sure your translation fields are set up properly. This tutorial will help you to do that.

Note, if you haven't set up your languages, you should do that first. Find instructions here: Manage Translations: Set up Languages

1. Create Translation Fields

There are two ways to create new translation fields: In the Manage Translations Page or in the Manage Fields page

1A. Manage Translations

To add fields directly in the Secondary Language page, just go to Manage Translations, choose Languages, and select the Language that you want to add the fields to. (In this example, I chose Spanish)

In the page the comes up, just add as many fields as you want in the "Fields" area. Don't forget to click Save!

This will create new translation fields for each field that you added. So, in my example, it would create Translation fields called "Department Name Spanish" and "Room Name Spanish"

1B. Manage Fields

You can also add translations to fields individually in the Manage Fields page. First, select the field you'd like to add a new language to.

Next, add as many languages as you'd like to the "Languages to translate" field. Don't forget to Save afterwards!

Option 1A is better if you're adding multiple fields to a single language

Option 1B is better if you're adding multiple languages to a single field

2. Add Fields to Sign Types

Once you've got your translated fields created, you just need to add them to whatever sign types need translation!

You can add translation fields the exact same way that you would add any other field to your sign types. For more details on this, see this tutorial: Customizing Fields in Sign Types

Note that you do need to add translation fields manually, based on which sign types may need translations or not. They won't be added automatically.


Add your comment

E-Mail me when someone replies to this comment