Safari Portal's language translation feature makes it easy to create multilingual Lookbooks and Itineraries, whether you're preparing documents for international clients or working with content in multiple languages.
With Superbuilder, you can translate an entire document, translate only system-generated text, or create and save individual translated content pages for future use.
Note: Superbuilder Lookbooks are available now, with Superbuilder Itineraries coming soon!
Your clients can also view shared documents in their preferred language, with automatic browser-language detection and a built-in translation widget.
Important: The Language Translation add-on must be enabled on your Safari Portal account to access the translation functionality within Superbuilder and the Content Library.
1. Translating an Entire Lookbook or Itinerary
If you've created a Lookbook or Itinerary in one language and want to produce a complete version in another language, you can translate the entire document.
Step 1: Create Your Document
- Navigate to your Files dashboard.
- Click Create New.
- Select Lookbook → Superbuilder Lookbook, or choose a Superbuilder Itinerary where available.
- Add the content pages you'd like to include, either from your Content Library or by creating new pages. To add a new page, hover between pages in the Table of Contents and click the blue + button.
Step 2: Translate Your Document
Once you've finished adding your content:
- Click More Options → Translate.
- Select your desired language.
- Choose the option to translate everything.
- Select the option to save all translated content pages back to your Content Library.
- Proceed with the translation.
Safari Portal will translate the document into your selected language, including the content pages and system-generated text.
Tip: We recommend saving translated pages to your Content Library so you can reuse them in future documents without translating the same content again.
Step 3: Review and Refine Your Translations
Automated translation can save considerable time, but if you're fluent in the target language, we recommend reviewing the translated content before sharing it with clients.
You can edit translated pages directly within Superbuilder to refine the wording, adjust terminology, or ensure the content reflects your company's preferred tone and style.
If you've made changes to a translated page and want to preserve your preferred version:
- Locate the page in the Table of Contents.
- Click the three-dot menu beside the page.
- Select Overwrite.
This updates the corresponding page in your Content Library with your preferred translation.
The next time you need that page, you can simply add the saved translated version from your Content Library. Translated pages are tagged with their respective languages, making them easy to identify and find again later.
2. Translating Only System-Generated Text
If you've already created or selected content pages in your preferred language, you don't need to translate everything again.
Instead, you can choose to translate only the system-generated text.
This includes elements such as dates, navigation labels, and other default interface text that you wouldn't otherwise be able to manually edit.
For example, if you've already created a complete French Lookbook using your own professionally translated French content, you can translate just the system-generated elements into French without changing any of your existing content.
To do this:
- Open your document in Superbuilder.
- Navigate to More Options → Translate.
- Select your desired language.
- Choose the option to translate only system default texts.
- Proceed with the translation.
Why use this option?
- Preserve your preferred or professionally reviewed translations.
- Translate dates, navigation, and other system-generated labels.
- Avoid unnecessary retranslation of content you've already prepared.
- Maintain consistent terminology and editorial style across your documents.
This is particularly useful if you maintain separate Content Library pages for different languages.
3. Translating Individual Pages from the Content Library
You don't need to create an entire Lookbook or Itinerary to translate your content.
You can also translate individual content pages directly from your Content Library.
How to Translate a Content Page
- Open your Content Library.
- Locate the page you'd like to translate.
- Click the three-dot menu beside the page.
- Select the language you'd like to translate it into.
- Proceed with the translation.
The translated page becomes a separate content page that you can review, edit, and reuse in future Lookbooks and Itineraries.
Building a Multilingual Content Library
Over time, you can develop a collection of reusable content in different languages.
For example, you might maintain English, French, Spanish, and German versions of your most frequently used hotel descriptions, destination guides, and activity pages.
When creating a new document, simply pull in the content pages in your desired language.
You can then use the Translate System Default Texts option to ensure that navigation, dates, and other system-generated elements match the language of your content.
Important: Translated Pages Become Independent Pages
Once you translate a content page, the translated version becomes a separate page in your Content Library.
This means that automated updates from the original page will no longer flow through to the translated version.
For example:
- You create an English hotel description.
- You translate it into French and save the translated page.
- You later update the original English description.
The French version will not automatically inherit those changes.
You'll need to update the translated version separately if you want it to reflect the latest information.
This gives you complete control over your translated content, but it's important to keep in mind when maintaining pages in multiple languages.
4. Exporting Translated Documents to PDF or Word
Once you've translated your Lookbook or Itinerary, you can export it in the selected language.
Superbuilder supports exporting translated documents to:
- Word
This is particularly useful when you need to send a downloadable itinerary or proposal to a client, partner agent, or other recipient.
Clients can also export their client-facing document to PDF in the language you've prepared and shared with them.
5. Automatic Language Translation for Clients
In addition to translating documents within Superbuilder, Safari Portal also supports automatic language translation when clients view shared Lookbooks and Itineraries.
Automatic Browser-Language Detection
Safari Portal can automatically detect the language configured in your client's browser and translate a shared Lookbook or Itinerary into that language.
For example:
- You create and share an itinerary in English.
- Your client opens the link using a browser configured in Spanish.
- Safari Portal automatically displays the itinerary in Spanish.
This allows clients to view your content in their preferred language without requiring you to create and share separate versions for each recipient.
How to Enable Automatic Browser-Language Detection
- Open your Lookbook or Itinerary in Superbuilder.
- Navigate to More Options → Translate.
- Choose whether to Translate Everything or Translate Only System Default Texts, if you'd also like to translate the document into a specific language.
- Enable Auto-translate to the client's browser language.
- Apply your settings.
Tip: You don't need to translate your document into another language to use this feature. You can leave the document in its original language and simply enable Auto-translate to the client's browser language. Safari Portal will then automatically translate the shared document based on each client's browser settings.
Save Your Translation Preferences as Defaults
You can also save your translation settings as defaults, so you don't have to configure them each time you create a new Lookbook or Itinerary.
For example, if you typically create documents in English but want clients to automatically see them in their preferred language, you can save that configuration as your default.
The next time you create a Lookbook or Itinerary, Safari Portal will remember and apply your saved translation preferences automatically.
Client-Facing Translation Widget
Clients can also use the translation widget available in the shared document to select another language.
For example, a client viewing an itinerary in English can use the widget to switch to French, German, Spanish, or another supported language.
Important: Client-Side Translation and PDF Exports
There is an important distinction between translations created in Superbuilder and translations selected by clients through the translation widget or automatically through the client's browser only.
Translations created within Superbuilder:
These are part of the document's prepared content and can be exported to PDF or Word in the translated language.
Translations selected by clients using the translation widget/ through the client's browser language:
These are applied to the client-facing viewing experience.
If a client changes the language using the translation widget and then exports the document to PDF, their selected translation will not carry over to the PDF.
The PDF will instead use the language of the document as prepared and shared.
Recommendation: If your client needs a downloadable PDF in a specific language, translate the document into that language within Superbuilder before sharing it.
6. Supported Languages
Safari Portal currently supports 25 language options, including regional variations of English, Portuguese, and Spanish.
Arabic | Japanese |
Catalan | Korean |
Chinese | Norwegian |
Czech | Polish |
Danish | Portuguese (Portugal) |
Dutch | Portuguese (Brazil) |
English (American) | Romanian |
English (British) | Russian |
Finnish | Spanish |
French | Spanish (Latin American) |
German | Swedish |
Greek | |
Italian |
These languages are available through Safari Portal's translation functionality.
7. Best Practices for Multilingual Content
Start with polished source content.
Clear, well-written original content generally produces better automated translations.
Review translations before sharing.
Pay particular attention to destination names, travel terminology, dates, inclusions, exclusions, and other important details.
Save your preferred translations.
Once you've reviewed and refined a translated page, save it to your Content Library so you can reuse it in future documents.
Use system-only translation when appropriate.
If your content pages are already in the correct language, translate only the system-generated text to preserve your preferred wording.
Remember that translated pages are independent.
Updates to the original page won't automatically update its translated versions. Be sure to maintain your translated pages when important details change.
Prepare the document language before exporting.
If you need a client to download a PDF in a particular language, prepare that language version in Superbuilder rather than relying on the client-facing translation widget.
Frequently Asked Questions
Do I need the Language Translation add-on?
Yes, the Language Translation add-on is required to access the full translation functionality in Superbuilder and the Content Library.
The exception: You can translate system-default text in Lookbooks and Itineraries using the Translate feature, even without the add-on. However, translating your own content requires the Language Translation add-on.
Can I translate an entire Lookbook or Itinerary at once?
Yes. Use More Options → Translate and select the option to translate everything.
Can I translate just the dates and navigation without changing my content?
Yes! Choose the option to translate only the system default texts. This preserves your existing content pages and preferred translations.
Can I translate individual pages without creating a document?
Yes. You can translate individual content pages directly from the Content Library using the three-dot menu.
Can I edit automated translations?
Absolutely. You can refine the translated content and save your preferred version for future use.
Will translated pages automatically update when the original page changes?
No. Translated pages become independent content pages. Changes to the original page will not automatically flow through to translated versions.
Can clients view a document in their own language?
Yes. Safari Portal automatically detects the client's browser language and translates the shared document accordingly. Clients can also select another language using the translation widget.
Can clients download a translated PDF?
Yes, if the document has been prepared in that language within Superbuilder. However, if a client changes the language using the client-facing translation widget, that translation will not be reflected in their PDF export.
Can I export translated documents to Word?
Yes. You can export translated documents from Superbuilder to both PDF and Word.
Get Started
Whether you're creating a fully translated itinerary, building a multilingual Content Library, or simply making your documents more accessible to international travelers, Safari Portal's language translation tools help you deliver a more personalized experience.
To get started, open a Superbuilder Lookbook or Itinerary and navigate to More Options → Translate.
If you don't yet have access to the Language Translation add-on, contact Safari Portal Support to learn more about enabling it for your account.
language translation, translate, translations, multilingual, Superbuilder, Lookbooks, Itineraries, Content Library, translated pages, translate content, automatic translation, browser language, client-facing translation, translation widget, system default text, system-generated text, translate dates, navigation translation, PDF translation, Word export, language settings, international clients, foreign languages, translated itinerary, translated lookbook, language add-on, reusable translations, overwrite translated pages
