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
  • Language Configuration
  • Example:
  • Source Language
  • Target Languages

Language Configuration

PreviousSample Translation ConfigurationNextUsing the Lionbridge Connector (Manual Workflow)

Details on how to upgrade an existing language configuration from the old file format to the new file format can be found in the article .

Language Configuration

Lionbridge and inRiver uses different language codes for each of their languages, and therefor a language configuration file needs to be set up.

The language configuration is part of an xml file that will be used as a setting for the Outbound Connector, if you're running inRiver 6.3, or the Extensions if you are using inRiver PMC.

Example:

I want to translate English (Great Britain) into Swedish and Norwegian.

Considering that scenario, here is a possible language configuration file

<Languages>
    <Language key="engb" lionbridgeCode="en-gb" inRiverCode="en" />
    <Language key="svSE" lionbridgeCode="sv-SE" inRiverCode="sv" />
    <Language key="nbNO" lionbridgeCode="nb-NO" inRiverCode="no" />
</Languages>

The only information we need to know about is the "key", "lionbridgeCode" and "inRiverCode" attribute for each language.

  • key - The CVL value key that also needs to be defined in the source/target language CVL, this is how we locale the language configuration.

  • lionbridgeCode - The language code used by Lionbridge

  • inRiverCode - The language code used by inRiver

An example of how the source and target language CVL's might look like:

Source Language

Key

Value

engb

English

Target Languages

Key

Value

svSE

Swedish

nbNO

Norwegian (Bokmål)

Language Configuration - Upgrading