Difference between revisions of "Install quick tests"

From Apertium
Jump to navigation Jump to search
(Created page with "More convincing if you have a language pair on the computer somewhere :) == If you only compiled Apertium core == One way to test you have something, immediately, it to try i...")
 
Line 2: Line 2:


== If you only compiled Apertium core ==
== If you only compiled Apertium core ==
One way to test you have something, immediately, it to try invoke a tool. Without language data you can't see a translation, but you can see the help. Try,
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,


<pre>
<pre>
Line 11: Line 11:




== If you downloaded and compiled a language pair==
== If you installed a language pair by packaging, or manual install ==
You may have done this as a quick test for a compiled core. Or because you do not want to develop, only use the language data. Or you used packaging, and installed, as a test, a pair.
You downloaded and compiled language data, but did not install.

Go into the bilingual dictionary and try,


<pre>
<pre>
echo 'This is a test sentence.' | apertium -d . xxx-yyy
echo 'This is a test sentence' | apertium xxx-yyy
</pre>
</pre>


e.g.
e.g.


<pre>
<pre>
echo 'This is a test sentence' | apertium -d . eo-en
echo 'This is a test sentence' | apertium eo-en
</pre>
</pre>


The <code>-d .</code> means "use the language data in this directory".
This command does not need to use the <code>-d</code> switch. The language pair is installed, so Apertium can find it, whatever directory you're in.




== If you installed a language pair by packaging, or manual install ==
== If you downloaded and compiled a language pair==
You downloaded and compiled language data, but did not install.
You may have done this as a quick test for a compiled core. Or because you do not want to develop, only use the language data. Or you used packaging, and installed, as a test, a pair.

Go into the bilingual dictionary and try,


<pre>
<pre>
echo 'This is a test sentence' | apertium xxx-yyy
echo 'This is a test sentence.' | apertium -d . xxx-yyy
</pre>
</pre>


e.g.
e.g.


<pre>
<pre>
echo 'This is a test sentence' | apertium eo-en
echo 'This is a test sentence' | apertium -d . eo-en
</pre>
</pre>


This command does not need to use the <code>-d</code> switch. The language pair is installed, so Apertium can find it, whatever directory you're in.
The <code>-d .</code> means "use the language data in this directory".



[[Category:Installation]]
[[Category:Installation]]

Revision as of 08:47, 23 April 2017

More convincing if you have a language pair on the computer somewhere :)

If you only compiled 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,

lt-proc

You should see the help files?


If you installed a language pair by packaging, or manual install

You may have done this as a quick test for a compiled core. Or because you do not want to develop, only use the language data. Or you used packaging, and installed, as a test, a pair.

 echo 'This is a test sentence' | apertium xxx-yyy

e.g.

 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 downloaded and compiled a language pair

You downloaded and compiled language data, but did not install.

Go into the bilingual dictionary and try,

echo 'This is a test sentence.' | apertium -d . xxx-yyy

e.g.

 echo 'This is a test sentence' | apertium -d . eo-en

The -d . means "use the language data in this directory".