XLIFF file connector

The Translations module has this connector setup by default. You can add more than one XLIFF file connector. By default, only the Xliff connector is configured. To create more connectors, perform the following:

  1. Click Administration » Settings » Advanced » Translations » Connectors.
  2. Click Create new.
  3. In Name, enter a name for the connector.
    The name must be unique.
  4. In Title, enter the title that will appear in the UI
    For example, Export to XLIFF file 2
  5. In ConnectorType, enter Telerik.Sitefinity.Translations.Xliff.DefaultXliffConnector
  6. In Supported languages, enter the languages which you want the connector to work with and for which you have an account.
    For example, if you enter en-us -> fr-fr; en-us -> es-es, it means you have account for translation service for US English to French and Spanish.
  7. Select Strip HTML tags, if you want to remove all HTML tags and send for translation text only.
    EXAMPLE: If you have the following paragraph that you want to send for translation:

    <p>This is just a test paragraph with a <a href="#">link</a>,
    a <strong>strong</strong> tag and nothing else.</p>

    • If you have the checkbox selected, which is the default behavior, the following will be sent:
    • If you have the checkbox deselected, the following will be sent:
  8. Save your changes.
    The connector appears under Connectors.
  9. Click the new connector.
  10. Click Parameters and create the parameters with the following keys:
    • splitJobsPerLanguage
      This parameter indicates whether the exported translation files should be split by language or exported into a single file. In Value, enter true or false
    • librariesProviderName
      This is the library provider. In Value, enter the name of your translation library provider.
      The default translations provider in Sitefinity CMS is sf_translations_lib_provider
    • exportLibraryId
      In Value, enter the ID of the library that will hold the exported XLIFF files.
      To use the default Exported Translations library, copy the Value from Administration » Settings » Advanced » Translations » Connectors » Xliff » Paramers » exportLibraryId.
      For more information about using library IDs, see Create document libraries.
    • importLibraryId
      In Value, enter the ID of the library that will hold the XLIFF files for the import.
      To use the default Imported Translations library, copy the Value from Administration » Settings » Advanced » Translations » Connectors » Xliff » Paramers » importLibraryId.
  11. Click Parameters and create a new parameter with Key acknowledgeEveryMessage and Value false
    The default value of this parameter is true. It means that different users, who work with different translation projects with the same connector credentials, can have access to each other's projects and potentially cause conflicts.
    For example, one user can approve the translation of another user in a different project.

    If this use case is applicable to your scenario, you should create this parameter, set its value to false, and save your changes.

  12. Save your changes.

NOTE: If you do not explicitly set the libraries that will store the exported and imported files, you can view and download these files from the User files. To do this, click Administration » User files. You can see folders Exported Translations and Imported Translation.

Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.

Web Security for Sitefinity Administrators

The free standalone Web Security lesson teaches administrators how to protect your websites and Sitefinity instance from external threats. Learn to configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.

Foundations of Sitefinity ASP.NET Core Development

The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.

Was this article helpful?