Show HN: QR code renderer in a TrueType font
11–19 of 19 posts
Re: Show HN: QR code renderer in a TrueType font
#12Re: Show HN: QR code renderer in a TrueType font
#13Not mentioned is the fact that the resulting QR Fonts are huge --- much larger than the javascript needed to render a QR code.
Re: Show HN: QR code renderer in a TrueType font
#14This is absolute black magic. I never realized OpenType rules were powerful enough to render something as complex as a QR matrix inline.
Font shaping rules are actually turing complete. An incredible amount of engineering effort has gone into this not being a total disaster everywhere at all times.
If there is a turing complete VM inside the font renderer that makes perfect sense.
I'm not sure if it's the case but at one point on Windows, font rendering happened in the kernel.
Re: Show HN: QR code renderer in a TrueType font
#15Earlier quoted context omitted.
Font shaping rules are actually turing complete. An incredible amount of engineering effort has gone into this not being a total disaster everywhere at all times.
Coming late to this thread, but this is reminding me that many remote execution vulnerabilities have come from font rendering code paths. If there is a turing complete VM inside the font renderer that makes perfect sense. I'm not sure if it's the case but at one point on Windows, font rendering happened in the kernel.
as an aside- I find the fact even microsoft's own modal dialogs don't all support DPI scaling- aka they are blurry.
Re: Show HN: QR code renderer in a TrueType font
#16Side question: Why is nobody making QR codes on web pages clickable (regardless if it’s an image or text-based)? Not every QR code represents a URL, of course, but many do. Maybe there should be a qrcode URL scheme that lets browsers behave the same way as a camera scanning a QR code.
Re: Show HN: QR code renderer in a TrueType font
#17Earlier quoted context omitted.
Font shaping rules are actually turing complete. An incredible amount of engineering effort has gone into this not being a total disaster everywhere at all times.
Coming late to this thread, but this is reminding me that many remote execution vulnerabilities have come from font rendering code paths. If there is a turing complete VM inside the font renderer that makes perfect sense. I'm not sure if it's the case but at one point on Windows, font rendering happened in the kernel.
Both Windows and Macintosh spent years trying to isolate type rendering from kernel operations specifically because of Adobe Type 1's legacy alone, including the fact that it was an ugly vendored 3rd party spaghetti. IIRC, both Apple and Microsoft ended up paying Adobe tons of money to rewrite their Type 1 Font Manager code from scratch rather than keep paying Adobe to write that code. (TTF and OpenType were also both somewhat direct responses to Type 1's legacy and mistakes.)
Re: Show HN: QR code renderer in a TrueType font
#18Re: Show HN: QR code renderer in a TrueType font
#19Side question: Why is nobody making QR codes on web pages clickable (regardless if it’s an image or text-based)? Not every QR code represents a URL, of course, but many do. Maybe there should be a qrcode URL scheme that lets browsers behave the same way as a camera scanning a QR code.