Under Community Review

Please improve the design of Trados to be able to translate large file or big file smoothly and quickly

My computer has high specifications, with excellent CPU and 32GB of RAM. However, when I use Trados to process an Excel worksheet of about 300,000 words (Characters), which contains approximately 50,000 segments in trados, Trados almost completely freezes. It cannot batch lock repeated segments and cannot translate normally. It is just one excel worksheet, and we can not seperate it. Please improve the design of Trados to enable it to handle large files of several hundred thousand or even a million words.

Besides, can you make trados split large sdlxliff document when necessary? could you also add the function to allow trados to divide one big sdlxliff to several ones that can be handled seperately?

jack zhong
Parents

  • Hi    - on your question around splitting SDLXLIFF files - see for example the SDLXLIFF toolkit app at RWS AppStore. Also while it is desirable to have a more robust handling of large files (Studio 2022 SR2 has some improvements in that area BTW), I also consider this a "get it right at the source" problem. If a file with 300,000 words and 50,000 segments enters the translation supply chain, something has gone wrong "at the source", i.e. where you get the file from. It is not good practice to work with such unwieldy files in any use case, including translation. But we acknowledge this happens very often so the CAT tool has to handle this as robustly as possible.

  • in reply to Daniel Brockmann

    The splitting would need to be consistent with the structure of the source file, i.e. breaking down into individual sections, chapters, etc., for coherent handling of the component source files in Studio. I think this need may be answered in StudioViews, which I have just glimpsed in the AppStore. But would it be possible to automate the splitting by pinpointing the section, chapter etc., markers?

Comment
  • in reply to Daniel Brockmann

    The splitting would need to be consistent with the structure of the source file, i.e. breaking down into individual sections, chapters, etc., for coherent handling of the component source files in Studio. I think this need may be answered in StudioViews, which I have just glimpsed in the AppStore. But would it be possible to automate the splitting by pinpointing the section, chapter etc., markers?

Children
No Data