• State Verified Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 181 subscribers
  • Views 1064 views
  • Users 0 members are here
Options
Related

DeepL Plugin version 6.2.1.0 for Trados Studio 2022 Professional: Empty segments with Hungarian Translation

Aries S.

We have the latest version of the DeepL plugin (version 6.2.1.0) for Trados Studio 2022 Professional (2022 SR2 - 17.2.11.19134) and used it with the DeepL API to undergo a batch pre-translation of our source HTML 5 files from English to Hungarian. However, we encountered an issue on the pre-translation with the Hungarian language were there were some target segments left as empty segments but they are marked as NMT and as translated If we also try to use the Filter to show untranslated segements these empty target segments are not shown either. This issue with empty target segments has not been seen with other languages such as French, German, Spanish, Italian, Portuguese etc where all segments are translated with identical HTML files. We had also recreated the project several times and the same target segments that were empty on the first attempt were also not pre-translated in Hungarian in subsequent attempts.

The issue is similar to the one that was in the post below which was posted 4 years ago however, the difference is that the target cells in our project that are empty have the status set as NMT translated.

 RE: New DeepL plugin for Studio 2019: empty segments with ZH-SI and JP 

We tried translating the same file that had an issue to other languages (French, German, Spanish, Italian, Portugues and Bulgarian) with the same pre-translation settings and exactly the same HTML files but the target segments that were blank in the Hungarian translation were translated successfully in the other languages - this eliminates the possibility of any possible issues with the source segments.

All our HTML5 files have been validated with a HTML5 validator so it cannot be due to invalid HTM in the source files.

Therefore this is only with the Hungarian translation.

The Hungarian translation is also showing the following error and not sure what is causing the issue because the Bulgarian translation did not have the same issue.

Translation Failed: The start tag with ID ‘138’ does not have a matching end tag within the segment

Here is a screenshot showing the issue. Had to blur the translations for privacy/security purpose.

Screenshot of Trados Studio with DeepL plugin error message: 'Translation Failed: The start tag with ID '53' does not have a matching end tag within the segment.' Some segments are marked as NMT and translated, but the content is blurred.

Again, this issue is in the Hungarian translation only but not in any other language we have tried. As an examples here is a screenshot of the Bulgarian translation. I highlighted the same sections.

Screenshot of Trados Studio interface showing segments translated into Bulgarian. Segments are marked as NMT, and the content is blurred. No error messages are visible.

What is causing this issue? And what can we do so that all our source segments are pre-translated to Hungarian?

Generated Image Alt-Text
[edited by: RWS Community AI at 1:35 AM (GMT 1) on 10 Sep 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0

      

    It would be more helpful if you provided sample files for this... should be trivial to make and probably easier than showing obfuscated screenshots.  However, I did manage to create such a file, with custom elements.  "Comment" is not a standard element, and as you have this as a placeholder I'd also note that HTML5 doesn't natively support self-closing tags for custom elements)... so my file may not represent what you have:

    <!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Exploration of Space</title>
</head>
<body>

<p>
    <a href="#section1">The Beginning of Space Exploration<comment text="This is a reference to early satellites." /></a><br>
    Space exploration started in the mid-20th century with the launch of the first artificial satellites.<br>
</p>

<p>
    <a href="#section2">The First Human in Space<comment text="This is about Gagarin's Vostok 1 mission." /></a><br>
    Yuri Gagarin became the first human to journey into outer space on 12 April 1961.<br>
</p>

<p>
    <a href="#section3">Moon Landings<comment text="A historical milestone in human space exploration." /></a><br>
    The Apollo program achieved the first manned moon landing in 1969.<br>
</p>

<!-- Additional section with more information -->
<section id="section1">
    <h2>The Beginning of Space Exploration</h2>
    <p>During the Cold War, both the United States and the Soviet Union invested heavily in space technologies...</p>
</section>

<section id="section2">
    <h2>The First Human in Space</h2>
    <p>Yuri Gagarin's flight aboard Vostok 1 was a major achievement for humanity and the Soviet space program...</p>
</section>

<section id="section3">
    <h2>Moon Landings</h2>
    <p>Neil Armstrong and Buzz Aldrin became the first humans to walk on the moon during the Apollo 11 mission...</p>
</section>

</body>
</html>

    However, with this file I can reproduce the issue!

    Screenshot of a translation software interface showing side-by-side comparison of English to Hungarian translation with highlighted segments and comments.

    I'm not sure why this occurs or where the problem lies.  My initial thoughts were around the use of the self-closing tag, but the other segments populate it's clearly something else.  I also check in German, and it was fine... so can only conclude this is a valid problem somewhere.  Don't know yet whether this is the plugin or DeepL:

    Screenshot of a translation software interface showing side-by-side comparison of English to German translation with highlighted segments and comments.

    I'll log this with the Trados AppStore Team to review.

    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



    Generated Image Alt-Text
    [edited by: RWS Community AI at 11:09 AM (GMT 1) on 10 Sep 2024]
  • +1 in reply to Paul

     

    Where segment 2 did not want to produce translation results which I know is a different "issue" from your reported error of:

    Aries Simbulan said:
    Translation Failed: The start tag with ID ‘138’ does not have a matching end tag within the segment

    But I was able to get translations for all segments, using  sample file.
    Initially I also had difficulties as Paul described but then I changed the Tag handling from setting from none to HTML as noted below.

    Screenshot of a translation software interface showing segments of text in English and their Hungarian translations. Each segment is labeled with 'NMNT'.

    Keen to see if that makes a difference for you

    Regards

    Lyds

    Lydia Simplicio | 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

    emoji


    Generated Image Alt-Text
    [edited by: RWS Community AI at 9:32 PM (GMT 1) on 10 Sep 2024]
  • 0 in reply to Lydia Simplicio

    Thanks for the response  and  , I tested the DeepL setting update and retranslated the file with the issue and it did fix the issue. We were not aware the setting exist. Even the documentation in the Plugin page below did not have that option.

    https://appstore.rws.com/Plugin/24?tab=documentation

    Can you send a link with the updated documentation or instructions that explains the new options? I see a "Preserve formatting" option as well which did not exist before and we don't know its function.

    Thank you.
    emoji