Fusion or confusion?
It's Christmas time! Let's check it out if the Word behaves nicely at this time. It is somehow amazing to see this "carbonized" program working together with Cocoa application.
The Word 2004 sure does better with unicode strings than earlier versions. Due to its classic text engine, however, it never gets rid of trouble processing multi-byte characters mixed in single-byte language. Well, I guess the old soldier came too far to turn back...
The Word 2004 sure does better with unicode strings than earlier versions. Due to its classic text engine, however, it never gets rid of trouble processing multi-byte characters mixed in single-byte language. Well, I guess the old soldier came too far to turn back...
posted by hiruneko at 11:30 PM
10 Comments:
So, that looks like just what I'm looking for... but what exactly do I need to get this going on my Mac? And how do I get started?
Any help at all would be appreciated!
Lara
dame.lac@gmail.com
Hi Lara. Why don't you start with the user's guide? You can open this online manual from Help > AppleTrans Users Guide menu item.
It is a plugin called WildCAT that you might notice in the clip in this post. Check it out in this blog or with SIG for more information.
Thank you. I'll check out WildCAT. I've read the User's Guide from cover to cover and can't figure out how to get the source text in a Word document automatically replaced by the target text during translation. I have figured out how to do basic translation/corpus building within Apple Trans. Just not on a Word document simultaneously. I also experimented with an RTF file, but lost the headers/footers and footnotes in the process... And haven't figured out how to not lose them from the UG yet, either...
Hi again. The RTF reader/writer that AppleTrans hired is not fully compatible with the Word's proprietary formats. You may not expect AppleTrans (or many other Cocoa based editors as a matter of fact) to retain those Word document properties - header/footer, hyperlinks, bookmarks, inline graphics, etc.
WildCAT might help you work it around. But still you would lose some text attributes in the process. It sometimes appears to me faster copying text content directly from a Word document, translate it in AppleTrans, and copy it back to the original document. This is what one of AppleTrans friends suggested in his posting a while ago.
Hummm.... If I only needed to do the copy-paste-translate-copy-paste routine for headers and footers in Word, that might work. But I'm currently using WordFast so...
WHich version of WildCAT does this film feature? And is this version available to the public anywhere? I have downloaded and installed WildCAT 1.1 but it only offers me the opportunity to contact to InDesign (which I don't use). It would be interesting to at least try it out with Word. Do I have to work out how to write my own filter to do that or is there another version of WildCAT somewhere I should know about?
I have the same question as Tam McTurk, now that I've taken a look at WildCAT...
It's an additional script for WildCAT. Still in early stage but It will be posed soon for your test run.
I look forward to it. Good timing given the debates on the MacLingua forum about the relative merits of the various TM alternatives :-)
The script is up on the SIG by the time you read this. I hope people do not expect too much out of it. MS Word assumedly offers fairly good support of AppleScript, but still it is puzzling you because of a few missing pieces. Feel like talking to my gramma... (oops)
Post a Comment
<< Home