Forum: SDL Trados support
Topic: Studio 2014 11.0.3688.0
Poster: Shai Nave
Post title: Checking the measurement format
[quote]Enrico C - ECLC wrote:
I want "1,23" mm in a 20 item list, i change the first item and it's all ok; i change the second item (sometimes autopropagation doesn't work with numbers, that's another issue) as "1,45 mm" and immediately the first one goes from "1,23 mm" to "1,23mm". I have to lock segments to make all this work.
[/quote]
Have you checked: File > Options > [Relevant Language Pair] > Translation Memories and Automated Translation > Auto-substitution > Measurements to make sure that the unit of measurement format setting is in ling with your preferences/requirements?
The slowness when editing terms is not really a problem (in the sense of something that doesn't work as supposed to) or incompatibility, as I've tried to explain here:
[quote]Shai Nave wrote:
The slowness that you are referring to is "by design", a side effect of adapting to Oracle's security concept. This concept requires components to be digitally signed, and the slowness occurs when the Java Runtime Environment verifies these signatures. It should be noticeable only the first time editing a term in a session, but from my experience it usually occurs for the following terms as well.
The benefit from all of this is a better integration that should reduce the amount of security prompts and tweaking - which is quite an issue for some users - and overall make the user experience more stable and reliable (the latter got off to a bad start, but hopefully this was solved).
I think that this is an acceptable trade-off in the interim, but strongly believe that SDL should drop Java altogether as a long-term security solution and for a better user experience.[/quote]
Topic: Studio 2014 11.0.3688.0
Poster: Shai Nave
Post title: Checking the measurement format
[quote]Enrico C - ECLC wrote:
I want "1,23" mm in a 20 item list, i change the first item and it's all ok; i change the second item (sometimes autopropagation doesn't work with numbers, that's another issue) as "1,45 mm" and immediately the first one goes from "1,23 mm" to "1,23mm". I have to lock segments to make all this work.
[/quote]
Have you checked: File > Options > [Relevant Language Pair] > Translation Memories and Automated Translation > Auto-substitution > Measurements to make sure that the unit of measurement format setting is in ling with your preferences/requirements?
The slowness when editing terms is not really a problem (in the sense of something that doesn't work as supposed to) or incompatibility, as I've tried to explain here:
[quote]Shai Nave wrote:
The slowness that you are referring to is "by design", a side effect of adapting to Oracle's security concept. This concept requires components to be digitally signed, and the slowness occurs when the Java Runtime Environment verifies these signatures. It should be noticeable only the first time editing a term in a session, but from my experience it usually occurs for the following terms as well.
The benefit from all of this is a better integration that should reduce the amount of security prompts and tweaking - which is quite an issue for some users - and overall make the user experience more stable and reliable (the latter got off to a bad start, but hopefully this was solved).
I think that this is an acceptable trade-off in the interim, but strongly believe that SDL should drop Java altogether as a long-term security solution and for a better user experience.[/quote]