any (ambitious) future plans?

[guillaume-d]

ATM this fork seems the most lively one: any plans to fix digitapex#2, impleement digitapex#4 or even digitapex#5?
Are MRs welcome? (No promises though.)

[machiav3lli]

If you'd like we can work on it together as OABX is my main focus for now and am still waiting the FDroid MR to be merged.

[guillaume-d]

(Took me a while to find that OABX is https://github.com/machiav3lli/oandbackupx 😉!)

Until the end of the year I will probably be busy with other things but still, at some point:

• I'd like to fix some words can have several genders: support? digitapex/DerDieDas#2 by removing the few "problematic" words from the app's word list, unless someone else has time to implement a better solution
• I might try to implement 2. from some words can have several genders: support? digitapex/DerDieDas#2 (comment)
• I would definitely like to try to implement teach rules instead of single words digitapex/DerDieDas#4 by folding all words following rules that are correct more than n% of the time (or get rid of more than 50 words) into a single word: for example: Einfachheit, Einheit, ... -> *heit: die
• I have no time to implement teach plurals too? digitapex/DerDieDas#5 myself

IIRC implementing the above might need only forking https://github.com/digitapex/ParseWiktionary but I'd be happy already if you would accept a modified word list generated by such a fork and make the modified DerDieDas app available in F-Droid and/or IzzySoft's F-Droid repo.

[machiav3lli]

Actually I was thinking to turn to a sqlite(room)-based DB to facilate future changes to the logic along with conversion to kotlin. This will possibly happen slowly and your contribution is always welcomed.

[machiav3lli]

About FDroid, the MR is already hanging there since couple of months, but as the team is laging behind, I would say it'll take some more time. The app is also already available on IzzyOnDroid though.

[guillaume-d]

Actually I was thinking to turn to a sqlite(room)-based DB to facilate future changes to the logic along with conversion to kotlin. This will possibly happen slowly and your contribution is always welcomed.

SQL certainly makes more sense than the not-sorted-whatsover https://github.com/digitapex/DerDieDas/blob/master/app/src/main/res/raw/list_nouns.txt!

About Kotlin: I sympathise with the idea but cannot promise to help with Kotlin coding, as I would still need to learn it and am not sure I can find the time for that.

But for me the biggest issue is now #3. Anyway I am still determined to work on https://github.com/digitapex/ParseWiktionary to get a better wordlist as starting point.

[machiav3lli]

Ok, so it'll stay in Java.