Install quick tests - Revision history

Rcrowther at 06:02, 24 April 2017

2017-04-24T06:02:25Z

Rcrowther at 06:01, 24 April 2017

2017-04-24T06:01:33Z

Rcrowther at 05:59, 24 April 2017

2017-04-24T05:59:43Z

Rcrowther: new tests

2017-04-24T05:58:29Z

new tests

Rcrowther at 08:47, 23 April 2017

2017-04-23T08:47:03Z

Rcrowther: 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..."

2017-04-22T19:40:59Z

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..."

New page

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. Without language data you can't see a translation, but you can see the help. Try,

<pre>
lt-proc
</pre>

You should see the help files?

== 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,

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

e.g.

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

The <code>-d .</code> means "use the language data in this directory".

== 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.

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

e.g.

<pre>
echo 'This is a test sentence' | apertium eo-en
</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.

[[Category:Installation]]
[[Category:Documentation in English]]

← Older revision		Revision as of 06:02, 24 April 2017
Line 43:		Line 43:

	The <code>-d .</code> means "use the language data in this directory".		The <code>-d .</code> means "use the language data in this directory".



	== If you installed new (empty) language directories ==		== If you installed new (empty) language directories ==

@@ Line 11: / Line 11: @@
-== If you installed a language pair by packaging, or manual install ==
+== If you OS-installed a language pair ==
-You may have done this because you do not want to develop.
+...by packaging, or manual install. You may have done this because you do not want to develop.
 <pre>
@@ Line 43: / Line 43: @@
 The <code>-d .</code> means "use the language data in this directory".
 == If you installed new (empty) language directories ==

← Older revision		Revision as of 05:59, 24 April 2017
Line 43:		Line 43:

	The <code>-d .</code> means "use the language data in this directory".		The <code>-d .</code> means "use the language data in this directory".


	== If you installed new (empty) language directories ==		== If you installed new (empty) language directories ==

@@ Line 1: / Line 1: @@
 More convincing if you have a language pair on the computer somewhere :)
-== If you only compiled Apertium core ==
+== 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,
+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>
@@ Line 12: / Line 12: @@
 == 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 may have done this because you do not want to develop.
 <pre>
@@ Line 27: / Line 27: @@
-== If you downloaded and compiled a language pair==
+== If you compiled a language pair with no install ==
+You probably want to develop a language pair.
-You downloaded and compiled language data, but did not install.
 Go into the bilingual dictionary and try,
@@ Line 43: / Line 43: @@
 The <code>-d .</code> 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 <code>./autogen</code> and <code>make</code> first.
+Go into the monodix, then try invoking a mode e.g. 'tagger',
+<pre>
+echo house | apertium -d . xxx-tagger
+</pre>
+Should return,
+<pre>
+^house/house<n><attr>/house<n><sg>$^./.<sent>$
+</pre>
+(If the word had not been recognised, this command would return <code><pre>^horse/*horse$^./.<sent></pre></code>)
+=== To test a new bidix ===
+You must have run <code>./autogen.sh --with-lang1=../apertium-XXX --with-lang2=../apertium-YYY</code> and <code>make langs</code> 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',
+<pre>
+echo house | apertium -d . xxx-yyy
+</pre>
 [[Category:Installation]]