Hello everyone,
I'm receiving a lot of XLF files these days and would like to know if there is a way of modifying the tag definition rules as we would do with a regular XML, or if maybe there's another way.
I need to set as inline tags some expressions like these that Studio currently treats as regular text:
<[[text_to_be_blocked]]>
{{text_to_be_blocked}}
Thank you very much in advance,
Berta
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
I strongly doubt that this will ever be changed. You are basically barking the wrong tree.
The main point here is that the Drupal so-called XLIFFs are notoriously known to be a COMPLETE CRAP, which hardly has anything else in common with XLIFF than the file extension.
The people who created the so-called XLIFF export in Drupal apparently had absolutely no idea about the XLIFF format and how it works...
What they do is that they basically just enclose the COMPLETE HTML code in <source> element and put it in a file with XLIFF extension :-(. This is of course totally wrong. It's very similar to a changing a Word file extension to AVI and pronouncing it a videoclip... :-\
So, the problem lies on the Drupal side. THEY produce crippled format. It's NOT XLIFF.
EDIT: Attaching a sample "XLIFF" just exported from Drupal 8 - it's a complete joke :(
EDIT2: Another sample saved with Drupal's "Extended XLIFF processing" option turned on. Result - file is crippled even more :(.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
For duplicating text use Studio. The easiest and fastest way. Just open the file as single file project or create a project with all files. The language direction must fit. If creating a single-file project, open the file and copy all source to target. In a project let this be done in a pretranslation task (without a TM). Now your file(s) are bilingual in Studio. Go to project settings, select the File types, XLIFF file type and activate the option "Do not store segmentation in translated file"
Then save the file(s) as target. This way you will have bilingual XLIFF files.
In Studio create a new file type XML (embedded content).
Give it a decent name, also name the file type identifier. In the next step chose "Create on default settings". Add the xpath parser rule //* NOT translatable, then add //target as always translatable, and in the line "Structure info" go to Edit, click on top and select "Paragraph". Next step add "xliff" as a root element.
This way your file type will be ready. When you confirm it, go to Embedded content and select HTML 5... for "paragraph" - this should do the trick.
We (Loctimize) can also create the file type for you, if you wish. To have it done, send the file(s) to support at loctimize dot com.
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Translate
