Difference between revisions of "Lt-trim"

From Apertium
Jump to navigation Jump to search
(Created page with "==See also== * Automatically trimming a monodix *")
 
Line 1: Line 1:
  +
'''lt-trim''' is the application responsible for trimming compiled dictionaries. The
  +
analyses (right-side when compiling lr) of analyser_binary are trimmed
  +
to the input side of bidix_binary (left-side when compiling lr,
  +
right-side when compiling rl), such that only analyses which would
  +
pass through `lt-proc -b bidix_binary' are kept.
  +
  +
Both compund tags (`<compound-only-L>', `<compound-R>') and join
  +
elements (`&lt;j/&gt;' in XML, `+' in the stream) and the group element
  +
(`&lt;g/&gt;' in XML, `#' in the stream) should be handled correctly.
  +
  +
You should not trim a generator unless you have a '''very''' simple
  +
translator pipeline, since the output of bidix seldom goes unchanged
  +
through transfer.
  +
  +
 
==See also==
 
==See also==
* [[Automatically trimming a monodix]]
+
* [[Automatically trimming a monodix#lttoolbox]]
*
 

Revision as of 17:12, 9 February 2014

lt-trim is the application responsible for trimming compiled dictionaries. The analyses (right-side when compiling lr) of analyser_binary are trimmed to the input side of bidix_binary (left-side when compiling lr, right-side when compiling rl), such that only analyses which would pass through `lt-proc -b bidix_binary' are kept.

Both compund tags (`<compound-only-L>', `<compound-R>') and join elements (`<j/>' in XML, `+' in the stream) and the group element (`<g/>' in XML, `#' in the stream) should be handled correctly.

You should not trim a generator unless you have a very simple translator pipeline, since the output of bidix seldom goes unchanged through transfer.


See also