Submit a ticket My Tickets
Welcome
Login

Translations Overview

If you have a multi-language Brandworkz instance (e.g. English and Spanish) then the Language translations feature enables you to view and modify any existing translations and also translate any missing translations.

Please note:  it is not possible to enable multi-language mode yourself as a sys admin, you must contact Brandworkz for this.


The effects of having a site multi-language enabled are:


  • A language dropdown will show up in the top utility bar for switching the User Interface language (note that until some language translations are actually entered, everything will still show in the master language - typically English)
  •  If you are using CMS pages, you go in to enter/edit the content of a page in each language in turn (note that if no 'foreign' content has been entered for a CMS page then the content entered in the master language will be shown regardless of which language the end-user has selected).
  • If you are an admin and have text or textarea fields as part of a metadata/tagging set for assets (e.g. a Description field), then you can go and enter the text in one language first, switch to another language in the utility bar and then enter the text in that language for the asset, etc.
  • If you are an admin and have multiple-choice fields as part of a metadata/tagging set for assets (e.g. Season with the options Spring, Summer, Autumn and Winter), then you can go to the metadata admin for that field, enter the options you want, switch to another language (while still on the metadata field admin page) and then overtype the English options with the local language options - e.g. if French is enabled: printemps, été, automne and hiver (remember to use the Modify button, otherwise you will get new options). That way, when you upload assets, and need to tag them with these multiple-choice fields, you only have to do it once - and it doesn't matter which language you are in when you do it.
  • In the above example, if an asset is uploaded when in English mode and this is tagged with a Season of Summer, then the English search index for that asset will automatically get populated with Autumn and the French search index for that asset will get populated with Automne)


To recap, remember the following regarding translations:


  • The 'Language translations' section is only for managing translations within the general user interface (e.g folder names, system phrases, etc)
  • Translations for metadata/tagging labels and options are managed from the Metadata admin section
  • Translations for CMS pages are done by going to Edit mode for an individual page, switching to the relevant language in the utility bar and entering the page text in this language.

Finally, if you have a specific person/people in your organisation - or an external translation agency - who manages translations but aren't sysadmins, then you can give them a login where you enable the 'Translation admin' role in their user profile. This way they will be able to see the 'Language Translation' button under settings but no other admin buttons. 

There are five different tabs in this section for managing translations in the general user interface.

Translate new phrase tab

 


Phrase to translate from:

Here we can enter any single word or phrase within the system that has not been translated yet if you already know that it's missing. Note that these missing words/phrases will typically show up under the 'Missing' tab so you would typically just use that tab first (the default)

Language to translate to:

This drop down will show all the available languages to translate to, that have been enabled within the site.


Translated phrase:

in this field we'll enter the translated version of our English word/phrase


Current translations tab


 In the drop down we can select the language that we'd like to see current translations of.


The first column shows the original and the second the translated version.


Click the little pencil icon to the right for a particular item if you want to edit the current translation.


Also note that this will typically be a fairly long list, so use the Search widget in the top-left corner of the table to find the phrase you are looking for.

Missing tab


 

This section lists all the terms/words/phrases that have been identified as missing a translation in one of the other enabled languages.


Note that phrases don't show up here until an end-user (or you as the administrator) has gone to the page where this word/phrase is on and viewed it in a 'foreign' language. We have done it this way to avoid you having to incur translation charges/time for sections/features of the Brandworkz system that you our your end-users may never use. If you would like to do a comprehensive up-front translation of every single possible phrase in your system, then please contact our support for this.


You - or your translation agency - will need to go to this tab on a regular basis because as you add e.g. new folders over time, they will be missing translations unless you diligently do this every time you add a new folder. Note that asset titles are not translatable. We have made this choice because our clients typically have thousands of assets and translating all of all asset titles on an ongoing basis would incur significant translation effort/charges on your behalf.


The "translate" link next to a missing term will take you to the first tab 'translate new phrase' where you can translate it.


Page First Found On - by clicking on this option you will be taken to the specific page within the system where the translation was first found to be missing. This is helpful when you need to see the context of where that phrase is used. Note that if the same phrase is used on other pages, then the same translation will be used there.


If some of the missing translations don't need translating (e.g. measurements, people's names, brand names, etc) you can select them and then press the "Suppress selected" button to stop them showing up as missing.


Finally, you can export all the missing translations for the language currently selected in the dropdown above the table by clicking Export All. This will generate and download a Microsoft Excel spreadsheet.


The spreadsheet will have three columns:

  • The "locale"  (or language code) which these words/phrases should be translated to
  • The phrase in the original/master language (typically English)
  • An empty third column for the translation where you put in the translated phrase which matches the local in the first column.


Once you have entered all the translations, you can then go and re-import it under the Import spreadsheet tab (see below)


Suppressed tab


This is simply a listing of the words/phrases which you have suppressed as not needing translation (see previous section).

If you wrongly suppressed a word, you can go and translate it here.


Import spreadsheet tab


Here you can re-import the spreadsheet which you exported under the "Missing" tab and then filled out.


Note that this will not work if you modify the structure/columns of the exported spreadsheet. 

Tip: If you have more than two languages enabled for your site, then you can do the following.


  • Under the "Missing" tab, switch to the "foreign" language which is your most popular one - as this will have the most missing entries as the end-users using that language are likely to have hit more pages and then "found" more missing languages.
  • Export the missing translations for that language.
  • Make a copy of this spreadsheet for each of your other languages, and as you do so modify the locale column to your other locales. E.g. if your most popular "foreign" language is "Spain Spanish", then the locale exported would be "es-ES".
  • If you also have "France French" enabled for your site, change all of the es-ES locale entries in the first column to "fr-FR".
  •  Translate each of these local language spreadsheets and import them in turn.
  • Once you import these phrases, they will stop showing up under the Missing tab.



Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.