By definition, zones cannot overlap, and the distance between any two zones must be at least 1 + 2 * BlueFuzz.
What are the threats posed by a top zone (e.g. smcp) overlapping with a bottom zone (e.g. a zone for the tittle and the droplet terminal of f, if that is even a thing)?
Comments
Plus, you need a tool that will allow this. No doubt some will, but some will doubtless not allow you to set such a conflict in the first place.
Assuming you do it? I don’t know, but I assume that the results will likely vary by rasterizer. Likely options include:
- use one and ignore the other
- try to use both zones, with potentially bad/confusing results
- ignore both conflicting blue zones
- ignore all blue zones
Less likely options:In your particular case, I am not sure I see why "the tittle and the droplet terminal of the f" would even be an appropriate candidate to get a blue zone. Is it that you hope that the bottom of the tittle would get rounded up to the f terminal position? I suppose I can see why that might be vaguely nice to have, but hardly critical. I would omit that zone before I would try to violate the spec.
I also think that if you really want that level of hinting control, you ought to be working with TrueType outlines and using manual hinting.
But also, hinting (PS or TT) does not affect all environments. Apple rendering ignores the font’s built-in hinting at all but microscopic sizes. (I gather Android can do this too, depending on the vendor and/or user’s choices.)
Or FontLab's own auto-hinter.
Or manual TT hinting.
I find manual TT hinting kind of fun, but a bit time-consuming.