The burden of locked grids & blooming dots


Stuck in a rut, boxed in by restraints, griddled by grids?

You know what I love? Beautiful type. Gorgeous books, letterpress, ink and the swish of the pen. The flow of thought communicated through the way words are placed on a page, and the artistry and design intent hidden behind a functional form.

You know what I work with? Yep that’s right. Grids and dots. LCD displays and CRT monitors. I also work with developers, architects and mad mathematicians – let alone the infamous fearless Scotsman who runs our group!

For a typophile such as myself, you know where I’d like to be? I’d like screen viewing and reading to be as flawless as possible. But at the moment we have a ways to go before we get there and that’s the challenge.

In the past and at the moment type on-screen is limited by the resolution of the screen. No matter how delicate and subtle the outline shapes may be, when they are being rendered onscreen at small sizes they have to be mapped to a fairly crude grid of pixels. Here’s a short video for those of you who have not come across hinting for type before:

This video explains what a fairly coarse grid does to black and white rendering. Black & white rendering is pretty stark, and aliased stair-stepped jaggy text is just plain ugly. It’s a far cry from the original intent of the design, although it was the best we could do at the time.

And simply put whether the edges of these pixels are sharply defined or blurred depends on the method of rendering, the kind of anti-aliasing used and the quality of the light emission behind the screen and so on.

Also for starters there’s a small matter of hardware and screen resolution. Now don’t get me wrong, there’s been huge leaps in improvements along this axis. Today, most displays are 100DPI or less, but there are newer displays out there with a resolution of around 130DPI, 150DPI, and 200DPI. And the higher you go the smaller the grid, the smaller the pixel, until eventually you won’t even notice there is a grid, or dot behind the line…more to follow…

Hi. My name is Geraldine Wade and I’m a Design Program Manager in the Advanced Reading Technologies team. Our group is particularly involved with rasterisation, technological type advancement and the science of reading. I have been involved with hinting, designing and managing font projects tied to technology advancements for Microsoft since the Windows 3.1 core fonts and I want to talk about the restraints we have with designing for onscreen reading, where we have been, where we are now and where we’d like to go in the future.

 

Edit: Update Image References


Comments (19)

  1. Cornflake says:

    Good blog! Keep up the good work. πŸ˜‰

  2. StoneSans says:

    Great start – subscribed!

    oh, for any CSS gurus who manage blogs.msdn.com — the fonts on this blog appear unreadably small on Firefox πŸ™ … a fix would be great. And thanks for the Vista fonts preview!

  3. Edge says:

    Is it my imagination or does the article get cut off just after the video link? It looks like it starts mid-paragraph.

    Love the blog though, keep up the good work!

  4. Si says:

    GW > I also work with developers, architects and mad mathematicians…

    don’t forget researchers πŸ™‚

    Will > Is it my imagination…

    No

  5. fbcontrb says:

    Thanks Will! Have updated this – should make more sense now;)

  6. LarryOsterman says:

    Either you guys need bigger pipes on the server streaming that video or you need to allow us to download it. It’s essentially unwatchable because of al the audio and video dropouts…

  7. Dave Solimini says:

    The video is GREAT… i never knew how that worked and now i’m hooked — awesome

  8. λͺ‡ 가지 ν₯λ―Έλ‘œμ› λ˜ λ…Όμ˜μ™€ ν•¨κ»˜, High DPI에 λŒ€ν•œ λ§Žμ€ λŒ“κΈ€μ„ λ‹¬μ•„μ£Όμ…¨μŠ΅λ‹ˆλ‹€. λŒ€λΆ€λΆ„μ€ μš°λ¦¬κ°€ μˆ˜μ§‘ν•΄ 온 데이터와 μΌμΉ˜ν•˜λŠ” 쒋은 μ˜ˆλ“€ μž…λ‹ˆλ‹€. μš°λ¦¬κ°€ 데이터λ₯Ό 가지지 μ•ŠλŠ” 뢄야에