• State Verified Answer
  • Replies 4 replies
  • Subscribers 431 subscribers
  • Views 2352 views
  • Users 0 members are here
Options
Related

Studio 2015 SR2, QA check warnings

Shyam Gupta

hallo,

I am using studio 2015 SR2 and trying to translate from German (DE) to English (GB).

I am using a "DE -->EN" Termbase and also a "DE --> EN" TM.

The source file is an ".xlf" file and also the output (saved file) is a ",xlf" file. 

All is running well except ha see two warnings from the QA3.0 as follows:

Warning 1: " The language abbreviation 'en' given in the output language file is not fully qualified for the target language"

Warning 2: " The language abbreviation 'en' given in the output language file is not fully qualified for the target language (under usage  of 'de - DE')

Please note the english text of warnings above may not have be 100% correct (Original warning text was in German).

Actually, name of the output file is created by Studio itself. If there is something inappropriate as the warning is, why is it created like this in the first place?

I believe the problem might be in the naming of TB and/or TM files.  Just in case they matters, the names are:

Termbase: 160510 xxx-DE-EN_final

Translation Memory: 160512 xxx TM DE-EN(GB)

Could someone guide me towards avoiding these warnings please.

Thanks for your support in advance

Best regards

Shyam Gupta
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    I think the problem is, that the program expects something like en-GB or en-US as target language code in the XLF file, while the source has had just en. You can easily check that using Notepad++

    _________________________________________________________

    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.

  • 0 in reply to Jerzy Czopik
    Hi Jerzy,
    Thanks a lot for very quick response. In fact I have to translate 5 such files from the same customer. When I translated the first two files there was no QA warning. The warnings came with the 3rd and the 4th file.

    As you suggested, I opened the files in Notepad and found that they are absolutely identical. For your ref. here is a short excerpt from the file with few lines from the top - showing upto "source language" and target language"..

    <?xml version="1.0" encoding="UTF-8"?>
    <xliff
    version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:xsi="www.w3.org/.../XMLSchema-instance"
    xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2-strict.xsd" xmlns:MadCap="www.madcapsoftware.com/.../MadCap.xsd">
    <file
    xml:space="preserve"
    original="TitelseiteILS.htm"
    source-language="de"
    MadCap:file-filter=""
    datatype="xhtml"
    target-language="en">
    <header>

    If the files have the same structure and two are showing warnings but the other two do not - would lead me to believe that the QA 3.0 settings for these files must be different.

    I'll check that. But in case you can read something else in the file excerpt above, please do let me know. And in case if the changes were to be made, where and what could those possibly be?

    Thanks for your support again.
    Best regards
    Shyam
  • 0 in reply to Shyam Gupta
    There is probably no need to change anything here. This is most likely information to tell you that the language pairs are not recognised properly by Studio.
    Can you still translate them and can you save the target file? If you can then don't worry about it. It's only verification as for some companies it's important to have this check on the source files because they always want them to be correctly identified with the full language code.

    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

  • 0 in reply to Paul
    The file looks like it would come from MadCap. It is worth nothing to say, that you can also translate these files directly and not via XLF. The other part of the answer has already been given by Paul (thank you :))

    _________________________________________________________

    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.