Lttoolbox - Revision history

Hectoralos at 06:37, 16 February 2020

2020-02-16T06:37:38Z

Hectoralos: /* Troubleshooting */

2019-06-25T21:34:41Z

Troubleshooting

Unhammer: /* See also */

2019-01-30T09:32:54Z

Unhammer: /* Troubleshooting */

2015-04-01T16:47:12Z

Troubleshooting

Unhammer: /* Troubleshooting */

2015-04-01T16:46:26Z

Troubleshooting

Jacob Nordfalk: /* Troubleshooting */

2015-04-01T13:02:59Z

Troubleshooting

Jacob Nordfalk: /* Troubleshooting */

2015-04-01T13:02:29Z

Troubleshooting

Bech: Link to French page

2014-10-07T12:59:45Z

Link to French page

Unhammer: /* Wishlist / TODO */

2014-03-10T13:59:56Z

Wishlist / TODO

Unhammer: /* Wishlist / TODO */

2014-03-10T13:57:17Z

Wishlist / TODO

@@ Line 212: / Line 212: @@
 </pre>
+Or also in the bilingual dictionary, for instance:
+<pre>
+<e>       <p><l>cave<s n="n"/><s n="f"/></l>      <r> soterrani<s n="n"/><s n="m"/></r></p></e>
+</pre>
 ; lt-expand/lt-proc on different machines gives different output for metadix

@@ Line 152: / Line 152: @@
 This means you should look for the "kunna" verb; where the left side is empty, you should either put something there or add something to the invariant section.
@@ Line 191: / Line 189: @@
 (This one seems like a bug: https://sourceforge.net/p/apertium/tickets/65/ )
+;Entry beginning with whitespace
+If you get a message like:
+<pre>
+Error: Invalid dictionary (hint: entry beginning with whitespace)
+Error: Input is null - nothing to parse!
+</pre>
+The problem may be in a monolingual dictionary. You may have an entry like:
+<pre>
+<e lm="Pilato"><i> Pilato</i><par n="Juan__np"/></e>
+</pre>
+or
+<pre>
+<e lm="Pilato"><i><b/>Pilato</i><par n="Juan__np"/></e>
+</pre>

@@ Line 260: / Line 260: @@
 ==See also==
+* [[Lttoolbox/weights]] for how to make weighted transducers with lttoolbox
 * [[Monodix basics]]
 * [[Using an lttoolbox dictionary]]

← Older revision		Revision as of 16:47, 1 April 2015
Line 191:		Line 191:

	(This one seems like a bug: https://sourceforge.net/p/apertium/tickets/65/ )		(This one seems like a bug: https://sourceforge.net/p/apertium/tickets/65/ )


	; lt-expand/lt-proc on different machines gives different output for metadix		; lt-expand/lt-proc on different machines gives different output for metadix

← Older revision		Revision as of 16:46, 1 April 2015
Line 190:		Line 190:


			(This one seems like a bug: https://sourceforge.net/p/apertium/tickets/65/ )

	; lt-expand/lt-proc on different machines gives different output for metadix		; lt-expand/lt-proc on different machines gives different output for metadix

@@ Line 153: / Line 153: @@
 This means you should look for the "kunna" verb; where the left side is empty, you should either put something there or add something to the invariant section.
-; lt-expand/lt-proc on different machines gives different output for metadix
-When trying to e.g. lt-expand dictionaries with the alt-attribute (which is not valid XML according to the dix DTD), some machines might give lines with the attribute and some might skip them. If lttoolbox was compiled against an older version of libxml2, you will get the lines included, with newer libxml2 they will be skipped. To ensure you get the same output for lt-expand/lt-proc on all machines, you might have to do a "make clean; ./autogen.sh && make && make install" (after ensuring your system is up-to-date).
-(In any case, metadix should not be expanded/compiled directly, run the commands on the files that have been through xsltproc, typically in .deps)
@@ Line 194: / Line 188: @@
       </e>
 </pre>
+; lt-expand/lt-proc on different machines gives different output for metadix
+When trying to e.g. lt-expand dictionaries with the alt-attribute (which is not valid XML according to the dix DTD), some machines might give lines with the attribute and some might skip them. If lttoolbox was compiled against an older version of libxml2, you will get the lines included, with newer libxml2 they will be skipped. To ensure you get the same output for lt-expand/lt-proc on all machines, you might have to do a "make clean; ./autogen.sh && make && make install" (after ensuring your system is up-to-date).
+(In any case, metadix should not be expanded/compiled directly, run the commands on the files that have been through xsltproc, typically in .deps)
 ==Speed==

@@ Line 159: / Line 159: @@
 (In any case, metadix should not be expanded/compiled directly, run the commands on the files that have been through xsltproc, typically in .deps)
+;Empty left side II
+If you get a message like:
+<pre>
+Error: Invalid dictionary (hint: the left side of an entry is empty)
+</pre>
+and grep doesn't find anything, then look in your pardefs. You probably have something like:
+<pre>
+   <pardef n="na__S">
+      <e>
+        <p>
+          <l></l>
+          <r></r>
+        </p>
+      </e>
+</pre>
+Add a dummy entry to make it work:
+<pre>
+   <pardef n="na__S">
+      <e>       <p><l>NON_ANALYSIS</l>          <r>DUE_TO_LT_PROC_HANG</r></p></e>
+      <e>
+        <p>
+          <l></l>
+          <r></r>
+        </p>
+      </e>
+</pre>
 ==Speed==

@@ Line 1: / Line 1: @@
+[[Lttoolbox (français)]]
 {{TOCD}}
 '''lttoolbox''' is a toolbox for lexical processing, [[morphological analysis]] and generation of words. ''Analysis'' is the process of splitting a word (e.g. cats) into its lemma 'cat' and the grammatical information <code><n><pl></code>. ''Generation'' is the opposite process.

@@ Line 190: / Line 190: @@
 * Being able to have multichar symbols/tags without '<' and '>'
 * https://scan.coverity.com/projects/1192 has some static analysis results, showing some bugs that should probably be fixed.
+===Postgenerator alarms===
+Many monodixes handle postgenerator alarms <code>&lt;a/></code> explicitly in each entry. As a result, left-to-right entries have to be separated from right-to-left entries. However, it could be much easier to write a paradigm like
+<pre>
+<pardef n="wiggle">
+    <e r="LR">
+       <i/>
+    </e>
+    <e r="RL">
+        <l><a/></l>
+        <r></r>
+    </e>
+</pardef>
+</pre>
+and then invoke it in entries as follows
+<pre>
+<e lm="a">
+   <par n="wiggle"/>
+   <i>a</i>
+   </par n="a__pr"/>
+</e>
+</pre>
+This suggests that perhaps it would be even easier to change the meaning of <code><a/></code> so that it only works right to left, or perhaps endow it with the <code>r</code> attribute as follows: <code><a r="RL"/></code>.
 ==See also==