Blogs to follow

Here are a couple of blogs I'm going to be following:

• Translation Tribulations
• eMpTy Pages (on machine translation and the industry thereof)

It's really shocking how little I know about my adoptive industry.

General TTX utility

So File::TTX may be slipping ever closer to irrelevance, but I'm still using it for a number of things. The only problem is, it's a pain always having to write a special-purpose Perl script just to change, say, the source language of a TTX.

Obviously, a command-line program would be the first step towards usability. (And way easier than a GUI program, obviously.) Let this stand as my to-do for that command-line utility.

Also: I think it's time to admit that I'm going to write the UI portions of the Xlat project in Decl, not plain Perl. This will probably require the definition of a Xlat::Declarative module. (That's a good thing.)

Automotive engineering glossary HU>EN

Wow! This is a great find!

Terminology

Another non-Xlat post!

Automotive terminology is kind of tricky and I'm finding it hard to find good references - although I'm seeing more demand. Here are a couple of links not to forget.

• A list of glossaries from ATS Group.
• Translation Journal has a short glossary.

Second topic: I really want to mine the SAP help site for accounting terminology. Here's just a teaser link that's been open on my browser for a couple of weeks now - the technique is simple. Google "site:help.sap.com xxx" for a likely term, then replace the language in the link with "en". Then align your results. It works! A list of likely terms (from a tagger, perhaps) is the right place to start.

A generalized terminology research framework would be useful.

File::TTX 0.03 released

I haven't been moving very fast on this project, have I?

That whole MT project

OK, so the post-editing project I foolishly agreed to help with consisted of:

• OCR with Able2Extract
• MT with a mixture of (I think) Google Translate and Systran
• First-pass proofreading
• Second-pass post-editing

So let's talk about that. A far, far better workflow would have been:

• OCR with whatever
• Source-language spell checking and correction
• Identification of key phrases and terminology as cues for MT
• TRADOS or similar to avoid rework of existing sentences
• MT with whatever
• Target-language spell checking, feeding results back through MT until at least everything is English
• First-pass post-editing
• Second-pass proofreading

This workflow uses (or at least could use) the exact same tools as above, but without the introduction of errors at each step that make later steps impossible to manage. First-pass post-editing should be done by a bilingual translator, using specialized post-editing tools (not yet written) plus a normal translation memory (and of course the TM should also be used before passing text off to the MT stage). Systematic errors should be documented and recycled through the MT process.

One key insight: terminology research really starts to get a lot more important in this workflow than in normal CAT.

More thoughts on a non-stupid text editor

I'm doing some post-editing for Portuguese today (I know, I know, never do MT post-editing, but this customer is a good one and I just couldn't say no). As usual with post-Systran work, there is a lot of dragging and dropping involved, and frankly? Word freaking sucks at dragging and dropping. Why should that be? Why can't I drag a word from the end of a punctuated sentence into its middle and have Word get the spacing right?

The mind boggles.

So it looks like I'm just going to have to break down and address non-stupid text editing again.