Re: Case for letters j and J with acute

From: Asmus Freytag (t) <>
Date: Tue, 9 Feb 2016 14:19:34 -0800
On 2/9/2016 1:36 PM, Ken Whistler wrote:

On 2/9/2016 1:23 PM, David Faulks wrote:
Perhaps Unicode could create a ‘default position’ property for combining characters, and encourage OpenType and other font engines to adopt it for automatic use when no other font information is provided. Adoption would take a while, but I cannot help but think that otherwise, this issue will never go away.

It does. General_Category=Mn and ccc=230 indicates that a character is
a non-spacing mark positioned *above* its base.

Attempting to get more precise that that with a *character* property would
be a mistake. Such interaction in detail between a mark and its base is
an attribute of glyphs and their design, and properly belongs to the realm
of rendering and fonts.

What about GC=Mn and ccc=0?

For those, an actual positional property would make sense.

It wouldn't need to be overly specific.

For example, for Unibook, I allow a convention to supply this information to place a glyph in relation to the dotted circle; it's described in the help file. There are some special wrinkles there, because the values are tweaks that get applied to known fonts (that just happen to not do the right thing when combined with an the standard dotted circle in the charts).

However, this approach would seem to indicate that such a scheme is possible and with just a few values sufficiently differentiated to be of practical use (= immensely improve on the fallback).



Received on Tue Feb 09 2016 - 16:20:38 CST

This archive was generated by hypermail 2.2.0 : Tue Feb 09 2016 - 16:20:38 CST