hallowxiii / pylaut Goto Github PK

Issue trackers are a nice thing b/c you can tick the box when you have implemented e.g. unlimited rice pudding and they provide an incidental way of logging conversation.

Syllables fail to correctly analyze their own structure. This includes some segments not being counted as consonants when they should be, but most pressingly syllables with resonant nuclei automatically also take their nucleus as a coda consonant, which fucks with syllabification by obscuring syllables of the form CRV.

Where do user-specified featuresets, sound change libraries etc get included
How do we make this not a huge chore

It would be great if this were done properly. Like with pyre.

Further to the Boxing Day webinar, I have thought it over and am personally offended by the idea that we should try to accurately model the basically stochastic nature of sound change and think this should be a firm Neogrammarians Only Zone.

That said...
By all means, the LangTree infrastructure should be strong enough to support arbitrary exemption of lexemes from arbitrary sound laws, but they should be programmed in manually by Dhok.

Or, at the very most, there should be a module which would generate exemption lists automatically.

With coverage metrics, and so on.

goes well with Milchreis

Jokes aside, the dill library can actually serialize Change objects. Look into this!

The biggest example for this is anything phone-related. We want people to be able to use non-Monophone classes they write themselves, but we depend on certain capabilities for use in e.g. phonologies. Best way to do this is write e.g. an Phone (or Phoneme) ABC so typechecking is uncomplicated.

a) how many diacritics will we support
b) tautological forms

User-facing documentation, especially for things that are by their nature not documentable via code comments, such as PyLautLang, and how to set up a PyLaut workflow.

"basically, a bit of probability shit on top of our word-handling"

• noting when irregular forms/declensions/conjugations/analogy opportunities are created

The entire thing must be readable and commented, as well as as devoid of shitty kludges as possible.

Including:

*updating of clever phonology stuff

*warnings about gaps in systems/Systemzwang stuff produced by sound changes

The user should be able to save the current state of their language rejiggling efforts to disk to pick them back up later and also share them, as best as possible

This is trivial for objects with text representations, but may be hard for e.g. sound changes that are supplied as user-defined functions. Do we just skip those or do we attempt pickling?

idk how much of this u did already, the Urwunschlist has:

a) deriving FROM lexicon
b) defining manually/correcting autoderived rules
c) detecting errors in lexicon
d) autosyllabification of words

Milchreis, auch Dicker Reis oder Reisbrei, ist eine Süßspeise aus Rundkornreis, der langsam in Milch gekocht wird. Dabei werden im Reis enthaltene kurzkettige Stärkemoleküle gelöst und dicken die Milch ein (Verkleisterung). Das Ergebnis hat eine sämige, weiche Konsistenz, in der die einzelnen Körner noch erkennbar sind. Der für die Zubereitung verwendete Rundkornreis wird gelegentlich selbst als Milchreis bezeichnet.

when u have it boy u have it made

everyone likes a phonology chart

• bearing in mind that they pattern differently from consonant clusters and take roles
  more like pure vowels in systems-analyses