Per Tunedal <[email protected]> writes: > Hi, > why is: > > NON_ANALYSIS > > appended after words at many lines? > > eg. > > aktrisernaNON_ANALYSIS
There's a bug in lt-comp, where if you have a pardef that looks like
<par n="foo">
<e></e>
</par>
then it'll produce an FST that leads to lt-proc hanging. So if you want
a pardef like
<pardef n="cmp">
<e> <p><l></l> <r></r></p></e>
<e r="RL"><p><l></l> <r><s n="cmp"/></r></p></e>
</pardef>
which adds the "cmp" tag only for the RL FST, then the LR FST uses
<pardef n="cmp">
<e> <p><l></l> <r></r></p></e>
</pardef>
which gives this bug. Thus we do
<pardef n="cmp">
<e> <p><l></l> <r></r></p></e>
<e r="RL"><p><l></l> <r><s n="cmp"/></r></p></e>
<e> <p><l>NON_ANALYSIS</l> <r>DUE_TO_LT_PROC_HANG</r></p></e>
</pardef>
Yes, the bug should be fixed, it just hasn't been annoying enough yet
that anyone's gotten around to it :-)
(And the "NON_ANALYSIS" of course will presumably never be seen in a
corpus[1] so it's harmless to have it in there.)
[1] Except for the corpus of apertium-stuff emails and #apertium IRC
logs.
--
Kevin Brubeck Unhammer
GPG: 0x766AC60C
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ Apertium-stuff mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/apertium-stuff
