Forum: SDL Trados support
Topic: tmx imports takes too much time
Poster: Andrew052
Post title: Preparation Procedure
[quote]SDL Support wrote:
If the TMX is full of tags, contains duplicates, filled with placeables etc. then it could indeed take a long time as Studio will do what it can to remove content it does not need.
When you say "prepare"... what do you mean by this?
Regards
Paul [/quote]
I have a number of files, 20 files, each of which contains 50 pages. These documents are PDFs with a lot of graphics, tables and schematics. I would like to prepare the "pseudo-memory", i.e. I would like to do the following:
1. create a list of folders,
2. name them, 1, 2, 3 ...
3, place an original file and a translation of a file in folder 1
4. open file 1 in trados (click "copy source to target if no match is found" before uploading the file to trados).
5. open file 1 in editor
6. select all segments
7. mark them as "approved"
8. update main translation memory, typing "1" in the field setting (you need to create a TM with the following field setting: column 1: something like "Register Number", colum 2: Number).
Result of the procedure:
1. open a file to be translated in editor. If you have a match in your file versus file 1, you TM results window will display this match and to the right you will see "1" in your TM results window. When you see a match, open folder 1 and copy/paste the needed sentences in your translation.
This approach should be used for a particular customer in case, when you expect a lot of matches between the files translated and files translated earlier, provided that 1) you have pdfs that are very difficult to align (otherwise I would just align them in memo), 2) you expect a lot of matches or need to develop from scract an extensive background termbase for a customer.
---
Preparation in Memo:
I would just upload all files at once in a new project. I would create a TM named "1", then open file 1 in the editor, copy source to target across the file, approve them, export tm in tmx . Then I would open trados and import tmx 1 into the TM, typing '1" in the last screen of the tmx import procedure.
P.S.
I have successfully imported large numbers of files earlier as per procedure "memo prep + tmx import with field setting used into trados TM", but this time for some reason it takes a very long time.
It's actually faster to do the update memory task as per above versus memo-created import into trados TM. But, the problem is that I would need to do a lot of actions, which is tedious, but when I upload a tmx into trados TM, I would just open two windows of trados 2014. I would place one of them so that I can see the runner at the bottom of my screen and when it's gone I would do the next tmx import.
So, my question is:
How does "accuracy-speed" runner work? Can I just go to the middle and expect satisfactory results. I mean, I have 1K pages and do not want to manually check the results of the runner changes, as, presumably, the outcome for one of tmxs may significantly differ from the outcome for the tmx runner changes...
Topic: tmx imports takes too much time
Poster: Andrew052
Post title: Preparation Procedure
[quote]SDL Support wrote:
If the TMX is full of tags, contains duplicates, filled with placeables etc. then it could indeed take a long time as Studio will do what it can to remove content it does not need.
When you say "prepare"... what do you mean by this?
Regards
Paul [/quote]
I have a number of files, 20 files, each of which contains 50 pages. These documents are PDFs with a lot of graphics, tables and schematics. I would like to prepare the "pseudo-memory", i.e. I would like to do the following:
1. create a list of folders,
2. name them, 1, 2, 3 ...
3, place an original file and a translation of a file in folder 1
4. open file 1 in trados (click "copy source to target if no match is found" before uploading the file to trados).
5. open file 1 in editor
6. select all segments
7. mark them as "approved"
8. update main translation memory, typing "1" in the field setting (you need to create a TM with the following field setting: column 1: something like "Register Number", colum 2: Number).
Result of the procedure:
1. open a file to be translated in editor. If you have a match in your file versus file 1, you TM results window will display this match and to the right you will see "1" in your TM results window. When you see a match, open folder 1 and copy/paste the needed sentences in your translation.
This approach should be used for a particular customer in case, when you expect a lot of matches between the files translated and files translated earlier, provided that 1) you have pdfs that are very difficult to align (otherwise I would just align them in memo), 2) you expect a lot of matches or need to develop from scract an extensive background termbase for a customer.
---
Preparation in Memo:
I would just upload all files at once in a new project. I would create a TM named "1", then open file 1 in the editor, copy source to target across the file, approve them, export tm in tmx . Then I would open trados and import tmx 1 into the TM, typing '1" in the last screen of the tmx import procedure.
P.S.
I have successfully imported large numbers of files earlier as per procedure "memo prep + tmx import with field setting used into trados TM", but this time for some reason it takes a very long time.
It's actually faster to do the update memory task as per above versus memo-created import into trados TM. But, the problem is that I would need to do a lot of actions, which is tedious, but when I upload a tmx into trados TM, I would just open two windows of trados 2014. I would place one of them so that I can see the runner at the bottom of my screen and when it's gone I would do the next tmx import.
So, my question is:
How does "accuracy-speed" runner work? Can I just go to the middle and expect satisfactory results. I mean, I have 1K pages and do not want to manually check the results of the runner changes, as, presumably, the outcome for one of tmxs may significantly differ from the outcome for the tmx runner changes...