Cybernetic⚡Datapredator is a user on vulpine.club. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.
Cybernetic⚡Datapredator @Azure

The downside of trying to make a logographic conlang is it's not in Unicode and never will be. If they didn't let Tengwar in they certainly won't let my stuff in, and a logography is a much bigger ask than an alphabet anyway.

@Azure There are two different registries that utilize the Private Use blocks for Tengwar, Cirth, and other conlangs, among other things.
@Azure I'm also amused by how Unicode quietly added a couple Tolkienic runes.

@Azure Yeah. I can sorta reproduce Standard Isarthakan because the alphabet for it is similar looking enough to Latin that I can 1337sp33k it with assorted Unicode characters, but most anything beyond that is off limits without either making custom fonts or just writing the whole thing.by hand.

@Azure I knowwwwwww. ;_;

...though there's some reserved blocks, right? Could you use the codepoints for one of those along with a custom font?

@icefox Though at the moment I'm thinking of variable width logograms and huffing.

@Azure Variable-width how? That seems like a font issue, not an encoding one...

@icefox As in, commonly used logograms would be fairly thin and have relatively few strokes, more uncommon ones or technically specialized vocabulary may have many strokes and extend further on the page. Making them all around BIGGER would be appealing, though I'm not sure how to do a sane text layout when some letters are both wider AND taller than others and it's not just a case of drop caps.

@Azure Okay that IS somewhat problematic. What do you imagine the line spacing looking like in general, then?

@icefox Well, that's why i said variable width, so I can have consistent line spacing. I might try playing around with something else. If I could solve the problem it would have a somewhat aesthetically appealing consequence that bigger characters were less common words. Which would mean that structure/function words would be tiny and the more information a word carried the larger it was, so you could just glance over the 'big' words to see what a document is about.

@icefox But this makes linearization a NIGHTMARE so I'll probably just do something sensible and stick to width.

@Azure Stroke thickness might be a good way of doing it too. Actually I'm a little amused by the thought of particularly "meaty" words actually overrunning the smaller text on lines above or below.

Can always experiment and see what works well!

@icefox @Azure There's ConScript evertype.com/standards/csur/, and then Under-ConScript kreativekorp.com/ucsur/ since ConScript seems to not be updated, though both of them are broken over HTTPS and that's not very confidence-inspiring.

Still, if you want to use the private-use codepoints that might be a good place to check first.