285 Resources available

Clear all
RYSTUDIO Workflow Automation Package

Paid

RYSTUDIO Workflow Automation Package

By RyStudio

<strong>RYSTUDIO Workflow Automation Package</strong><br /> <strong><i>Make your life a breeze!</i></strong><br /> <br /> This amazing package inherit almost all modules from our flagship AutoML System, except the machine learning and custom model traning parts. Instead, it offers users with a rich choice of 7 general-purpose MT services: Google NMT, DeepL Pro, MS Bing Translator, Sogou, Baidu, Youdao and RYSTUDIO Neural Translator. <br /> <br /> RYSTUDIO Neural Translator, in particular, will give you amazingly good translation that is in most case much better than Google NMT or DeepL Pro, especially when Chinese, Japanese and Korean languages is involved. <br /> <br /> <strong>HIGHLIGHTS</strong> <br /> <br /> <strong>Pay Once & Use Forever:</strong><br /> <br /> All modules, for example, Machine Translation, Term Extract, QA and so on, are all ready to use once installed. No api keys required, no additional usage fees charged, no limit and quota imposed. <br /> <br /> <strong>Machine Translation:</strong><br /> <br /> The package comes standard with 7 most acclaimed neural machine translation services that are used day to day by translators around the world: Google NMT, DeepL Pro, Microsoft Bing, Sogou, Baidu, Youdao and RYSTUDIO NMT, of course, for translators working with Chinese, Japanese and Korean languages.<br /> <br /> <strong>Auto-Post-Editing:</strong><br /> <br /> Without a handy post-editing tool, a translator's life will be much harder and unbearable. RYSTUDIO Post-editing Module will remember all changes you made over a piece of text and apply them automatically either during machine translation or to a translated file or files in a batch manner.<br /> <br /> You can add as many post-editing list as you want to automatically change machine translation. For translated files, it is quite often that your PM or client will send you a what-to-change list, just import them into a post-editing list and click apply, the file or files will be automatically changed. <br /> <br /> <strong>Auto Terminology Standardization and In-process QA:</strong><br /> <br /> The MT models come standard with robust term standardization and QA modules with which you can specify how terms and entities, e.g. dates, names, money, measurements, phone numbers etc., be translated and/or auto-converted.<br /> <br /> SDL MultiTerm termbases, Excel files or your own glossary files are supported as the sources of standardization.<br /> <br /> <strong>AI-based Bilingual Term Extract: </strong> <br /> <br /> Perhaps, the most accurate one for the moment. Unlike conventional statistics-based term extract software, SDL MultiTerm Extract, for example, that will leave lots of terms unextracted and involve a great deal of laboring and infrustrating works after extraction, RYSTUDIO Neural Term Extract is powered by our finely-trained neural models. It just knows what a term looks like, even it appears only once in a file. What a translator or PM is supposed to do after extraction is to go through the term list and check if or not they are to be kept for the project at hand. <br /> <br /> Another exicting feature, of course, is that you can extract and align terms and correspodng translation from your translation memories, translated project files or other bilingual documents to create a project termbase quickly. <br /> <br /> <strong>MT Trace Eraser:</strong><br /> <br /> Your clients or PM will put on a unhappy face when he or she finds out that the file is translated with the aid of or based on a MT service. This tool will erase all MT meta data and traces off a project file. What a client sees is a file translated by human, not machine.<br /> <br /> What really matters is that because all files are machine-translated by your private neural model or our custom-built models, there is no way to trace back the origin of your translation by comparing them with those from a public MT service, Google NMT or DeepL Pro, for example. <br /> <br /> <strong>Job Assignment: </strong><br /> <br /> This is undoubtedly a favorite of all project managers. For files received for translation, a PM can use this module to exclude all segments that have an exact or fuzzy match against your TMs and among the files themselves as well as those that are perfectly translated by your private MT model, and re-generate one or more new documents with all these segments marked “NOT TO TRANSLATE” for job assignment to other translators. <br /> <br /> On completion of the assignment, a PM just selects translated documents from his or her translators and all project data, including project TM and main TM, will be updated instantly.<br /> <br /> <strong>Re-segmentation for Subtitles and PDF: </strong> <br /> <br /> When translating subtitle files or PDF with complex layout in Trados Studio, missegmentation, i.e. a sentence is wrongly broken into two or more separate segments, is a commonly-seen annoying problem and will result in poor-qualty machine translation. <br /> <br /> This tool will restore original sentences during machine translation stage so that translation quality will not be compromised.<br /> <br /> <strong>Please visit <a target="_blank" href="http://www.rycat.cn/">our official website </a>for details and more productivity-boosting plugins that will bring your career up to a higher level.</strong><br /> <br />

Record Source TU

Free

Record Source TU

By Trados AppStore Team

<p><strong>Note: This application is no longer maintained or supported.<br>Custom TM fields can be used out the box as an alternative, or <a href="https://appstore.rws.com/Plugin/89">SDLTM Import Plus</a>.</strong></p> <p>SDL Trados 2007 used to have a feature that stamped the name of the file you were translating on the Translation Unit in your Translation Memory. This feature was not implemented in any of the Studio versions to date. So this plugin for SDL Trados Studio 2015 brings this back and adds some interesting options. You can decide whether you want to stamp your Translation Units with:</p> <ul> <li><p> The filename you are working on</p> </li> <li><p> The filename plus it’s full path</p> </li> <li><p> The Project name</p> </li> </ul> <p>You can add any of these, or all of them, so they are automatically recording what you worked on when you translated your projects.</p> <p>This gives you the ability to filter on these for translating work in the future and for carrying out batch editing tasks to remove unwanted translations from your translation memory, or export an extract to provide to a colleague or a client.</p> <p>The plugin works as a Translation Memory provider, so you just choose RecordSourceTU when you add a Translation Memory to your project.</p> <p>You’ll be asked to select whether you want a new field created, or if you wish to append this information to an existing one, and you’re good to go.</p> <p>As always it’s a good idea to back up your Translation Memories before you start so if you decide you don’t like to work this way it’s easy to go back.</p> <p>Once installed, you can now start using Record Source TU by selecting it as a translation memory provider when you translate a new document or in the project settings.</p> <p><strong>Warning:</strong> The application will not record any information if there is no change made to an existing TU.</p> <p>If you want to learn more about working with fields in Studio then this article might be worth a read :<a href="https://multifarious.filkin.com/2013/07/12/fields_attributes/&quot;">multifarious-fields and attributes</a></p> <p>As well as <a href="https://community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/4720/recordsource-tu"><strong>Record Source TU</strong></a> in the RWS Community wiki</p> <style> :root { --table-striped: rgba(0, 0, 0, 0.05); --table-border: #dee2e6; --lightgray: #e9ecef; } code { color: black; background-color: var(--lightgray); border-radius: 5px; padding: 1.5px; } blockquote { border-left: 3px solid var(--lightgray); padding-left: 10px; } table { border: 1px solid var(--table-border); border-collapse: collapse; width: 100%; } table th, table td { border: 1px solid var(--table-border); padding: 8px; text-align: left; color: black; } table th { background-color: var(--table-striped); color: black; } table tr:nth-child(even) { background-color: var(--table-striped); color: white; } table tr:nth-child(odd) { background-color: white; color: var(--table-striped); } </style>

Reports Viewer Plus

Free

Reports Viewer Plus

By Trados AppStore Team

<p><strong><u>The Problem</u></strong></p> <p> The built-in &quot;Reports&quot; view in Studio is useful because it provides the ability to read the various Studio reports available and print or share them with others. But it does have some limitations:</p> <ul> <li>it can take a while to render each report when you click on it</li> <li>there is no possibility to customise the existing reports</li> <li>there is no possibility to introduce reports in other formats, possibly an analysis from another tool for example</li> </ul> <p> <strong><u>The Solution</u></strong></p> <p> The &quot;Reports Viewer Plus&quot; application creates a new View in Studio that mirrors the reports in the &quot;Reports&quot; view. This new view comes with several advantages:</p> <ul> <li>click on a report and it&#39;s rendered instantly</li> <li>you can edit the name of the Studio reports so they are easier to manage when you start to get a lot of reports in the list</li> <li>you can import an XML analysis file of some sort, along with an appropriate stylesheet, and attach it to your project</li> <li>you can define different stylesheets to be used for each type of Studio report and/or language so that they are automatically used in this view when you create a new project</li> </ul> <p>All in all, this is a great solution for anyone who would like to have more control over the type of reports that are created and who wants to be able to use them more often now that they display instantaneously.</p> <p>To learn how to use this application, please check the Documentation tab.</p> <style> :root { --table-striped: rgba(0, 0, 0, 0.05); --table-border: #dee2e6; --lightgray: #e9ecef; } code { color: black; background-color: var(--lightgray); border-radius: 5px; padding: 1.5px; } blockquote { border-left: 3px solid var(--lightgray); padding-left: 10px; } table { border: 1px solid var(--table-border); border-collapse: collapse; width: 100%; } table th, table td { border: 1px solid var(--table-border); padding: 8px; text-align: left; color: black; } table th { background-color: var(--table-striped); color: black; } table tr:nth-child(even) { background-color: var(--table-striped); color: white; } table tr:nth-child(odd) { background-color: white; color: var(--table-striped); } </style>

SDLTmFindVars

Free

SDLTmFindVars

By TMServe

<strong>Current version is 1.0.5</strong><br /><br /> Find the variables in your TM from what you have left untranslated in it. SDLTmFindVars is a utility that reads translation units from a given Trados Studio translation memory (TM) file and by comparing the items found in the Source and Target segments identifies potential Variables. That is, it searches for non-translatable text. Variables are usually company names, product names, trademarks, tokens or any word or phrase that it is left untranslated within each TM. The program writes the potential Variables in a TXT file for checking and further processing before the variables are added by the user in a Studio TM. <br /><br />It can also output the frequency of appearance in the output log and if needed, it can provide details for each Variable found in a CSV file. <br /><br />The user can also choose how the program performs the search and what is outputted through a number of options. <br /><br />Trados Studio considers Variables as replaceable parts of text with no real language meaning (such as the numbers or tags). Therefore it automatically enters them in the suggested target text allowing for increase of the matches provided by the TM and makes them accessible through the quick insert function to the users. <br /><br />SDLTmFindVars does not require a version of Trados Studio to be installed on the PC to function. The free version supports TMs of up to 50,000 translation units and can be upgraded to the unlimited version at a cost of 35 Euro. <br /><br />Once installed, you will now find SDLTmFindVars in your programs (All Programs-> TMServe-> SDLTmFindVars). It will then open up as a stand alone app outside of Trados Studio.