Lexurgy SC on the Command Line¶
Run SC using the command line:
lexurgy sc changes words
changes file needs to use the Lexurgy SC Rules format; by convention these have a
words argument should be one or more text files, each containing
an old-language word per line.
By convention, these files should have a .wli extension.
Lexurgy SC accepts the following command-line options:
If this is specified, Lexurgy will ignore every rule before the specified rule (including the deromanizer). This is useful if you want to introduce loanwords or affixes partway through the language’s history.
If this is specified, Lexurgy will ignore the specified rule and every rule after it. This is useful if you want to evolve some forms partway, then modify them and resume (using
If this is specified, each input file name will have the specified suffix added. For example,
lexurgy sc changes.lsc nouns.wli verbs.wli -i oldwill actually look for the files
verbs_old.wlito read old-language words from.
By default, the new-language words are written to files with the same names as the input files, but with
_evattached to the file name (so the words in
nouns.wliwill have their new-language forms written to
nouns_ev.wli. But if
-ois specified, the output files will have that suffix instead. For example,
lexurgy sc changes.lsc nouns.wli verbs.wli -i newfangledwill produce output files
Indicates a word to trace through its changes. Each change applied to the word will be displayed in the terminal and also written to a file with the suffix
_traceon it. Depending on your terminal font and encoding, IPA characters might not render correctly in the terminal, so check the
_tracefile if you think there’s a problem with the terminal output.
This option can be specified more than once to trace several words. For example,
-t pika -t talimu -t atepinowill show how the changes to apply to pika, talimu, and atepino.
This activates intermediate romanizers, so that Lexurgy will produce a
.wlifile for each intermediate romanizer in addition to the main romanizer at the end of the .lsc file.
This deactivates the main romanizer, so the output files will have the phonetic forms instead of the romanized forms. This is useful if you think there might be mistakes in your romanizer.
This turns off the
<old-word> => <new-word>format in the
This makes Lexurgy compare its output files to the existing contents of those files before replacing them. The existing words are written to the
.wlmfile after an
XX. For example, if the previous version of the .lsc file turned kehati into kiade, but you’ve now added a palatalization rule that turns ki into ch, then the
.wlmfile will show
kehati => chade XX kiade.
This is useful if you’re making tweaks to the sound changes for an established language and want to make sure that the tweaks don’t have unintended consequences.