Clipped rendering of negative kerning custom fonts

I'm experimenting with custom fonts that have negative kerning, i.e. glyph bounding boxes may overlap one another. The example I'll use in this post is https://fonts.google.com/specimen/Griffy

When a letter like Y is rendered in the simulator, the edges of the letter are cropped:

Is there any way to convince the renderer to render the entire character beyond the negative xoffset and short xadvance values that support negative kerning?

Here's myfont.fnt file:

info face="Custom" size=120 bold=0 italic=0 charset="" unicode=1 stretchH=100 smooth=1 aa=1 padding=0,0,0,0 spacing=1,1 outline=0
common lineHeight=207 base=147 scaleW=256 scaleH=256 pages=1 packed=0 alphaChnl=0 redChnl=1 greenChnl=1 blueChnl=1
page id=0 file="myfont.png"
chars count=3
char id=32 x=122 y=79 width=0 height=0 xoffset=0 yoffset=147 xadvance=53 page=0 chnl=15
char id=89 x=0 y=0 width=121 height=119 xoffset=-23 yoffset=33 xadvance=65 page=0 chnl=15
char id=111 x=122 y=0 width=65 height=78 xoffset=4 yoffset=69 xadvance=72 page=0 chnl=15

And the corresponding myfont.png file:

And the XML:

<fonts>
  <font id="CustomFont" filename="myfont.fnt" filter="" antialias="true" />
</fonts>

Top Replies

All Replies

  • No. I said that there (likely) wasn’t a way to do what you wanted and explained why.

    Although it's worth asking what's possible in the context of evolving technologies and competitors and user expectations. And in this case the issue seems like an implementation oversight or perhaps an over-optimisation.”

    You shifted the discussion with this.

    Battery life and the issue of legacy software is relevant to what you wrote (here).

    (Saying Garmin doesn’t care about battery life seems simply incorrect and saying Garmin is lying about it seems obviously irrelevant.

  • I think Apple and others are giving Garmin a run for their money, and if they manage to solve the battery longevity issue then there's going to be some hard talks in Kansas!

    Yes. (Though, it’s mostly Apple, by far, at the moment.)

    It seems almost certain Garmin is aware of this (and has for a while already).


    Garmin is “making hay while the sun shines”. 

    Garmin went through the same sort of thing with car navigation systems. (And a similar thing is happening with more cyclists using phones rather than Garmin Edges.)

    People have been talking about battery “breakthroughs” for years and they haven’t panned-out.

    —————————

    Apple was smart in realizing a large market could live with limited battery life.

    Seeing Apple’s success, Garmin might have realized that battery life was negotiable and that many people would be willing to trade battery life for other features (like AMOLED). 

    Easing up on battery life appears to have been a successful move for Garmin but it upset a few people (like one person here). Garmin still provides watches (the Enduro line, for example) for them but they still insist on features (along with retaining the same battery life) that require more power. This makes no sense. And you can’t please everyone anyway.