• State Verified Answer
  • Replies 2 replies
  • Subscribers 433 subscribers
  • Views 164 views
  • Users 0 members are here
Options
Related

Issue with AutoText and AutoSuggest Functionality in Trados Studio (Arabic Language Support)

Sameh Elsharkawy

Dear RWS Support Team,

I hope this message finds you well.

I am writing to report what appears to be a set of issues with the AutoText and AutoSuggest functionalities in Trados Studio when working with Arabic (Saudi Arabia) as the target language. I have tested these thoroughly and documented the behavior in the attached screenshots for your reference.

1. AutoText Import and Non-Functionality

  • After importing an existing .autoTxt AutoText list (via Options > AutoText > Import), no suggestions are shown when typing the expected entries in Trados Studio Editor (e.g., football player names such as "ليونيل ميسي").

  • Even though the imported entries are visible in the AutoText list in the settings dialog, they do not appear during typing in the editor.

  • This persists even with AutoText properly enabled in the AutoSuggest options list.

2. Limitations in Managing AutoText Lists

  • It appears that Trados Studio saves AutoText lists to a single settings file, without allowing multiple .autoTxt lists to be added in parallel.

  • Importing a new list does not seem to overwrite the previous entries or I am not sure if it appends or what, it is not clear at all!

  • This prevents batch management of entries and forces manual editing of one list at a time, which is both restrictive and error-prone.

  • Ideally, AutoText should allow multiple .autoTxt files to be loaded, merged, or edited externally, with Studio applying changes automatically.

3. Priority Confusion Between AutoSuggest Sources

  • I noticed inconsistent behavior depending on the order of AutoSuggest providers:

    • When I moved AutoSuggest Dictionaries to the top of the list, suggestions began working.

    • However, when I moved them down to the 4th rank, the suggestions also worked, which was confusing and not aligned with my expectation (I wanted Termbase suggestions to always take priority). It is amazing why it worked now after reordering the priority list! Before it was not working at all as per the screenshot.

  • This suggests that AutoSuggest source prioritization may not be functioning consistently.

4. AutoSuggest Dictionary Not Triggering in Arabic

  • Even when using an AutoSuggest Dictionary (.bpm) that I confirmed contains multiple entries for “Lionel Messi” (verified directly via the database), suggestions are not triggered when typing in Arabic.

  • Curiously, the same dictionary setup works correctly for English terms.

  • This indicates a possible issue with AutoSuggest recognition for Arabic script.

Impact

  • These issues significantly reduce productivity when translating into Arabic, especially in projects requiring consistent terminology and frequent insertion of predefined entries.

  • The inability to manage multiple AutoText lists or reliably use AutoSuggest dictionaries in Arabic creates unnecessary manual overhead and inconsistency. There should be also an option to batch delete the entries instead of having to reset to default! 

Request

Could you please confirm:

  1. Whether this is a known limitation or bug in Trados Studio?

  2. If there are any workarounds for making AutoText and AutoSuggest work reliably with Arabic?

  3. If the handling of multiple .autoTxt lists and Arabic AutoSuggest dictionaries is planned to be improved in future updates?

I would be happy to provide additional test files or logs if required.

Thank you very much for your time and support.
I look forward to your guidance on resolving this matter.

Best regards,
Sameh Elsharkawy

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

    Probability score: 0.85  

    Question improvement suggestion: Provide specific details about the version of Trados Studio you are using and any recent updates or changes made to your system.  

    In the meantime, based on the information you have provided, here is a suggested answer to your question:  

    Hello Sameh,  

    Thank you for your detailed report regarding the issues with AutoText and AutoSuggest functionalities in Trados Studio when working with Arabic. I appreciate the thoroughness of your documentation, which will help in addressing your concerns effectively. Here’s a step-by-step breakdown of your issues and potential solutions:  

    **Step 1: AutoText Import and Non-Functionality**  

    - Ensure that the AutoText entries you imported are indeed saved correctly. You mentioned they are visible in the settings but not in the editor. This could be due to the minimum character threshold for AutoText suggestions, which is 4 characters. Make sure you are typing at least this many characters to trigger the suggestions.  

    **Step 2: Limitations in Managing AutoText Lists**  

    - Currently, Trados Studio supports only one AutoText list per target language, and duplicates are ignored. Unfortunately, there is no built-in feature to manage multiple .autoTxt files simultaneously. A workaround could be to create a comprehensive termbase that includes all your frequently used phrases, which can be managed more flexibly.  

    **Step 3: Priority Confusion Between AutoSuggest Sources**  

    - The behavior you observed with the AutoSuggest sources is indeed perplexing. It’s essential to ensure that the AutoSuggest settings are configured correctly. You can try resetting the AutoSuggest provider order and testing again. If the issue persists, it may be worth reporting as a potential bug.  

    **Step 4: AutoSuggest Dictionary Not Triggering in Arabic**  

    - The issue with the AutoSuggest dictionary not triggering for Arabic terms could be related to how the dictionary is set up. Ensure that the AutoSuggest dictionary is correctly linked to your project and that it contains the necessary entries. If it works for English but not Arabic, this may indicate a limitation in the recognition of Arabic script within the current version of Trados Studio.  

    **Impact and Request for Confirmation**  

    - Your concerns about productivity and consistency in terminology management are valid. I recommend checking for any updates to Trados Studio that may address these issues, as improvements are often included in new releases.  

    **Conclusion**  

    - If these suggestions do not resolve your issues, please consider providing additional test files or logs, as this may help in diagnosing the problem further.  

    I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

    RWS Community AI
    emoji
Reply
  • 0

    Probability score: 0.85  

    Question improvement suggestion: Provide specific details about the version of Trados Studio you are using and any recent updates or changes made to your system.  

    In the meantime, based on the information you have provided, here is a suggested answer to your question:  

    Hello Sameh,  

    Thank you for your detailed report regarding the issues with AutoText and AutoSuggest functionalities in Trados Studio when working with Arabic. I appreciate the thoroughness of your documentation, which will help in addressing your concerns effectively. Here’s a step-by-step breakdown of your issues and potential solutions:  

    **Step 1: AutoText Import and Non-Functionality**  

    - Ensure that the AutoText entries you imported are indeed saved correctly. You mentioned they are visible in the settings but not in the editor. This could be due to the minimum character threshold for AutoText suggestions, which is 4 characters. Make sure you are typing at least this many characters to trigger the suggestions.  

    **Step 2: Limitations in Managing AutoText Lists**  

    - Currently, Trados Studio supports only one AutoText list per target language, and duplicates are ignored. Unfortunately, there is no built-in feature to manage multiple .autoTxt files simultaneously. A workaround could be to create a comprehensive termbase that includes all your frequently used phrases, which can be managed more flexibly.  

    **Step 3: Priority Confusion Between AutoSuggest Sources**  

    - The behavior you observed with the AutoSuggest sources is indeed perplexing. It’s essential to ensure that the AutoSuggest settings are configured correctly. You can try resetting the AutoSuggest provider order and testing again. If the issue persists, it may be worth reporting as a potential bug.  

    **Step 4: AutoSuggest Dictionary Not Triggering in Arabic**  

    - The issue with the AutoSuggest dictionary not triggering for Arabic terms could be related to how the dictionary is set up. Ensure that the AutoSuggest dictionary is correctly linked to your project and that it contains the necessary entries. If it works for English but not Arabic, this may indicate a limitation in the recognition of Arabic script within the current version of Trados Studio.  

    **Impact and Request for Confirmation**  

    - Your concerns about productivity and consistency in terminology management are valid. I recommend checking for any updates to Trados Studio that may address these issues, as improvements are often included in new releases.  

    **Conclusion**  

    - If these suggestions do not resolve your issues, please consider providing additional test files or logs, as this may help in diagnosing the problem further.  

    I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

    RWS Community AI
    emoji
Children
No Data