problems with xml in WF Classic and Pro Автор темы: Krzysztof Kożurno
|
|---|
Hello,
I’ve received a sizeable xml file to be translated from English into Polish.
The problem is Word (2003) cannot open it. When I try to open (either after coping, pasting and saving the contents as UTF-8 or directly), Word displays an error message saying there is something wrong with the content. (Wrong parameter, error location line: 6, column 34, though these number vary when opening the file on different machines. A more recent Word release said it’s a DTD issue and indi... See more Hello,
I’ve received a sizeable xml file to be translated from English into Polish.
The problem is Word (2003) cannot open it. When I try to open (either after coping, pasting and saving the contents as UTF-8 or directly), Word displays an error message saying there is something wrong with the content. (Wrong parameter, error location line: 6, column 34, though these number vary when opening the file on different machines. A more recent Word release said it’s a DTD issue and indicated a different location within the file.)
Thus I cannot even see, if I can do this job using my preferred WF Classic.
When I tried WF Pro, I’ve read the instructions on how to prepare a properties file, failed to understand the step where I should actually get the prefixes and suffixes from. I tried using each of the sample properties files provided by WF Pro support, as reading the forum I understood this is some typical stuff (but I am not sure about that).
I am not sure, if there is anything wrong with the file as I imported it effortlessly into memoq, which I would use, willy-nilly, if I had my own license. I am using it under a license provided by my client, so it will expire before I finish the job.
I am quite lost what to do not to lose too much time tackling it. The job is big, the deadline short and too many problems.
I am not a code nerd, but can understand simple issues, if needed.
Thanks in advance for any reasonable suggestions.
Krzysztof ▲ Collapse
| | | | | Export to RTF from memoQ | Jan 29, 2013 |
big_fish wrote:
I am not sure, if there is anything wrong with the file as I imported it effortlessly into memoq, which I would use, willy-nilly, if I had my own license. I am using it under a license provided by my client, so it will expire before I finish the job.
Yes, memoQ has much better support for XML than Wordfast Pro. Since you were able to obtain a usable output in memoQ, you could export the document to bilingual RTF and translate it with Classic. You just need to rename the mqInternal style to tw4winInternal so that tags are recognized as placeables in Classic.
Once your translation is ready, you can reimport the RTF back into memoQ and export the translated XML from there. If your license is no longer available, you can install the trial version (not possible if you have already installed the trial on the same computer). memoQ is a good investment anyway, for instance to take care of files and formats Wordfast can't cope easily with.
| | | | | only memoq can handle it | Jan 29, 2013 |
Dominique Pivard wrote:
Yes, memoQ has much better support for XML than Wordfast Pro. Since you were able to obtain a usable output in memoQ, you could export the document to bilingual RTF and translate it with Classic. You just need to rename the mqInternal style to tw4winInternal so that tags are recognized as placeables in Classic.
Once your translation is ready, you can reimport the RTF back into memoQ and export the translated XML from there. If your license is no longer available, you can install the trial version (not possible if you have already installed the trial on the same computer). memoQ is a good investment anyway, for instance to take care of files and formats Wordfast can't cope easily with.
Thank you for your suggestion.
I believe this is what I would try to do. I am still waiting as a DTD file is definitely missing there. And my other tools don't accept the file. Perhaps if I get it, I will be able to process with Classic in Word, though I am generally sceptical about this method as I am afraid it will ultimately ruin the file code.
Still there is the mystery of "preparing" the *.properties file. Is this the painstaking procedure that may take as long as the translation itself, or longer? Definitely seems I cannot prepare it myself.
| | | | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » problems with xml in WF Classic and Pro | Trados Business Manager Lite | Create customer quotes and invoices from within Trados Studio
Trados Business Manager Lite helps to simplify and speed up some of the daily tasks, such as invoicing and reporting, associated with running your freelance translation business.
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 Wordfast
