Automatic Translation¶
Overview¶
To improve multilingual accessibility and ensure that users always receive some form of translated content, our system performs automatic translations at the time of publishing. This is especially important because many of the source data we receive lacks complete translations.
Our automated translation system ensures a minimum level of linguistic availability for key content, making it easier to browse, search, and engage with the platform regardless of language gaps in the original input.
Supported Languages¶
We currently support automatic translation for the following languages:
- German (de)
- French (fr)
- English (en)
- Italian (it)
These languages are translated bidirectionally, depending on the missing fields in the localized content.
Future Expansion¶
We are exploring the possibility of adding support for additional languages as a business service. This could address the needs of partners who require translations beyond our current set. Such an extension would be considered a new feature and is not yet implemented.
Automatically Translated Properties¶
Our translation logic selectively targets properties that are considered user-facing and valuable for localization. The following is a list of object types and their associated fields that we currently configure for automatic translation:
Info
This list is based on the current implementation and may not be exhaustive.
Category¶
Name
Tag¶
Name
Award¶
NameDescriptionLevel
Thing (Generic Content)¶
NameDescriptionDisambiguatingDescription
Place¶
OpeningHoursPublicTransportGettingThereParkingDirectionsFeesOpeningHoursSpecification: (Name,Description,DisambiguatingDescription)SpecialOpeningHoursSpecification: (Name,Description,DisambiguatingDescription)
AmenityFeature (via LocationFeatureSpecification)¶
ValueDescription
SkiResort¶
Includes recursive translation of summaries and reports:
- SnowConditions
- SnowConditionsSlope
- SkiLiftSummary
- SkiSlopeSummary
- SnowboardSummary
- CrossCountrySummary
- TobogganingSummary
- HikingSummary
Condition¶
RiskDescriptionWeatherDescription
Tour¶
TitleStartingPointDescriptionSafetyGuidelinesEquipmentTipAdditionalInformationDestinationTrackSignageLiteratureMaps
Event¶
PriceInformationTicketingContactOpeningHours
MediaObject¶
Caption
Product¶
PriceInformation
ProductVariant¶
Name
ProductVariantOption¶
NameValue
ProductPrice¶
PriceCategoryName
API-Level Localization Metadata¶
When accessing objects through the API, several metadata fields are exposed to inform consumers about language availability and translation status:
-
availableLanguage(schema.org/availableLanguageonTouristAttraction)
A list of 2-letter ISO codes (e.g.,en,de,it, ...) indicating the languages spoken at the attraction. -
availableDataLanguage
A list of ISO 2-letter codes specifying the languages that the data for this object is available in. This is calculated automatically during publishing. -
autoTranslatedData(boolean)
Indicates whether the object contains automatically translated content.
Localization in the API¶
The API supports localized responses using the Accept-Language HTTP header. When specified, the response includes only the properties in the requested language. This ensures efficient delivery of language-specific content without requiring consumers to filter properties manually.
The API always returns localized responses. The language is determined by the Accept-Language HTTP header. When this header is provided, the response includes only the properties in the requested language, ensuring efficient delivery of language-specific content without requiring consumers to filter properties manually.
If no Accept-Language header is specified, the API defaults to German (de).
Contact and Feedback¶
If you have suggestions for additional fields or object types to include in the translation logic, or if your organization requires support for new languages, feel free to contact our team. We're happy to collaborate on extending the capabilities of our translation system.