User:Firespeaker/HFST bug - Revision history

Tino Didriksen: Freenode -> OFTC

2021-05-27T06:33:12Z

Freenode -> OFTC

2013-05-05T17:42:27Z

2013-04-28T15:56:12Z

2013-02-04T16:08:57Z

2013-01-18T15:00:53Z

2013-01-18T14:59:21Z

Notes

2013-01-18T07:20:04Z

2013-01-18T07:17:38Z

Notes

2013-01-18T07:15:34Z

Other materials

2013-01-18T07:07:47Z

@@ Line 75: / Line 75: @@
 == Other materials ==
 * [http://wiki.apertium.org/wiki/Talk:Ideas_for_Google_Summer_of_Code/Closer_integration_with_HFST spectie explains the bug to firespeaker]
-* irc.freenode.net#hfst
+* irc.oftc.net#hfst

@@ Line 2: / Line 2: @@
 In 2011, a bug in how HFST handles words containing spaces was [http://sourceforge.net/p/hfst/bugs/59/ documented and resolved] (apparently in [http://hfst.svn.sourceforge.net/viewvc/hfst?view=revision&revision=1518 r1518]?), but it introduced a new bug.  This page documents the new [incorrect!] behaviour.  It appears to only affect transducers written in lexc.
-[https://sourceforge.net/p/hfst/bugs/153/ A bug report] was filed in January of 2013 along with a patch for a test case.  In March of 2013, [[User:Ftyers|spectie]] posted a patch that fixed the bug but introduced an issue with newlines and full stops.  As of today, the bug has still not been fixed.
+[https://sourceforge.net/p/hfst/bugs/153/ A bug report] was filed in January of 2013 along with a patch for a test case.  In March of 2013, [[User:Francis Tyers|spectie]] posted a patch that fixed the bug but introduced an issue with newlines and full stops.  As of today, the bug has still not been fixed.
 == text.lexc ==

@@ Line 2: / Line 2: @@
 In 2011, a bug in how HFST handles words containing spaces was [http://sourceforge.net/p/hfst/bugs/59/ documented and resolved] (apparently in [http://hfst.svn.sourceforge.net/viewvc/hfst?view=revision&revision=1518 r1518]?), but it introduced a new bug.  This page documents the new [incorrect!] behaviour.  It appears to only affect transducers written in lexc.
-[https://sourceforge.net/p/hfst/bugs/153/ A bug report] has been filed (included is a patch for a test case).
+[https://sourceforge.net/p/hfst/bugs/153/ A bug report] was filed in January of 2013 along with a patch for a test case.  In March of 2013, [[User:Ftyers|spectie]] posted a patch that fixed the bug but introduced an issue with newlines and full stops.  As of today, the bug has still not been fixed.
 == text.lexc ==

@@ Line 1: / Line 1: @@
 {{TOCD}}
 In 2011, a bug in how HFST handles words containing spaces was [http://sourceforge.net/p/hfst/bugs/59/ documented and resolved] (apparently in [http://hfst.svn.sourceforge.net/viewvc/hfst?view=revision&revision=1518 r1518]?), but it introduced a new bug.  This page documents the new [incorrect!] behaviour.  It appears to only affect transducers written in lexc.
+[https://sourceforge.net/p/hfst/bugs/153/ A bug report] has been filed (included is a patch for a test case).
 == text.lexc ==

@@ Line 1: / Line 1: @@
 {{TOCD}}
-In 2011, a bug in how HFST handles words containing spaces was [http://sourceforge.net/p/hfst/bugs/59/ documented and resolved] (apparently in [http://hfst.svn.sourceforge.net/viewvc/hfst?view=revision&revision=1518 r1518]?), but it introduced a new bug.  This page documents the new [incorrect!] behaviour.
+In 2011, a bug in how HFST handles words containing spaces was [http://sourceforge.net/p/hfst/bugs/59/ documented and resolved] (apparently in [http://hfst.svn.sourceforge.net/viewvc/hfst?view=revision&revision=1518 r1518]?), but it introduced a new bug.  This page documents the new [incorrect!] behaviour.  It appears to only affect transducers written in lexc.
 == text.lexc ==

@@ Line 66: / Line 66: @@
   <li><code>$ echo "right the" | apertium -d . eng-kaz-morph</code></li>
 : <code>^right/right<adj>/right<adv>/right<n><sg>$ ^the/the<det><def><sp>$^./.<sent>$</code>
+  <li><code>$ echo "right therein" | apertium -d . eng-kaz-morph</code></li>
+: <code>^right/right<adj>/right<adv>/right<n><sg>$ ^therein/*therein$^./.<sent>$</code>
 </ul>
 </ul>

@@ Line 59: / Line 59: @@
 == Notes ==
+<ul>
-* This doesn't seem to affect transducers written in other formats.  E.g., the transducer that results from <code>apertium-eng-kaz.eng.dix</code> outputs the following:
+<li>This doesn't seem to affect transducers written in other formats.  E.g., the transducer that results from <code>apertium-eng-kaz.eng.dix</code> outputs the following:</li>
-** <code>$ echo "right there" | apertium -d . eng-kaz-morph</code>
+<ul>
-:: <code>^right there/right there<adv>$^./.<sent>$</code>
-** <code>$ echo "right the" | apertium -d . eng-kaz-morph</code>
+  <li><code>$ echo "right there" | apertium -d . eng-kaz-morph</code></li>
-:: <code>^right/right<adj>/right<adv>/right<n><sg>$ ^the/the<det><def><sp>$^./.<sent>$</code>
+: <code>^right there/right there<adv>$^./.<sent>$</code>
+  <li><code>$ echo "right the" | apertium -d . eng-kaz-morph</code></li>
+: <code>^right/right<adj>/right<adv>/right<n><sg>$ ^the/the<det><def><sp>$^./.<sent>$</code>
+</ul>
+</ul>
 == Other materials ==

← Older revision		Revision as of 07:07, 18 January 2013
Line 1:		Line 1:
			{{TOCD}}
	In 2011, a bug in how HFST handles words containing spaces was [http://sourceforge.net/p/hfst/bugs/59/ documented and resolved] (apparently in [http://hfst.svn.sourceforge.net/viewvc/hfst?view=revision&revision=1518 r1518]?), but it introduced a new bug. This page documents the new behaviour.		In 2011, a bug in how HFST handles words containing spaces was [http://sourceforge.net/p/hfst/bugs/59/ documented and resolved] (apparently in [http://hfst.svn.sourceforge.net/viewvc/hfst?view=revision&revision=1518 r1518]?), but it introduced a new bug. This page documents the new behaviour.