nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqfhywkegwd6vccuetxrqze9vefd2th07yk57rwpva8avnl9knphcs3r9ng9 (nprofile…9ng9) I’m familiar with the script ordering, which, frustratingly, ignores the most relevant and reliable data point which is the dlng tag in the meta table.
The first versions of the Tiro Indic fonts had a relatively small Latin subset, and they were sorted with by the Indic script. The new versions have a larger Latin subset, and ID is sorting those newer versions with the Latin fonts, even though the meta table specifies the Indic script as dlng.
_
Something else seems to be going on with this one font, though, because the error is affecting only one member of the font family. All the fonts have identical glyph sets and cmap tables. And the problem is limited to ID 2026: in the previous version it is fine.
Tiro Typeworks
npub1rm…wuntj
2026-08-18 14:54:36 UTC
in reply to nevent1q…e5ll
Author Public Key
npub1rmg092al9kzwfgzrv57jx3frhm2efcw4eu42n8hfswjewv3autuq0wuntjSeen on
wss://relay.ditto.pubPublished at
2026-08-18 14:54:36 UTCEvent JSON
{
"id": "94701eb992927b6fe161a6e3c6c28f4f16dc314dc252d8a4579ddf064d1ef797",
"pubkey": "1ed0f2abbf2d84e4a043653d234523bed594e1d5cf2aa99ee983a597323de2f8",
"created_at": 1787064876,
"kind": 1,
"tags": [
[
"p",
"4dc8eb650e6e998c732b30c02c95994b54bbbfc4b53c37059d3f593f96d30df1",
"wss://relay.ditto.pub"
],
[
"p",
"b0f2f53242d2911aeef19ef75e999fcc658d8dd9e9e9cf1bc03fd9fa7048a7a4",
"wss://relay.ditto.pub"
],
[
"e",
"e12f6b7045973295dbb3f3f3cb186cc397435d2740c661d1d049cb8d34bd02d9",
"wss://relay.ditto.pub",
"reply"
],
[
"proxy",
"https://typo.social/users/TiroTypeworks/statuses/117117083755415787",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqfhywkegwd6vccuetxrqze9vefd2th07yk57rwpva8avnl9knphcs3r9ng9 I’m familiar with the script ordering, which, frustratingly, ignores the most relevant and reliable data point which is the dlng tag in the meta table.\n\nThe first versions of the Tiro Indic fonts had a relatively small Latin subset, and they were sorted with by the Indic script. The new versions have a larger Latin subset, and ID is sorting those newer versions with the Latin fonts, even though the meta table specifies the Indic script as dlng.\n_\n\nSomething else seems to be going on with this one font, though, because the error is affecting only one member of the font family. All the fonts have identical glyph sets and cmap tables. And the problem is limited to ID 2026: in the previous version it is fine.",
"sig": "53cd17664970c00f5e5f893c2d24337ade1721eb614f7d76fc0e206cb5e2cb58f75f0430059fb2b67bc84f0786b7868a1d0aec000aa17757b2422a1e59febd67"
}