Instead of qtpl and l18n, I used html/template
and some functions. This is experimental, but
overall looks much more maintainable in the
future. Thinking...
This has several advantages over using an external CLI tool to generate
the files, such as having fewer dependencies, less generated files bloat
and more flexibility over the localization code. "Sadly", this solution
doesn't check for validity of JSON files at compile-time (the only
advantage of using an external tool such as go-localize). However, I
easily fixed this huge "issue" by making the program crash at startup if
any locale files are invalid.
Also, no more "go-localize removed from go.mod" "go-localize added to
go.mod" "go-localize removed from go.mod" spam. A utility for making
sure all translation stay in sync soon! (not sure where to put it)
* There is a link to the hypha in question in the heading, similar to other pages related to a selected hypha.
* The locale keys (?) are reworded to get rid of the word ‘query’.
* The phrasing is more precise. Kinda verbose doe.
