Translations Follow

Overview

The Editor’s Translations page enables support for different languages in your Meridian-powered app. If one of your visitors has their device set to use Spanish and you have enabled Spanish support in the Editor, your Meridian app on their device will be in Spanish. If a visitor has their device set to Spanish and you haven’t enabled Spanish support,  they will still get Spanish for OS-level translations, but app-level translations will be in your preset default language. 

The first time you use Translations you will need to add one of the below supported languages:

• Arabic
• Czech
• Chinese (Simplified)
• Chinese (Traditional)
• Dutch
• English (US)
• English (British)
• French
• German
• Hebrew
• Italian
• Japanese
• Korean
• Norwegian
• Portuguese
• Russian
• Spanish
• Swedish
• Vietnamese

English will be preset as the default language. Once you have added language support for any additional languages, you will be able to change the default to one of your supported languages.

Managing Translations

Once you’ve added a supported language, the Translations tab provides several options for organizing and managing your text strings and their translations in the Editor.

You can filter your list of translations by language, the type of translation (e.g. building, event, floor, placemark), or by incomplete translations.

The search & edit field can be used to search for a translation to edit it. You can also select a translation directly from the list to edit it.

Exporting and Importing Translations

If you prefer to manage your translations outside of the Meridian Editor, you can export a translations file, edit your translations in the file, and then import the file back into the Meridian Editor.

Note: the Meridian Editor doesn’t support importing language files that didn’t originate from the Editor.

Export a Translation File

By navigating to the Export tab, you will trigger the generation of a languages.zip file, which you can then download or regenerate as needed. The languages.zip contains an individual .po file for each language you have enabled.

Note: When you edit your .po files, don’t delete or add any existing content; only add your translations. Don’t change the filename. Doing so may prevent the Editor from importing the file.

Import a Translation File

Once you have edited your .po files as needed, you can navigate to the Imports tab to begin uploading your files. You can upload all files at once as a languages.zip or you can upload your individual .po files.

Processing speed varies—an import can be nearly instant or take several minutes. If a file hasn't been uploaded yet, it will appear in the 'Pending Imports' list, and disappear  from the list upon successful import. If a file is displaying an error, the status will display as failed instead of importing. Please cancel the import and re-upload your file.

Issues with U.S. and British English

The Meridian Editor’s search function is used to search for user created content in the Editor. This includes the search box at the top of the sidebar, as well as any field where you can add a link to a page, placemark, or event.

The search function searches for U.S. English content. When you enter non-U.S. English content in the Editor, the Editor’s search won’t find that content until it has an English translation. This includes British English content, which the Editor treats as a separate language.

For example, if you created a page with a Russian title, you wouldn’t be able to add a link to that page in your Meridian app until you added a U.S. English translation for that Russian page title. Similarly, if you created a page using a British English title, you wouldn’t be able to search for it in the Editor until you add a U.S. English translation for it even if the text appears to be identical.