Browsing through the Global Voices ‘Most Read in 2012‘ articles, I noticed for the first time the effort that the site makes to accomodate multiple languages.
First, each article has a header saying ‘this post is also available in…’ Then, within the text, any quotes are presented in their original language, followed by a translation. This article on a Citizens’ Basic Income initiative in Switzerland is a good example.
Such efforts always introduce a design problem. The foreign language breaks the ‘flow’ of the text, much like a banner advert in the middle of an an article. On the Global Voices pages, the designers have made some slight attempt to slightly de-emphasise the original text in favour of the English translation. However, the long list of alternative languages at the tope of the article presents a barrier to actually reading the text, even when the type size is small.
Technical advances could help solve this problem. Automated tools like Google Translate allow you to put a rudimentary translation behind a single mouse click (you can read this very blog post in French, Arabic, Chinese or Hindi, for example).
However, it strikes me that some development of HTML standards to accomodate alternative languages would help. It is possible to embed extra data into any piece of text on a website. I ranted a bit last month about how quotes and links should include citation information within their code. The abbreviation tag (<abbr>) typically allows the writer to include more information for the reader, about a particluar acronym. An example of this feature in action: HTML.
It would be great if a ‘translation’ tag or an ‘original language’ tag were made available in HTML. Then, any given piece of text could be directly associated with any alternative language translations. This would allow web designers or app creators to display the translations in the way most appropriate to their content. It would also give readers the flexibility to show or hide the orginal language text.
Translation is a highly cultural and political act. How a piece of text is translated matters, and the nuance and tone imposed on the text by a sympathetic or antagonistic translator can have huge consequences. Technical innovations that allow the original and translated texts to be compared easily would mean more transparency, greater international and inter-cultural understanding, and perhaps even help students to learn foreign languages, and the art of translation. It may also help unify projects like Wikipedia, where there are almost three-hundred encyclopædias evolving in disparate directions.
Does anyone know if there has been any work or research done on this subject?
The mess under the bonnet of the Houses of Parliament website
Excuse me if I go off on a technical rant for a moment. I find it very irritating when people don’t use HTML mark-up properly. I can forgive the occasional user, or those relying on WYSIWYG editors, but for large, professionally coded websites, there is no excuse for mark-up which does not apply standards correctly.
What has vexed me so? The Houses of Parliament website. In many ways this is a great resource. They offer video of parliamentary debates, and the Hansard of the previous day’s proceedings is posted promptly the following moring. However, the underlying mark-up is flawed. Continue reading “The mess under the bonnet of the Houses of Parliament website”