Latest news Older news
Fixed a bug wherever there were comments
Yet another subtle thing changed in newer Django's that lead to the dreaded "500 Server Error", this time whenever there were comments on something. The fix is easy to verify by checking the language page for Testarossa since that one always predictably failed.
Pinned: 2026-01-03 22:07
Logout bug fixed
There was an error when clicking on the "Log out" link, this has been fixed.
Pinned: 2026-01-03 16:43
2025-12-30 15:55 Django updated
CALS depends on Django for most of its magic, and as of today CALS runs on the latest stable version: 5.2.
More importantly, the "new" way to deploy CALS is finished, done and working. Once upon a time, CALS the website was updated via ssh, rsync and a phat Makefile. These days it is much simpler, thanks to git version 2.3 and being able to update a checked out branch via push. (Search for "git push to deploy"). Both old and new methods are worthy of proper blog posts, but this is not the right venue and Your Humble Admin do not have an official blog space for longer stuff atm.
Most importantly, it is now easy to update CALS.
2025-12-27 20:54 Lots updated!
CALS and its dependencies have been greatly updated, thus ended an odyssey that started in September 2025. There were some surprises even today.
All twitter support is gone.
- OS: debian
- bullseye → trixie. Going from bullseye to bookworm was easy-peasy but the next jump from bookworm to trixie had some surprises.
- Database: PostgreSQL
- 13 → 17. Bookworm had version 15. Trixie has version 17 and there were some oddities re. collation that I need to check out more closely, some other day.
- Python
- 3.9 → 3.13.
- Django
- 1.8 (1.11 dev.cals) → 4.2. Dependency hell, this one, started working on it in September this year. This was fun, not.
Also, how to push changes to CALS's code proper has changed and is not 100% finalized yet. The code currently hosted on Codeberg (CALS repo) is slightly out of date, some dependencies needs to be added.
The RelayMuseum has not been updated yet (needs code update) and is down until further notice.
What defines your conlang?
By adding your language here, and answering the questions by choosing a single value for each relevant WALS-feature (e.g. it's not a goal to answer every single one of them!), you might discover new things in your conlang, or grammar gaps that need to be filled somehow. By reading the descriptions of each feature at WALS, you also get a crash course in linguistic typology and universals – but be warned, some of those papers are overly scholarly...
CALS challenges
- Pick some features and values at random, then try to make a language out of that.
- What would the most average conlang look like? Should it be updated to stay the most average?
- Contrary, would a conlang with many rare and unusual features be usable at all?
|
|
|
|
New stuff and changes have been moved to its own page. See also the link in the footer.
