The prime objective of MediaWiki is to serve Wikipedia pages. The prime objective of Wikipedia is to share in the sum of all knowledge. In order to achieve this goal, the content has to be readable and get to its audience. Once this is accomplished, any further improvements are the icing on the cake. They are the nice problems to have.
The Webfonts functionality was introduced to prevent "tofu". Tofu is named after tofu, the soya based ingredient, because it is typically served in rectangular blocks. When you are served tofu, you do not get to see the meat of the matter. You cannot read what is on a page. Consequently, Webfonts were introduced to prevent this epic failure.
As mentioned before, when the same technology can be used for cosmetic reasons, it will be used for a secondary goal. When the requirements of such secondary goals prevent the primary goal of serving data, the priorities are dead wrong.
When the use of Webfonts for cosmetic reasons is considered, the bandwidth it uses is a luxury, the performance it asks of servers is a luxury. This does not make Webfonts a luxury, its primary purpose is still to prevent tofu and consequently serve our prime directive. Consequently, it is not a question for any operations staff to consider if Webfonts should run or not. At most it is for them to decide if Webfonts in its current incarnation is good enough to serve fonts to make Wikipedia look pretty.
This issue is not understood by many people who dabble with the Wikimedia infrastructure. This becomes clear when you read some of the responses to the excellent explanation by Niklas. To put it bluntly, the decision if primary functionality can be removed is not an operational but a business decision. Given the consistent failures to protect this primary functionality, it has become an issue for the highest level of the Wikimedia Foundation.
Thanks,
GerardM
Showing posts with label Usability. Show all posts
Showing posts with label Usability. Show all posts
Friday, March 14, 2014
Sunday, December 29, 2013
#Wikidata - how to reach its tipping points
If #Wikidata is to be useful, it has to be usable. What it is usable for, depends on who is using it and in what way. The information about Muhammad Shah, a mogul from India, is easier to digest when formatted by the Reasonator than by looking at the raw information in Wikidata. There is more information in a Wikipedia articles BUT, there are only 16 Wikipedias who have an article about him.
Currently there are labels in 19 languages for Muhammad Shah and consequently most of the Indian languages will not find him in their language.
Most people will not care that much about this mogul. They are more interested in what is in the news. The references shown are related to what is considered to be in the news in any language. Once people added labels missing in their language, items that are likely to be of interest can now be found. At the same time, everywhere where the associated items are referenced, these labels will be available as well.
Doing this helps build enough information for Wikidata to become usable in a language. But it still needs to be used. That is at this time very much a tripping point.
Adding Wikidata Search to a Wikipedia search helps. It gives Wikidata an application. More applications are possible. A separate place where the Wikidata information is leveraged would help. In this way pictures from Commons can be found, information presented by the Reasonator and articles in the available languages.
The beauty of Wikidata is that it takes so little effort to have a big effect. However, this effect is only realised when Wikidata is used. The question is very much what are we going to do to reach the tipping points and bypass the tripping points.
Thanks,
GerardM
Currently there are labels in 19 languages for Muhammad Shah and consequently most of the Indian languages will not find him in their language.
Most people will not care that much about this mogul. They are more interested in what is in the news. The references shown are related to what is considered to be in the news in any language. Once people added labels missing in their language, items that are likely to be of interest can now be found. At the same time, everywhere where the associated items are referenced, these labels will be available as well.
Doing this helps build enough information for Wikidata to become usable in a language. But it still needs to be used. That is at this time very much a tripping point.
Adding Wikidata Search to a Wikipedia search helps. It gives Wikidata an application. More applications are possible. A separate place where the Wikidata information is leveraged would help. In this way pictures from Commons can be found, information presented by the Reasonator and articles in the available languages.
The beauty of Wikidata is that it takes so little effort to have a big effect. However, this effect is only realised when Wikidata is used. The question is very much what are we going to do to reach the tipping points and bypass the tripping points.
Thanks,
GerardM
Monday, December 09, 2013
The best #Sinterklaas #gift ever
One type of gifts at a Sinterklaas party are the #surprises. They may come with a rhyme, with special packaging and some surprises are beyond special, they are personal; they have an impact. The wife of my nephew is an emergency ward physician. Well educated, highly trained, with great bed site manners, all in all a lovely lady.
She explained when the topic turned to writing, why for her writing in the same way as her husband who writes professionally is impossible. The conversation moved in the direction of reading and how hard it is for her. Differentiating between "rr" "m" and "nn" is hard; it takes two three tries to know for sure what word is in front of her.
This sounded like dyslexia and, I asked her to have a look at Wikipedia with the OpenDyslexic font enabled. This was an eye opener for her. Every word showed itself the first time. Reading was not the big effort it usually is.
The OpenDyslexic font is a free font. It is easy to download. You can use it in Windows, Linux or MacOS. It can be used with Chrome and Firefox. You can select it in many Wikipedias.
For me the surprise was in learning how much of a struggle it was for her to learn to read. My respect for her has grown considerably. Learning first hand how much of a difference a different font makes is different from knowing this intellectually.
The configuration of language settings is well hidden on a Wikipedia page. My concern is how dyslexic people will find the functionality that is there to help them.
Thanks,
GerardM
She explained when the topic turned to writing, why for her writing in the same way as her husband who writes professionally is impossible. The conversation moved in the direction of reading and how hard it is for her. Differentiating between "rr" "m" and "nn" is hard; it takes two three tries to know for sure what word is in front of her.
This sounded like dyslexia and, I asked her to have a look at Wikipedia with the OpenDyslexic font enabled. This was an eye opener for her. Every word showed itself the first time. Reading was not the big effort it usually is.
The OpenDyslexic font is a free font. It is easy to download. You can use it in Windows, Linux or MacOS. It can be used with Chrome and Firefox. You can select it in many Wikipedias.
For me the surprise was in learning how much of a struggle it was for her to learn to read. My respect for her has grown considerably. Learning first hand how much of a difference a different font makes is different from knowing this intellectually.
The configuration of language settings is well hidden on a Wikipedia page. My concern is how dyslexic people will find the functionality that is there to help them.
Thanks,
GerardM
Sunday, November 17, 2013
#Wikimedia #HOWTO - Supporting dyslexic people
One small detail that deserves much more attention is the ability to support people who are dyslectic. This support is thanks to a wonderful little project called OpenDyslexic. It is a font that is designed in such a way that most persons with dyslexia find it a lot easier to read.
There are several reasons why our support for dyslectic people deserves more attention;
The CEE conference in Modra was really constructive; so many subjects were discussed including OpenDyslexic. The bug to enable OpenDyslexic for Polish, indicates that many of the things discussed are actionable and are being acted upon.
Thanks,
GerardM
There are several reasons why our support for dyslectic people deserves more attention;
- seven percent of a population is dyslectic
- people who have found how to enable this font are happy
- we do not know how many people use OpenDyslexic
- we are told that people find it hard to enable the font
- OpenDyslexic could be used for languages like Polish
- some languages cannot use OpenDyslexic because characters are not supported
The CEE conference in Modra was really constructive; so many subjects were discussed including OpenDyslexic. The bug to enable OpenDyslexic for Polish, indicates that many of the things discussed are actionable and are being acted upon.
Thanks,
GerardM
Tuesday, October 29, 2013
Using #Babel should be obvious in #Wikidata
When you know multiple languages, you want to see the Wikidata labels used for the languages that are relevant to you.
My current list of languages is defined using the #Babel template on my user page. The syntax is:
Thanks,
GerardM
My current list of languages is defined using the #Babel template on my user page. The syntax is:
{{#babel:nl|en-4|de-3|fr-1|ar-0|id-0|jv-0|ase-0}}It makes a world of a difference when you are able to add useful labels in the languages you know. Added labels ensure that subjects can be found.
Thanks,
GerardM
Friday, August 02, 2013
Use #Wikidata in the #UI of #Wikipedia
Some people do not like the Visual Editor. They think it is not mature enough. It has been explained to them how important it is for the developers to get continuous feedback. The perfect VE will not come fully mature out of the head of Zeus like Pallas Athena did. It is more likely that it will take continuous incremental improvements from being a product with great promise to a great product.
One of the arguments used against the VE is that it will not be possible to include a button or something for all the templates that are in use on a Wikipedia.
This is true at this time. However, it is possible to narrow this number down substantially. This is done by looking at the context of an article. To the right you find the current genealogical map of the Ottoman dynasty. For all these people many things are known in Wikidata and for many of these people one or more templates are already in use.When we know that a specific article is about a certain type of topic, we can exclude most templates because they are not relevant. Conversely when we know that a specific template is in use on a Wikipedia, we can suggest the use of this template in another Wikipedia.
My point is not so much that this can be done but more that with the Visual Editor new opportunities become available. Such opportunities are not what people are used to but they deserve consideration. They will enable more people to improve their Wikipedia particularly in all the "other" languages.
Thanks,
GerardM
Tuesday, July 02, 2013
#OpenDyslexic provides support on the English #Wikipedia
Today the "Universal Language Selector" premièred on the English Wikipedia. There is a ton of functionality in there and it has a lot of potential. The one thing that may prove to be a game changer for people with dyslexia is the inclusion of the OpenDyslexic font.
Once people with dyslexia start to adopt this font, chances are that they can actually read/use Wikipedia. A lot of people are dyslexic; to quote the en.wp article on the subject: "It is believed the prevalence of dyslexia is around 5-10 percent of a given population although there have been no studies to indicate an accurate percentage".
The one thing left to do; let people know that Wikipedia has improved usability for people with dyslexia. Please tell it to the teachers, the parents and most importantly to all the people you know who are dyslexic.
Thanks,
GerardM
NB it is also available for many other languages on many other Wikis.
Tuesday, June 04, 2013
#OmegaWiki supports #OpenDyslexic
#OmegaWiki aims to be useful as a platform. Much of its functionality is in the extension that allows us to be special. The core functionality however is provided by MediaWiki. The Universal Language Selector is an extension of MediaWiki waiting in the wings to become available on all the wikis of the Wikimedia Foundation.
Part of the ULS is the use of webfonts and, OpenDyslexic is a font available for many languages that use the Latin script. Languages like English, French, German, Dutch... The font looks odd to most people but for many people who are dyslexic it makes text actually .. readable.
Thanks,
GerardM
Part of the ULS is the use of webfonts and, OpenDyslexic is a font available for many languages that use the Latin script. Languages like English, French, German, Dutch... The font looks odd to most people but for many people who are dyslexic it makes text actually .. readable.
Thanks,
GerardM
Saturday, January 05, 2013
#MediaWiki for dyslexic people
#Wikipedia states: "It is believed that #dyslexia can affect between 5 and 10 percent of a given population". There are some 315,113,038 USAmericans and therefore there are something like 23,633,478 people in the USA who have a problem with Wikipedia; they find Wikipedia hard if not impossible to read.
The Website of Dyslexia USA has on its information pages a very simple drop down box. It offers 8 different background colours. Each background colour helps a different group of people with dyslexia.
It is a cheap and easy way of growing the numbers of readers of Wikipedia in the USA. Add to this the Open-Dyslexic font we are waiting for and we help them to the resource that has been there for all the rest of us.
PS It will work for people in other countries or who speak other languages too.
Thanks,
GerardM
The Website of Dyslexia USA has on its information pages a very simple drop down box. It offers 8 different background colours. Each background colour helps a different group of people with dyslexia.
It is a cheap and easy way of growing the numbers of readers of Wikipedia in the USA. Add to this the Open-Dyslexic font we are waiting for and we help them to the resource that has been there for all the rest of us.
PS It will work for people in other countries or who speak other languages too.
Thanks,
GerardM
Wednesday, November 14, 2012
A #font for people with #dyslexia III
Yesterday I met a teacher. I also met someone who was a counselor in Mali. She was really enthusiastic about the news that there is a freely licensed font that works especially well for people who suffer from dyslexia.
Today I received a mail where I was told that the availability of the Open-Dyslexic font will be the basis of a possible project in Mali.
Thanks,
GerardM
Today I received a mail where I was told that the availability of the Open-Dyslexic font will be the basis of a possible project in Mali.
Thanks,
GerardM
A #font for people with #dyslexia II
The good news is: the Open-Dyslexic font will be part of the initial roll out of the "universal language selector". The font is already available for some 25 languages on Wikidata and translatewiki.net where the "universal language selector" is already deployed. These languages are listed below.
- en - English,
- af - Afrikaans
- ca - Catalan
- cy - Welsh
- da - Danish
- de - German
- es - Spanish
- et - Estonian
- fi - Finnish
- fo - Faerours
- fr - French
- ga - Irish
- gd - Scottish Gaelic
- hu - Hungarian
- is - Icelandic
- it - Italian
- lb - Luxembourgisch
- mi - Maori
- ms - Malay
- oc - Occitan
- pt - Portuguese
- sq - Albanian
- sv - Swedish
- sw - Swahili
- tr - Turkish
- wa - Walonian
When you consider that languages with special characters like Icelandic and French are in this list it is obvious that many more languages are already supported by this font. When you consider that the WMF has good relations with the creator of the font it is more than likely that missing characters for your language can be added to the font.
So check out first if all the characters used in your language are supported by the Open-Dyslexic font. If it is, ask for it to be enabled either by making the request on the support page of translatewiki.net or by requesting them on bugzilla. You can also send a mail with this happy news to all the teachers you know. When it is not, identify the missing characters and, ask nicely for them to be added.
Open Source is such a wonderful enabler. Consider; not only is this font available to all the teachers and the sufferers of dyslexia, it is also available for use on websites like Wikipedia. Given that our aim is to share in the sum of all knowledge this is an important step in the right direction.
Open Source is such a wonderful enabler. Consider; not only is this font available to all the teachers and the sufferers of dyslexia, it is also available for use on websites like Wikipedia. Given that our aim is to share in the sum of all knowledge this is an important step in the right direction.
Thanks,
GerardM
A #font for people with #dyslexia
Today I was able to make some difference. I met a teacher who is specialised in children with "special needs". The conversation got onto the subject of language technology and I mentioned the existence of the Open-Dyslexic font.
She was so happy to learn about the existence of this font. She asked me to send details today so that she can install the font on her pc tomorrow. This week she is going to meet some thirty persons who will be happy to learn about the existence of this freely licensed font as well. A lot of children are going to benefit.
I cannot wait for the Wikimedia Foundation to make the Open-Dyslexic font available for use on its wikis. It will affect so many more people. It is likely to be mentioned in the international press; it is that relevant.
Thanks,
GerardM
She was so happy to learn about the existence of this font. She asked me to send details today so that she can install the font on her pc tomorrow. This week she is going to meet some thirty persons who will be happy to learn about the existence of this freely licensed font as well. A lot of children are going to benefit.
I cannot wait for the Wikimedia Foundation to make the Open-Dyslexic font available for use on its wikis. It will affect so many more people. It is likely to be mentioned in the international press; it is that relevant.
Thanks,
GerardM
Sunday, September 30, 2012
Open #Wikipedia for people who are #Dyslexic II
Great ideas are not uncommon. I am really happy to learn that Reedy had the idea to support the Open-Dyslexic font in MediaWiki before me. As you can see in the screen shot, progress has been made.
It is now just a question of dotting the i and crossing the t and pushing it out.
Thanks,
GerardM
Saturday, September 29, 2012
Open #Wikipedia for people who are #Dyslexic
We have the technology to make an important improvement for the usability of Wikipedia. The technology exists in the ability to provide web fonts from within MediaWiki. The opportunity is to improve the readability for people who are dyslexic.
What it takes is to enable web fonts functionality on for instance the English Wikipedia and allow the use of the Open-Dyslexic font. The license is a bit weird for a font but it is within what the WMF is comfortable with; the CC-by license.
It should not take long to appreciate why this is a good idea.. it should not take too much after that to help people with dyslexia.
Thanks,
GerardM
Saturday, July 14, 2012
Can everybody read #Wikipedia?
A lot of effort goes into making "Wikipedia the encyclopaedia everybody can edit". The result is wonderful; there are Wikipedias in over 280 languages, a big effort is under way to make editing even easier and as so many people do edit, it became a rich almost authoritative resource. When Wikipedia goes off-line, students despair.
People do read Wikipedia, it is very popular but the notion that Wikipedia is hard to read is not really considered. Take for instance today's featured article.There are too many words on a line. For many people this makes it hard to read, some give up on an article or on Wikipedia.
Yes, you can change the way content is displayed on a computer screen. The problem is that people who have problems read websites in the default format.
The Wikimedia Foundation does have the expertise to consider these issues. The people who do have already too much on their plate to support the current software development. However, the proof of the pudding that is Wikipedia is in people READING its content and that makes this a key concern.
Thanks,
GerardM
People do read Wikipedia, it is very popular but the notion that Wikipedia is hard to read is not really considered. Take for instance today's featured article.There are too many words on a line. For many people this makes it hard to read, some give up on an article or on Wikipedia.
Yes, you can change the way content is displayed on a computer screen. The problem is that people who have problems read websites in the default format.
The Wikimedia Foundation does have the expertise to consider these issues. The people who do have already too much on their plate to support the current software development. However, the proof of the pudding that is Wikipedia is in people READING its content and that makes this a key concern.
Thanks,
GerardM
Friday, June 29, 2012
The Hebrew #Wikipedia is bigger than all of #Wikisource
When you compare the statistics for Wikipedia and Wikisource, the Wikipedia in Hebrew gets more eyeballs than all Wikisources combined. When you consider the potential public for both projects, the public for Wikisource is bigger by orders of magnitude.
On the main page of the English Wikisource it says: "We now have 783,122 texts in the English language library". It is less clear how many of these texts are in a final form; meaning ready for casual readers. The pages linked to the proof read tool indicate 691 completed pages and 3588 pages ready for proofreading. This does not imply that there are 691 text that are ready.
For a reader, the sources at Wikisource are works in progress. A text featured on the Wikisource main page, like the Celtic Fairy tales, is very much a Wiki page. The presentation of the text and illustrations is very much accidental. It is a bit sad is, but the pages where easier to read when they still needed to be proofread.
As you can see, the long lines below are not easy to read and the font used in the original book made the text more legible.
The Hebrew Wikipedia is easy to read. We can and should do better for Wikisource.
Thanks,
GerardM
On the main page of the English Wikisource it says: "We now have 783,122 texts in the English language library". It is less clear how many of these texts are in a final form; meaning ready for casual readers. The pages linked to the proof read tool indicate 691 completed pages and 3588 pages ready for proofreading. This does not imply that there are 691 text that are ready.
For a reader, the sources at Wikisource are works in progress. A text featured on the Wikisource main page, like the Celtic Fairy tales, is very much a Wiki page. The presentation of the text and illustrations is very much accidental. It is a bit sad is, but the pages where easier to read when they still needed to be proofread.
As you can see, the long lines below are not easy to read and the font used in the original book made the text more legible.
The Hebrew Wikipedia is easy to read. We can and should do better for Wikisource.
Thanks,
GerardM
Friday, June 01, 2012
#WMDEVDAYS - Using #Commons
Commons works best when you use known pictures. As it says on Commons, it is "a database of 12,959,488 freely usable media files to which anyone can contribute". Anyone can and, it is becoming ever easier to contribute even more media files. The problem is not so much contributing files, it is finding them and using them. Many people I know prefer to find pictures elsewhere. I tried to find pictures of a bunch of keys on Commons for a recent blog post but after too many pictures of Alicia Keys, I gave up.
At the Berlin Hackathon 2012, it is the kind of thing that merits some shared consideration. The existing categories on Commons just do not help. When looking for keys, you want to choose from all keys and not navigate a structure. It makes more sense to have tags and possibly disambiguate those tags. Combine them with other tags and you have a result that will be more satisfying.
The value of a collection is in its use.
Thanks,
GerardM
Sunday, November 20, 2011
Typing made easier for six languages
The #MediaWiki Narayam extension provides keyboard mapping. This means that when you have an International keyboard the keystrokes will be mapped to what it would be on a keyboard with another layout. This is a great help when you can type blind.
The Mumbai Hackathon has provided us with new keyboard methods for Urdu, Panjabi, Gujarati, Bodo, German and Marathi. All these keyboard methods are available now for testing in translatewiki.net.
These keyboard methods are a step towards making it as easy to use MediaWiki in these languages as it is to use MediaWiki in English. This challenge is one for the Localisation team. The challenge to enhance the usability for English is outside its remit; this is what all the other developers are working on but keeping up with their good work will keep the team occupied.
Thanks,
GerardM
The Mumbai Hackathon has provided us with new keyboard methods for Urdu, Panjabi, Gujarati, Bodo, German and Marathi. All these keyboard methods are available now for testing in translatewiki.net.
![]() |
| Photo Victor Vigras |
Thanks,
GerardM
Monday, November 07, 2011
Improved #usability means more work gets done at #translatewiki.net
One item on the "to do" list of Niklas was making it easier to become a translator at translatewiki.net. We have had a procedure to follow for a long time. It is intended to ensure that people know at least some English. Knowing English is important because all the software we localise at twn start off in English.
The procedure is now more rational, easier to understand and, a newbie still needs to understand some English. The usability improvements do serve its purpose; more people are admitted as a localiser for their language. These new people are certainly as enthusiastic as people new to translatewiki have always been. As more people are becoming active all the projects that we support benefit.
As always, there is more work that needs doing. Please consider spending some of your time localising freely licensed software at translatewiki.net.
Thanks,
GerardM
The procedure is now more rational, easier to understand and, a newbie still needs to understand some English. The usability improvements do serve its purpose; more people are admitted as a localiser for their language. These new people are certainly as enthusiastic as people new to translatewiki have always been. As more people are becoming active all the projects that we support benefit.
As always, there is more work that needs doing. Please consider spending some of your time localising freely licensed software at translatewiki.net.
Thanks,
GerardM
Sunday, October 23, 2011
#Commons, how about adding some #usability
Working for the #Wikimedia Foundation, I am expected to use Commons for the pictures I use when I blog. To be honest, when I have a new picture I do not mind to upload it and use it. When I am looking for a picture of a "horse" for instance, Google provides me with a useable interface. It gives me pictures, I can select one and get more info, I can click on it to get even more info and do what is needed to get a picture in a usable format.
PS recognise the first picture ?
Now compare this with the interface I get at Commons..
What I am doing is looking for a picture of a horse. All the intellectual activity that produced this text is wasting my time. I want pictures. Pictures of a horse. When I scroll down, I get some pictures..
I am still plagued with too much text, too much white space and pictures that are too small. To make it worse, many of the pictures with horses on them will not be presented because they are hiding in categories.
I am looking for a picture of a horse. I need to be presented with all the pictures I can choose from. I do not want white space, text, categories or anything. My need is to efficiently find the picture that fits my current need.
At this moment Commons is a database with 11,420,809 freely usable media files to which anyone can contribute. Yes, it is wonderful that anyone can contribute but please, we are now at a state where there is so much that it is certainly as relevant to have 11,420,809 freely usable media files which everyone can use.
Thanks,
GerardM
PS recognise the first picture ?
Now compare this with the interface I get at Commons..
What I am doing is looking for a picture of a horse. All the intellectual activity that produced this text is wasting my time. I want pictures. Pictures of a horse. When I scroll down, I get some pictures..
I am still plagued with too much text, too much white space and pictures that are too small. To make it worse, many of the pictures with horses on them will not be presented because they are hiding in categories.
I am looking for a picture of a horse. I need to be presented with all the pictures I can choose from. I do not want white space, text, categories or anything. My need is to efficiently find the picture that fits my current need.
At this moment Commons is a database with 11,420,809 freely usable media files to which anyone can contribute. Yes, it is wonderful that anyone can contribute but please, we are now at a state where there is so much that it is certainly as relevant to have 11,420,809 freely usable media files which everyone can use.
Thanks,
GerardM
Subscribe to:
Posts (Atom)



























