Localization, Content, Context, XLIFF, and Images - Automating Translations

Related products: PX Engagements

Our team uses the localization features quite frequently for 4 of our flagship solutions. The Gainsight PX (GPX) product team (thank you @aharkut) has made some tremendous strides with these features in the six months or so alone. 

 

Tools:

Between the GPX localization features for articles, k-bots, and engagements and the localization management platform we use (Crowdin), we have a nearly fully automated process.

Challenge:

With continued edits and updates to content for visual acuity, we run into a number of unique formatting challenges that require HTML code review. This ends up costing us nearly an hour to update and sync each engagement/article each time we need to make edits in English. Add this up to the hundreds of engagements we create each quarter and the impact grows exponentially.

 

Guides that look nice in the WYSIWYG don’t only look great in the XLIFF file. And because our translators are generally working only with the files, they don’t easily see what the end product should look like. This ends up requiring multiple revisions just to get one or two sentences to look right in multiple languages.

  <unit id="t">
<segment>
<source>T</source>
<target>T</target>
</segment>
</unit>
<unit id="ogenerateresultsfirstselectcriteria">
<segment>
<source>o generate Results, first select criteria. </source>
<target>oder generieren Sie Ergebnisse, nachdem Sie Auswahlkriterien getroffen haben.</target>
</segment>
</unit>
<unit id="chooselocationcriteria">
<segment>
<source>Choose location criteria</source>
<target>Wählen Sie die Standortkriterien</target>
</segment>
</unit>
<unit id="hereunder">
<segment>
<source>here under </source>
<target>hier unter</target>
</segment>
</unit>
<unit id="location">
<segment>
<source>Location</source>
<target>Ort</target>
</segment>
</unit>
<unit id="chooseacitystateorcountry">
<segment>
<source>Choose a city, state or country</source>
<target>Wählen Sie Stadt, Bundesstaat oder Land</target>
</segment>
</unit>
<unit id="afteryouchooseyourcriteriaclickthe">
<segment>
<source>After you choose your criteria, click the </source>
<target>Nachdem Sie Ihre Kriterien ausgewählt haben, klicken Sie auf den</target>
</segment>
</unit>
<unit id="buttonbelow">
<segment>
<source>button below.</source>
<target>Button unten.</target>
</segment>
</unit>
</unit>

Recommended Solution:

  1. Offer a unit-id button for contextual XLIFF files. This would allow the content creator to define the text string unit and would help keep context aligned with text for translators.
  2. Pass thumbnail images with the XLIFF file for translation tools to show the screenshot of the text along with the raw text file.

 

@link_black @jean.nairon @VBennyGainsight @david_streichl @rweimar @gaurav_kotak @tohodesigns @romihache @Molly.McQ @mrooney_trimble @sai_ram @rschlette @jmobley @katkenny23 @woodlande @JayS @Lake1211 @lpicone @aharkut @Katharina @jp_lingamaneni @shireesha_reddy @jean.nairon @kate_green @sreddygari @Susanne 

Be the first to reply!