User:Unhammer/wishlist - Revision history

Unhammer: /* Allow the chunk tag wherever we allow other "strings" */

2023-01-20T07:27:28Z

Allow the chunk tag wherever we allow other "strings"

Unhammer: /* Consider: */

2023-01-20T07:26:29Z

Consider:

Unhammer: /* Consider: */

2023-01-20T07:25:58Z

Consider:

Unhammer: /* lt-proc mode for adding analyses to already analysed text */

2023-01-20T07:21:05Z

lt-proc mode for adding analyses to already analysed text

Unhammer: /* Fallthrough option in transfer */

2023-01-20T07:20:37Z

Fallthrough option in transfer

Unhammer: /* lt-proc mode for adding analyses to already analysed text */

2023-01-20T07:18:59Z

lt-proc mode for adding analyses to already analysed text

Unhammer: /* compound-only-R */

2023-01-20T07:16:20Z

compound-only-R

Unhammer: /* corpus-testing makefile */

2018-04-16T06:49:41Z

corpus-testing makefile

Unhammer: /* Gamification! */

2018-04-16T06:45:05Z

Gamification!

Unhammer: /* A "grouping" tag for bidix */

2017-05-29T10:53:45Z

A "grouping" tag for bidix

@@ Line 140: / Line 140: @@
 : If you, in transfer, know that they used to be part of the same lexical unit in the source language, this probably doesn't matter too much.
-==<s>Allow the chunk tag wherever we allow other "strings"</s>==
+==WISH GRANTED: Allow the chunk tag wherever we allow other "strings">==
 Implemented by sortiz as of r39106.

@@ Line 111: / Line 111: @@
 So how can you avoid *"Effekten til Vitaminet" or *"Effekten til c-vitaminet"?
-<small>(In nn-nb we dealt with this by using only lowercase lemmata for stuff like "C-vitamin", and RL entries which apply correct capitalisation -- not very pretty, and pardefs don't really help here. Then we changed to marking all LU's with a tag showing input-casing <code><nowiki><aa>/<Aa>/<AA></nowiki><code> which is non-pretty in a different way and required way too many fiddly changes to enable initially but works quite well.)</small>
+<small>(In nn-nb we dealt with this by using only lowercase lemmata for stuff like "C-vitamin", and RL entries which apply correct capitalisation -- not very pretty, and pardefs don't really help here. Then we changed to marking all LU's with a tag showing input-casing <code><nowiki><aa>/<Aa>/<AA></nowiki></code> which is non-pretty in a different way and required way too many fiddly changes to enable initially but works quite well.)</small>
 {{comment|:See how it is done in <code>is-en</code> with gentilics, e.g. "English-speaking", etc. - [[User:Francis Tyers|Francis Tyers]] 19:56, 11 March 2010 (UTC)}}
-:: Switched to that method as it's slightly better, but still... <code><e lm="BCG-vaksine"><par n="Bb"/><par n="Cc"/><par n="Gg"/><i>-vaksin</i><par n="r/e__n"/></e></code> --[[User:Unhammer|unhammer]] 08:26, 12 March 2010 (UTC)
+:: We used that method as it's slightly better, but still... <code><e lm="BCG-vaksine"><par n="Bb"/><par n="Cc"/><par n="Gg"/><i>-vaksin</i><par n="r/e__n"/></e></code> --[[User:Unhammer|unhammer]] 08:26, 12 March 2010 (UTC)
 ===Solution:===

@@ Line 111: / Line 111: @@
 So how can you avoid *"Effekten til Vitaminet" or *"Effekten til c-vitaminet"?
-<small>(At the moment, this is dealt with in nn-nb by using only lowercase lemmata for stuff like "C-vitamin", and RL entries which apply correct capitalisation -- not very pretty, and pardefs don't really help here.)</small>
+<small>(In nn-nb we dealt with this by using only lowercase lemmata for stuff like "C-vitamin", and RL entries which apply correct capitalisation -- not very pretty, and pardefs don't really help here. Then we changed to marking all LU's with a tag showing input-casing <code><nowiki><aa>/<Aa>/<AA></nowiki><code> which is non-pretty in a different way and required way too many fiddly changes to enable initially but works quite well.)</small>
 {{comment|:See how it is done in <code>is-en</code> with gentilics, e.g. "English-speaking", etc. - [[User:Francis Tyers|Francis Tyers]] 19:56, 11 March 2010 (UTC)}}

@@ Line 49: / Line 49: @@
 ==lt-proc mode for adding analyses to already analysed text==
-EDIT: More or less deprecated by lt-append (though this was about doing it runtime, not compile-time)
+EDIT: More or less done by lt-append (though this was about doing it runtime, not compile-time)
 (or for combining several analysers at once)

@@ Line 74: / Line 74: @@
 Probably there are other tokenisation pitfalls too.
-==Fallthrough option in transfer==
+==WISH GRANTED: Fallthrough option in transfer==
 Some times, you match an input pattern in a rule, eg. "n vblex", and you check whether the target-language n has some feature, and then only if it has that feature do you do something special with it. It would be great if we could specify in the <code><otherwise></code> that we want to fall through, ignoring that this rule matched.
 There are two options for how to "ignore", the best (but possibly slowest?) would be to go on with trying to match on the rest of the rules, the other option is to act as if no rules matched. Both would be an improvement.
-: This has been implemented in [[User:jimregan|jimregan]]'s [http://thread.gmane.org/gmane.comp.nlp.apertium/151/focus=159 <code>exception</code> patch]
+: This has been implemented in [[User:jimregan|jimregan]]'s [http://thread.gmane.org/gmane.comp.nlp.apertium/151/focus=159 <code>reject-current-rule</code> patch]
 ==tl-lemma/tl-tags attributes in t1x def-cat's (pattern-items)==

@@ Line 35: / Line 35: @@
 ==compound-only-R==
-Having compound-only-L and compound-R is silly, you end up using pardefs anyway.
+Having compound-only-L and compound-R seems silly, you end up using pardefs anyway.
 https://sourceforge.net/p/apertium/tickets/57/
+(but it seems like compound-only-R is harder to implement than compound-R)
 ==call-macro with-param var?==

@@ Line 323: / Line 323: @@
 make -f corptest.make # now it re-runs from bidix onwards
 </pre>
+(This is actually implemented for wiki-based regression tests in apertium-sme-nob if you <code>export AP_LAZY=true</code>. See t/lazytranslate and t/translate.make. Not yet done for corpus tests, but it should be easy to build on that.)
 ==Gamification!==

@@ Line 327: / Line 327: @@
 https://unhammer.org/k/gamification.html
+(only ''half''-joking … The Document Foundation actually sends out a congratulations email when you get your first patch merged, with a little PDF certificate)
-(only ''half''-joking …)

@@ Line 250: / Line 250: @@
        <uzb_Latn>uuu</uzb_Latn>
  </e>
+ gives
+ tat-bak.dix:
- giving
+ <e r="LR"><l>ttt</><r>aaa</>
+ <e r="RL"><l>ttt</><r>bbb</>
+ uzb_Latn-bak.dix:
+ <e r="LR"><l>uuu</><r>aaa</>
+ <e r="RL"><l>uuu</><r>bbb</>
+ uzb_Latn-tat.dix:
+ <e><l>uuu</><r>ttt</>
+ and you get cartesian products the expected way, e.g.
+ <e>
+       <bak r="NG">bbb</bak>
+       <bak r="NA">aaa</bak>
+       <tat>ttt</tat>
+       <tat>ttt2</tat>
+       <uzb_Latn>uuu</uzb_Latn>
+ </e>
+ gives
  tat-bak.dix:
  <e r="LR"><l>ttt</><r>aaa</>
  <e r="RL"><l>ttt</><r>bbb</>
+ <e r="LR"><l>ttt2</><r>aaa</>
+ <e r="RL"><l>ttt2</><r>bbb</>
  uzb_Latn-bak.dix:
  <e r="LR"><l>uuu</><r>aaa</>
@@ Line 261: / Line 282: @@
  uzb_Latn-tat.dix:
  <e><l>uuu</><r>ttt</>
+ <e><l>uuu</><r>ttt2</>
 </pre>