2 ms·
The article you linked clearly shows lines labeled "baseline", "descender", "Latin x-height" and "ascender". And yes, it says do not use the term "cap height"
by crazygringo 6y ago
The article you linked clearly shows lines labeled "baseline", "descender", "Latin x-height" and "ascender".
And yes, it says do not use the term "cap height" but I already stated that a more inclusive term would be better. It's still obvious what's being referred to.
In current practice (e.g. put roman and Arabic fonts next to each other on the same line in your browser), the Latin "baseline" and "cap height" lines clearly are conceptually equivalent to the Arabic "descender" and "ascender" lines.
Do you see it now?
I don't understand how anyone's trying to argue that there are languages that don't have obvious logical top/bottom boundaries (or right/left for vertical scripts) for basing font metrics on.
- taejo 6y ago> I don't understand how anyone's trying to argue that there are languages that don't have obvious logical top/bottom boundaries (or right/left for vertical scripts) for basing font metrics on. I don't argue that at all. I agree that Arabic has ascent and descent. I just don't see that Arabic ascent corresponds to Latin cap height (rather than, say, Latin ascent).
- int_19h 6y agoThe argument that the article is, essentially, trying to make is that some such correspondence obviously does exist visually - i.e. that you can write e.g. English and Arabic text in the same line, sized such that they look the same size.