this post was submitted on 15 Jun 2025
7 points (88.9% liked)

Typography & fonts

556 readers
2 users here now

A community to discuss and share information about typography and fonts

Sibling community:

!typography@lemmy.world

Rules of conduct:

The usual ones on Lemmy and Mastodon. In short: be kind or at least respectful, no offensive language, no harassment, no spam.

(Icon: detail from the title of Bringhurst's Elements of Typographic Style. Banner: details from pages 6 and 12, ibid.)

founded 2 years ago
MODERATORS
top 3 comments
sorted by: hot top controversial new old
[–] threeganzi@sh.itjust.works 1 points 6 days ago

I skimmed the article and not sure I understand the problem. Turkey has some additional glyphs variant of i. So what?

[–] matj1@lemmy.world 2 points 1 week ago (1 children)

I think that Unicode implements Turkish wrong. I tried to make a proposal to Unicode, but, when I gave that for checking to someone involved in Unicode, I was told that such proposal would be futile because Unicode can't break compatibility.

Presently, there is a case pair of I where the small I is dotted, and the capital I is dotless, then there are separate dotless small I and dotted capital I. My proposal was that the common case pair of I would have unspecified dottedness, and there would be a separate case pair of dotted I and a pair of dotless I for Turkish.

This was done with the idea that, in most languages, dottedness of I is just a typographic choice similar to the shape of small A. My proposal would enable fonts where small I is by default dotless like in the Carolingian minuscule but which support Turkish.

[–] threeganzi@sh.itjust.works 1 points 6 days ago

Does Unicode define case pair relationships of glyphs? My understanding was that it doesn’t and in that case it doesn’t matter.l, right. But I’m sure I’m wrong :)

Not sure I understand what you want these fonts to be able to do. Isn’t that already possible regardless of approach?