Hey, PX team!
Localization is a crucial business function for our company, however, we’ve been running into a significant challenge when it comes to the XLIFF files exported from our engagements in PX. Not only do these files often contain unnecessary HTML clutter, but it also breaks up text strings if there’s different font formatting (bold, italic, etc) - making it difficult for our team of localizers to work efficiently.
We believe there are a few ways that can improve this:
@JPKelliher has recently suggested something that our team strongly agrees would improve localization workflow since it would give context to our localizers. This is the suggestion: “Pass thumbnail images with the XLIFF file for translation tools to show the screenshot of the text along with the raw text file.”- In addition, we are currently using the CrowdIn plugin for automating the process, yet the XLIFF files are either loaded with broken strings mid-sentence, or are full of clutter. If the file was set up in a cleaner way that ultimately doesn’t generate confusion to the localizers and/or significantly delay their workflow, it would really help our processes.
We hope and appreciate your time considering this improvement, as it would greatly benefit our localization efforts.