Table of Contents
🧪 Launchpad localization is currently in beta
Please contact Appcues support if you are interested in joining the beta group.
This article covers Launchpad localization, for more information on localization refer to the Localize Flows, Localize Banners and Localize Mobile Experiences articles.
Localizing experiences allows you to add translated content that will show in a Launchpad based on a user's browser language. This article covers Launchpad localization.
Configuring Languages
In order to localize content you will need to have languages set up in your account. These will be the languages that can be selected from when localizing individual experiences. If you've already set up languages for web and mobile flows those languages will already be available for use for Launchpads.
Languages can be configured through the account localization settings, or by clicking on Localization settings in the dropdown in the banner builder and then Manage languages on the next panel.
A new language can be configured by selecting the + Add language button. This will allow you to set the name for the language, the property that's used for the language, and the properties that should be included in the group.
When the language is fully configured select the Save button and add it to the list of selectable languages.
Localizing content manually
After the target languages are configured, any editable text can be localized by manually editing the text in the builder.
To add a new translation to the Launchpad: Click the language dropdown > Toggle on the languages you want to add.
To update the content: Switch to the added language in the dropdown.
Translations can then be added directly in the builder.
Using XLIFF files to upload translations
After the target languages are configured the content for those languages can be added by using a translation file, this can be particularly useful if you're using a translation service. Xliff is a file format used for localizing content. In most cases when the format is used it's used with a specialized service or editor like Smartcat or Lokalise. The file will include all editable text content in your experience.
With these services the xliff file and be uploaded into the platform and the content will be displayed in their editors for localizing and validating the translations.
To download the translation file: Click the language dropdown > Select “Localization Settings” > Click the gear icon for the desired language > Click the “Download .xliff” button
Editing xliff files
For quick updates there may be cases where you want to edit an xliff file manually, this can be done using a text editor. Preinstalled editors TextEdit (Mac), Notepad (Windows), or specialized editors like Sublime and VSCode support the xliff format.
When working with a xliff translation file the content will be displayed in trans-unit blocks. In the block the source will be the original source content for the block. The target will be the content to be used for that block when it is localized.
<xliff xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 http://docs.oasis-open.org/xliff/v1.2/os/xliff-core-1.2-strict.xsd" xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2">
<file original="e97ce916-643b-4182-8cd9-7279ee065bf4" datatype="plaintext" target-language="pt-br">
<body>
<group id="ad0175a5-fe4c-45fd-b264-f9f7e69c6263">
<trans-unit id="3a8780a6-5d1e-4991-840d-2f8dbafebf7c">
<source>Resource Center</source>
<target>Centro de Recursos</target>
</trans-unit>
<group id="7c1efe31-ea40-4ff5-8add-c07f77257a3d">
<trans-unit id="e5b552ef-63f3-440e-9a91-fe694fd88e3b">
<source>How can we help you?</source>
<target>Como podemos ajudar você?</target>
</trans-unit>
<trans-unit id="e37d1804-b8a2-4103-be3d-0ddf590358ba">
<source>Contact Support</source>
<target>Suporte</target>
</trans-unit>
<trans-unit id="574f3246-cdcf-4a70-90f4-999717712f7d">
<source>Read Help Docs</source>
<target>Documentação</target>
</trans-unit>
<trans-unit id="1fa0f5c7-ecab-4931-99e7-0c2eab91abe1">
<source>Submit Feature Request</source>
<target>Envie uma ideia</target>
</trans-unit>
</group>
<trans-unit id="7c33460c-2320-4857-8e50-c866cd0163cc">
<source>Need Help?</source>
<target>Precisar de ajuda?</target>
</trans-unit>
</group>
</body>
</file>
</xliff>To upload the translated file: Click the language dropdown > Select “Localization Settings” > Click the gear icon for the desired language > drag-and-drop or browse files to upload the xliff file you edited. When the file is uploaded the experience content will update with the content from the translation .
AI translation
This option will take the current Launchpad content and replace it with an automatic translation into the target language.
For assistance managing AI features in your account contact support@appcues.com.
Translating Flow names in the Flow List block
After a web Flow has been localized, you can also translate the display name that will appear in the Launchpad's Flow List block. Just click the Localize display name button in the Localization panel on the Flow settings page. Add your translation in the slideout panel, hit Save, and you're ready to go!
.png)
Right-to-left (RTL) language support
Right-to-left support is handled automatically in the SDK for right-to-left languages. When the user has their device set to a RTL language the contents will automatically adjust to align appropriately. With RTL, components will be flipped so content on the right will be on the left, content that is right aligned will be left aligned, and vice versa.
When building Launchpads, the RTL toggle can be used to view content in the preview panel with the RTL layout.
FAQ
Q: Can articles returned from a Knowledge Base integration be translated?
A: This is not currently supported, but it is a feature we are exploring.