mron

joined 2 years ago
[–] [email protected] 2 points 2 years ago* (last edited 2 years ago)

The UK is effectively an entrenched two party system by design rather than by democratic means.

[–] [email protected] 1 points 2 years ago* (last edited 2 years ago)
[–] [email protected] 5 points 2 years ago (8 children)
[–] [email protected] 3 points 2 years ago

Changes in vote share barely correlating with seat changes will never not be depressing.

[–] [email protected] 2 points 2 years ago* (last edited 2 years 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).

[–] [email protected] 1 points 2 years 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?