• Replies 37 replies
  • Subscribers 440 subscribers
  • Views 15180 views
  • Users 0 members are here
Options
Related

SDL Trados Studio 2017 is coming...

Daniel Lifton

We are delighted to announce that the latest version of SDL Trados Studio 2017 is coming soon. SDL Trados Studio 2017 will bring revolutionary innovation to help you translate faster and ensure high quality translations - including a totally transformed, personalized Machine Translation Experience. 

Here are just some of the new features included in SDL Trados Studio 2017:

AdaptiveMT 

Our AdaptiveMT engines self-learn from your post edits, so your MT output is unique to your style, content and terminology. 

upLIFT technology 

Our upLIFT technology will help you translate new segments faster, even when you do not have a Translation Memory match. Studio will now automatically find even more matches for you, so you don’t have to.

The upLIFT technology will also use your trusted resources to help repair fuzzy matches.

To find out more about SDL Trados Studio 2017, please visit our website: 

If you are a freelance translator, click here>>

If you are a Language Service Provider, click here>>
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • in reply to Wojciech Matyszkiewicz
    Hello Wojciech,

    Probably not worth it at this stage... although we do like "hot under the collar" beta testers :-) Every time we finish a major release I go through the Beta community and remove everyone from the Beta other than those who contributed, so I have a clean sheet each year, and the ones who contributed have an opportunity to continue to feedback between releases to the developers and product management teams if they wish.

    I keep a list of interested people too, so I'll add you to this list and definitely involve you from the start next time around.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Looking forward to the new release. I just thought I would give some feedback about my experience with the Studio 2015 user interface.

    - Preview: I tried Preview mode previously and just tried it again in Studio 2015 SR2. My computer has a very fast processor and all files are on a SSD. Regardless of this, there is a 2 to 3 second lag and the cursor disappears when changing from one segment to another, or confirming a segment. This occurs in Normal or Print Mode, in Preview or Live Preview modes. Nice idea, but unusable in practice as it unacceptably interferes with the flow of translation, in particular my flow of thought.

    - Windows for Termbase Search, Termbase Viewer, Translation Results, Concordance, etc.: I tried to relieve the crowding on my display by separating these windows from the main window and moving them to another display. I wanted them to move to the background unless I needed them, but implementation is inconsistent. If the windows are pinned, then whenever I move to the main window, the pinned windows on the other display also move to the foreground. If the windows are not pinned, then using Concordance (Ctrl-F3), for example, performs the concordance search, but does not move the window to the foreground, forcing me to manually find the window and bring it to the foreground. Nice idea, but essentially unusable in practice, so I am forced to stuff all windows into one display.

    - Studio editor and Dragon: Studio can suffer sudden long pauses or even freeze when dictating into segments, and text in segments cannot be edited using normal Dragon commands. In my view this makes the Studio editor unusable in practice with Dragon.

    Studio commands and Dragon: Unlike other programs, such as Word, there are many Studio commands that simply do not have keyboard shortcuts, forcing you to use the mouse, which interrupts the flow of work when using Dragon. In addition, I use the filters a lot when checking terminology. When the cursor is manually placed in the input field in the View->Display Filter ribbon it disappears into limbo, requiring a second click before the cursor "sticks" in the field. This forces me to click, pause and click again before I can type text. In my opinion, Studio commands are cumbersome and essentially cannot be performed using Dragon.

    As a result, when translating files with large sections of new text, I generally use Studio as a glorified terminology reference tool.

    My standard procedure is to create a PDF file from the source file to use a reference while translating and then I use Dragon to dictate segment by segment into a Word file. When I have translated a section of text, I use a Dragon command to collect a list of segments from the Word file, and another Dragon command to insert them one after the other into the segments in Studio. I then do a final review of the segments and confirm them.

    I only use Trados during this process to check the concordance for terms or phrases that I think may be in the TM, or check a term in a termbase.

    To summarise, I use a PDF file to refer to the source text because Studio Preview is essentially unusable due to long lags. I dictate into a Word file and use Dragon commands to transfer groups of segments from Word to Studio because the Studio editor and Studio interface are essentially unusable with Dragon.

    I am looking forward to Studio 2017, but Paul has already indicated that the user interface is a low priority for the future, so I will probably continue using Studio as a glorified terminology reference tool for the foreseeable future ... Looking forward to a possible change in priorities.

    Best regards,
    Bruce Campbell
    A S A P Language Services
  • It's been 3 years living with messed up menus (since I got my first hi-dpi display). I do hope this will finally be fixed now because every other computer has at least WQHD if not UHD display.
  • in reply to Lennart Luhtaru

    Hi Lennart,

    Have you tried resolving this problem by following the details in Workaround 3 from this KB article?

    http://kb.sdl.com/#tab:homeTab:crumb:7:artId:4959

    I resolved many hi-res issues with this workaround for users experiencing the problem you described.

    Studio 2017 should not have this problem, but in the meantime you might be glad to know of this one.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Is it a mistake or is Studio 2017 available for download from the ftp already? Hush, hush.
  • in reply to Paul
    HI Paul,

    Sorry for answering so late, but I somehow lost the track of this thread. It's a very good news and I would be very glad to participate in the future beta programme! Looking forward to it.
    Do I need to register anywhere to gain access?

    Cheers,

    Wojciech
  • in reply to Wojciech Matyszkiewicz
    Hi Wojciech,

    I close the Beta each time as we always have far too many people in there who don't contribute at all, so the best thing to do is drop me an email or ask in here, as soon as we start sharing info on the next release (some time away now!!).

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub