Aubeline Brandamir 

Aubeline Brandamir said:

Has anyone been able to solve a similar issue?

No.

If you open the XLF file with Notepad or Notepad++, you’ll see in the header the source and target languages. Could you check it is something like this?

source-language="en-GB" target-language="es-ES"

Do the language codes consist of 4 letters plus the hyphen?

If everything seems OK, try downloading the XLF file again from XTM.

Hello Jesús Prieto 

 I have this <file source-language="en-US" target-language="fr-FR" 

so it seems perfectly fine.

I've already tried and downloaded/uploaded the file twice as I thought it could simply be a temporary bug. But same issue.

Aubeline Brandamir 

Can you check these?

1. Inspect the first 3–5 lines of the .xlf and confirm version and namespace.

2. Validate XML well-formedness - make sure it's a complete file.  Easiest way is to load the XLF into here and click validate - https://codebeautify.org/xmlvalidator
   It's report where the problem is... if there is one!

If you paste the first 20 lines of the file here that could also help.

Hi Paul 

here this what you're looking for?

">www.w3.org/.../XMLSchema-instance" xmlns:xtm="urn:xliff-xtm-extensions" version="1.2" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 ">www.xtm-intl.com/.../xliff-core-1.2-transitional.xsd"><file source-language="en-US" target-language="fr-FR" datatype="xml" original="227803c6b5f74b28b9aa26e13bd95611" xtm:xliff-identifier="2852d2422c0f44efb326193f14329c40" product-name="XTM International Limited xml:tm" product-version="2.0" tool="xtm-intl_XLIFF_Extract" xml:space="default" xtm:populate-target-with-source="no"><header><skl><internal-file crc="13a6a4b3">

The validator did find one issue:

Error : InvalidXml
Line : 1
Message : Invalid '[ "xliff", "file", "header", "skl", "internal-file"]' found.

This is strange as it a straight forward export from XTM

Aubeline Brandamir 

These are the 2 lines you should find in your XLF file until the 1.2 version:

<?xml version="1.0" encoding="UTF-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:metrics="urn:lisa-metrics-tags" xmlns:term="urn:xliff-term-extensions" xmlns:xref="urn:xmlintl-xref" xmlns:xsi="">www.w3.org/.../XMLSchema-instance" xmlns:xtm="urn:xliff-xtm-extensions" version="1.2"

I think if you copy this text (or you grab it from any old XLF) to your XLF, it’ll be fine.

Anyway I’m thinking that you may have issues after all: everyting goes well in Trados Studio, you translate it and create the target XLF but XLF may fial to import your target XLF. So I’d first try to Generate again the XLIFF in XTM, download the new version, and check that header is OK this time. 

These see to be my first lines. Sorry, it was complicated in NotePad++ but I can see much better in the validator tool Paul  shared

<?xml version="1.0" encoding="UTF-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:metrics="urn:lisa-metrics-tags" xmlns:term="urn:xliff-term-extensions" xmlns:xref="urn:xmlintl-xref" xmlns:xsi="">www.w3.org/.../XMLSchema-instance" xmlns:xtm="urn:xliff-xtm-extensions" version="1.2" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 ">www.xtm-intl.com/.../xliff-core-1.2-transitional.xsd"><file source-language="en-US" target-language="fr-FR" datatype="xml" original="227803c6b5f74b28b9aa26e13bd95611" xtm:xliff-identifier="2852d2422c0f44efb326193f14329c40" product-name="XTM International Limited xml:tm" product-version="2.0" tool="xtm-intl_XLIFF_Extract" xml:space="default" xtm:populate-target-with-source="no"><header><skl><internal-file crc="13a6a4b3">

Aubeline Brandamir 

That file is invalid.

Required fixes:

1. Bind the namespace. Your file had xmlns:xsi="". Must be xmlns:xsi="">www.w3.org/.../XMLSchema-instance".

2. Make xsi:schemaLocation a valid two-token value.  Yours split the second token outside the attribute:
   xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 ">www.xtm-intl.com/.../xliff-core-1.2-transitional.xsd"
   It must be inside the quotes as a pair:
   xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 ">www.xtm-intl.com/.../xliff-core-1.2-transitional.xsd".

So this will open (although there are no translations in it of course!)

<?xml version="1.0" encoding="UTF-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2"
       xmlns:metrics="urn:lisa-metrics-tags"
       xmlns:term="urn:xliff-term-extensions"
       xmlns:xref="urn:xmlintl-xref"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:xtm="urn:xliff-xtm-extensions"
       version="1.2"
       xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 http://www.xtm-intl.com/.../xliff-core-1.2-transitional.xsd">
  <file source-language="en-US"
        target-language="fr-FR"
        datatype="xml"
        original="227803c6b5f74b28b9aa26e13bd95611"
        xtm:xliff-identifier="2852d2422c0f44efb326193f14329c40"
        product-name="XTM International Limited xml:tm"
        product-version="2.0"
        tool="xtm-intl_XLIFF_Extract"
        xml:space="default"
        xtm:populate-target-with-source="no">
    <header>
      <skl>
        <internal-file crc="13a6a4b3"/>
      </skl>
    </header>
    <body/>
  </file>
</xliff>

Paul 

Thank you.

So you mean : if I replace with this fixed version at the proper place in my xlf file, I'll  have a working file?

I'm sorry if I don't always understand, but I must admit this is getting too complex for me.

 Aubeline Brandamir 

I can only confirm the header as I don’t know what else might be wrong with the file.

If you want to send me the full filel I can take a look for you?

Paul 

Noted.

I sent you the file via DM

Aubeline Brandamir 

Thanks for the file.  I did a bit of work on it and there is no way you will be able to work on this file as it is in Trados Studio.  Aside from the fact that it is invalid XLIFF, even if I fix that this is what you're dealing with in that one file:

Number of groups: 141008

Total translation units: 159152

Translation unit states:

• signed-off: 42,729 (26.8%)
• translated: 89,769 (56.4%)
• unknown: 26,654 (16.7%)

Too large for Trados.  I wanted to test in the cloud as this may have worked, but there are too many problems with the file and I gave up!

What I did manage to do was split the original into 32 files with around 5000 TUs in each one, and ensure they are all valid.  I tested the first and the last... both open ok:





So if you like I can send you all 32 files on the basis you could translate these and then provide a Translation Memory for your client and they can pre-tranlsate in XTM or whatever tool created that file in the first place!

Frankly... I think this is a last resort and you should probably go back to your client and ask them to send you something manageable.

Aubeline Brandamir 

Thanks for the file.  I did a bit of work on it and there is no way you will be able to work on this file as it is in Trados Studio.  Aside from the fact that it is invalid XLIFF, even if I fix that this is what you're dealing with in that one file:

Number of groups: 141008

Total translation units: 159152

Translation unit states:

• signed-off: 42,729 (26.8%)
• translated: 89,769 (56.4%)
• unknown: 26,654 (16.7%)

Too large for Trados.  I wanted to test in the cloud as this may have worked, but there are too many problems with the file and I gave up!

What I did manage to do was split the original into 32 files with around 5000 TUs in each one, and ensure they are all valid.  I tested the first and the last... both open ok:





So if you like I can send you all 32 files on the basis you could translate these and then provide a Translation Memory for your client and they can pre-tranlsate in XTM or whatever tool created that file in the first place!

Frankly... I think this is a last resort and you should probably go back to your client and ask them to send you something manageable.

Thank you so much Paul  for all your efforts on this. I really appreciate your help. 

Yes, please do send me the splitted files and I'll see what I can do.

The client would like me to work in XTM. Not wanting to be un pleasant to that tool, I'll just say I would much rather work in Studio.