Started Attempt To Download !LINK! Xliff File. The Process Did Not Finish

0 views

Skip to first unread message

Vallie Kleinert

unread,

Jan 20, 2024, 6:07:36 AM1/20/24

to fellenagon

STF Export: First export your metadata in STF files. This article doesn't cover XLIF files because of this known issue since the time I started on translations which is last October. See Salesforce known issues: _view?id=a1p3A000000mCg3QAE&title=translation-workbench-export-as-xliff-fails

It took me a while to figure out what was going wrong with my file format and in general this entire process and how important it is to not mess with the STF file. It is a learning process and I hope this will be useful for those who need to do this translation process.

started attempt to download xliff file. the process did not finish

Download ✺✺✺ https://t.co/vteRKZXbdL

yeah there appears to be a lot missing from the orginalData section in that segment - do you happen to have the original file that was sent to the translator - it might be that the translator's processes removed them :( (i don't think the copy of to changes that bit of the file.

The quickest way to translate a lot of text is still using the XLIFF file. Because this is an international standard, an XLIFF file can be handled by any translation service. An XLIFF file is always built the same way: a header and a body. The first part of the header shows some information about the file, the original application, and the translation target application. Because this is commented, it will not be used by a processing application.

The state of software and documentation localisation before XLIFF was that a software or documentation provider delivered their localisable resources to a localisation service provider in a number of disparate file formats. Once software providers and technical communicators commenced implementing XLIFF, the task of interchanging localisation data was simplified. Using proprietary and/or non-standard resource formats force either the source provider or the localisation service provider to implement costly and inefficient pre-processing of localisable content. For publishers with many proprietary or non-standard formats, this requirement becomes a major hurdle when attempting to localise their software. For software developers and technical communicators employing enterprise localisation tools and processes, XLIFF defines a standard but extensible vocabulary that captures relevant metadata for any point in the lifecycle which can be exchanged between a variety of commercial and open-source tools.