The support for the German Capital Sharp S character (ẞ) on desktop operating systems is already quite good, considering the fact that the Unicode 1E9E was assigned just four years ago and that the need for this character is a pretty local and still controversial subject. On Windows all major system fonts like Arial, Times New Roman, Segoe UI and Verdana are equipped with an ẞ since Windows 7. On Mac OS the only official Apple font which has a (pretty ugly) Capital Sharp S is Geneva. But even if a text is displayed in a typeface like Lucida Grande, most users will see the character anyway, since many apps will just pick the missing character from a different font like Arial.
In addition to system fonts, a growing number of commercial font families (currently over 200) and OpenSource fonts like Linux Libertine provide support for the ẞ character.
On mobile devices the support is still pretty much non-existent. Which is rather disappointing since the use and discussion about the ẞ character mainly happens on websites and social networks like Facebook and Twitter. And even if you don’t like the idea of a Capital Sharp S use for German text, you should be able to see it in a Tweet and not a NOTDEF square, which tells you nothing about the missing character.
Capital Sharp S (U+1E9E) used in tweets. Left: iOS5.1, Middle: LG Android 2.3.4, Right: Nokia X7 Symbian
(Thank to @bakooa for providing the screenshots)
Surprisingly only the Symbian phone shows an ẞ from a fallback font. iOS and Android neither have it in their default fonts, nor do they show a fallback character from a different font. As expected, Windows Phone devices show the ẞ in most fonts correctly, as it they are using the same fonts as the Windows on desktop computers.
I have set up a test page to check the Capital S support in the browsers of mobile devices.
On my own iOS 5.1 device (see screenshot), the only way to see a ẞ is using a webfont, but many apps will use the default fonts on the device and therefore not show the character. I am curious: Does your phone already support the Capital Sharp S with pre-installed fonts? If so, please leave a comment.
The Capital Sharp S does not work with Opera Mobile 12 on a Nokia 5230.
Android (in my case, ICS on an HTC Sensation) is a mess. In some places, it shows the NOTDEF blob, in others some white space. Maybe one of the system fonts actually has U+1E9E but it is just white space?
The various browsers are odd, too. The system browser shows the NOTDEF in Times N.R., white space everywhere else and the proper character in the webfont. Chrome shows white space everywhere, including the webfont which it doesn’t load. Something must be broken with your test page, though, since webfonts work fine elsewhere (e.g. http://partim.de/pub/goethe/). Firefox Mobile has white space everywhere except in the webfont.
“Surprisingly only the Symbian phone shows an ẞ from a fallback font.”
I reckon, since Nokia had[1] the benefit of Erik Spiekermann’s type work, it may not be surprising to see a ẞ via a fallback typeface. (I assume that’s being rendered in the native Symbian browser.)
[1] But apparently their corporate typeface changed recently, and things may be different inside the handsets too, now: http://spiekermann.com/en/nokia-sans-character/