• State Suggested Answer
  • Replies 6 replies
  • Answers 3 answers
  • Subscribers 432 subscribers
  • Views 2328 views
  • Users 0 members are here
Options
Related

File Extension Repeated_Question

Zeena Faulk

Hi,

We have been using SDL Professional 2017 to do a lot of translations in three major languages. Recently, my colleague run into what is probably considered a minor issue, but it is annoying considering the pressure of deadlines. When the target file is generated, it comes out as having two extensions at the end of the file name instead of one (one extension seems to reflect that of the source file and the second; the bilingual file). Please take a quick look and let me know if you have any thoughts. Many thanks in advance for your input. 

 

 
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi ,

    Your screenshot is a little bit confusing. Are you getting one file or two? Did you just remove the SDLXLIFF part of the extension from the second one in your screenshot?

    Was the source file for this translation an SDLXLIFF? I have a suspicion that it was based on the file name and if this is the case then the extension is only SDLXLIFF. The XML part would just be a reference to the original source file that was used to create the SDLXLIFF. If you did remove it to get the second file with the XML extension then just open both files with the text editor and they will be exactly the same… obviously.

    So unless I've completely misunderstood you I don't think there is a problem here.

    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
    Thank you, Paul, for the prompt response.

    This is an issue that one of my colleagues in our team faces, and we wanted the issue to be reported on her part. To answer your first question, it is one file that is generated from an xml Source Text. So, the target text comes out carrying the same name as the Source, obviously, but the extension is .xml._en-US_es-ES.xml. When the target text is returned to the management system, the plug-in fails because the management system does not recognize the additions to its original name.

    The Source text is not an SDLXLIFF. Thank you, again and I appreciate your time.
    Zeena
  • 0 in reply to Zeena Faulk
    Hi ,

    Okay, I think I'm a little clearer on what you mean now. But I am confused on how this could happen. If you create a single file project then the language codes are added to the SDLXLIFF, but when you save the target file the name should be the same as the original file. Can you ask your colleague to provide a step-by-step guide to how the file is being loaded into studio and how the target files are saved? And we can try to reproduce it and figure out what's going on.

    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
    Hi, Paul,

    Thank you for the response above and for your patience while I was getting the step-by-step guide from my colleague. Here is the details that my colleague followed in translating the assignment:

    • The original (English) file was not an SDLXLIFF file, it was sent and received as an xml file
    • I imported it into SDL by dragging it into the SDL screen when prompted
    • I had no problems opening and working with it
    • I made sure that all paragraphs were checked off

    When I saved it after I finished:
    • I used the “Save” icon that appears on the upper left hand
    • When I open the translation I finished last, it appears, in Trados, as:
    o 3b82b64c-31be-4a53-b2c6-b20fb05e8255-1510154149170.xml_en-US_es-419.sdlxliff [Translation]
    So it already has a double extension!

    How I tried to save it to be an xml (and not an SDLXLIFF):
    • Home/Batch Tasks/Generate Target Translations/Next/(went into Batch Processing)/Finish

    • System declared it done with 0 errors, 0 warnings

    And this is how the latest file I translated appears in my folder on the desktop, after I saved it as detailed above:
    925c7d96-6130-4f50-8de3-8c40c2837fc1-1508871271842.xml_en-US_es-ES.sdlxliff (no xml)

    Best regards,
    Zeena
  • 0 in reply to Zeena Faulk

    Hi  

    Thanks for the additional detail.

    Unknown said:
    When I saved it after I finished:
    • I used the “Save” icon that appears on the upper left hand
    • When I open the translation I finished last, it appears, in Trados, as:
    o 3b82b64c-31be-4a53-b2c6-b20fb05e8255-1510154149170.xml_en-US_es-419.sdlxliff [Translation]
    So it already has a double extension!

    Nothing unusual about this so far.  If you just save the file like this then you are in effect saving the sdlxliff.  The naming convention is exactly as I explained before because you have created a single file project and the file is named using the language codes.  So your original file was probably this:

    3b82b64c-31be-4a53-b2c6-b20fb05e8255-1510154149170.xml

    When it's saved you get an SDLXLIFF and this is created by using your language pair:

    en(US) to es(419)

    and then adding the Studio bilingual file extension:

    SDLXLIFF

    So far this all looks fine to me.

    Unknown said:
    How I tried to save it to be an xml (and not an SDLXLIFF):
    • Home/Batch Tasks/Generate Target Translations/Next/(went into Batch Processing)/Finish

    If you do this then the target file will be generated in whatever folder you have set up for this batch task, or it will place it in the project folder.  I would recommend going to your files view and then click on the icon called "Explore Containing Folder" in the Hole -> File Actions ribbon group.  This will open up the location of your project files and you should find the XML there.

    Alternatively, open up your translation and then press Shift+F12, or use the File -> Save Target As to save the target file wherever you like instead of using the automated approach which is really only useful when you have a whole project of files to generate the targets for.

    I'm sure your problem is something like this and is not because Studio is doing something wrong or unusual.

    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
    Paul,

    There was no mention of Studio doing something wrong or unusual in the email chain before. We needed some support, which you provided and I am going to send to my colleague. Thank you!

    Best regards,
    Zeena
Reply Children
No Data