Using an lttoolbox dictionary - Revision history

Unhammer: /* Requirements */

2015-09-09T07:34:26Z

Requirements

2015-09-09T07:32:54Z

2014-10-06T12:04:28Z

Link to French page

2014-01-16T09:09:23Z

2013-12-08T08:27:24Z

generate

2013-12-08T08:21:16Z

Compile

2013-12-08T08:16:47Z

refer to installation instead; old text likely to give people problems with PKG_CONFIG_PATH etc etc etc

2011-12-21T20:26:29Z

Minor English syntactic improvement in description

2011-09-03T10:15:44Z

2010-03-26T13:08:14Z

Use

@@ Line 15: / Line 15: @@
 The second is necessary for the [[deformatters]]. The tools in [[lttoolbox]] have a set of escaped characters which must be escaped in running text (see [[Apertium stream format]]).
-The page [[Installation]] shows how to install lttoolbox and apertium. When you get to the step [[Minimal installation from SVN]], it will assume you're installing <code>apertium-lex-tools</code> and a full language pair, but you can simply skip those two packages.
+The page [[Installation]] shows how to install lttoolbox and apertium. On most systems, you don't have to install more than the Prerequisites.
 ==Using the dictionary==

@@ Line 2: / Line 2: @@
 {{TOCD}}
-This page is intended as an answer to the question "I've found one of these <code>.dix</code> files; how can I use it to analyse text?" First of all, it is worth explaining what a <code>.dix</code> file is: a finite-state transducer for a language encoded in XML. More information on this can be found at the page [[lttoolbox]] and [[monodix basics]], but this page only concerns how it is used.
+This page is intended as an answer to the question "I've found one of these [[List of dictionaries|<code>.dix</code> files]]; how can I use it to analyse text?" First of all, it is worth explaining what a <code>.dix</code> file is: a finite-state transducer for a language encoded in XML. More information on this can be found at the page [[lttoolbox]] and [[monodix basics]], but this page only concerns how it is used.
+(If you haven't found a .dix file for your language yet, see [[List of dictionaries]].)
 ==Requirements==

@@ Line 1: / Line 1: @@
+[[Utilisation d'un dictionnaire lttoolbox|En français]]
 {{TOCD}}
 This page is intended as an answer to the question "I've found one of these <code>.dix</code> files; how can I use it to analyse text?" First of all, it is worth explaining what a <code>.dix</code> file is: a finite-state transducer for a language encoded in XML. More information on this can be found at the page [[lttoolbox]] and [[monodix basics]], but this page only concerns how it is used.

@@ Line 64: / Line 64: @@
 * [[List of dictionaries]]
+* [[Daemon]] – using an lttoolbox dictionary as a "server", without re-loading the dictionary for each request
 [[Category:Documentation in English]]

@@ Line 27: / Line 27: @@
 </pre>
-===Use===
+===Analyse===
 Note that the <code>apertium-destxt</code> command is important.
@@ Line 50: / Line 50: @@
 (on a Mac, you'll typically see a <code>9Exception</code>)
+===Generate===
+When generating, you basically input the analyses given by the analyser, but only one analysis per [[lexical unit]]. The general input format is
+<pre>^lemma<tag><tag2><tag3>$ ^otherlemma<othertag><tag2>$</pre>
+E.g. to generate a couple of the analyses given in the analysis example above:
+<pre>
+$ echo '^বাংলা<adj><mf>$ ^।<sent>$ ^এই<det><dem>$' | lt-proc -g bn.generator.bin
+বাংলা । এই
+</pre>
 ==See also==

@@ Line 20: / Line 20: @@
 {{see-also|Compiling dictionaries}}
+This compiles an analyser:
 <pre>
 $ lt-comp lr apertium-bn-en.bn.dix bn.analyser.bin

@@ Line 11: / Line 11: @@
 The second is necessary for the [[deformatters]]. The tools in [[lttoolbox]] have a set of escaped characters which must be escaped in running text (see [[Apertium stream format]]).
+The page [[Installation]] shows how to install lttoolbox and apertium. When you get to the step [[Minimal installation from SVN]], it will assume you're installing <code>apertium-lex-tools</code> and a full language pair, but you can simply skip those two packages.
-If you have a machine running GNU/Linux or Mac/OS then you can probably install both of these programs fairly easily. For lttoolbox:
-<pre>
-$ svn co http://apertium.svn.sourceforge.net/svnroot/apertium/trunk/lttoolbox
-cd lttoolbox/
-sh autogen.sh
-./configure
-make
-make install
-</pre>
-And for apertium:
-<pre>
-$ svn co http://apertium.svn.sourceforge.net/svnroot/apertium/trunk/apertium
-cd apertium/
-sh autogen.sh
-./configure
-make
-make install
-</pre>
-Subversion (<code>svn</code>) is a version control system. If you don't have it installed, on Debian/Ubuntu GNU/Linux you can use <code>apt-get install subversion</code> (or get it through Synaptic). On Mac/OS you can use <code>port install subversion</code> (requires [http://www.macports.org/ MacPorts]).
-See [[Installation]] for more information and troubleshooting.
 ==Using the dictionary==

@@ Line 78: / Line 78: @@
 * [[List of dictionaries]]
-[[Category:Documentation]]
+[[Category:Documentation in English]]
 [[Category:Lttoolbox|*]]
 [[Category:Morphological analysers]]

@@ Line 65: / Line 65: @@
 </pre>
-If unescaped special characters appear in the [[Apertium stream format|stream]], the error will be <code>std::exception</code>:
+because if unescaped special characters appear in the [[Apertium stream format|stream]], you will get a <code>std::exception</code>:
 <pre>
@@ Line 71: / Line 71: @@
 This is a test std::exception
 </pre>
+(on a Mac, you'll typically see a <code>9Exception</code>)
 ==See also==