Since the script currently (as far as I am aware) uses the headings to find the part-of-speech for deciding the part-of-speech of accelerated entries, it doesn't work for the new format of comparative or superlative adjectives, since they still have "Adjective" as the heading. Would it be possible to instead possibly check the head template or similar of the existing entry for finding the part-of-speech? I could look at it myself as well. — surjection ⟨?⟩ 15:50, 10 January 2019 (UTC)
{{grc-adecl}} to specify that an adjective was a comparative or superlative and then adding |comparative or |superlative to the form-of acceleration parameter.wgCategories variable available in the mw.config object and it would be possible to determine that the page is in a category containing the name of the current language and "comparative adjectives" or "superlative adjectives", but there is no way to determine which links actually belong to the comparative or superlative and which might belong to another part of speech. Even if the closest part-of-speech header to a link is "Adjective", there could be a page with both a positive adjective and a comparative adjective.{{head}} sure, but that's language-specific and should be handled in the language-specific modules. — surjection ⟨?⟩ 08:58, 11 January 2019 (UTC)
@Erutuon In the case of Slovene mešati, most forms of the imperative have more than one form, but the difference is only in the accentuation, which is not a part of normal Slovene orthography. If these forms were created with acceleration, you'd end up with two ===Verb=== headers on the page mešajte, one with the headword mẹ́šajte and another with mešȃjte. In the case of hvaliti, there is a present-tense form that matches one of the imperatives, so it would be grouped under the hválite heading, leaving the second imperative hvalȋte by itself.
In the case of mešajte, it would be useful if both imperative forms were grouped under a single heading, with head=mẹ́šajte|head2=mešȃjte. This could be done relatively simply by making another merging function that handles cases where all but the headwords are the same. But I'm not sure how this should interact with the existing definition-merging code. There is a choice to be made: group the first imperative hválite with the present-tense form (thus merging the definitions), or with the second imperative hvalȋte (thus merging the headwords)? Which should take precedence? I'm leaning towards merging the headwords in this case. But one could imagine more complicated cases where both the headword and the definition can be merged, and I don't think this would work out of the box. —Rua (mew) 08:56, 12 July 2019 (UTC)
origin and origin-transliteration could be conceptually arrays, so that multiple headwords can be specified in the acceleration data and the acceleration script doesn't have to figure out how to merge the entries. Not sure if that makes sense though. — Eru·tuon 18:37, 12 July 2019 (UTC)
I found a problem with the creation of German verb forms. When you go to abmurksen and click on the past tense form (second green link of the headword line), it generates the following inflection template:
# {{infl of|de|abmurksen||1//3//1//3|s|pret|;|1//3|s|sub|II}}
As you can see, the first and third person are listed twice for the preterite. So, why does that happen? When you look at the URL parameters of the creation page, you get this:
&accel_lang=de &accel_lemma=abmurksen &accel1=pos-verb 1//3|s|pret-form-of &accel2=pos-verb 1|s|pret-form-of origin-abmurksen &accel3=pos-verb 1|s|sub|II-form-of origin-abmurksen &accel4=pos-verb 3|s|pret-form-of origin-abmurksen &accel5=pos-verb 3|s|sub|II-form-of origin-abmurksen
accel1 comes from the headword line, while accel2 and accel4 come from the conjugation table. This module doesn't seem to deduplicate these three parameters, so that's why we get the result we get. Is there an easy way to fix that?
By the way, when you click on the first green link of the headword line, it will generate an inflection template where the third person is listed before the second one:
# {{infl of|de|abmurksen||3//2|s|pres|;|2|p|pres|;|p|imp}}
Can we also sort the person numbers in increasing order?
Tc14Hd (aka Marc) (talk) 13:27, 1 December 2024 (UTC)
&accelX parameters? Of course, these links wouldn't work if there is no conjugation table present on that page. Tc14Hd (aka Marc) (talk) 01:47, 2 December 2024 (UTC)
&accel1=pos-verb 1//3|s|pret-form-of in our case) and that parameter caused the duplication. Since the JavaScript aggregates these parameters for all occurrence of the same verb form (murkste ab in our case), the links in the conjugation table also received this parameter. My idea now is to make the headwords links clickable (e.g. green) without them adding their own parameters. But even though they don't add their own parameters, they will still work correctly since the links in the conjugation table provide the correct parameters. (This would also mean that the headword links won't work on pages without a conjugation table.)