Under Community Review

add direct mutual conversion functionality between sdlxliff, sdltb, sdltm, and Microsoft Excel in Trados Studio

  1. User Requirements:

Please add the functionality to Trados Studio (desktop software) to directly and mutually convert sdlxliff files, termbases (sdltb), and translation memories (sdltm) with Microsoft Excel files.

  1. Background and Rationale:

The file formats associated with Trados Studio (desktop software)—namely sdlxliff, sdltb, and sdltm—are unstable and prone to issues. When problems arise, the entire file may become inaccessible for opening, editing, or copying. In contrast, Microsoft Excel files are highly stable and easy to modify.

  1. Current Situation:

3.1 The third-party plugin "Glossary Converter" currently allows for quick mutual conversion between sdltb and Excel formats. However, Glossary Converter sometimes suffers from version instability, rendering it unusable. Moreover, it does not support mutual conversion to Excel format for large termbases (sdltb) containing hundreds of thousands of entries or translation memories (sdltm) with millions of segments.

3.2 The Trados plugin "Export to Excel" can quickly convert sdlxliff to Excel format, but it does not support converting Excel files back to sdlxliff format. Additionally, with the continuous updates to Trados Studio (desktop software), plugins in the Trados AppStore often encounter version incompatibility issues.

3.3 Although MultiTerm can convert Excel files to sdltb format, the process is complex, involves many steps, and is time-consuming, rendering it of little practical value.

  1. Conclusion and Recommendations:

It is recommended that Trados Studio (desktop client) directly add the capability to quickly export sdlxliff files, termbases (sdltb), and translation memories (sdltm) to Microsoft Excel format, as well as to directly import Microsoft Excel files and convert them into sdlxliff, sdltb, and sdltm formats.

jack zhong
Parents

  •   

    Please explain why you really want this? What will you do with these excel files containing this sort of data?

  • in reply to Paul

    Dear Mr. Paul, 

    thank you for your reply,

    1. Prevent Data Loss and Project Delays
      Trados Studio (computer software) files (sdlxliff, sdltb, sdltm) often encounter errors and unexpected issues. When this happens, files can become corrupted or inaccessible, leading to lost translation data and missed deadlines. Since Trados 2019, I have personally experienced hundreds of unpredictable problems, many of which caused serious project delays and financial loss. If we could always export these files to Excel, translators could continue their work in Excel, then re-import the data back into Trados, ensuring projects can move forward without interruption.
    2. Stronger Editing and Data Management
      Trados Studio provides only basic editing for its file formats. Exporting to Excel would allow translators to use powerful features such as advanced editing, custom sorting, find and replace, batch processing, deduplication, and filtering. Excel, especially with Microsoft 365 Copilot, enables complex and automated data management that Trados cannot currently offer.
    3. Solve Compatibility Issues and Enable Long-term Storage
      With each new version of Trados Studio, compatibility problems with old file formats are common. Excel files are stable and can be stored for longer time. When needed, translators could easily import these Excel files back into Trados, regardless of software version, and quickly resume their projects.
    4. Save Time by Reducing Software Dependencies
      Currently, converting between these formats requires several different tools—Trados Studio, downloading various plugin which might not function well or make trados studio even slower. Glossary Converter, and other TMX editors. This wastes valuable time for translators. If all conversions could be done directly within Trados Studio, it would greatly simplify the workflow and boost productivity.
    5. Business Value for RWS
      This feature would make Trados Studio much more attractive to users by improving reliability, flexibility, and efficiency. I believe it would help RWS increase both sales and market share.

    In summary:
    Direct, reliable conversion between Trados formats and Excel would protect valuable translation data, save time, empower users with better editing tools, solve compatibility issues, and make Trados Studio more competitive in the market.

    best regards

    jack

Comment
  • in reply to Paul

    Dear Mr. Paul, 

    thank you for your reply,

    1. Prevent Data Loss and Project Delays
      Trados Studio (computer software) files (sdlxliff, sdltb, sdltm) often encounter errors and unexpected issues. When this happens, files can become corrupted or inaccessible, leading to lost translation data and missed deadlines. Since Trados 2019, I have personally experienced hundreds of unpredictable problems, many of which caused serious project delays and financial loss. If we could always export these files to Excel, translators could continue their work in Excel, then re-import the data back into Trados, ensuring projects can move forward without interruption.
    2. Stronger Editing and Data Management
      Trados Studio provides only basic editing for its file formats. Exporting to Excel would allow translators to use powerful features such as advanced editing, custom sorting, find and replace, batch processing, deduplication, and filtering. Excel, especially with Microsoft 365 Copilot, enables complex and automated data management that Trados cannot currently offer.
    3. Solve Compatibility Issues and Enable Long-term Storage
      With each new version of Trados Studio, compatibility problems with old file formats are common. Excel files are stable and can be stored for longer time. When needed, translators could easily import these Excel files back into Trados, regardless of software version, and quickly resume their projects.
    4. Save Time by Reducing Software Dependencies
      Currently, converting between these formats requires several different tools—Trados Studio, downloading various plugin which might not function well or make trados studio even slower. Glossary Converter, and other TMX editors. This wastes valuable time for translators. If all conversions could be done directly within Trados Studio, it would greatly simplify the workflow and boost productivity.
    5. Business Value for RWS
      This feature would make Trados Studio much more attractive to users by improving reliability, flexibility, and efficiency. I believe it would help RWS increase both sales and market share.

    In summary:
    Direct, reliable conversion between Trados formats and Excel would protect valuable translation data, save time, empower users with better editing tools, solve compatibility issues, and make Trados Studio more competitive in the market.

    best regards

    jack

Children
  • in reply to jack zhong

     

    Thanks, but in my opinion (I am not the Studio product manager) this is not technically sound or reasonable when weighed against how Trados Studio works in practice.

    There are some reasonable aspects:

    • Your desire to prevent data loss: It's understandable that you would want a fallback mechanism should Trados files become corrupted.

    • Your frustration with plugin/version issues: The pain points around plugin compatibility and large file handling are legitimate concerns, albeit better resolved in other ways.

    • Your wish for simpler editing workflows: Excel certainly feels easier to many non-technical users, especially when facing cumbersome import/export processes in MultiTerm or Studio.

    But this is where I think the rationale falls apart:

    • Excel as a stable alternative: Excel isn't built for complex linguistic data structures and can't safely substitute the database-backed formats used in Studio.

    • Assumption of reversible editing: The idea that users could safely reimport changes to SDLXLIFF or SDLTM from Excel without significant risk is simply flawed.

    • Overgeneralisation of personal experience: Claiming "hundreds" of unpredictable issues since Trados 2019 may reflect localised problems (e.g. hardware, environment, misuse), not something addressable by fundamentally changing file architecture.

    So whilst I do believe you have genuine frustrations, and you presented them coherently, the solution they propose don't stand up to technical scrutiny in my opinion.  Your reasoning is most likely rooted more in personal workflow challenges than in what is realistically or safely achievable in a product like Trados.  Perhaps a good solution would be to extend your use of AI to writing your own code and then build the solutions you would like to have yourself?  That would most likely help you to see why your request may not be the most desirable, or appropriate, solution to your problems.