Hello,
This never occured before. I suspect this has something to do with formatting I got from my client.
What shall I to not to get each segment split into several translation suggestions like this one. PIC 2 This text is impossible to work with.
Here is the full tag text PIC 1.
Please, help!
I have made a rule for xlf files to make TS read tags as "inline" but it wont help. I think I need a professional technical help from the support. Is it possible to make a case to get help?
Support Team 
Hi Paul If you scroll up the screen, so you will see it.
Hmnn... show me where I can see the XLIFF itself and not just screenshots of what it looks like in Trados Studio? If you want some help you need to make this easy!
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
Im sorry. I misunderstood. Do you mean this one?
ok - a pretty horrible use of XLIFF. I think the best way for you to handle this file given there seems to be no target elements populated is this.
First, open the source xlf files, copy all source to target and immediately save the target file. This will get you something like this:
Translate
<?xml version="1.0" encoding="UTF-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:ispring="ispringsolutions.com/custom-xliff" version="1.2">
<file datatype="x-is-ispring-presentation" ispring:id="presentation:{DUMMY-ID}" original="presentation" source-language="nb">
<body>
<group id="presentation.slides">
<group id="slide1">
<group id="slide1.shapes">
<group id="slide1.shapes.textbox1">
<trans-unit id="slide1.shapes.textbox1.text">
<source>
<g ctype="x-is-par" id="p0">
<g ctype="x-is-run" id="p0_r0" ispringstart-data="d0">Leksjon 1 - Innledning</g>
</g>
<g ctype="x-is-par" id="p1">
<g ctype="x-is-run" id="p1_r0" ispringstart-data="d1">Leksjon 2 - Lover og forskrifter</g>
</g>
<g ctype="x-is-par" id="p2">
<g ctype="x-is-run" id="p2_r0" ispringstart-data="d2">Leksjon 3 - Arbeidsmiljø, ansvar og konsekvenser</g>
</g>
<g ctype="x-is-par" id="p3">
<g ctype="x-is-run" id="p3_r0" ispringstart-data="d3">Leksjon 4 - Ytre miljø - Miljøvern</g>
</g>
<g ctype="x-is-par" id="p4">
<g ctype="x-is-run" id="p4_r0" ispringstart-data="d4">Leksjon 5 - Sikkerhetsbestemmelser arbeidsutstyr</g>
</g>
<g ctype="x-is-par" id="p5">
<g ctype="x-is-run" id="p5_r0" ispringstart-data="d5">Leksjon 6 - Farlig gods</g>
</g>
</source>
<target state="new">
<g ctype="x-is-par" id="p0">
<g ctype="x-is-run" id="p0_r0" ispringstart-data="d0">Leksjon 1 - Innledning</g>
</g>
<g ctype="x-is-par" id="p1">
<g ctype="x-is-run" id="p1_r0" ispringstart-data="d1">Leksjon 2 - Lover og forskrifter</g>
</g>
<g ctype="x-is-par" id="p2">
<g ctype="x-is-run" id="p2_r0" ispringstart-data="d2">Leksjon 3 - Arbeidsmiljø, ansvar og konsekvenser</g>
</g>
<g ctype="x-is-par" id="p3">
<g ctype="x-is-run" id="p3_r0" ispringstart-data="d3">Leksjon 4 - Ytre miljø - Miljøvern</g>
</g>
<g ctype="x-is-par" id="p4">
<g ctype="x-is-run" id="p4_r0" ispringstart-data="d4">Leksjon 5 - Sikkerhetsbestemmelser arbeidsutstyr</g>
</g>
<g ctype="x-is-par" id="p5">
<g ctype="x-is-run" id="p5_r0" ispringstart-data="d5">Leksjon 6 - Farlig gods</g>
</g>
</target>
</trans-unit>
</group>
</group>
</group>
</group>
</body>
</file>
</xliff>
Now create a custom XML filetype like the attached: emi.zip
That has two rules:
1. only extract the target translation
2. don't extract anything at all
That should get you this which should be easier to handle:
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 - a pretty horrible use of XLIFF. I think the best way for you to handle this file given there seems to be no target elements populated is this.
First, open the source xlf files, copy all source to target and immediately save the target file. This will get you something like this:
<?xml version="1.0" encoding="UTF-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:ispring="ispringsolutions.com/custom-xliff" version="1.2">
<file datatype="x-is-ispring-presentation" ispring:id="presentation:{DUMMY-ID}" original="presentation" source-language="nb">
<body>
<group id="presentation.slides">
<group id="slide1">
<group id="slide1.shapes">
<group id="slide1.shapes.textbox1">
<trans-unit id="slide1.shapes.textbox1.text">
<source>
<g ctype="x-is-par" id="p0">
<g ctype="x-is-run" id="p0_r0" ispringstart-data="d0">Leksjon 1 - Innledning</g>
</g>
<g ctype="x-is-par" id="p1">
<g ctype="x-is-run" id="p1_r0" ispringstart-data="d1">Leksjon 2 - Lover og forskrifter</g>
</g>
<g ctype="x-is-par" id="p2">
<g ctype="x-is-run" id="p2_r0" ispringstart-data="d2">Leksjon 3 - Arbeidsmiljø, ansvar og konsekvenser</g>
</g>
<g ctype="x-is-par" id="p3">
<g ctype="x-is-run" id="p3_r0" ispringstart-data="d3">Leksjon 4 - Ytre miljø - Miljøvern</g>
</g>
<g ctype="x-is-par" id="p4">
<g ctype="x-is-run" id="p4_r0" ispringstart-data="d4">Leksjon 5 - Sikkerhetsbestemmelser arbeidsutstyr</g>
</g>
<g ctype="x-is-par" id="p5">
<g ctype="x-is-run" id="p5_r0" ispringstart-data="d5">Leksjon 6 - Farlig gods</g>
</g>
</source>
<target state="new">
<g ctype="x-is-par" id="p0">
<g ctype="x-is-run" id="p0_r0" ispringstart-data="d0">Leksjon 1 - Innledning</g>
</g>
<g ctype="x-is-par" id="p1">
<g ctype="x-is-run" id="p1_r0" ispringstart-data="d1">Leksjon 2 - Lover og forskrifter</g>
</g>
<g ctype="x-is-par" id="p2">
<g ctype="x-is-run" id="p2_r0" ispringstart-data="d2">Leksjon 3 - Arbeidsmiljø, ansvar og konsekvenser</g>
</g>
<g ctype="x-is-par" id="p3">
<g ctype="x-is-run" id="p3_r0" ispringstart-data="d3">Leksjon 4 - Ytre miljø - Miljøvern</g>
</g>
<g ctype="x-is-par" id="p4">
<g ctype="x-is-run" id="p4_r0" ispringstart-data="d4">Leksjon 5 - Sikkerhetsbestemmelser arbeidsutstyr</g>
</g>
<g ctype="x-is-par" id="p5">
<g ctype="x-is-run" id="p5_r0" ispringstart-data="d5">Leksjon 6 - Farlig gods</g>
</g>
</target>
</trans-unit>
</group>
</group>
</group>
</group>
</body>
</file>
</xliff>
Now create a custom XML filetype like the attached: emi.zip
That has two rules:
1. only extract the target translation
2. don't extract anything at all
That should get you this which should be easier to handle:
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
Oh yes, I forgot to mention, you need to translate the new xlf files you have that contain both source and target, not the original as that will get you this:
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 so far. Iwill try and come back later.
In case it's interesting... and because I come across these problems quite often... I also created some AI generated Python scripts to automate this so you don't need to open in Studio, copy source to target etc. The scripts will prepare the files for you:
https://github.com/paulfilkin/Python-scripts/tree/main/iSpring-style%20XLIFF
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
Im back. Your solution works! But I have probbably used the wrong file. Should I use the file that I saved after applying All source to target ? or have i misundestood. What I see now is this: There is only one problem now, that all the segments that were locked by the clients are open and have status "not translated" and it is very frustrating as half of the document were locked segments. You can see one on the screen shot here. 
Thats fantastic!
.xlf? not xml? I changed the file extension to xml. Im a bit confused here. Which file I should use?
The settings file I gave you uses .xlf so there is no need to change the extension to .xml.
There is only one problem now, that all the segments that were locked by the clients are open and have status "not translated" and it is very frustrating as half of the document were locked segments.
This is why not providing a sensible test file leaves you with answers that may not be appropriate because we have to guess what you're working with!
If you provide a test file that includes examples of the different scenarios you are working with I'll be happy to help. But I'm not guessing any 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
Of course I can provide the files, but I dont know how. The file is huge.
I don’t need the whole file. Copy it, open in a text editor and then delete all the TUs apart from some examples of the parts that are causing you problems. I imagine a file with only half a dozen TUs in it would probably do it. But you need to identify which are the appropriate bits.
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
Sorry for late reply...
I have managed to fix it today. I have inserted a rule to exclude metadata from the editor and now it is not showing. Thank you for your help so far! Have a nice day.