4 ms·
So the proposal is to prebuild subpixel-smoothed images of your text for the web? Not everyone can read subpixel rendering correctly (CRTs, LCDs with weird sub
by mquander 17y ago
So the proposal is to prebuild subpixel-smoothed images of your text for the web?
Not everyone can read subpixel rendering correctly (CRTs, LCDs with weird subpixel orders, people with rotated screens.) You can't increase or decrease the font size in your browser, and you can't wrap it on a smaller screen. Plus, the text isn't selectable or searchable, which is a showstopper. That's why things like sIFR exist.
What is the point? I completely disagree that this is pretty cool. This sucks (compared to other solutions, including not doing it at all.) It is the ultimate triumph of form over function. It is like something someone would have suggested in 2001. If you want something cool, check out modern solutions to this problem like Cufon, which generates fonts that can be rendered as real text with Javascript.
That, or, you know, let the user decide how he wants to read your text instead of trying to control every last pixel on his screen.
- Maro 17y agoAnd all you need is a Mac, OSX, Ruby and some Ruby package, and then you can have really cool imagetexts on your relaxed ROR web app that you generate from the command line! But it's on github!
- tptacek 17y agoI get the sense that most modern web apps don't use sIFR or Cufon for custom typography; they use images, just like in '01. The only thing that I see changing is that it's become fashionable to use browser type in places where it wasn't before. That being the case, this is just a presentation on how to do a better job generating type images, and it is pretty cool that he put so much effort into doing a better job than Photoshop does.
- rbanffy 17y agoI think "This sucks (compared to other solutions, including not doing it at all.)" sums up pretty well what I would like to say. Thanks.