| Infos and explanations. Wordfast || Jan 29, 2003 |
This WILL take some testing, but here are some informations you should have :
1. a pxf file is a compressed file. Right click on it, select \"open with\", and open with winzip. Winzip will open it like any other archive, and you will have different files including always at least 2 language files. In my case, \"*.eng\" and \"*.fra\"
You can open the target language file in Word. You will see each line finishing by
\"-#\" where # is the number of the segment
Now, you will have to protect the segment markers - with wordfast, apply the external tag style (using a search and replace with options). You have to study the files you have to see how they are made, so that you can tag properly and restore that exact format.
Once tagged, use wordfast and translate only the target file. When your translation is completed and reviewed, don\'t forget to add an \"*\" after each segment number to tell transit the segment was approuved. Otherwise, you will have to go through the whole file in transit
The same applies for the other files, terminology, ...that you find in the decompressed archive. Open in Word, recognize paterns of information, and convert in the format you want, while remembering that if you are expected to update, you will have to know how to convert it back as well. (or take note of the corrections/additions separately, so that you can enter them in transit. That\'s easy enough.)
Before you try anything, make a copy of the original PXF file with an other name, and work on that. When you think you have made it to prepare your target file, (note that you don\'t have to touch the \"source\" file at all) translate about 10 segments, make a copy, clean that copy and reconstruct the original archive. Then, receive the reconstructed archive with transit satellite PE as a usual project, and see what happens. try to \"send\" that project to see if the project does compile. When everything works fine (be ultra careful that nothing is missing.), you have found how to do it and you will be able to handle transit format with wordfast, DV, or even antics such as trados.
Don\'t forget that your project may include several files to translate, and some files already translated, that Transit use as a TM for fuzzy matching. If you have already translated files, you must convert those into a TM and use that TM in wordfast.
It all sound very complicated, but it may pay off once you know how to do it, because, between us, transit satellite is a real pain, where you can\'t configure anything, can\'t spell check unless you bought the addition, can\'t search context, can\'t use other ressources, and if your PM forgot to put references INSIDE the pxf. gee, what a pain!
Hope this helps. You need to take time and experiment. Since I only worked on tight projects with transit, I never had the time to do it all the way, but with testing I\'m pretty sure it can be done.
You can contact me at email@example.com. I\'m quite interested by the results, and I can help debug the problems you meet.
| || || |