Mayerle’s Lithographed International Test Chart, 1907 – Circulating Now from the NLM Historical Collections
An impressive piece of internationlisation and inclusive design.
An impressive piece of internationlisation and inclusive design.
Be liberal in what you accept:
Basically, if your form can’t register Beyoncé – it has failed.
This is a great explanation of the difference between the [lang]
and :lang
CSS selectors. I wouldn’t even have thought’ve the differences so this is really valuable to me.
These are good challenges to think about. Almost all of them are user-focused, and there’s a refreshing focus away from reaching for a library:
It’s tempting to read about these problems with a particular view library or a data fetching library in mind as a solution. But I encourage you to pretend that these libraries don’t exist, and read again from that perspective. How would you approach solving these issues?
A really deep dive into the lang
attribute, and the :lang()
pseudo-class (hitherto unknown to me). This is all proving really useful for a little side project I’m working on.
Practical advice from Ire on localising web pages.
It’s a bit finger-pointy but this blog should be useful for anyone working on internationalisation.
This blog has two general aims: to show the fundamental flaws in using flags to represent languages and how to create good experiences when dealing with multilingual and multi-regional content.
The second part of Bruce’s excellent series begins by focusing on the usage of proxy browsers around the world:
Therefore, to make websites work in Opera Mini’s extreme mode, treat JavaScript as an enhancement, and ensure that your core functionality works without it. Of course, it will probably be clunkier without scripts, but if your website works and your competitors’ don’t work for Opera Mini’s quarter of a billion users, you’ll get the business.
But how!? Well, Bruce has the answer:
The best way to ensure that everyone gets your content is to write real, semantic HTML, to style it with CSS and ensure sensible fallbacks for CSS gradients, to use SVG for icons, and to treat JavaScript as an enhancement, ensuring that core functionality works without scripts. Package up your website with a manifest file and associated icons, add a service worker, and you’ll have a progressive web app in conforming browsers and a normal website everywhere else.
I call this amazing new technique “progressive enhancement.”
You heard it here first, folks!
Paul is digging deep into flexbox and finding it particularly useful for internationalisation …but there are still some gotchas.
Some very handy techniques for working with right-to-left text.
Richard gives the lowdown on the new translate attribute in HTML.
A terrific overview by Richard of the variations in names around the world:
How do people’s names differ around the world, and what are the implications of those differences on the design of forms, ontologies, etc. for the Web?
A fascinating look at the intersection of typography and internationalisation on the BBC’s World Service site.
An excellent explanation from Richard of the bdi element (bi-directional isolate) for handling a mixture of left to right and right to left languages in HTML5.
Some excellent cross-polination between HTML5 and internationalisation — remember the other two Ws that come before Web in WWW.
This. This right here is how you manage sites in multiple languages. Are you listening, Google?
Yahoo have created a Twitter alternative... but they don't state anywhere on this site that it's US-only.
Stuart posts a really handy string for testing internationalisation: Iñtërnâtiônàlizætiøn