[Madlug] sed script behaving oddly

[Steve Herrick]

On Mon, Nov 17, 2008 at 8:05 PM, Will Maier <willmaier at ml1.net> wrote:

> Whoa -- that is long. I'm not convinced that sed is the best tool to
> do what I think you're doing (ie, natural language processing).

Yup, pretty long. I've looked at NLP a bit, and it seems broader than
what I want to do, which is translation.

> I assume 'CAT' here is a term of art != cat(1).

Yeah, sorry. Computer-Assisted Translation. No serious translator
would be without one, but there's considerable controversy about which
is best, whether or not to stick to open-source ones, etc. My issue is
that I want one that works from the command line, which is why I went
with vim/sed. BTW, wanting a CLI isn't because I dislike GUIs, it's
because I do the bulk of my work on an N800 (during down time at my
night job), so efficiency and access are at a premium. I simply can't
run normal CAT software, but I do have ssh.

Either way, I still
> recommend something > sed. For example, Python has the Natural
> Language Toolkit[0], about which quite a bit has been written[1].

Interesting. At first, I though you were referring to another highly
promising project, the Translate Toolkit
(http://translate.sourceforge.net/wiki/), also written in Python.
Frankly, I think this will give me better results, because it's
exactly what I want, as opposed to being related to what I want. I'd
be more enthusiastic still if the project were farther along (read:
easier to install).
-- 
Steve Herrick

Maybe we can eventually make language a complete impediment to understanding.
- Hobbes the tiger