Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

HarfBuzz Slug Support with WebGL

harfbuzz.github.io

Post reply on HN
Print view View original

1–9 of 9 posts

Re: HarfBuzz Slug Support with WebGL

#2

Post by tikimcfee »

Very cool. I've noticed slug popping up more often on HN and I've been thinking of finding a way to incorporate it into my project as well.

Is this yours? What's your rendering system like - anything novel or fun you run into when working with text and GPU parallelism?

Re: HarfBuzz Slug Support with WebGL

#3

Post by mcraiha »

tikimcfee wrote: post #2

Very cool. I've noticed slug popping up more often on HN and I've been thinking of finding a way to incorporate it into my project as well. Is this yours? What's your rendering system like - anything novel or fun you run into when working with text and GPU parallelism?

Not mine. I noticed that Aras was mentioning it https://mastodon.gamedev.place/@aras/116335267839588454

Re: HarfBuzz Slug Support with WebGL

#8

Post by eviks »

behdad wrote: post #7
eviks wrote: post #6

Are there good explanations/demos comparing this to msdf?

msdf still suffers from detail loss at large sizes, which this method doesn't have.

Thanks, how large of a size? And at lower sizes, what's the performance/quality like? Is this the silver bullet?

Re: HarfBuzz Slug Support with WebGL

#9

Post by amitp »

eviks wrote: post #6

Are there good explanations/demos comparing this to msdf?

Slug preserves the vector shapes. MSDF first converts to a texture, which can lose small details. How much depends on the size of your texture and the complexity of the font. I expect MSDF will never look better than Slug.

However, MSDF can handle lots of distance-based effects (glow, shadow, outline, gradient, etc.)[1], and I don't think Slug does that. And MSDF is constant time whereas (I think) Slug is going to vary depending on the complexity of the font.

The Slug paper [2] says:

  All of the techniques that store data in a texture atlas are inherently using a discrete
  sampling of what is actually an infinitely precise description of a glyph outline. This
  inescapably leads to limitations that can be mitigated by increasing the resolution of
  the texture atlas, but that can never be completely removed. For applications that
  need to render a wide range of characters at potentially large font sizes, a texture atlas
  capable of producing glyphs at an acceptable level of quality may have prohibitively
  large storage requirements.
[1] https://www.redblobgames.com/articles/sdf-fonts/#demo

[2] https://jcgt.org/published/0006/02/02/

Post reply on HN