Awesome!  Thanks for the advice (Flammie and Sushain).  To be honest, I'm
still not 100% sure on this.  The command above seems a little unintuitive
to me (perhaps because of the pipes :) ).  It seems like I would have to
have some deep knowledge of Apertium to reverse engineer that myself.
Perhaps after more study I'll understand it better.  In any event, I was
wondering whether or not Apertium can really meet my needs and it sounds
like it can.  You have given good advice for me moving forward, and even
provided some examples.  I will try what you suggest.

Thanks again for taking the time to point me in the right direction.

Joel

On Tue, Sep 8, 2015 at 11:05 PM, Flammie Pirinen <[email protected]> wrote:

> 2015-09-08, Joel Wenzel sanoi:
>
> > Also, if there is a command line version, it would be much easier for
> > me. I can find things on the wiki that imply that there is a command
> > line but I'm having trouble finding solid docs for it?
>
> I guess the developer documentation might have more clues to
> command-line usage. I'd say, follow installation whichever method[1],
> download language data and compile it[2]. Once you have a translator
> running on commannd line, you can start reverse-engineering how to
> input a word-form and POS (and other stuff) to get a translation.
> At this point, the command-lines that are used for translation are
> simply stored in a directory called modes. E.g. for apertium-en-eo
> mentioned in the docs:
>
>  svn checkout
>  https://svn.code.sf.net/p/apertium/svn/trunk/apertium-eo-en
>  cd apertium-eo-en/ 2011  ./autogen.sh
>  make
>  cat modes/en-eo.mode
>
>     lt-proc /home/flammie/Koodit/apertium-eo-en/en-eo.automorf.bin
>     |apertium-tagger -g
>     $2 /home/flammie/Koodit/apertium-eo-en/en-eo.prob
>     |apertium-pretransfer|apertium-transfer
>     -n
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.genitive.t1x
> /home/flammie/Koodit/apertium-eo-en/en-eo.genitive.t1x.bin
>     |apertium-transfer
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.t1x
> /home/flammie/Koodit/apertium-eo-en/en-eo.t1x.bin
> /home/flammie/Koodit/apertium-eo-en/en-eo.autobil.bin
>     |apertium-interchunk
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.antaux_t2x
> /home/flammie/Koodit/apertium-eo-en/en-eo.antaux_t2x.bin
>     |apertium-interchunk
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.antaux2_t2x
> /home/flammie/Koodit/apertium-eo-en/en-eo.antaux2_t2x.bin
>     |apertium-interchunk
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.t2x
> /home/flammie/Koodit/apertium-eo-en/en-eo.t2x.bin
>     |apertium-postchunk
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.t3x  /
>
> So, check the first command:
>
>     lt-proc /home/flammie/Koodit/apertium-eo-en/en-eo.automorf.bin
>
>
> buffalo
> ^buffalo/*buffalo$
> house
> ^house/house<n><sg>$
> hit
>
> ^hit/hit<n><sg>/hit<vblex><inf>/hit<vblex><pres>/hit<vblex><past>/hit<vblex><pp>$
>
> Unfortunately, apertium's English dictionary does not have any entries
> for buffalo, but to show the other ones (my mail client totally
> destroys this one though, just ignore repeated |'s):
>
> $ echo "^house/house<n><sg>$" |apertium-tagger
> -g /home/flammie/Koodit/apertium-eo-en/en-eo.prob
> |apertium-pretransfer|apertium-transfer
> |-n /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.genitive.t1x
> /home/flammie/Koodit/apertium-eo-en/en-eo.genitive.t1x.bin
> ||apertium-transfer
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.t1x
> /home/flammie/Koodit/apertium-eo-en/en-eo.t1x.bin
> /home/flammie/Koodit/apertium-eo-en/en-eo.autobil.bin
> |||apertium-interchunk
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.antaux_t2x
> /home/flammie/Koodit/apertium-eo-en/en-eo.antaux_t2x.bin
> ||||apertium-interchunk
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.antaux2_t2x
> /home/flammie/Koodit/apertium-eo-en/en-eo.antaux2_t2x.bin
> |||||apertium-interchunk
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.t2x
> /home/flammie/Koodit/apertium-eo-en/en-eo.t2x.bin
> ||||||apertium-postchunk
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.t3x
> /home/flammie/Koodit/apertium-eo-en/en-eo.t3x.bin
> |||||||lt-proc -g /home/flammie/Koodit/apertium-eo-en/en-eo.autogen.bin
> |||||||domo $ echo "^hit/hit<n><sg>$" |apertium-tagger
> |||||||-g /home/flammie/Koodit/apertium-eo-en/en-eo.prob
> ||||||||apertium-pretransfer|apertium-transfer
> ||||||||-n
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.genitive.t1x
> /home/flammie/Koodit/apertium-eo-en/en-eo.genitive.t1x.bin
> |||||||||apertium-transfer
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.t1x
> /home/flammie/Koodit/apertium-eo-en/en-eo.t1x.bin
> /home/flammie/Koodit/apertium-eo-en/en-eo.autobil.bin
> ||||||||||apertium-interchunk
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.antaux_t2x
> /home/flammie/Koodit/apertium-eo-en/en-eo.antaux_t2x.bin
> |||||||||||apertium-interchunk
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.antaux2_t2x
> /home/flammie/Koodit/apertium-eo-en/en-eo.antaux2_t2x.bin
> ||||||||||||apertium-interchunk
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.t2x
> /home/flammie/Koodit/apertium-eo-en/en-eo.t2x.bin
> |||||||||||||apertium-postchunk
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.t3x
> /home/flammie/Koodit/apertium-eo-en/en-eo.t3x.bin
> ||||||||||||||lt-proc
> ||||||||||||||-g /home/flammie/Koodit/apertium-eo-en/en-eo.autogen.bin
> frapo
> $ echo "^hit/hit<vblex><inf>$" |apertium-tagger
> -g /home/flammie/Koodit/apertium-eo-en/en-eo.prob
> |apertium-pretransfer|apertium-transfer
> |-n /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.genitive.t1x
> /home/flammie/Koodit/apertium-eo-en/en-eo.genitive.t1x.bin
> ||apertium-transfer
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.t1x
> /home/flammie/Koodit/apertium-eo-en/en-eo.t1x.bin
> /home/flammie/Koodit/apertium-eo-en/en-eo.autobil.bin
> |||apertium-interchunk
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.antaux_t2x
> /home/flammie/Koodit/apertium-eo-en/en-eo.antaux_t2x.bin
> ||||apertium-interchunk
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.antaux2_t2x
> /home/flammie/Koodit/apertium-eo-en/en-eo.antaux2_t2x.bin
> |||||apertium-interchunk
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.t2x
> /home/flammie/Koodit/apertium-eo-en/en-eo.t2x.bin
> ||||||apertium-postchunk
> /home/flammie/Koodit/apertium-eo-en/apertium-eo-en.en-eo.t3x
> /home/flammie/Koodit/apertium-eo-en/en-eo.t3x.bin
> |||||||lt-proc -g /home/flammie/Koodit/apertium-eo-en/en-eo.autogen.bin
> |||||||frapi
>
> Should be relatively straightforward, but if you need some help,
> there's an IRC channel #apertium on Freenode for live chats that may be
> of use.
>
> [1] <http://wiki.apertium.org/wiki/Installation>
> [2] <http://wiki.apertium.org/wiki/Minimal_installation_from_SVN>
> --
> Flammie, computer scientist bachelor + linguist master = computational
> linguist doctor, free software Finnish localiser,
> and more! <http://www.iki.fi/flammie/>
>
>
>
>
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> _______________________________________________
> Apertium-stuff mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Reply via email to