LogoLogo
Website
  • 📣What's new @GUIBO
    • Power Users Program
  • Get Started
    • Intro to GUIBO
    • Getting started
      • Initial account setup
      • Prepare library
      • Create your first guidebook
      • Publish to travelers
    • Support
  • Content Management
    • Overview
    • Routes, POIs and Markers
      • Routes
        • Edit route
        • Edit route data
        • Turn-by-turn directions
      • Markers
    • Textpages
    • Libraries
      • Import POIs from libraries (manuel)
      • Import Pois from libraries (automatic)
        • Import Geo Data (linked to libary)
      • Import textpages from libary
        • turn by turn navigation (App/PDF)
    • Language & Translation
  • Publishing
    • How to publish
      • Personalized Accommodation
    • Release Page
    • Tour Guide App
      • First-Level Support Guide
      • Photo Competition
      • App publishing
        • External links
        • Testcode & Download Code
      • White-label App
      • Traveler feedback
    • Roadbook PDF
      • Publishing Roadbooks
      • Customizing Roadbooks
    • Webshop Maps
    • B2B Network
  • Developers
    • Releases API
      • Release | Create guidebook release
      • Release | Read release details
      • Release | Update release details
      • Release | Revoke guidebook release
      • Release | Add documents to release
      • Release | Delete documents in release
    • Content API
      • Content | Create and update routes
      • Content | Create and update Point-Of-Interests (POIs)
      • Content | Create library or guidebook
      • Content | Create category
      • Content | Create text page
  • Administration
    • Users & groups
    • Data backup
  • FAQ
    • Which image types does GUIBO support?
    • How can I test my guidebooks on the smarthone?
    • Support System: How do I create an "App Issue"
    • Support System: How to create a ticket?
    • Support System: How do I assign the correct priority to a ticket?
    • Support System: How to make a screenshot?
    • How are the towns on guidebook overview maps selected?
    • Navigation Issues
    • What are the smartphone requirments for the Tour Guide App?
Powered by GitBook
On this page
  • Change Webportal Language
  • Setup Content languages
  • Account-level content languages
  • Guidebook-specific languages
  • Creating Multilingual Content
  • Content Creation Workflow
  • Managing Languages in Libraries
  • Language Tabs in Editors
  • Automatic Translation
  • Glossary for automatic translation
  • Language Handling in Publishing
  • Tour Guide App
  • PDF Roadbook
  • Best Practices for multilingual content
  • Translation Workflow
  • Prioritizing Languages
  • Testing Multilingual Content
  • Language Strategy by Market
  • Navigation Instructions
  1. Content Management

Language & Translation

Managing Guidebooks in Multiple Languages in GUIBO

GUIBO provides comprehensive multilingual support, allowing you to create content in multiple languages and deliver personalized travel experiences to international travelers. This guide explains how to set up, manage, and use language features in GUIBO.

Change Webportal Language

Configure the language for the GUIBO administration interface:

  • You can switch the GUIBO interface language using the language selector in the top-right corner.

  • This affects the system interface only, not your content.

  • Available interface languages include English, German, and other supported languages.

Setup Content languages

GUIBO offers a two-tier approach to content language management, giving you flexibility to configure languages both globally and for specific products.

Account-level content languages

Define languages that will be available across your entire account for all guidebooks:

  1. Navigate to Account Settings.

  2. In the language section, add the languages you need for all guidebooks.

  3. Enter the language code (e.g., "EN" for English, "DE" for German, "NL" for Dutch).

  4. Save your changes.

Example: If you set English (en), German (de), and French (fr) as account languages, these will be available for all guidebooks in your account.

Guidebook-specific languages

In addition to account languages, you can add languages specific to individual guidebooks:

  1. Open the guidebook you want to customize.

  2. Navigate to the guidebook settings.

  3. Add additional languages that will only apply to this specific guidebook.

  4. Save your changes.

Example: With account languages set as English (en), German (de), and French (fr), you could add Spanish (es) to a specific guidebook targeting Spanish-speaking travelers. This guidebook would then have four available languages, while others would maintain the three account languages.

Creating Multilingual Content

Content Creation Workflow

When creating content in GUIBO, you'll see language tabs for each configured language:

  1. Create your content in your primary language first.

  2. Switch to other language tabs to add translated versions.

  3. Each language tab operates independently, allowing for customized content per language.

Managing Languages in Libraries

All content types support multiple languages:

  • Routes: Descriptions, navigation instructions, and other text can be maintained in multiple languages.

  • POIs: Names, descriptions, and additional information can be translated.

  • Text Pages: Create fully translated versions of all text content.

Language Tabs in Editors

When editing content (routes, POIs, text pages), you'll see tabs for each configured language:

  • Content in each tab is independent.

  • Required fields must be filled in for at least your primary language.

  • Secondary languages can be completed when needed.

Automatic Translation

GUIBO offers automatic translation to help you quickly translate content:

  1. Create content in your primary language.

  2. Use the translation feature to automatically translate to other languages.

  3. Review and adjust the translated content as needed.

Note: Our integrated translation service is powered by DeepL - the leading translation provider. However, we recommend reviewing your translations for accuracy.

Glossary for automatic translation

Account âž” Account Settings âž” Language Settings

The Translation Glossary allows you to customize how GUIBO's automatic translation handles specific words or phrases. When you define terms in the glossary, they will always be translated according to your specifications, overriding the standard DeepL translations.

Language Handling in Publishing

Tour Guide App

  • The GUIBO app automatically detects the traveler's device language.

  • Content is displayed in the traveler's language if available.

  • If content isn't available in the traveler's language, it falls back to your primary language.

PDF Roadbook

  • When creating a release, you can select which language the PDF roadbook will be generated in.

  • The language setting for the release only affects the PDF, not the app content.

Release Page

  • The release page interface respects the traveler's language preferences.

  • Content displayed on the release page will appear in the language selected during release creation.

Best Practices for multilingual content

Translation Workflow

  1. Complete Your Primary Language First: Fully develop content in your main language.

  2. Use automatic translation: Use GUIBO's built-in translation to translate your content at once.

  3. Review and Refine: Have fluent speakers review important content.

  4. Maintain Consistency: Ensure navigation instructions and critical information are clear in all languages.

Prioritizing Languages

  • Focus on languages most important to your travelers.

  • Start with essential content (safety information, navigation instructions).

  • Gradually expand to additional languages based on your market needs.

Testing Multilingual Content

  • Preview your content in the GUIBO app in different languages.

  • Check PDF outputs in various languages.

  • Verify special characters and language-specific formatting display correctly.

Language Strategy by Market

  • Use account-level languages for your core markets.

  • Add guidebook-specific languages for specialized products.

Navigation Instructions

  • Keep navigation instructions clear and precise in all languages.

  • Be mindful of direction terminology differences across languages.

Previousturn by turn navigation (App/PDF)NextHow to publish

Last updated 3 months ago