Non-breaking hyphens in Trados Studio 2021

Dear community members,

I'm trying to resolve an issue related to non-breaking hyphens in Trados Studio. Please note I'm using Trados Studio 2021 SR2 - 16.2.12.9338 on Windows 10/11.

While I can insert non-breaking hyphens in Studio Editor (e.g. in 2022-2023 or 19-22 février 2024), which display correctly in docx target files, it does not show up correctly in Studio Translation Memories.

Whenever a stored unit comes up in concordance searches (and when applying matches in target segments), it displays as "20222023" or "1922 février 2024" in Studio.

Any idea or suggestion to make sure non-breaking hyphens are stored correctly in TM and show up as such in Studio?

Thanks your help

emoji
  • Hello,

    I understand your concern about non-breaking hyphens not displaying correctly in Trados Studio Translation Memories. Here are some steps you can follow to resolve this issue:

    Step 1: Open Trados Studio and go to the "File" menu.

    Step 2: Select "Options" from the drop-down menu.

    Step 3: In the Options window, navigate to the "Editor" section.

    Step 4: Under the "Editor" section, select "Auto-substitution".

    Step 5: In the Auto-substitution settings, ensure that the "Hyphen to non-breaking hyphen" option is checked.

    Step 6: Click "OK" to save the changes.

    This should ensure that non-breaking hyphens are stored correctly in your Translation Memories and display as such in Trados Studio. If the issue persists, it might be due to the specific formatting of the source document. In such cases, you might need to manually adjust the hyphenation in the source document before importing it into Trados Studio.

    I hope this helps! If you have any other questions, feel free to ask.

    Best regards,

    RWS Community AI

    emoji
  • I get this in the Translation Results window (Trados Studio 2022):

    Trados Studio 2022 Translation Results window showing a segment with a non-breaking hyphen tag displayed with almost no width.

    Although using another tag view, I can get this (the tag has almost no width):

    Trados Studio 2022 Translation Results window showing a segment with a non-breaking hyphen tag displayed correctly.

    Is this what you get? If not, please post screenshot of what you see.

    BTW: Tag view is changed here:

    Trados Studio interface with the Options button highlighted indicating where to change the tag view settings.

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 1:29 PM (GMT 0) on 29 Feb 2024]
  • Thank you Jesús, This is what I get in the Translation Results window:

    Screenshot showing Trados Studio Translation Results window with a 99% match error. Source text '31 January-2 February 2024 and 19-22 February 2024' is not a 100% match with the target text '31 janvier-2 fevrier 2024 et 1922 fevrier 2024'. Incorrect date format in French displayed.

    You can notice, while the source text is strictly identical, that it does not show up as a 100% match, and dates are not correctly displayed in french (1922 instead of 19-22).

    If I use normal hyphens, it shows up correctly (here 19-22) in the Translation Results window.

    Any idea how to sort this out?

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 1:29 PM (GMT 0) on 29 Feb 2024]
  •  

    You can notice, while the source text is strictly identical, that it does not show up as a 100% match

    It’s not a 100% match, since there is an extra hyphen after the number 19 in Source. That’s why it’s only a 99%.

    If you press CTRL+T (or the button Icon of Trados Studio showing two green squares and a blue arrow pointing right. ) in the Translation Results window, does the non-breaking hyphen between 19 and 22 populates the Target segment?

    I can't repro it in my Trados Studio 2022.

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 1:30 PM (GMT 0) on 29 Feb 2024]
  • Hello,

    If I press CTRL+T, the non-breaking hyphen does not populate the target segment.

    emoji
  •  

    ok, so far it makes sense to me.

    Are you sure that the non-breaking hyphen goes correctly to the final generated DOCX document? Could youi please test it for this particular segment?

    emoji