I have an issue when working with xml files that contain emojis (for example the lighbulb emoji). After the file is imported, the emoji is completely lost from Trados and does not appear again after the translation is exported. I can see this subject was opened in the past, but I had the impression it was fixed for Trados 2021. Is this still a problem that cannot be solved?
Thank you in advance.
Please provide a small sample XML so we can test it?
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
Hello Paul,
Thank you for replying. I am sending a sample attached.
<?xml version="1.0"?> <xliff xmlns="urn:oasis:names:tc:xliff:document:2.0" version="2.0" srcLang="en-GB"> <file id="Text for translation"> <group id="header"> <unit id="title"> <notes> <note>The title</note> </notes> <segment> <source>Text for translation</source> </segment> </unit> <unit id="description"> <notes> <note>The description</note> </notes> <segment> <source>Text for translation 💡Text for translation</source> </segment> </unit> <unit id="keywords"> <notes> <note>The keywords</note> </notes> <segment> <source></source> </segment> </unit> </group> <group id="steps"> <unit id="s1" name="72726109-304d-4855-8526-53c513422498"> <segment> <source>Text for translation.</source> </segment> </unit> <unit id="s2" name="bb9a227c-377b-4f11-b4d8-0bc60fbea6f6"> <segment> <source>Text for translation. Text for translation. Text for translation.</source> </segment> </unit> <unit id="s3" name="06aebbf5-7044-4c2a-b090-eb14d9eba117"> <segment> <source>Text for translation.</source> </segment> </unit> <unit id="s4" name="60e71273-f36d-490b-91c9-a9c3ac444fde"> <segment> <source>Text for translation. Text for translation.</source> </segment> </unit> </group> <group id="ingredients"> <unit id="i1" translate="no" name="461ba80e-f4a9-49e0-a62d-07941fe058c3"> <segment id="singular"> <source>Text for translation</source> </segment> <segment id="plural"> <source>Text for translation</source> </segment> </unit> <unit id="i2" translate="no" name="020cc78b-031f-4ec1-b951-b980939e8889"> <segment id="singular"> <source>Text for translation</source> </segment> <segment id="plural"> <source>Text for translation</source> </segment> </unit> <unit id="i3" translate="no" name="bcb752e1-e5bf-484a-9dea-1c45a98a68db"> <segment id="singular"> <source>Text for translation</source> </segment> <segment id="plural"> <source>Text for translation</source> </segment> </unit> <unit id="i4" translate="no" name="52644ec8-f4f4-4824-91c1-bb9a70ff1227"> <segment id="singular"> <source>Text for translation</source> </segment> <segment id="plural"> <source>Text for translation</source> </segment> </unit> <unit id="i5" translate="no" name="c6b09784-46ab-45c2-b9c0-f10bb37dba70"> <segment id="singular"> <source>Text for translation</source> </segment> <segment id="plural"> <source>Text for translation</source> </segment> </unit> <unit id="i6" translate="no" name="c4f9717d-e978-481e-9c89-2f7b2b2ad098"> <segment id="singular"> <source>Text for translation</source> </segment> <segment id="plural"> <source>Text for translation</source> </segment> </unit> <unit id="i7" translate="no" name="0ba9f73b-8dcb-429a-804f-594185c47414"> <segment id="singular"> <source>Text for translation</source> </segment> <segment id="plural"> <source>Text for translation</source> </segment> </unit> <unit id="i8" translate="no" name="5293aff4-be32-4137-9ad1-c98e016f25fc"> <segment id="singular"> <source>Text for translation</source> </segment> <segment id="plural"> <source>Text for translation</source> </segment> </unit> </group> </file> </xliff>
We have the template saved locally and we apply it every time we set up a project. I tried to use the editing function to see the makings of the template (from the same place as you screenshoted above), but I cannot know which specific settings are applied. For example, if I go under File types, I don't even know what type of files the template refers to, if any settings need to be applied under the SDL xliff file type, or XML file type (and there are 10 XML file types to choose from). In short, I have the impression that the template is really complex because it knows precisely which segments to lock and which segments are translateble content and which ones are not, and I cannot see that sort of setting anywhere in this template. I'm sorry if this is ignorant, but our main tool is memoQ, so maybe we're just lost.
so maybe we're just lost.
Maybe... if you preview the file in Studio using that template you will see this:
This tells you exactly what filetype is being used as I already pointed out. If you look at that filetype you will see there are no changes to the default at all other than to make sure your file, that has an XML extension is handled by the XLIFF 2.0 filetype. You can see that here:
Perhaps you can also share another screenshot as you cut off the orange tabs at the top which could have been helpful, to show what filetype was used to open the file in your example. Press Ctrl+Alt+D a few times until you see the filetype used:
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
Thank you for all the info. I created a new template in Trados 2021 from scratch where the only thing I defined is the xliff 2.0. file type and the language pair. When I improted the test file, the emoji is still not there. The filetype at the top is xliff 2.0. It has to be xliff and not XML because we need a bilingual XML file at the end, containing both source and target.
What version of 2021 are you using? The current version is Trados Studio 2021 - 16.2.12.9338 and MultiTerm 2021 - 16.2.1.1044
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
We are using Trados 2021 SR1 - 16.1.8.4404
We are using Trados 2021 SR1 - 16.1.8.4404
ok... in your first post you said:
I had the impression it was fixed for Trados 2021
The current version is: Trados Studio 2021 - 16.2.12.9338
So this is SR2. I suggest you upgrade and try again. It won't cost anything.
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
Thank you for the suggestion, I managed to upgrade Trados and the template seems to work as far as emojis go :) but I noticed the segmentation is now wrong. The XML is divided into steps, and each step needs to be in a separate segment, but with the new template, each sentence is in a new step. Do you have an idea where this is defined in the template?
This is the correct segmentation from Trados 2017
And this is the wrong one from Trados 2021
I found some additional info on how the original template was set up if that helps at all:
Filetypes:
XML Any: File dialog wildcard expression needs to be set to *.doc
XLIFF 2.0.: File dialog wildcard expression needs to be set to *.xml;*.xlf;*.xliff
Text: Common: Unicode UTF-8 (...) select "Remove if present"
I recreated all of this in the new template and the segmentation is still wrong.
In 2021 with your template I see this:
Frankly I think we're wasting time here because I don't trust what you're showing me as the result of using that template in the current version of 2017 and because I think 2021 is handling this as it should be handled. I don't believe the template has anything to do with the segmentation of this file at all. What you are seeing in the behaviour of the out of the box filetype.
I think you must have been using a TM with paragraph segmentation to force the filetype to segment based on the paragraph units. So I created a TM like that, added it and now I see this:
Seems a stupid way to handle the file, but I do believe this is what you were doing.
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 agree it is stupid but it needs to be handled that way. I applied a language resource template with paragraph segmentation and that solves this issue, so thank you.
But I just noticed another thing occured that does not happen in our previous Trados. The title and the body of the text in the XML file attached get smooshed into one segment (even without paragraph segmentation) Do you have an idea how to work around this (even if we have to sacrifice paragraph segmentation)? Let me know if you would like me to start a new thread for this.
<?xml version="1.0"?> <xliff xmlns="urn:oasis:names:tc:xliff:document:2.0" version="2.0" srcLang="en-GB"> <file id="MT-E3AD2ADB"> <group id="header"> <unit id="title"> <notes> <note>The title</note> </notes> <segment> <source>Title</source> </segment> </unit> <unit id="description"> <notes> <note>The description</note> </notes> <segment> <source>Text for translation</source> </segment> </unit> </group> <group id="steps"> <unit id="s1" name="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"> <segment id="title"> <source>Title</source> </segment> <segment id="description"> <source>Text for translation. Text for translation. </source> </segment> </unit> <unit id="s2" name="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"> <segment id="title"> <source>Title</source> </segment> <segment id="description"> <source>Text for translation. Text for translation. </source> </segment> </unit> <unit id="s3" name="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"> <segment id="title"> <source>Title</source> </segment> <segment id="description"> <source>Text for translation. Text for translation. </source> </segment> </unit> <unit id="s4" name="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"> <segment id="title"> <source>Title?</source> </segment> <segment id="description"> <source>Text for translation. </source> </segment> </unit> </group> </file> </xliff>
I agree it is stupid but it needs to be handled that way. I applied a language resource template with paragraph segmentation and that solves this issue, so thank you.
But I just noticed another thing occured that does not happen in our previous Trados. The title and the body of the text in the XML file attached get smooshed into one segment (even without paragraph segmentation) Do you have an idea how to work around this (even if we have to sacrifice paragraph segmentation)? Let me know if you would like me to start a new thread for this.
<?xml version="1.0"?> <xliff xmlns="urn:oasis:names:tc:xliff:document:2.0" version="2.0" srcLang="en-GB"> <file id="MT-E3AD2ADB"> <group id="header"> <unit id="title"> <notes> <note>The title</note> </notes> <segment> <source>Title</source> </segment> </unit> <unit id="description"> <notes> <note>The description</note> </notes> <segment> <source>Text for translation</source> </segment> </unit> </group> <group id="steps"> <unit id="s1" name="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"> <segment id="title"> <source>Title</source> </segment> <segment id="description"> <source>Text for translation. Text for translation. </source> </segment> </unit> <unit id="s2" name="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"> <segment id="title"> <source>Title</source> </segment> <segment id="description"> <source>Text for translation. Text for translation. </source> </segment> </unit> <unit id="s3" name="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"> <segment id="title"> <source>Title</source> </segment> <segment id="description"> <source>Text for translation. Text for translation. </source> </segment> </unit> <unit id="s4" name="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"> <segment id="title"> <source>Title?</source> </segment> <segment id="description"> <source>Text for translation. </source> </segment> </unit> </group> </file> </xliff>
Yes, please can you post this question as a new thread. It is a different topic altogether.
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
Ok, thank you for all your help!
Translate
