Localization String Order

Related products: PX Engagements

Does anyone know how a localization file is ordered? I have used SRT files and XLIFF files in other platforms and the strings tend to be broken up in a pretty logical manner. However, when I export the XLIFF from a dialog, guide, or K-Bot, none of the strings make sense and are broken up and split all over the file. This is really frustrating my translators. 

 

<?xml version="1.0" encoding="UTF-8"?>
<xliff srcLang="en" trgLang="de" version="2.0"
xmlns="urn:oasis:names:tc:xliff:document:2.0" xmlns:mda="urn:oasis:names:tc:xliff:metadata:2.0">
<file id="1">
<mda:metadata>
<mda:metaGroup category="gainsight_attributes">
<mda:meta type="engagementId">4da76341-9da8-4173-86c0-1f1a24b8c2fa</mda:meta>
</mda:metaGroup>
</mda:metadata>
<unit id="clearingyourbrowsercachepleasecontactcustomerservice">
<segment>
<source>clearing your browser cache, please contact Customer Service. </source>
</segment>
</unit>
<unit id="automatingportfoliooptimizationatrenewal">
<segment>
<source>Automating Portfolio Optimization at Renewal</source>
</segment>
</unit>
<unit id="fridaymayth">
<segment>
<source>Friday, May 20th</source>
</segment>
</unit>
<unit id="ontheeveningof">
<segment>
<source>On the evening of </source>
</segment>
</unit>
<unit id="viewfullreleasenotes">
<segment>
<source> View Full Release Notes </source>
</segment>
</unit>
<unit id="thefirst">
<segment>
<source> the first </source>
</segment>
</unit>
<unit id="dbfinanceanalyticscreditintelligencewillbeupdatedwiththefollowingimprovements">
<segment>
<source>, D&B Finance Analytics Credit Intelligence will be updated with the following improvements: </source>
</segment>
</unit>
<unit id="fixesforcustomerreportedissuesandotherminorimprovements">
<segment>
<source>Fixes for customer reported issues and other minor improvements</source>
</segment>
</unit>
<unit id="pleasenoteaftereachreleaseyoumayneedto">
<segment>
<source>Please note, after each release, you may need to </source>
</segment>
</unit>
<unit id="schedulingdataimportsexportsforportfolioinsightcustomers">
<segment>
<source>Scheduling Data Imports &amp; Exports for Portfolio Insight customers</source>
</segment>
</unit>
<unit id="singlesignonssoavailableglobally">
<segment>
<source>Single Sign-On (SSO) Available Globally</source>
</segment>
</unit>
<unit id="debtenforcementextractforswitzerland">
<segment>
<source>Debt Enforcement Extract for Switzerland</source>
</segment>
</unit>
<unit id="dunsregisteredsealintegration">
<segment>
<source>D-U-N-S Registered Seal Integration</source>
</segment>
</unit>
<unit id="sslcertificateupdate">
<segment>
<source>SSL Certificate Update </source>
</segment>
</unit>
<unit id="youlogintoensureproperfunctionalityifyoucontinuehavingdifficultiesafter">
<segment>
<source>you log in to ensure proper functionality. If you continue having difficulties after </source>
</segment>
</unit>
<unit id="clearyourbrowsercache">
<segment>
<source>clear your browser cache</source>
</segment>
</unit>
<unit id="time">
<segment>
<source>time </source>
</segment>
</unit>
</file>
</xliff>

 

@aharkut could you pl check this?


Hi @JPKelliher ,

This is a known issue - and we are working on priority to fix this. Very soon, the XLIFF files generated will have the content in order.

 

Thanks,

Abhilash


No StatusPlanned

@JPKelliher the order of XLIFF in Contextual formats has been fixed in November 2022. Please check the release notes.

 

https://support.gainsight.com/PX/Release_Notes/2022/01_PX_Release_Notes_November_2022#Engagement_Localization

 

Thanks


PlannedImplemented