Hi Zanga,
I believe you're running into a know issue with the tagger as apertium-init
sets it up:
https://github.com/apertium/apertium-init/issues/31
The fix is to add -x to the apertium-tagger lines in your bilingual
modes.xml. A work-around is to just remove the apertium-tagger blocks
Thanks for the insight. Will look into that.
On Mon, Jan 13, 2020 at 1:21 PM Hèctor Alòs i Font wrote:
>
> Hi Zanga,
>
> I've downloaded your code and compiled it. It doesn't hang in my computer:
> https://drive.google.com/open?id=16GLQjMIlwJx2Dtx585JFpmvV61dUrpUH
>
> According to your
Hi Zanga,
I've downloaded your code and compiled it. It doesn't hang in my computer:
https://drive.google.com/open?id=16GLQjMIlwJx2Dtx585JFpmvV61dUrpUH
According to your screenshot you have a problem in apertium-tagger.
Seemingly, you get a result if you type:
$ echo "houses" | apertium -d .
I have followed the guidelines on bootstrapping a new language pair
(with no existing monolingual packages) at:
http://wiki.apertium.org/wiki/How_to_bootstrap_a_new_pair
I have made one change only to one of the monolingual language
dictionaries, replacing “house” with “casa” in a couple of
