![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
alexpgpThere are few things as discouraging as having an application spew technical language at you when things go wrong (except, perhaps, having the application not do a blessed thing to clue you in on said fact).
In any event, there I was,dead in the water, twelve miles off Shanghai... oops, wrong story...
Frustration with the way that Wordfast handles this one particular espèce of file (crazy segmentation) led me to essay using MemoQ for these files, wherein I learned a couple of things:
(1) I should have "does not handle numbers gracefully" come up on the MemoQ splash screen whenever I invoke it. The workarounds offered in various places simply suck, to the point where I have to do extra proofreading work.
(2) There are some kinds of XML characters that not only survive importation from text TM files, but are also not displayed by MemoQ. By itself, this is not a big deal. However, inserting these XML characters in the MemoQ output intended for consumption by Microsoft Word causes the latter to complain bitterly about not being able to open the file.
I found this out because Word actually told me the location of the error (illegal XML character in line 2, column so-and-so of word/document.xml), and the curious circumstance that .docx files are basically zip files (changing the extension to .zip changes what application opens them).
So, I ended up opening the cited file in Notepad++ and tracked down the problem, which turned out to be problems (as said types of characters occurred several times in the text), and in the end was able to repackage the zip file, rename it back to .docx, and open it in Word.
In the end, I probably would've saved a few minutes by retranslating the blessed thing from scratch in Wordfast, but I would not have learned this neat little прием.
Cheers...
In any event, there I was,
Frustration with the way that Wordfast handles this one particular espèce of file (crazy segmentation) led me to essay using MemoQ for these files, wherein I learned a couple of things:
(1) I should have "does not handle numbers gracefully" come up on the MemoQ splash screen whenever I invoke it. The workarounds offered in various places simply suck, to the point where I have to do extra proofreading work.
(2) There are some kinds of XML characters that not only survive importation from text TM files, but are also not displayed by MemoQ. By itself, this is not a big deal. However, inserting these XML characters in the MemoQ output intended for consumption by Microsoft Word causes the latter to complain bitterly about not being able to open the file.
I found this out because Word actually told me the location of the error (illegal XML character in line 2, column so-and-so of word/document.xml), and the curious circumstance that .docx files are basically zip files (changing the extension to .zip changes what application opens them).
So, I ended up opening the cited file in Notepad++ and tracked down the problem, which turned out to be problems (as said types of characters occurred several times in the text), and in the end was able to repackage the zip file, rename it back to .docx, and open it in Word.
In the end, I probably would've saved a few minutes by retranslating the blessed thing from scratch in Wordfast, but I would not have learned this neat little прием.
Cheers...
