Define a Language when Uploading Content - Fluid Topics - 3.4 - Technical Notes

Manage Languages in Fluid Topics

Fluid Topics
Fluid Topics Version
Technical Notes
Target Audience

When uploading a structured or unstructured document, ADMIN and KHUB_ADMIN users can configure the content language.

Attention: Uploading content without defining a language is not recommended.

It is possible to define a content language in the publishing software or in a control file.

Since AFS v7.9, all language codes in Fluid Topics include an ISO 639-1 language designator in lowercase and an ISO 3166-1 region designator in uppercase, for example: en-US, fr-CA, zh-TW, etc.

Tip: The International Organization for Standardization (ISO) maintains a list of official region designators.
Note: The version of the connector used to publish content has an effect on how languages are defined in Fluid Topics.

Connectors with APIs earlier than v2

  • If a user uploads content without defining a content language, the result depends on the publication format:
    • For Author-it documents: Fluid Topics uses the default content language (en-US).
    • Note: If the defaultContentLocale parameter is present in the conf.json configuration file, its value is ignored.
    • For DITA documents: Fluid Topics uses the default content language (en-US).
    • Note: The language extension defined in the DITA map DOCTYPE declaration is not taken into account.
    • For FTML documents: Fluid Topics does not publish FTML documents if no language is defined.
    • For Unstructured Documents: Fluid Topics derives the language from the content of the unstructured document if possible.
  • If a user provides only a language designator without a region designator, Fluid Topics uses a mapping table .
  • If a user provides a language listed in the mapping table, Fluid Topics expands it using the associated language code.
  • If the language is not part of the mapping table, Fluid Topics falls back to the default content language.
  • Connectors with API v2

    Defining a content language is mandatory with API v2.