<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>CAT tools padlet by Julia Szmidt</title>
      <link>https://padlet.com/juliaszmidt1/CAT</link>
      <description></description>
      <language>en-us</language>
      <pubDate>2023-01-24 16:39:44 UTC</pubDate>
      <lastBuildDate>2025-12-06 12:32:54 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title>What&#39;s new since Trados Studio 2017 31.10.22</title>
         <author>juliaszmidt1</author>
         <link>https://padlet.com/juliaszmidt1/CAT/wish/2457794632</link>
         <description><![CDATA[<div>From this short webinar from the Trados website, I learned what specifically has changed between the latest versions of the program, namely the 2017 and 2022 version.<br><br>New features that have been added include:<br>- creating new projects quicker (the view is more user-friendly, it is easy to navigate between translation resources, termbases, batch tasks; you can basically create project in the first page)<br>- the same applies to adding new files to the project (you can add file in just two clicks, moreover you get your new file automatically pre-translated)<br>- it is possible to add the latest file formats including enhanced Microsoft Office and new file types, such as Microsoft Visio, JSON, emails, PhotoShop<br>- easier replacement files while the project is on-going (mid-project update scenario)<br>- possibilty to see the preview of the translated document while doing the project, you can also see the layout of the source and target document<br>- easy transfer of documents and data to the cloud - thanks to that function you may give or receive access to termbases , translation memories and translated documents to other translators, reviewers or project managers<br>- integrated AppStore with new plug-ins: subtitling, multilingual XML and Excel, etc.<br>- online editor, which allows you to work on your project even when you don't have your computer on hand<br><br>link: https://www.trados.com/video/whats-new-since-trados-studio-2017/206629/</div>]]></description>
         <enclosure url="https://www.trados.com/video/whats-new-since-trados-studio-2017/206629/" />
         <pubDate>2023-01-26 15:41:53 UTC</pubDate>
         <guid>https://padlet.com/juliaszmidt1/CAT/wish/2457794632</guid>
      </item>
      <item>
         <title>Translating subtitles in SDL Trados Studio - webinar recording 19.11.22</title>
         <author>juliaszmidt1</author>
         <link>https://padlet.com/juliaszmidt1/CAT/wish/2457801416</link>
         <description><![CDATA[<div>As someone who is interested in audiovisual translation and subtitling in particular, I became very curious about the possibility of creating them in SDL Trados Studio.</div><ul><li>It is enabled by several plugins - subtitling plugin, new filetypes (webVTT, STL (Spruce), SBV (YouTube)). Additionally, the TQA model has been introduced, so the Studio can run Translation Quality Assessment (FAR Methodology) and you can cutomise it as you like. However, the plugin works just for SDL Trados Studio 2019 or more recent versions.&nbsp;</li><li>The filetype support include time-codes, formatting, positioning.</li><li>TQA is based on the FAR methodology (functional equivalence, acceptability and readability).</li><li>You can get a preview of the exact moment of the video you want.</li></ul><div>Features</div><ol><li>Synchronised selection and content changes.</li></ol><div>The selected segment from the editor is synchronised with the subtitle track that is displayed in the video. When you move to a new segment in the editor, the corresponding track is selected in the video and similarly when you select a subtitle track in the video, focus is moved to the corresponding segment in the editor.&nbsp;<br>Additionally, changes applied to the translation are immediately visible in the subtitle caption from the video, including any formatting that was applied.<br><br>2. Real time verification feedback.<br>Displays real time verification feedback as the content is being updated, providing you with a much more informed approach in making decisions as they are translating.<br><br>3. Splitting &amp; Merging segments.</div><div>Support for splitting and merging segments within and across paragraph boundaries.&nbsp; When merging across paragraphs, all context and structure related to the paragraphs that have been fully merged to the parent paragraph are excluded from the native file that is regenerated with the target content.<br><br>4. Merged and Virtually merged files.</div><div>Support for working with both merged and virtually merged files.&nbsp; Ideally each subtitle file that is added to the project should have a corresponding video reference with the same name (<em>with exception to the file extension</em>). Each time you navigate to a new file within the document, the relative video is loaded (<em>if available</em>) and corresponding track in the video is selected.<br><br>5. Editable time tracks.</div><div>Support for updating the display time of the subtitle captions.&nbsp; This feature permits you to adapt the Start and End time-codes to align better with the translated content.&nbsp; This also includes hotkeys to automatically set the Start/End times from the current position of the video.<br><br>6. Time-code Format.</div><div>Support for converting and displaying the time-code format between Frames and Milliseconds.<br><br>7. Setting a minimum time span between subtitles.</div><div>Support for applying the rules of a styleguide to set a minimum time span between subtitles.<br><br>8. Keyboard Shortcuts.</div><div>Support for assigning keyboard shortcuts to help automate interaction with the subtitling controls from the editor (<em>e.g. jump back/forward from the video in seconds or frames, link/unlink the video, play back from previous subtitle etc...</em>)<br><br></div><div><br>webinar: https://www.trados.com/video/introducing-a-new-and-easy-way-to-translate-subtitles-in-trados-studio/149285/thankyou<br>other sources: https://community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/4680/studio-subtitling<br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/1608354881/bc21e4cc6e4287d80d85900e5023a0ea/subsiv.webp" />
         <pubDate>2023-01-26 15:46:23 UTC</pubDate>
         <guid>https://padlet.com/juliaszmidt1/CAT/wish/2457801416</guid>
      </item>
      <item>
         <title>Using Google Translate with MemoQ 12.12.22 </title>
         <author>juliaszmidt1</author>
         <link>https://padlet.com/juliaszmidt1/CAT/wish/2457810598</link>
         <description><![CDATA[<div>https://www.youtube.com/watch?v=qN_cIfr4e5o<br><br>I've learnt how to add MT machine to MemoQ in order to use it later for pre-translation.&nbsp;</div>]]></description>
         <enclosure url="https://drive.google.com/drive/u/0/folders/1nYWlg5DdIxPnR5wQREor73DwChSiNeez" />
         <pubDate>2023-01-26 15:52:19 UTC</pubDate>
         <guid>https://padlet.com/juliaszmidt1/CAT/wish/2457810598</guid>
      </item>
      <item>
         <title>Best practices of using MT - memoQ talks 10.01.23</title>
         <author>juliaszmidt1</author>
         <link>https://padlet.com/juliaszmidt1/CAT/wish/2457810994</link>
         <description><![CDATA[<div>Intrigued by the possibilities MT can offer, I decided to listen to the talk with Jost Zetzsche - independent translator, localisation consultant, and writer, who talks about best practices for translators when using machine translation (MT). Jost explains how the output from NMT and SMT can differ, what translators should look at when using MT or when post editing, and what verticals and types of text lend themselves to the use of MT for translation.<br><br></div><ul><li>Jost rightly points out that both SMT and NMT rely on professional translations. He notices that NMT generally provides us more "smooth" text that reads well, but in the same time it tends to drop information, not knowing how to deal with translation of given element, because it doesn't have it in database. If you post-edit text from NMT you need to stick to the target text to be able to recognise mistakes or omissions. When it comes to SMT, it is easier to find a mistake. For SMT it is more popular not to have translator to post-edit the text - mistakes are so obvious, but the NMT requires at least bilingual translator or well-trained posteditor to revise the text.&nbsp;</li><li>Jost also talks about the influence that MTs have on our own translations, how they dictate the way we see the text. We have to value the data MT provide us. We should take into consideration various types of MT, but filter the information. They are amazing storages of information, we just have to know how to use them to optimise the process of translation.&nbsp;</li><li>The speaker also raises the issue of pronouns in MT. The results that we usually get are masculine pronouns. MT is usually confused, it does not recognise genders properly, the suggestions may be all over the place.</li><li>Translators - afraid that MT companies in return for the access to their service will use their data</li></ul><div><br>It was a truly interesting conversation, which allowed me to take a closer look at machine translations from a different perspective - the specialist in the field.</div><div><br>https://open.spotify.com/episode/6TK3Q6gANG64tjnmfwMqoC?si=yBcl7SP_TBuC-5ObzfPbdw&amp;nd=1<br><br></div>]]></description>
         <enclosure url="https://open.spotify.com/episode/6TK3Q6gANG64tjnmfwMqoC?si=yBcl7SP_TBuC-5ObzfPbdw&amp;nd=1" />
         <pubDate>2023-01-26 15:52:35 UTC</pubDate>
         <guid>https://padlet.com/juliaszmidt1/CAT/wish/2457810994</guid>
      </item>
   </channel>
</rss>
