shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

278
active users

#unicode

3 posts3 participants0 posts today

#Unicode is one of those little things in life that I can't help but smile about.

Is it perfect? No, of course not. Is it better than the alternative? Yes, so much so that every time I'm confronted with a long list of character encodings I can choose from, I feel a sense of relief when I find #UTF8 among them.

I wouldn't have thought it possible to standardize a single character encoding for everyone, and yet, somehow, there is just such a standard.

#itch #itch_io #gamedev #devlog #commonLisp #programming
Getting back into that game dev saddle.

Demo successfully shows that *this* *was easy* *for everyone*.

#McCLIM #gui #unicode character world adventure for a
> (unget:unsy '(smiling cat))
😸
"😸"
|#x1F638|
#\GRINNING_CAT_FACE_WITH_SMILING_EYES

lispy-gopher-show.itch.io/lisp

I became tired while writing the codes so it's a story told through pictures and a video clip of #emacs.

Encourage me to write it up later. lispy-gopher-show.itch.io/lisp

Today I learned that there is a specific #unicode "record separator" symbol, formally known as "U+001E Information Separator Two".

codepoints.net/U+001E

It is meant to be used to indicate a separation between two units of information. An example of where this could be used is in a separated-value file, e.g. a CSV, but using this symbol instead of a comma.

This is interesting because there are vanishingly few instances where the record separator symbol would appear in most contexts, but many instances where a comma appears. Using this symbol instead of a comma (or a semi-colon, or an exclamation point, or any one of the usual separators) could make some data hygiene scenarios much more straightforward.

Codepoints.netU+001E INFORMATION SEPARATOR TWO*: ␞ – Unicode␞, codepoint U+001E INFORMATION SEPARATOR TWO* in Unicode, is located in the block “Basic Latin”. It belongs to the Common script and is a Control.

Hey everyone. I must admit, I don't believe I have ever seen someone enter #utf8 #unicode characters on a #computer in a natural way. Which seems weird, because a bunch of languages use them.

I wrote a #commonLisp #asdf package that just looks up a list of symbols in a file that has every non-surrogate unicode codepoint in it, and an #emacs #elisp function that just calls the #lisp one.

codeberg.org/tfw/unicode-chars

Multilingual people, what can you tell me about doing this at all?

Hello, I'm an open source software engineer in my late 30s living in #Seoul, #Korea, and an avid advocate of #FLOSS and the #fediverse.

I'm the creator of @fedify, an #ActivityPub server framework in #TypeScript, @hollo, an ActivityPub-enabled microblogging software for single users, and @botkit, a simple ActivityPub bot framework.

I'm also very interested in East Asian languages (so-called #CJK) and #Unicode. Feel free to talk to me in #English, #Korean (#한국어), or #Japanese (#日本語), or even in Literary Chinese (#文言文, #漢文)!

A typographical sin that's been annoying me recently:

#Unicode has a specific code point U+2212 for MINUS SIGN, for use when you mean the mathematical notion of subtraction or negation. Any other uses of a horizontal line have separate code points: hyphens, various lengths of dash, box-drawing characters. You can _tell_ when someone means mathematical minus.

Why would a font deliberately make U+2212 a _different width_ from PLUS SIGN?!

Here are some emojidentifiers for your next Python code:

import math
乁_ツ_ㄏ = None
乁_益_ㄏ = math.nan

def minnums(values: list | 乁_ツ_ㄏ = 乁_ツ_ㄏ):
if (
values is 乁_ツ_ㄏ
or not all(isinstance(n, (float, int))
for n in values)
):
return 乁_益_ㄏ
return min(values)

In the old #ASCII days, you could change a letter between upper and lower case by XORing its character code with 0x20. Of course, if you tried this with anything that wasn't a letter, you'd get nonsense results.

If you try that with #Unicode code points, it sometimes works, and sometimes doesn't. But Unicode can deliver much more impressive nonsense when it doesn't.

A fun example I just found: the "lower-case" version of CAR is NO PEDESTRIANS.

>>> chr(ord('🚗') ^ 0x20)
'🚷'