Detecting language please wait for.......
Could you advise me on how to handle in Studio XLF files created by DocFactory CMS?
It's basically a standatd XLIFF 2.0 files type, but they just added a few extra attributes and tags to it for their own purposes, but they're outside the scope of translation.
Studio throws an error when importing these xliff files (An element named 'X' is an invalid child for the File element). How can I change the filetype definition of XLIFF 2.0 to allow these extra elements?
Before we start wondering what we might need to contemplate changing, any chance we can see a sample file rather than the specification?
Hi Paul, sure, find attached a sample file. Studio has a problem with the <mda:metaGroup> tag, I think.0017_wiring.zip
Hi Krisztian Sinko
The problem is not any extra tags or attributes. The problem is the file has been constructed in an invalid way. Here's a corrected version:
Correct these two things and the file is fine, but it has to be changed in the source file, there is no way to do this with the Studio settings because we don't handle invalid files.
Thanks for the explanation, I will go back to the developers of DocFactory to review their xliff export definitions.
Paul said:The language code used is nonsense:srcLang="x-unknown"
Well, not really...
Assuming that the language code follows the RFC 5646 language tag standard, "x-unknown" is perfectly legal code.
See the paragraph starting at the bottom of page 8 of the RFC section 2.2: https://tools.ietf.org/html/rfc5646#section-2.2 and also the following section 2.2.1.
Coincidentally, I was knee-deep into language tags recently, solving puzzles with identifying spoken languages/dialects using language tags...
Perfectly legal, but still nonsense for us. Quite an interesting document through, I've not read that before. Thank you.
Paul said:Perfectly legal, but still nonsense for us.
Yup, can be... Then the application must react user-friendly, i.e. by letting the user to select the source language, for example. Definitely not by throwing an error and refusing to continue (which is the typical developer-ish approach).
Evzen Polenka said:Then the application must react user-friendly, i.e. by letting the user to select the source language, for example. Definitely not by throwing an error and refusing to continue
I completely agree.