Custom XML: additional CR/LF added in target file

 

It wasn't like this before in previous versions. Now this is a real problem and I have to edit each file before delivery. Can you do something about it, dear SDL?

_________________________________________________________

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.

Parents
  • Hi Jerzy,

    I have no answer for you but is it normal in this sort of custom target xml that only one language <singlelanguage>polish</singlelanguage> is defined at the start of the file but then each translation contains both source and target language entries?
    And is it coincidental that each extra CRLF has been added only before each closing </polish> tag?
    In a bilingual xml/xlf file I would expect to see both the source language and target language defined in the headers.

    I know very little on this subject so perhaps 'single language' just means that there is only a single target language. I'm sure you know more about it than I do and would have noted the above already if it were not normal... ;-))

    Have a good evening!
    Ali :)

  • This is a very strange XML in fact.

    We get it with only "english" in the "translation" group. The customer has developed a "tool", which is to be used for the translation of these files. The tool reads the xml and adds the "polish" element as soon the translation has been entered. But the usability of the tool is really not good, so we developed a method to do that in Studio. First I open the XML in Notepad++, duplicate the "english" text into "polish" tag, then translate in Studio. Until S2017 there were no extra line breaks added, but now they are. I did not notice and delivered once, but the customer has moaned and I nearly lost them. Now I know I have to reprocess, but I don't understand why there are extra cr/lf added.

    _________________________________________________________

    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.

  • Indeed, this really is a very strange state of affairs, I agree.

    Can you see the unwanted CRLFs if you click 'All content' in the SDLXLIFF file? So long as it doesn't prevent generation of target, at least you could manually delete them there - a little bit easier than in the generated target file? Also are they in the source content? That would indicate whether they are getting inserted before/on creation of the sdlxliff or for some reason getting added on generation of the target file... ???!!! Sorry if I'm stating the obvious. Thinking 'out loud'.

    Could it be that some of the custom filetype settings have been lost in the migration to 2017? Have you compared your custom filetype settings between 2015 and 2017?

    I recall when migrating a template with a custom xml filetype from one version of Studio into one with a filetype settings file, I lost half of the custom settings and had to open the old version of Studio alongside the new one and manually compare and copy the filetype parser settings from the old to the new, which was laborious but worked fine. It would have been soo much easier if we'd had the new filetype preview that has been introduced in Studio 2017. No need to keep creating projects to see if the changes had worked. It would have saved so much time till I got the filetype settings sorted.

    As the CRLF is being inserted always and only before </polish> tags, what is different between the (settings for the) </english> closing tag/tag pair or indeed any other tag) and the <polish> tag pair that could cause this?

    Sorry, an awful lot of questions...!

    Ali :)
  • Hi Jerzy,

    Can you share your source xml for this and your sdlftsettings file? Would be good to understand why this is happenning?

    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

  • Hi Paul

    As I can't see how to do this here, I'll send you all relevant files off-forum.

    Best regards, Jerzy

    _________________________________________________________

    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.

Reply Children