User:Firespeaker/TODO

From Apertium
Jump to navigation Jump to search

Things for selimcan

Things for spectie

Things for hector2

  • tests/a_0.yaml at apertium-cv-tr : For some reason {а} in the present tense suffix doesn't fall in verbs like вула (ending in а)
This was occurring due to an undocumented exception in the {а} deletion rule, which I commented out. If this exception was there for a reason, those forms should be added to a new section of the a_0.yaml file and the issue should be "reopened" on this list. —Firespeaker 00:51, 1 August 2012 (UTC)
Oh yeah, the "fix" occurred in r39860Firespeaker 01:02, 1 August 2012 (UTC)
Thanks. I couldn't find yet why the fix was done. --Hèctor Alòs i Font 05:29, 1 August 2012 (UTC)
  • tests/ger1.yaml at apertium-cv-tr : For some reason м falls in ger1 (%>м%{А%}) (and it shouldn't), but м does not fall e.g. in <neg><pres> (%>м%{А%}с%>т)
I see nothing wrong in ger1.yaml. If there are forms that aren't working right, could you add them to the yaml file? —Firespeaker 01:00, 1 August 2012 (UTC)
Not really. Two forms are generated, I don't know why. One is the good one, but the other (without м) is odd:
[PASS] вула<v><tv><ger1> => вулама
[FAIL] вула<v><tv><ger1> => unexpected results: вулаа
--Hèctor Alòs i Font 05:29, 1 August 2012 (UTC)
The problem is in lexc. I don't know why yet there's a mix between ger1 and ger10, but there's nothing to do with twol.--Hèctor Alòs i Font 10:15, 7 August 2012 (UTC)
  • tests/пенсионер.yaml : After the 3rd person affix (ӗ) front vowels should be used, but the {RUS} tag blocks the vowel harmony for the whole word. It should block it only until {ӗ} is found
Genitive fixed in r40191, still working on dative —Firespeaker 06:19, 9 August 2012 (UTC)
Dative fixed in r40232 (and the wiki's back up!) —Firespeaker 20:47, 14 August 2012 (UTC)
Great! --Hèctor Alòs i Font 10:04, 15 August 2012 (UTC)
  • tests/кала.yaml : In some tenses the last vowel of the root falls, even if it's а or e and the tense (or person) affix begins with {Ӑ}. In order to avoid new archiphonemes that would have to be added in zillions of rules, I've created a new pseudoarchiphoneme {del2}, similar to {del}. A couple of rules in twol should do all the work (search del2). The problem is that when these two rules are uncommented all px3sp words are not recognized, nor the verbal forms with del2 are generated. The compiler doesn't show any rule conflict and I can't see it either. In the кала.yaml a few px3sp forms are added to be able to follow better the problem. There's also a file tests/кил.yaml which works well, as the verb doesn't end in a vowel.
    I put the problem in the first place of the pending list, as it affects lots of words.
    • I finally decided that's cleaner to create an archiphoneme {Ӑ2} (which is needed also for px2pl) and I'm working on it.--Hèctor Alòs i Font 07:27, 23 August 2012 (UTC)
  • tests/чикӗ.yaml, tests/училище.yaml : There are strange errors in the vowel harmony for some cases in the px2sg. In some cases the rule "Vowel harmony for archiphoneme {У}" is correctly applied, but in some others no. I've tried to add a couple of lines (search "училище" in the twol file), but they didn't solve the problem.
  • tests/хӑю.yaml : As in tests/ту.yaml (which works perfectly), there is a у/ӑв variation in this word. The problem is that (because of the Russian orthography) ю has to be split and an inexistent position for й has to be found. That's why, for instance, adding ю in the rule "в surfaces in у/ӳ > ӑв/ӗв before vowel (2)" may not solve part of the problem. A solution can be adding something at the end of this kind of words in lexc, but that may give problems in twol (fortunately there is not vowel harmony in this case). A very dirty trick could be use the morpheme boundary symbol for that.