Install quick tests
More convincing if you have a language pair on the computer somewhere :)
- 1 If you only compiled/installed Apertium core
- 2 If you installed a language pair by packaging, or manual install
- 3 If you compiled a language pair with no install
- 4 If you installed new (empty) language directories
If you only compiled/installed Apertium core
One way to test you have something, immediately, it to try invoke a tool. After a core has been installed, this should work for both packaged and compiled Apertium. Without language data you can't see a translation, but you can see the help. Try,
You should see the help files?
If you installed a language pair by packaging, or manual install
You may have done this because you do not want to develop.
echo 'This is a test sentence' | apertium xxx-yyy
echo 'This is a test sentence' | apertium eo-en
This command does not need to use the
-d switch. The language pair is installed, so Apertium can find it, whatever directory you're in.
If you compiled a language pair with no install
You probably want to develop a language pair.
Go into the bilingual dictionary and try,
echo 'This is a test sentence.' | apertium -d . xxx-yyy
echo 'This is a test sentence' | apertium -d . eo-en
-d . means "use the language data in this directory".
If you installed new (empty) language directories
They can still be tested. New language directories created by 'apertium-init' contain a single word, the English word 'house'. So,
To test a new language directory (or a monodix in a pair)
You must have run
Go into the monodix, then try invoking a mode e.g. 'tagger',
echo house | apertium -d . xxx-tagger
(If the word had not been recognised, this command would return
To test a new bidix
You must have run
./autogen.sh --with-lang1=../apertium-XXX --with-lang2=../apertium-YYY and
make langs first.
Go into the bidix. Then you can test in the same way as you would test a pair downloaded for compiling, except the only word available is 'house',
echo house | apertium -d . xxx-yyy