Under Community Review

Allow forcing/redefining locales in files

Basically an over-ride for the "unknown culture" (can someone also *please* change the wording of that error message?) problem.

It is not uncommon for clients to send files using odd locales (I still get files sent as ga-CA instead of gd-GB) or the client has made a general hash of the locale in a file and is unable or unwilling to fix this. End result, I either have to go through TM contortions, file conversions or content extraction to be able to use the TM. On one occasion, I had a 5k job which was basically ALL 100% matches but I ended up having to manually search for them in the TM because of the "unknown culture" thing.

Studio should offer the translator to option to convert or fake a locale. What I mean with fake is let's say the client sent ga-CA instead of gd-GB but expects ga-CA back, not gd-GB. But my TM/Studio expects gd-GB. I want to be able to tell studio to "treat this file as if the target was gd-GB but do not alter the locale defined in the file". In a sense, I want to be able to tell Studio that for my purposes, treat this "wrong" locale ga-CA as a sublocale of gd-GB. Whether that's ugly or not I don't care, if someone sends me ugly, I have to just somehow get ugly to work :)

Michael Bauer

  • We have similar issues. For example, we often receive .XLF files with "target language = es-LA". Studio does not allow that combination, the closest is "Spanish-Latin America" with code "es-419". Currently, the only workaround for us is to edit each .XLF file to match the "es-419" target language and when we're done to edit the files again to change them back to "es-LA". Studio should be able to identify "unknown" languages and offer a substitution, in line with your suggestion.