Three Dollar Quill

The good news is, I've managed to prototype an invocation of Lexurgy SC via tup. The not as good news is, it looks like Lexurgy SC's somewhat idiosyncratic file naming paradigm is going to require the use of Lua to actually generate the correct names, if I want to make this stuff parametric and reusable, which I do.

Let's take a look at what I had before I switched to Lua:

: src/words_old.wli |> lexurgy sc --in-suffix old --out-suffix new --out-dir ../build src/changes.lsc src/words.wli |> build/words_new.wli build/words_new.wlm

There are several things that can reasonably be varied:

• The out suffix
• The in suffix
• The path to the changes file
• The prefix to the word lists

Let's make a few assumptions:

• The user should specify the path to .lsc files exactly, since there's no funny business with the file names.
• .wli files reside in src and build, nowhere else.

From this, we have the following desired inputs, probably not in this order:

• Out suffix
• In suffix
• Input directory
• Input filename
• Sound changes

I'm going to need to think some about the exact format that I want some of those to be in. For now, I'm going to bed.

Good night.