inRiver Translation Connector
  • Introduction
  • Architecture
  • Workflow
  • Install - inRiver PMC
  • PMC install - inRiver Data Model Configuration
  • Updating Connector - inRiver iPMC
  • Install - inRiver 6.3
  • On-premise (6.3) Install - inRiver Data Model Configuration
  • Translation Configuration
    • Sample Translation Configuration
  • Language Configuration
  • Using the Lionbridge Connector (Manual Workflow)
    • Entity Translation Status
    • Translation Job Status & Actions
    • Linked Entities Translation Status
    • Cancelling Translation Jobs
    • Deleting Translation Jobs
    • Translation of CVL values
    • Translation of Specifications
    • Sending Entity Images for Reference.
    • Sending non-LocaleStrings for Reference
  • Using the Lionbridge Connector (Automatic workflow)
  • Appendix 1: Lionbridge Language List
  • Appendix 2: Troubleshooting
  • Upgrade - 6.3 > PMC
  • Upgrade - 6.3
  • Upgrade - 3.2.2 -> 3.3
    • inRiver 6.3
    • inRiver PMC
  • Language Configuration - Upgrading
  • Logging
  • Criteria Configuration
    • Criterias
  • TLS 1.2
  • Release Notes
Powered by GitBook
On this page
  1. Using the Lionbridge Connector (Manual Workflow)

Sending non-LocaleStrings for Reference

This page details how to send some additional strings for Reference purposes

PreviousSending Entity Images for Reference.NextUsing the Lionbridge Connector (Automatic workflow)

Last updated 5 years ago

Localizable content

By Default the Connector will only send an exported xml file in a Translation Job that contains localizable fields. These are the fields designated as "LocaleString" in the PIM Model.

If you would like to send strings that are not limited to "LocaleString" in the exported file in a Translation Job to provide more reference for the Translators to understand better the context of strings that may normally be sent out in isloation, you can update the Setting of Key "SendOnlyTranslatableData" from "TRUE" to FALSE" as shown below.

In your Control Center, navigate to the Lionbridge Extensions. Edit the Key "SendOnlyTranslatableData" to sat "FALSE" and Save.

Do this for each Lionbridge Extension and then restart Services.