mron

joined 1 year ago
[–] mron@lemmy.world 1 points 1 year ago* (last edited 1 year ago)
[–] mron@lemmy.world 5 points 1 year ago (8 children)
[–] mron@lemmy.world 3 points 1 year ago (1 children)

You'll see a version or so back in the pop shop as that allows you to downgrade easily if you need to. You don't need to install 525 if you're already on 530. You don't need to install 525 to see new versions, you'll always see new versions.

[–] mron@lemmy.world 2 points 1 year ago* (last edited 1 year ago)

Emoji support is probably the best way to demonstrate what I mean:

A simple example: if this (🐦‍⬛) renders as an image of a blackbird, your system supports Unicode 15.0.

A more complex example: if this (🧑‍⚖️) appears as a judge, your system supports Unicode 12.1, if it appears as a Person followed by Scales your system supports Unicode 10.0, and if you can only see the Scales, your system supports Unicode 4.1.

The downstream use case would be to avoid attempting to output specific characters for a user that wouldn't see them correctly (i.e. if I want to output a blackbird, I want them to see it, or if I output a judge I don't want them to see scales).

[–] mron@lemmy.world 1 points 1 year ago

I'm flexible tbh, but my initial checks with a Python approach led me to unicodedata.unidata_version, which is correct for Python support but not system support.

 

Is there an elegant, cross-platform, way to determine the latest Unicode version that a machine supports?