Very slow Studio Autopropagation with numbers Thread poster: Steve Yeadon
|
|---|
Hi
I'm working in Studio on a technical catalogue which naturally contains a lot of numbers. Autoprop doesn't like them at all. If I get a fuzzy match on a several digit number, revise it and try to confirm and move on Autoprop takes some two minutes to prossess it, while a sit there 'calmly' watching the little wheel go round.
Anybody else suffered this and found a cure? All tips very welcome. I have tried program restart.
Regards
Steve
<... See more Hi
I'm working in Studio on a technical catalogue which naturally contains a lot of numbers. Autoprop doesn't like them at all. If I get a fuzzy match on a several digit number, revise it and try to confirm and move on Autoprop takes some two minutes to prossess it, while a sit there 'calmly' watching the little wheel go round.
Anybody else suffered this and found a cure? All tips very welcome. I have tried program restart.
Regards
Steve
[Edited at 2009-12-10 14:13 GMT] ▲ Collapse
| | | | Tom Fennell
United States
Local time: 18:45
Russian to English
+ ...
| Even worse with long numbers | Dec 14, 2009 |
I was working on a project with 20-digit bank account numbers, and not only did Trados not propagate them quickly, it propagated false numbers!
Worse, it kept re-inserting the wrong numbers even after the correct ones had been "translated."
They stayed in place only after review confirmation.
| | | | | Related problem with context matches | Dec 14, 2009 |
I've previously had problems too with long serial numbers.
On my current project from Swedish, which uses a space as the thousands separator, "600 000 timmar" becomes "600 hours" as a context match, "540 000 timmar" becomes "540 hours", etc.
The customization features need to be enhanced, I'd say.
| | | | | Vanishing commas | Jan 21, 2010 |
I'm having a somewhat similar problem with large numbers. There are commas for every three digits in the source text and I've been using that same method with the target text. They seem to auto-prop right each time, but then the Context Match keeps automatically erasing the commas each time I enter one of those target segments. I wish there was a way to just turn "Context Match" off, as it's not working properly.
| | |
|
|
|
Kim Booth (X)
Local time: 01:45
German to English
| Same problem but options found | Feb 15, 2012 |
Feb 2012. I had exactly the same problem with a large catalogue and felt like throwing the computer out of the window due to the time it was taking. Once I calmed down I searched a bit and there is now a set of options to tame autopropogation which a... See more Feb 2012. I had exactly the same problem with a large catalogue and felt like throwing the computer out of the window due to the time it was taking. Once I calmed down I searched a bit and there is now a set of options to tame autopropogation which are described here.
http://producthelp.sdl.com/SDL%20Trados%20Studio/client_en/Ref/U-Z/Options/Options_Auto-propagation.htm
I chose "Always"
When this option is selected, you will always be asked if you want the auto-propagated translation to be applied to a segment.
with which I can work just fine.
Hope that helps the next person who hits autopropogation hell. Maybe Trados should thinks about their defaults. ▲ Collapse
| | | | Susanne Rieg (X) 
Local time: 01:45
English to German
+ ...
| A way to avoid the problem | Feb 15, 2012 |
Best way to avoid the problem in Studio 2011 is to "display" "numbers only", mark all segments and simply "lock all segments". Or, if you want to see the numbers in Studio on the target side: copy to target, change segment status to "translated" and then lock all. Then go back to display all segments.
This way you can still use autopropagation for the remaining text and numbers only segments are not autopropagated
Unfortunately there is no filter for number-letter codes... See more Best way to avoid the problem in Studio 2011 is to "display" "numbers only", mark all segments and simply "lock all segments". Or, if you want to see the numbers in Studio on the target side: copy to target, change segment status to "translated" and then lock all. Then go back to display all segments.
This way you can still use autopropagation for the remaining text and numbers only segments are not autopropagated
Unfortunately there is no filter for number-letter codes (such as part numbers etc.) so you will need a regex to filter.
Sanne ▲ Collapse
| | | | Tatiana Nikitina
Russian Federation
Local time: 02:45
Member (2011)
English to Russian
+ ...
| The same problem | Mar 7, 2012 |
Thank you, Susanne. I faced the same problem yesterday in Trados 2011.
It's a pity that they haven't fixed the problem in Trados yet (I can see the topic was started in 2009). Has anybody written to them?
[Редактировалось 2012-03-07 05:09 GMT]
| | | | | Using the display filter | Mar 7, 2012 |
Hi,
Because Studio bases its number recognition on the culture sets relevant to your language pairs this can create problems usingt AutoPropogation in at least these two common scenarios:
1. Handling numbers in the source that don't match the expected cultures. So 1,234.56 where 1.234,56 was expected
2. Handling patterns... so 123.45.678.3A for example
The best way to handle these is to use the display filter and a regular expression to filter... See more Hi,
Because Studio bases its number recognition on the culture sets relevant to your language pairs this can create problems usingt AutoPropogation in at least these two common scenarios:
1. Handling numbers in the source that don't match the expected cultures. So 1,234.56 where 1.234,56 was expected
2. Handling patterns... so 123.45.678.3A for example
The best way to handle these is to use the display filter and a regular expression to filter on all the segments before translating the document. Then copy source to target (or translate the affected segments), make any changes in the target with search and replace (if necessary) and then lock the segments before tackling the rest of the document.
We can help with the regular expressions if needed but some common ones that are quite useful would be;
^[\d,.]+$
Number only segments containing periods or commas
^\D+$
Segments that contain no numbers at all
[^\d.,]
Display everything apart from number only segments (again uses commas and periods)
^\d{2}\.\d{3}\.\d{3},\d{2}
Jerzy posted this one on TW_Users last week and it will find a very specific number pattern in the format xx.xxx.xxx,xx
These are probably quite handy to know about and the regex display filter is very powerful in this regard. Might be good to see what expressions other users have come up and build a little library. I'd also recommend an application called regexbuddy that is very good for building expressions, testing them and also saving in a catalogued library for reuse later. You can find this here if you are interested:
http://www.regexbuddy.com
Regards
Paul ▲ Collapse
| | |
|
|
|
| But what happens with percentages? | Mar 7, 2012 |
In Studio 2011, I have the values in the source:
20%
15%
10%
0%
Yet, when I copy source to target for the first one (20%),
I somehow get a mysterious space between number and sign, which makes the whole display funny:
% 20
% 15
% 10
% 0
Why oh why does this happen with auto-propagate?
| | | | | Must be your TM or your settings... I think | Mar 7, 2012 |
Hi Doron,
I did a quick test, english to hebrew with a new TM and after confirming the first segment I get this:
You can change the settings for spaces inbetween units in Tools - Options - Language Pairs and then your specific language pair rather than All language Pairs... See more Hi Doron,
I did a quick test, english to hebrew with a new TM and after confirming the first segment I get this:
You can change the settings for spaces inbetween units in Tools - Options - Language Pairs and then your specific language pair rather than All language Pairs, then under Translation Memory and Automated Translation - Auto-substitution - measurements.
Maybe you have something set in here that is causing the spaces to be added?
Even so, you could handle this with a regular expression and tackle all the segments containing percentages first... but I think your example should be handled without a problem. If you hhave a file you can share with me I'd be happy to look at it.
Regards
Paul ▲ Collapse
| | | |
That seems to be it, buried so deep in the Options that I'd never have found it without your help...
| | | | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » Very slow Studio Autopropagation with numbers | Trados Studio 2022 Freelance | The leading translation software used by over 270,000 translators.
Designed with your feedback in mind, Trados Studio 2022 delivers an unrivalled, powerful desktop
and cloud solution, empowering you to work in the most efficient and cost-effective way.
More info » |
| | TM-Town | Manage your TMs and Terms ... and boost your translation business
Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
Translation news related to SDL Trados
