John Smith's Blog

Ramblings (mostly) about technical stuff

Steve Jobs' grinning turd

Posted by John Smith on

Given the App Store's reputation for prurience when it comes to approving things, it's slightly eyebrowraising to find this delightful fellow in the iOS Unicode character set:

Screengrab from an iPod Touch showing unicode character e05a in Mobile Safari

This came to my attention via this post on Asiajin, which is largely derived from this Japanese-language blog post.

I recalled seeing some weird colour bitmap icons hidden a long way down, when using UnicodeTable a while ago. Digging around again, it turns out that this is character 0xE05A in the private use area (PDF link), where vendors can - and do - put whatever they like.

On Windows 7, OS X Snow Leopard and Android 2.1, nothing seems to be defined for these characters in the default browser font. On Fedora, they are a mix of Asian (?) glyphs and dingbats; 0xE023 is a smiley with an eyepatch, for example. On iOS... well you can see for yourself in the above screengrab, or go to this link if you don't believe me. The character entity itself is , which will render as a placeholder box or similar on machines without a glyph defined for it.

Helvetica is dangerous

Posted by John Smith on

For the past couple of months or so, I've been using the "Minefield" nightly builds of Firefox 4.0 rather than the "official" 3.6.x releases - 4.0 truly is an upgrade that merits the increment of the major version number.

It therefore came as a bit of a shock when I viewed this blog using 3.6.12 on my Mac - just about all the text was showing in an italic (or possibly oblique) typeface! My initial panic subsided when I confirmed that everything still looked as expected in every other browser, but this didn't get any closer to resolving the issue. Using Firefox's "Inspect Element" functionality gave no further clues, insisting that the text was in a regular font, despite the evidence in front of my eyes.

A quick hack-up of an HTML test file proved that I wasn't going insane, and that there is in fact a bug in Firefox 3.6:

Screen grab from Firefox 3.6 on Mac OS X, showing Helvetica text rendered at different font-weights.  The text at lower weights is italicized

Some cursory Googling didn't find any reports of exactly the same issue, but this thread (started by no less than Jeffrey Zeldman!) covers similar ground.

I did try explicitly setting the font to be Helvetica Neue Light, but it transpires that Firefox ignores this, and requires you to use font-weight, which as we've just seen is broken - thanks a bundle...

As the bug seems to have been around for a while, and is fixed in the 4.0 betas, I don't hold out much hope of it being rectified in the 3.6.x releases. As a workaround, I've fallen back to using Arial for the headings, as does work correctly with the lower font-weight values.

Windows ClearType makes Droid Sans look worse

Posted by John Smith on
Zoomed examples of rendering of Droid Sans upper-case C in various browsers/operating systems, using the default type rendering

TypeKit have recently posted a piece about font rendering in various browsers/operating systems that has inspired me to investigate something I'd noticed recently.

This blog uses Droid Sans for the headings. On Linux and OS X, this looks fine, as does Windows XP. On my Windows 7 machine however, it looks pretty horrible - the tops and bottoms of Cs are particularly bad, really jagged.

To work out why, I did rendered some test HTML using a couple of different fonts on several browsers. Here's an example, showing (from left to right)

  1. Firefox 4 beta on Linux (Fedora 11)
  2. Safari on OSX
  3. IE9 on Windows 7
  4. Firefox 3.6.11 on Windows 7
  5. Firefox 3.6.11 on a MacBook running Windows XP via Boot Camp

Examples of Helvetica/Arial/sans-serif and Droid Sans in various browsers

The four lines of text are. in turn:

  1. Helvetica/Arial/sans-serif lower case
  2. Helvetica/Arial/sans-serif upper case
  3. Droid Sans lower case
  4. Droid Sans upper case

(There's no difference between IE9 beta and Firefox 3.6.11 on Windows 7 in the image above, that I can see, but apparently they should be using different rendering technologies.)

The root cause turns out to be the different font rendering technologies used in various versions of Windows:

  • XP defaults to "Standard", which is regular anti-aliasing, with options for ClearType (sub-pixel rendering) or no aliasing at all (the latter being really horrible to look at.)
  • Win7 gives a choice of ClearType being on or off. Turning it off seems to be the same as "Standard" in XP, although I'm not 100% certain on that
It's not an issue with sub-pixel rendering per se, as Mac OSX uses it - but it looks like OSX is much more subtle about how it does it.

Arial looks better in Win7 with ClearType on, as does the Windows "system" font, so I wonder whether there's an issue with hinting, and/or font designers tweaking fonts to best cater for the underlying font technology?

On other thing that might be worth mentioning, if you're playing with the font rendering in Windows, various browsers react differently when you change the settings:

Firefox, OperaChange takes effect instantly
Chrome/IronChange takes effect when page is refreshed
SafariChange takes effect when browser is restarted
IE9No change - you are stuck with ClearType/DirectWrite, whether you like it or not

About this blog

This blog (mostly) covers technology and software development.

Note: I've recently ported the content from my old blog hosted on Google App Engine using some custom code I wrote, to a static site built using Pelican. I've put in place various URL manipulation rules in the webserver config to try to support the old URLs, but it's likely that I've missed some (probably meta ones related to pagination or tagging), so apologies for any 404 errors that you get served.

RSS icon, courtesy of RSS feed for this blog

About the author

I'm a software developer who's worked with a variety of platforms and technologies over the past couple of decades, but for the past 7 or so years I've focussed on web development. Whilst I've always nominally been a "full-stack" developer, I feel more attachment to the back-end side of things.

I'm a web developer for a London-based equities exchange. I've worked at organizations such as News Corporation and Google and BATS Global Markets. Projects I've been involved in have been covered in outlets such as The Guardian, The Telegraph, the Financial Times, The Register and TechCrunch.

Twitter | LinkedIn | GitHub | My CV | Mail

Popular tags

Other sites I've built or been involved with


Most of these have changed quite a bit since my involvement in them...