Pagine: [1 2] > |
Studio 2017 SR1 Yay! Iniziatore argomento: Wojciech_ (X)
|
Wojciech_ (X) Polonia Local time: 18:28 Da Inglese a Polacco + ...
Am I the only one to have noticed the SR1 for Studio 2017? I'm particularly interested in the LookAhead function - it sounds fantastic! | | |
I've just downloaded and installed it; everything looks good so far, but the links in their email take you to a wrong web page, which has nothing to do with SDL the company... I hope the software has been more thoroughly checked than the email message.
[Edited at 2017-07-25 15:45 GMT] | | |
error message | Jul 25, 2017 |
'an error occured and the program was aborted' that's what I got, so I'm not that excited. | | |
Studio 2017 SR1 | Jul 25, 2017 |
Hi, Can you share the URL in question? Just to clarify, the email does contain links to several SDL official websites such as; oos.sdl.com (account management), gateway.sdl.com (support), and goto.sdl.com (documentation downloads). Was it one of these? Many thanks David Epameinondas Soufleros wrote: I've just downloaded and installed it; everything looks good so far, but the links in their email take you to a wrong web page, which has nothing to do with SDL the company... I hope the software has been more thoroughly checked than the email message.
[Edited at 2017-07-25 15:45 GMT] | |
|
|
Pavel Slama Regno Unito Local time: 17:28 Membro (2014) Da Inglese a Ceco + ... Unrepaired fuzzy matches | Jul 25, 2017 |
So how does one pop in the unrepaired fuzzy matches? | | |
The link has been fixed already.
[Edited at 2017-07-25 17:55 GMT] | | |
Roy Oestensen Danimarca Local time: 18:28 Membro (2010) Da Inglese a Norvegese (Bokmal) + ... I hope everything is OK then, since this sounds suspect to me | Jul 25, 2017 |
Epameinondas Soufleros wrote: I've just downloaded and installed it; everything looks good so far, but the links in their email take you to a wrong web page, which has nothing to do with SDL the company... I hope the software has been more thoroughly checked than the email message.
[Edited at 2017-07-25 15:45 GMT] I am always wary of clicking a link in an e-mail since it often will be a phishing message from someone else than the company it is supposed to be from. Roy | | |
Wojciech_ (X) Polonia Local time: 18:28 Da Inglese a Polacco + ... AVVIO ARGOMENTO
Multiterm has a slider for browsing through terms! Finally! Shocker #2... No! I knew that there must be a bug and there is a huge one for Polish users! It's impossible to insert small "ł" (alt+l) letter now in the editor window! This refers only to the small letter, the large one is OK. SDL, please, do something about it ASAP!
[Edited at 2017-07-25 20:57 GMT] | |
|
|
Natalie Polonia Local time: 18:28 Membro (2002) Da Inglese a Russo + ... Moderatore di questo Forum SITE LOCALIZER The problem must be related to your local settings | Jul 25, 2017 |
Wojciech_ wrote: It's impossible to insert small "ł" (alt+l) letter now in the editor window! This refers only to the small letter, the large one is OK. In my Studio all Polish letters can be inserted without any problem. I use the [Ctrl+Alt+letter] and [Shift+Ctrl+Alt+letter] shortcuts, though. Just check and replace the (alt+l) shortcut, it must be assigned to some other command. | | |
Wojciech_ (X) Polonia Local time: 18:28 Da Inglese a Polacco + ... AVVIO ARGOMENTO OK problem solved | Jul 25, 2017 |
Natalie wrote: Wojciech_ wrote: It's impossible to insert small "ł" (alt+l) letter now in the editor window! This refers only to the small letter, the large one is OK. In my Studio all Polish letters can be inserted without any problem. I use the [Ctrl+Alt+letter] and [Shift+Ctrl+Alt+letter] shortcuts, though. Just check and replace the (alt+l) shortcut, it must be assigned to some other command. Problem solved. Thanks, Natalie. I simply deleted all the shortcuts where "l" or "L" was used and now the small "ł" is back again! | | |
Emma Goldsmith Spagna Local time: 18:28 Membro (2004) Da Spagnolo a Inglese |
Erik Freitag Germania Local time: 18:28 Membro (2006) Da Olandese a Tedesco + ... Look ahead feature - productivity killer for neighbouring fuzzy segments? | Jul 26, 2017 |
Dear Emma, I've just read your blog, very interesting, thanks! I'm slightly worried about the fact that finding fuzzy matches from neighbouring segments now requires me to press three(!) keys (instead of no action required before). In my experience, it's not exactly a rare occurrence that similar segments immediately follow each other (in lists, for example). This rather sounds like a productivity killer to me. Wouldn't it be better if Studio automatically ... See more Dear Emma, I've just read your blog, very interesting, thanks! I'm slightly worried about the fact that finding fuzzy matches from neighbouring segments now requires me to press three(!) keys (instead of no action required before). In my experience, it's not exactly a rare occurrence that similar segments immediately follow each other (in lists, for example). This rather sounds like a productivity killer to me. Wouldn't it be better if Studio automatically performed a regular search when the LookAhead feature hasn't yielded anything?
[Edited at 2017-07-26 07:52 GMT] ▲ Collapse | |
|
|
Emma Goldsmith Spagna Local time: 18:28 Membro (2004) Da Spagnolo a Inglese Customise the shortcut | Jul 26, 2017 |
Erik Freitag wrote: press three(!) keys (instead of no action required before). In my experience, it's not exactly a rare occurrence that similar segments immediately follow each other (in lists, for example). This rather sounds like a productivity killer to me. Wouldn't it be better if Studio automatically performed a regular search when the LookAhead feature hasn't yielded anything?
[Edited at 2017-07-26 07:52 GMT] Well, you can easily customise the shortcut (File>options>shortcuts, browse to Look-up) to a shorter key combination. I see what you mean about Studio doing this automatically, but the whole point of LookAhead is that Studio is busy working on other segments while we're translating the active one. I've found it works really well and speeds up my productivity rather than killing it. In the case of a list, you might better switching off LooKAhead completely for that section. | | |
Erik Freitag Germania Local time: 18:28 Membro (2006) Da Olandese a Tedesco + ...
Emma Goldsmith wrote: I see what you mean about Studio doing this automatically, but the whole point of LookAhead is that Studio is busy working on other segments while we're translating the active one. I find this a bit illogical - shouldn't finding a match for the active segment have priority over finding matches for subsequent segments? In other words: Why should Studio wait for a key command before it starts searching the TM for fuzzy matches? After proceeding to a new segment, shouldn't the software rather use a sequence like this: - Insert match previously found by LookAhead.
- If LookAhead hasn't yielded anything: Repeat TM search in order to make sure that matches from the segments just before the active one are included. The search could even be limited to those one or two segments in order to speed things up.
- Start looking ahead for the following segments.
Or, yet another way of putting it: Why would anyone ever not want Studio to look for matches if LookAhead hasn't found anything? So why the need for a key command for this? Emma Goldsmith wrote: I've found it works really well and speeds up my productivity rather than killing it. That's good to know, I'll surely give it a try after the update.
[Edited at 2017-07-26 09:06 GMT] | | |
Erik Freitag wrote: Emma Goldsmith wrote: I see what you mean about Studio doing this automatically, but the whole point of LookAhead is that Studio is busy working on other segments while we're translating the active one. I find this a bit illogical - shouldn't finding a match for the active segment have priority over finding matches for subsequent segments? In other words: Why should Studio wait for a key command before it starts searching the TM for fuzzy matches? ... 2. If LookAhead hasn't yielded anything: Repeat TM search in order to make sure that matches from the segments just before the active one are included I read Emma's example in her blog post. The fact you won't be automatically presented with a fuzzy match for segments you have just translated, because Studio is too busy(?) with the following segments seems rather irrational to me... especially if this has suddenly become the way Studio behaves by default (I guess someone might even regard and report this as a 'bug'...). On a related note, I personally quite dislike the MT-centric road SDL has been consistently treading for a while now... but I guess that's just me... | | |
Pagine: [1 2] > |