sorrel
f052c87c9c
All checks were successful
ci/woodpecker/push/build-and-deploy Pipeline was successful
55 lines
3.5 KiB
Scheme
55 lines
3.5 KiB
Scheme
'(article
|
|
((id "latl-primitives")
|
|
(class "composed-article"))
|
|
;; brief intro - restate the problem
|
|
(section
|
|
((id "intro"))
|
|
(hgroup
|
|
(h1 "what must be true of latl primitives")
|
|
(p (em "what will latl need to " (u "do") " out of the box?")))
|
|
(p "i've talked a little about "
|
|
(a ((href "/unsettled/1")) "conlanging and latl")
|
|
" previously here. the short version is this: making languages (for theoretical conscious beings) is fun! it's been a consistent hobby and artistic pursuit for me for much of my life. i've had different approaches from making extremely regular languages, to simulating the evolution of a family of spoken languages, to a family of synthesizer languages for a fractured machine society. every language project requires keeping track of a dictionary and a grammar (even if they never become more than quick sketches) and any sufficiently involved project can benefit from tools for generating new words that fit a language's 'phonotactics', generating derived words based on grammatical rules, simulating language change over time. conlanging is a hobby with enough overlap with computation, that some conlangers have created tools for some of these tasks. my own projects have become too ambitious to have my work live in spreadsheets over here and latex files over there and text files with the defintions i provide to web-based tools somewhere else entirely. i want to build on the work of those came before and create a substrate upon which any tool a conlanger needs could be built and in which i can define the entirety of a language in one system.")
|
|
(p "at it's base latl will be a tool for operating on languages, invented (or otherwise... maybe.) it helps then to think of the sorts of things that encompass language. spoken and signed languages will be the assumed base case, as those are the things real human beings usually use to communicate with each other. the modality of a language needn't be important to the primitives used, but it's always a good practice to state assumptions"))
|
|
(section
|
|
((id "contents"))
|
|
(ul (li (a ((href "#what-is-language")) "go to what-is-language"))
|
|
(li (a ((href "#what-conlangers-do")) "go to what-conlangers-do"))
|
|
(li (a ((href "#proposed-latl-primitives")) "go to proposed-latl-primitives"))
|
|
(li (a ((href "#signoff")) "go to signoff"))))
|
|
;; article contains three main sections:
|
|
;; 1. thinking about language
|
|
;; 2. talking about conlangers
|
|
;; 3. working through some ideas for primitives
|
|
;; ---
|
|
;; section 1. thinking about language
|
|
(section
|
|
((id "what-is-language"))
|
|
(hgroup
|
|
(h2 "thinking about what language is for a moment"))
|
|
(a ((href "/unsettled/latl-primitives_what-is-language")
|
|
(hx-get "/hx/unsettled/latl-primitives_what-is-language")
|
|
(hx-target "#what-is-language")
|
|
(hx-swap "outerHTML"))
|
|
"what-is-language"))
|
|
;; section 2. okay but conlangers
|
|
(section
|
|
((id "what-conlangers-do"))
|
|
(hgroup
|
|
(h2 "what conlangers do")
|
|
(p (em "moving from a pile of language stuff to a pile of problems to solve")))
|
|
(p "coming soon"))
|
|
;; section 3. introducing the primitives
|
|
(section
|
|
((id "proposed-latl-primitives"))
|
|
(hgroup
|
|
(h2 "introducing the primitives")
|
|
(p (em "things that definitely need to be present in latl")))
|
|
(p "coming soon"))
|
|
;; brief conclusion and next steps
|
|
(section
|
|
((id "signoff"))
|
|
(hgroup
|
|
(h2 "signing off")
|
|
(p (em "what's next for latl thinking?")))
|
|
"coming soon"))
|