QRpedia – Dealing With Minority Languages
Humans have devised hundreds of thousands of languages with which to express themselves. Some, like Cornish are on the verge of extinction. Others, like Catalan and Welsh, are only used by a small number of speakers. Some, like New Norse, are created for political purposes.
All these languages are valuable and hugely important to their communities. Many have Wikipedia version written in their language.
Unfortunately, very few phones support these languages.

This poses a problem for QRpedia. They way the system works is this:
- Read the phone’s language
- Look for a suitable translation in Wikipedia
- Return the correct article
- If a translation doesn’t exist, return a list of available articles
Suppose The National Library of Wales has a QRpedia code for the Black Book of Carmarthen.
A Welsh speaker will probably wish to go to the Welsh version of the article.
However, their phone does not support the Welsh language (unless it is a Samsung S5600) and is set to English.
QRpedia, therefore, redirects them to the English version and doesn’t give them a chance to read in their native language.
This is a problem we have faced with both Catalan and Norwegian.
Catalan
Catalan faces the very same problem as Welsh does in the previous theoretical example. Many people speak it but, because it’s rare for a phone to support it, their phones are set to Spanish.
This was how we solved the problem:
- If the QRpedia code was for a Catalan page (ca.wikipedia)…
- If the phone’s language is Catalan (CA) take them to the Catalan Wikipedia.
- If the phone’s language is Spanish (ES) take them to a language choice screen – they can then select between Spanish, Catalan, or any other available language.
- If the phone’s language is anything else (say EN) take them to the article in their language.
QRpedia doesn’t store the user’s language choice – so the user has to choose every time the scan which language they want.
The reasons we don’t store the language choice is that it would be very hard to undo if the user made a mistake, or ever wanted to change their language.
Norwegian
The Norwegians have two languages – Bokm%C3%A5l and Nynorsk.
The standard language codes are NB and NN. However, most phones only support NB – with the language header of NB-NO.
To complicate matters, the NB Wikiedia is located at NO.wikipedia!
So, after much discussion with some Norwegians, I discovered that comparatively few people read NN. So, we came up with the following fix.
- If the phone’s language is Bokm%C3%A5l (NB-NO) take them to the NO Wikipedia.
- If the phone’s language is Nynorsk (NN-NO) take them to the NN Wikipedia.
However, very few phones support NN (none have ever used QRpedia) so I’m not sure if this is the correct approach.
Others
There are lots of other languages with Wikipedia supports, but which aren’t well supported on phones. Wikipedia is available in nearly 300 different languages – from Scots and Simple English to Esperanto and Latin. Although, curiously, there’s no separate Wikipedia for British English – or other regional English variants, nor is there one in Klingon
The Future
So, what should QRpedia do in the future? How should it handle all the thousands of languages in conjunction with the hundreds of Wikipedia languages?
That’s where you come in.
If you’ve got a good idea on how we handle your favourite language – drop a comment on this blog.
If you’re a coder, QRpedia is open-source. Check out the code and leave a comment, or raise a bug.
We need your help to determine what we do next.
7 Responses to QRpedia – Dealing With Minority Languages
Leave a Reply Cancel reply
Buy My Time – MinuteBox
Switch site
QR Code
Tags
advertising android api Apple badvertising bbc bit.ly blackberry blog books dabr data drm ebook ebooks google government guardian iphone kindle linux meta microsoft mobile movies nablopomo news nokia oauth php politics qr qr code qr codes qrpedia review security stats twitter ubuntu usability video vodafone wikipedia wp7Recent Comments
- Terence Eden on Twitter API – pagination and IDs
- Riccardo on Twitter API – pagination and IDs
- Steve Harris on The SIM-less Phone Is Coming. And It Should Scare The Shit Out Of You
- Terence Eden on The SIM-less Phone Is Coming. And It Should Scare The Shit Out Of You
- Roger Parkinson (@RogerParkinson) on The SIM-less Phone Is Coming. And It Should Scare The Shit Out Of You
Categories
- /etc/ (175)
- badvertising (39)
- linux (22)
- mobile (187)
- politics (44)
- qr (80)
- qrpedia (26)
- Shakespeare (1)
- usability (39)
- voteuk (9)
- Woody Allen Challenge (5)
Archives
- May 2012 (7)
- April 2012 (15)
- March 2012 (13)
- February 2012 (8)
- January 2012 (14)
- December 2011 (17)
- November 2011 (30)
- October 2011 (7)
- September 2011 (11)
- August 2011 (5)
- July 2011 (6)
- June 2011 (8)
- May 2011 (8)
- April 2011 (12)
- March 2011 (11)
- February 2011 (11)
- January 2011 (13)
- December 2010 (9)
- November 2010 (30)
- October 2010 (7)
- September 2010 (11)
- August 2010 (8)
- July 2010 (15)
- June 2010 (3)
- May 2010 (4)
- April 2010 (13)
- March 2010 (12)
- February 2010 (15)
- January 2010 (6)
- December 2009 (15)
- November 2009 (31)
- October 2009 (22)
- September 2009 (12)
- August 2009 (10)
- July 2009 (10)
- June 2009 (8)
- May 2009 (12)
- April 2009 (6)
- March 2009 (3)
- February 2009 (5)
- January 2009 (1)
- December 2008 (1)
- November 2008 (2)
- October 2008 (3)
- September 2008 (1)
- August 2008 (3)
- July 2008 (1)
- May 2008 (2)
- April 2008 (3)
- March 2008 (1)
- January 2008 (2)
- December 2007 (5)
- November 2007 (4)





Obviously one great solution is to lobby phone operating systems to support these languages. My rather aged Android phone has a long list of languages which includes quite a few minority choices (several types of English). I’ve seen more recent installations where the choice of languages in English ….. only. If people are going to take the time to learn and use Welsh, Catalan or even Cornish then it would seem a small effort by comparison to allow them to load up language support for their choice.
Meanwhile … see Terence’s questions
What about using geo-location?
For example, if the phone is set to use English, and is in Wales, offer a choice of English or Welsh.
Not perfect, for sure, but possibly a work-around.
Oh, and for the history of the Klingon Wikipedia, see here: http://meta.wikimedia.org/wiki/History_of_the_Klingon_Wikipedia
[...] y gwyddom, nid yw ffonau ‘clyfar’ (ha!) yn medru adnabod os mai Cymraeg yw dewis iaith ei berchenog. Eglura John; I’m working with Roger Bamkin, a trustee of Wikipedia UK who has been very [...]
[...] This project has been the brain-child of Àlex Hinojo – the Wikipedian-in-Residence at the Museu Picasso. He first mentioned it to us in May and we’ve worked hard to deal with the challenges of the Catalan language. [...]
[...] blog post is designed to foster a technical and logistical discussion. In much the same way as the earlier QRpedia language discussion [...]
What if Wikipedia first asks which language the user wants to use?
I don’t know if it possible to do the following:
1. If Wikipedia website opens from a QR code from a mobile device
then show a pop up message (or a menu) with a list of languages.
2. Save the language choice via cookies on the mobile phone.
3. Next time when the user loads another article from Wikipedia, the article in the correct language is selected. If there is no article in the language, show a page “No article in your language is found. See below the list of languages for the article.”
I’m at GLAMCamp Amsterdam and have just been told this is also an issue for speakers of Serbian.