If there is one chasm between developers and the "community" it is how functionality is perceived. A well known graph explains much of the pain. Software once developed, goes live. When it does for software like MediaWiki everybody in the community will be confronted with the new functionality at the same time. Adoption according to the graph is very much absent.
Some software can be implemented without much opposition. Great examples were the implementation of functionality that improves performance or the implementation of Wikidata to replace the old interwiki links. It is rather obvious because the average Community Joe does not really notice either. When they hear that things improved they are mostly happy for a job well done.
When Community Joe hears about new functionality is relevant. Development is discussed in its own environment but for most people new software is news at the time of deployment. For developers production is end of the line; time to move on. In a typical process from moving from design to a working product, things change. It will not work completely as anticipated even when the best user interface experts were involved. People expect magic and they get what humans can make.
When the community is involved in architecture, there is an even bigger chasm. Many community members are well qualified to argue their case. There are many of them and typically they get disappointed.
After the recent upheavals, it is time to move on. I have participated in the "Inspire campaign" with two ideas. I do not expect much but by expressing these ideas in a place where they are likely to be seen they have a better chance.
What is your idea? What does it take for you to be "inspired"?
Thanks,
GerardM
Showing posts with label MediaWiki. Show all posts
Showing posts with label MediaWiki. Show all posts
Saturday, March 05, 2016
Wednesday, December 03, 2014
#Wikimedia and its content delivery
The #vision is "share in the sum of all knowledge" and all our projects contain a wealth of information. The infra structure, the software that brings this information is at this time very much centred on the two ends of delivery. It is in the data centres and it is in the last mile.
The effort of the last mile is the Wikipedia Zero project; This wonderful project brings information at no cost to the mobile phones of people who use the services of cooperating mobile operators. The content they use comes from the WMF datacentres in the USA and, that is suboptimal.
It is suboptimal because it takes time to get that data from the first world data centres of the WMF. It is suboptimal because the pipes are often oversubscribed. The consequence is that the service is not as good as it easily could be.
With a "content delivery network", this information is kept locally and it is only the updates that have to come and go all the way to the central servers in the USA. This is a lot less data for those pipes, it is a lot cheaper to operate for our cooperating mobile operators in Wikipedia Zero and the quality of service will improve a lot.
There are no technical reasons why the WMF cannot do this. All that I see is personal preferences and possibly some legal issues. The WMF has the experience because of its servers in Amsterdam. It should be relatively easy to mimic this at the sites of our cooperating mobile operators. Alternatively we could pay commercial rates and do it ourselves.
A lot of effort is invested in making Wikipedia, MediaWiki perform better. This is another obvious improvement that will make a big difference not only to our Wikipedia Zero users but for everyone who uses our projects outside of the USA and much of Europe.
Thanks,
GerardM
The effort of the last mile is the Wikipedia Zero project; This wonderful project brings information at no cost to the mobile phones of people who use the services of cooperating mobile operators. The content they use comes from the WMF datacentres in the USA and, that is suboptimal.
It is suboptimal because it takes time to get that data from the first world data centres of the WMF. It is suboptimal because the pipes are often oversubscribed. The consequence is that the service is not as good as it easily could be.
With a "content delivery network", this information is kept locally and it is only the updates that have to come and go all the way to the central servers in the USA. This is a lot less data for those pipes, it is a lot cheaper to operate for our cooperating mobile operators in Wikipedia Zero and the quality of service will improve a lot.
There are no technical reasons why the WMF cannot do this. All that I see is personal preferences and possibly some legal issues. The WMF has the experience because of its servers in Amsterdam. It should be relatively easy to mimic this at the sites of our cooperating mobile operators. Alternatively we could pay commercial rates and do it ourselves.
A lot of effort is invested in making Wikipedia, MediaWiki perform better. This is another obvious improvement that will make a big difference not only to our Wikipedia Zero users but for everyone who uses our projects outside of the USA and much of Europe.
Thanks,
GerardM
Sunday, October 12, 2014
#MediaWiki is about sharing the sum of all #knowledge
The organisational structure of the Wikimedia Foundation has been completed with the hiring of Mr Damon Sicore. In his first IRC #Wikimedia-Office chat the ugly head of Wikipedia centrism was found to be alive and well.
Mr Sicore made some important statements: "The most urgent issue seems to be software quality and shipping what we say we are going to ship, on time." and also "this urgency is compounded by the fact that we must be able to compete in mobile".
Wikidata is firmly part of us sharing in the sum of all knowledge and it is increasingly important at that. So far Wikidata was mostly about linking Wikipedia articles about the same subject. Increasingly available data is used in info-boxes. Once the wikidatification of multimedia files happens Wikidata needs to become editable from mobile phones and it needs to be easy and obvious in any and all languages..
Currently it is not easy nor obvious in any language.
This is not to say that it is not possible to make it increasingly easy and obvious in all languages. It is important because it is a requirement when the wikidatification of multi media files is to succeed. This is however only one use case where improved usability of Wikidata is essential for us to continue to share the sum of all the data we have available to us.
Only one challenge for Mr Sicore is the extend Wikidata will make a difference. There are many more he faces. I wish him well because his success is our success.
Thanks,
GerardM
Mr Sicore made some important statements: "The most urgent issue seems to be software quality and shipping what we say we are going to ship, on time." and also "this urgency is compounded by the fact that we must be able to compete in mobile".
Wikidata is firmly part of us sharing in the sum of all knowledge and it is increasingly important at that. So far Wikidata was mostly about linking Wikipedia articles about the same subject. Increasingly available data is used in info-boxes. Once the wikidatification of multimedia files happens Wikidata needs to become editable from mobile phones and it needs to be easy and obvious in any and all languages..
Currently it is not easy nor obvious in any language.
This is not to say that it is not possible to make it increasingly easy and obvious in all languages. It is important because it is a requirement when the wikidatification of multi media files is to succeed. This is however only one use case where improved usability of Wikidata is essential for us to continue to share the sum of all the data we have available to us.
Only one challenge for Mr Sicore is the extend Wikidata will make a difference. There are many more he faces. I wish him well because his success is our success.
Thanks,
GerardM
Sunday, August 17, 2014
#MediaWiki - #MediaViewer rehashed
Some things are plain stupid, sometimes I am and sometimes someone else is. I filed a bug about my experience of the MediaViewer. For me it is a show stopper; it prevents me from using it easily.
The problem is that Chrome shows a really awful URL for an image with funny characters in its title. When I look at it using the MediaViewer it is bad but it looks fine when I look at it from the Commons page.
Several reactions are possible. My choice was to shrug, mutter "it is the user experience stupid" and I got on with my life. Others find it a precursor to the invasion of an evil overlord who does not understand the world and prepare for war.
By filing a bug, by posting this blog I have rid myself of my frustrations. I know several developers; I met many of them at Wikimania and I know they are really dedicated and mean well. I also know that such things pass. I am sure someone will see the light or Google will fix Chrome (if that is where the bug lives). In the end I do not look at images that often as a result.
Thanks,
GerardM
The problem is that Chrome shows a really awful URL for an image with funny characters in its title. When I look at it using the MediaViewer it is bad but it looks fine when I look at it from the Commons page.
- File:%C3%89cole_normale_sup%C3%A9rieure_de_Paris,_26_January_2013.jpg
- File:École normale supérieure de Paris, 26 January 2013.jpg
Several reactions are possible. My choice was to shrug, mutter "it is the user experience stupid" and I got on with my life. Others find it a precursor to the invasion of an evil overlord who does not understand the world and prepare for war.
By filing a bug, by posting this blog I have rid myself of my frustrations. I know several developers; I met many of them at Wikimania and I know they are really dedicated and mean well. I also know that such things pass. I am sure someone will see the light or Google will fix Chrome (if that is where the bug lives). In the end I do not look at images that often as a result.
Thanks,
GerardM
Wednesday, July 23, 2014
#Mediawiki - the #Media viewer
The #Wikimedia Foundation has a problem with people accepting new functionality. The reasons why are often irrational and steeped in conservatism but that is another story. A blog post does not help much at that.
What may help is the assessment of bugs. In bug 68372 it has been identified that in certain browsers a name like MilutinDostanić.jpg will show up properly in the URL when seen from Commons and not from within the Mediaviewer. The Mediaviewer will show it like MilutinDostani%C4%87.jpg.
Technically, technically there is nothing wrong with that. From a user perspective it looks like shit. When a bug is closed because technically there is nothing wrong and a difference in behaviour is not considered as being of enough relevance, a user gets pissed off.
When bugs are reported and when user acceptance is important, differences between expected behaviour and actual behaviour become important because they are often what prevents acceptance of new functionality.
Thanks,
GerardM
What may help is the assessment of bugs. In bug 68372 it has been identified that in certain browsers a name like MilutinDostanić.jpg will show up properly in the URL when seen from Commons and not from within the Mediaviewer. The Mediaviewer will show it like MilutinDostani%C4%87.jpg.
Technically, technically there is nothing wrong with that. From a user perspective it looks like shit. When a bug is closed because technically there is nothing wrong and a difference in behaviour is not considered as being of enough relevance, a user gets pissed off.
When bugs are reported and when user acceptance is important, differences between expected behaviour and actual behaviour become important because they are often what prevents acceptance of new functionality.
Thanks,
GerardM
#Pywikibot - wants you to peek under the hood
For most #Wikimedia projects, Pywikibot has proven itself to be a trusted hard working tool. Literally millions and millions of edits were only possible because of the people operating the bot.
Before Wikidata, the interlanguage links were maintained by what was called "pywikipedia" bot. Now Wikipedia has been harvested for information with this bot to enrich Wikidata.
As time goes by, the architecture of MediaWiki has changed a lot. Consequently Pywikibot had to evolve as well. Its architecture changed as a result; it aims to use the latest API and other MediaWiki functionality.
From July 24th, 2014 and ending on Sunday, July 27th there will be a big online event to learn what more needs to be done for Pywikibot. What bugs need an urgent fix, what features are missing or incomplete. Obviously, it is a also time to look at the code and look for "bit rot".
It would be awesome when more people who care for the Wikimedia projects and know their Python get involved and ensure that Pywikibot will remain the meanest and most powerful bot platform around.
Thanks,
GerardM
Before Wikidata, the interlanguage links were maintained by what was called "pywikipedia" bot. Now Wikipedia has been harvested for information with this bot to enrich Wikidata.
As time goes by, the architecture of MediaWiki has changed a lot. Consequently Pywikibot had to evolve as well. Its architecture changed as a result; it aims to use the latest API and other MediaWiki functionality.
From July 24th, 2014 and ending on Sunday, July 27th there will be a big online event to learn what more needs to be done for Pywikibot. What bugs need an urgent fix, what features are missing or incomplete. Obviously, it is a also time to look at the code and look for "bit rot".
It would be awesome when more people who care for the Wikimedia projects and know their Python get involved and ensure that Pywikibot will remain the meanest and most powerful bot platform around.
Thanks,
GerardM
Wednesday, June 11, 2014
#MediaWiki Talk pages
#Wikidata uses talk pages. The #Wikimedia Foundation is working on a tool called "Flow". As is usual, there are those people who want to keep everything the same. They love their system.
It is fine and dandy. When I added a comment on the Wikidata "Chat" I could not click on the appropriate edit button and get the right section. As it is ,Talk is flaky as well and it is not as easy and obvious as it is made out to be.
Thanks,
GerardM
It is fine and dandy. When I added a comment on the Wikidata "Chat" I could not click on the appropriate edit button and get the right section. As it is ,Talk is flaky as well and it is not as easy and obvious as it is made out to be.
Thanks,
GerardM
Friday, May 30, 2014
The #MediaWiki #GeoData extension is a #dinosaur
"This extension adds a new parser function, {{#coordinates:}}, that saves coordinates to the database. Function's input format is made as compatible as possible with GeoHack".
What it does is save data for one Wikipedia article at a time. It links it to another dinosaur, GeoHack, and hopes for best results..
For as long as such dinosaurs are aliveish and kicking, it may be good. At the same time, it provides an excellent target for harvesting all this geo-data and include it in Wikidata. That will make the same geo-data available to all articles in any Wikipedia on the same subjects.
GeoData saves its data to "the" database, when it decides to evolve and store its data in Wikidata, it may have some future after all.
Thanks,
GerardM
What it does is save data for one Wikipedia article at a time. It links it to another dinosaur, GeoHack, and hopes for best results..
For as long as such dinosaurs are aliveish and kicking, it may be good. At the same time, it provides an excellent target for harvesting all this geo-data and include it in Wikidata. That will make the same geo-data available to all articles in any Wikipedia on the same subjects.
GeoData saves its data to "the" database, when it decides to evolve and store its data in Wikidata, it may have some future after all.
Thanks,
GerardM
Monday, February 17, 2014
The place of #language support in #MediaWiki support
At this moment #Wikipedia has 280+ versions. They represent 280+ different languages. Every language is written in a script. This script may be from right to left (eg Latin), from left to right (eg Arabic). Top down is not yet supported.
All these languages use Unicode to represent the characters in their script. As a consequence it is "just" a matter of configuring a language correctly and it will work in a wiki. The characters used in a script have to be defined in Unicode. Without this supporting a language is problematic. An example of this is the SignWriting script and all the sign languages. They are not supported by the Wikimedia Foundation and they are developing their software themselves.
When people want to have their own Wikipedia, they have to localise the MediaWiki software at translatewiki.net. This is a requirement for the people that request a new project to fulfil. All that is required to support another language is some configuration. To support all languages other than English, MediaWiki developers have to internationalise their software. This is a well established process, there is nothing special in there for "small languages", it is the same process for any language.
When people use MediaWiki it can be assumed that they use any of these 280+ languages. It cannot be assumed that they know any other language than their own. The Universal Language Selector allows people to select the language they need for their user interface. They can choose a language by typing in the name of their language in their own language.
Once a languages is selected, MediaWiki supports both input methods and web fonts. This is necessary because most devices do not support all the languages MediaWiki supports. At this point a user can read and write in MediaWiki. A special case is the OpenDyslexic font; is enables 7% of a population to read their language with less effort. This font works only for many languages that are written in the Latin script like English.
One other aspect of language support is in enabling search in all the 280+ languages. This is where Wikimedia engineers may have to do special things for a single language. When they do this well, they only have to do this once. Typically however, setting up search for a language is well documented, it is part of international standards.
Language support for MediaWiki is nothing but internationalising the software and for being mindful that MediaWiki is used by people representing over 300 cultures and languages. There is no special consideration for small or big languages.
Thanks,
GerardM
All these languages use Unicode to represent the characters in their script. As a consequence it is "just" a matter of configuring a language correctly and it will work in a wiki. The characters used in a script have to be defined in Unicode. Without this supporting a language is problematic. An example of this is the SignWriting script and all the sign languages. They are not supported by the Wikimedia Foundation and they are developing their software themselves.
When people want to have their own Wikipedia, they have to localise the MediaWiki software at translatewiki.net. This is a requirement for the people that request a new project to fulfil. All that is required to support another language is some configuration. To support all languages other than English, MediaWiki developers have to internationalise their software. This is a well established process, there is nothing special in there for "small languages", it is the same process for any language.
When people use MediaWiki it can be assumed that they use any of these 280+ languages. It cannot be assumed that they know any other language than their own. The Universal Language Selector allows people to select the language they need for their user interface. They can choose a language by typing in the name of their language in their own language.
Once a languages is selected, MediaWiki supports both input methods and web fonts. This is necessary because most devices do not support all the languages MediaWiki supports. At this point a user can read and write in MediaWiki. A special case is the OpenDyslexic font; is enables 7% of a population to read their language with less effort. This font works only for many languages that are written in the Latin script like English.
One other aspect of language support is in enabling search in all the 280+ languages. This is where Wikimedia engineers may have to do special things for a single language. When they do this well, they only have to do this once. Typically however, setting up search for a language is well documented, it is part of international standards.
Language support for MediaWiki is nothing but internationalising the software and for being mindful that MediaWiki is used by people representing over 300 cultures and languages. There is no special consideration for small or big languages.
Thanks,
GerardM
Monday, January 13, 2014
#Wikidata - the #discrimination between genders
The occupation of Mr Douglas and Mrs Zeta-Jones is according to Wikidata: "actor / actress". When you look at the picture it is obvious; one is an actor and the other is an actress.
Wikidata knows enough about Mr Douglas and Mrs Zeta-Jones to infer how to label them. One is known as a "male", the other as a "female".
To enable Wikidata to infer labels that are determined by gender, labels need their own statements. The MediaWiki software has the functionality to deal with gender; it is just a matter of applying this logic.
Thanks,
GerardM
Wikidata knows enough about Mr Douglas and Mrs Zeta-Jones to infer how to label them. One is known as a "male", the other as a "female".
To enable Wikidata to infer labels that are determined by gender, labels need their own statements. The MediaWiki software has the functionality to deal with gender; it is just a matter of applying this logic.
Thanks,
GerardM
Sunday, August 04, 2013
The battle of Verdun in #Wikidata
For some people it was news that Wikidata supports dates. The question put to me was: "This Q130847 has geo coordinates but no date". As this refers to the battle of Verdun, I replied by adding the start and end date to the Wikidata item for the battle of Verdun.
One bit of good news is that MediaWiki does support the Islamic calendar, as a consequence the issue of using the calendar got a new dimension. I was also asked if other calendars like the Balinese calendar could be supported. In principle MediaWiki should support any calendar however, I would prefer to start with the support of calendars that MediaWiki supports in Wikidata.
The bug for support for the Islamic calendar in Wikidata was given the I18N label in Bugzilla. I hope that our language team will take an interest in supporting calendars in Wikidata
As it is fairly obvious that the battle of Verdun is a battle, I added "Instance of" "battle". When you look where battle links in Wikidata you will find many more battles that are linked to the concept of battle. I added a few more battles that I just happened to know.
When you look at the info-box for the battle of Verdun, you find many bits of information that we should be able to support in Wikidata. It would be cool when we can.
Thanks,
GerardM
Sunday, May 26, 2013
#WMhack - About #Gerrit, #GIT and #SVN
When there is still so much noise about GIT and GERRIT more than a year after the transition from SVN, you can wonder if the move from SVN was the right one to make.
At the Amsterdam hackathon there was expert help available for everyone who wanted/needed to learn more about using GIT and Gerrit and as I was curious to the answer, I asked the question.
The most important reason to move was because of Git. Using Git many new functionalities became available that made the MediaWiki developers more productive. Gerrit is something of a pain but it is usable and it is improving. So much so that the conversation of dropping Gerrit has subsided.
When you wonder about the question "was it worth it", you also have to consider the TCO or, the total cost of ownership. I came up with the question if the increased productivity had to be offset with the cost of one person supporting Gerrit. I learned that SVN also required a lot of tweaking. The CodeReview extension was written by the Wikimedia staff.
A hackathon isn't a hackathon if it is not for showing off things that are in the works.. GitBlit is as I understand it one tool that is intended to make things easy.. More about GitBlit here.
Thanks,
GerardM
At the Amsterdam hackathon there was expert help available for everyone who wanted/needed to learn more about using GIT and Gerrit and as I was curious to the answer, I asked the question.
The most important reason to move was because of Git. Using Git many new functionalities became available that made the MediaWiki developers more productive. Gerrit is something of a pain but it is usable and it is improving. So much so that the conversation of dropping Gerrit has subsided.
When you wonder about the question "was it worth it", you also have to consider the TCO or, the total cost of ownership. I came up with the question if the increased productivity had to be offset with the cost of one person supporting Gerrit. I learned that SVN also required a lot of tweaking. The CodeReview extension was written by the Wikimedia staff.
A hackathon isn't a hackathon if it is not for showing off things that are in the works.. GitBlit is as I understand it one tool that is intended to make things easy.. More about GitBlit here.
Thanks,
GerardM
Sunday, April 28, 2013
Spouse does not translate
I love #Wikidata, it gets so many things right. At the same time it fails by design. Consider; there is this article about a woman. In English she may have a spouse. In translation there is a problem; because the spouse has a spouse and it is a different word depending on the gender of the person involved.
This is the kind of problem that has been solved for the MediaWiki software. It means that you consider the sex of the person involved. Applying this principle on Wikidata is possible because we do register if a person is male or female.
It seems obvious; sex matters. In many languages you address people based on their sex. As long as Wikidata is not able to address this issue, it is broken. When this is intentional, it is broken by design.
Thanks,
GerardM
This is the kind of problem that has been solved for the MediaWiki software. It means that you consider the sex of the person involved. Applying this principle on Wikidata is possible because we do register if a person is male or female.
It seems obvious; sex matters. In many languages you address people based on their sex. As long as Wikidata is not able to address this issue, it is broken. When this is intentional, it is broken by design.
Thanks,
GerardM
Friday, March 22, 2013
#FUEL makes for standards in localisations
#RedHat and #Wikimedia Foundation engineers have been collaborating on providing support for the languages of India for some time now. However, both Red Hat and the Wikimedia Foundation support people from all over the world. Both organisations know the perils of internationalisation intimately well.
As this cooperation is progressing nicely, one of the early results can be found at translatewiki.net. This is where MediaWiki is localised and this is where software is localised in more languages than anywhere else. What you will find is that the Fuelproject can now be localised in other languages than the languages from India.
This project "aims at solving the Problem of Inconsistency and Lack of standardization in Software Translation across the platform". For this to work optimally, such an approach should not be restricted to India but it should be aimed to any and all languages.
How the terminology defined in FUEL will be used in translatewiki.net is not yet clear. What is obvious is the intention to standardise terminology as much as possible. This will make using software more predictable and that is very much to the benefit of everyone.
Thanks,
GerardM
As this cooperation is progressing nicely, one of the early results can be found at translatewiki.net. This is where MediaWiki is localised and this is where software is localised in more languages than anywhere else. What you will find is that the Fuelproject can now be localised in other languages than the languages from India.
This project "aims at solving the Problem of Inconsistency and Lack of standardization in Software Translation across the platform". For this to work optimally, such an approach should not be restricted to India but it should be aimed to any and all languages.
How the terminology defined in FUEL will be used in translatewiki.net is not yet clear. What is obvious is the intention to standardise terminology as much as possible. This will make using software more predictable and that is very much to the benefit of everyone.
Thanks,
GerardM
#MediaWiki powers #jQuery for language support
#Wikipedia is powered by MediaWiki. Wikipedia has a version in over 280 languages and, more languages are waiting in the wings. All these languages need support. This support is needed in all the computer languages used for Wikipedia; in PHP, Javascript even Lua.
With so many languages to support, you really need a standardised way to provide the support. Support for localisation, for input methods, for fonts.
One of the really brilliant software projects provides language support in jQuery and consequently in Javascript. It is under active development and consequently more and more languages are supported in this way. Currently there are over 155 input methods for over 75 languages - it is already the largest repository of input methods on the Web and, it is open source ...
This development has not gone unnoticed. People who support languages and scripts not supported by the Wikimedia Foundation have a hard time finding support for their languages, for their fonts and input methods. I have seen an implementation for the Thuɔŋjäŋ languages developed by Andrew Cunningham.
Even better, Andrew was happy enough to talk to Martin and this may result in even more collaboration on languages that deserve the same support just like any other language.
Do you want to experience the full power of jQuery.ime like me? We just have to wait for the Wikimedia Foundation to roll it out to its own websites. It is great dogfood, they just have to eat it.
Thanks,
GerardM
With so many languages to support, you really need a standardised way to provide the support. Support for localisation, for input methods, for fonts.
One of the really brilliant software projects provides language support in jQuery and consequently in Javascript. It is under active development and consequently more and more languages are supported in this way. Currently there are over 155 input methods for over 75 languages - it is already the largest repository of input methods on the Web and, it is open source ...
This development has not gone unnoticed. People who support languages and scripts not supported by the Wikimedia Foundation have a hard time finding support for their languages, for their fonts and input methods. I have seen an implementation for the Thuɔŋjäŋ languages developed by Andrew Cunningham.
Even better, Andrew was happy enough to talk to Martin and this may result in even more collaboration on languages that deserve the same support just like any other language.
Do you want to experience the full power of jQuery.ime like me? We just have to wait for the Wikimedia Foundation to roll it out to its own websites. It is great dogfood, they just have to eat it.
Thanks,
GerardM
Monday, March 18, 2013
Help #Wikipedia Zero and localise the #mobile software
Learning about the current state of Wikipedia Zero can be done through this presentation. It is well worth it. The things that I found most interesting are:
- The use of mobile phones is different from what was expected
- The Wikipedia Zero project has a measurable and positive impact
- There are things that can be improved upon, things like localisation
What many people do not realise is that the localisation of the mobile software is not part of the MediaWiki software. Traffic from mobile devices is what grows traffic for Wikipedia a lot. The experience is that when the software has been properly localised, it has a big impact.
In India we have had multiple localisation drives. Every time we ask the same things;
- please do the most used messages first, they are what people see the most
- then do the rest of the MediaWiki messages
- The extensions used by Wikipedia are the next lot that need doing
- Yes, there are all these other MediaWiki messages as well
Localisation has a clear impact on the number of readers and that is what ultimately grows the community.
So what we really, really need are for the mobile messages to be localised as well because this is where the new readers for our projects can be found.
Thanks,
GerardM
Monday, January 14, 2013
Multiple languages, multiple scripts in a #Wikipedia article
Many Wikipedia articles describe something "foreign". For instance Moscow is known in the Russian language as Москва. It is a best practice to mention the native name of a subject and include the pronounciation expressed in IPA as well.
When an article includes text in multiple languages, it is important to be able to identify what text is in what language. Several purposes are served in this way.
When a Wikipedia article is parsed, such tags make it possible to enable relevant technology for that language. This is of particular relevance for the "smaller" languages because a Wikipedia in that language is quite often the biggest corpus. Research of such a corpus is a lot easier when all words that are explicitly in another language are marked as such.
Adding such tags is relatively easy. To a large extend bots can be used to add them. Making use of these tags in how MediaWiki works is something else. Tagging is however the first step that needs to be taken and, there is no reason I know of why this can not be done at this time.
Thanks,
GerardM
When an article includes text in multiple languages, it is important to be able to identify what text is in what language. Several purposes are served in this way.
- provide support for language technology like web fonts and input methods
- enable data mining for the building of spell checkers.
- create frequency lists for words
When a Wikipedia article is parsed, such tags make it possible to enable relevant technology for that language. This is of particular relevance for the "smaller" languages because a Wikipedia in that language is quite often the biggest corpus. Research of such a corpus is a lot easier when all words that are explicitly in another language are marked as such.
Adding such tags is relatively easy. To a large extend bots can be used to add them. Making use of these tags in how MediaWiki works is something else. Tagging is however the first step that needs to be taken and, there is no reason I know of why this can not be done at this time.
Thanks,
GerardM
Friday, August 17, 2012
#jQuery and #Internationalisation of YOUR application
There has been a lot of good news about jQuery this week.
- The Khan academy announced that they are providing training for computer science and they started with jQuery
- A Webmonkey report states that jQuery is installed on half the internet websites
- Hidden in a Wikimedia blogpost is the news of a library to provide a full i18n framework that supports parameter replacements and grammar-, plural-, and gender-dependent translations.
The news of this jquery.i18n library is wonderful news. As it is the same software as used for the internationalisation of MediaWiki, it represents the current knowledge of the 280+ languages that have their Wikipedia.
When your software is open source and when you adopt this library to implement internationalisation, you are that much closer to make use of that wonderful community at translatewiki.net. They are already doing a great job for many applications, why not yours?
Thanks,
GerardM
Tuesday, July 24, 2012
Levels of competence for #Arabic in #Wikipedia III
Tools like #Google #Chrome use an engine to do the rendering for them. For Chrome it is Webkit. It is responsible to connect two items that are in separate HTML elements and make sure that the rules for the Arabic script are addressed.
What started as an observation in MediaWiki became a Chrome bug and is now a Webkit bug.
Webkit is used in multiple browsers.. This makes a fix relevant for Apple's Safari browser as well. The one question left is what will it take to bring a fix in production within those browsers in the near future.
Thanks,
GerardM
What started as an observation in MediaWiki became a Chrome bug and is now a Webkit bug.
Webkit is used in multiple browsers.. This makes a fix relevant for Apple's Safari browser as well. The one question left is what will it take to bring a fix in production within those browsers in the near future.
Thanks,
GerardM
Monday, June 04, 2012
#wmdevdays - #accessibility
At the Berlin #hackathon 2012 many people were hacking on many subjects. Kai Nissen worked on the accessibility of MediaWiki by people with a visual impairment. At the end of the hackathon several bugs were squashed and ready for review in Gerrit.
It is wonderful when reports on defects are actionable and when something gets done.
Thanks,
GerardM
It is wonderful when reports on defects are actionable and when something gets done.
Thanks,
GerardM
How was the Berlin Hackathon 2012 for you
I participated in the Hackathon for the very first time and was quite amazed about so many people coming together and actually work productively on feature enhancements or bug fixes. I had a lot of talks with people who gave really helpful feedback about the project I'm currently working on.
You have been working on accessibility for the blind ... how did you get into this subject
I was pointed to an analysis report concerning accessibility in Wikipedia that was carried out by the Swiss initiative "Access for all". While reading this I realized that a lot of the mentioned issues were
quite easy to solve. A lot of the content available on the web seems to be designed without considering accessibility aspects, although a little tweak can always have a high impact.
How do you know what to focus on
The analysis report was quite thorough and included recommendations, so it ended up to be something like a task list.
You identified a number of issues to work on this weekend .. how did it go
The issues I was working on were quite easy to fix, whenever I had problems with something there was always somebody around to help out.
Did having all these other hackers make a difference ?
The gathering of all those experienced MediaWiki developers is a really helpful thing. That applies to having certain questions answered rightaway as well as just sharing experience in whatever topic might
come up.
Brion Vibber helped you with the parser tests ...
Brion figured out what the problems was in no time. There has been a language version related bug in another patch which he simply reverted.
Are there many more accessibility issues in MediaWiki people can help with
The accessibility analysis report mentions more issues that need to be fixed to make Wikipedia and all other projects based on MediaWiki more accessible. It is clearly written and points out lacks of accessibility very
How do you continually test for good accessibility of our software
Most of the time one seldomly notices lacks of accessibility when not being affected by disabilities. Whatever issue I fixed for improving accessibility I have to keep in mind to apply that again in a similar case.
Are there best practices for coding for accessibility
There are guidelines defined by the WAI, which should be considered when coding for accessibility.
Do you have thoughts on what the Visual Editor will do for accessibility ?
Since screen readers will read what is written on the screen it also reads the wikitext as is. That might be hard to understand, especially for newcomers. Reading out a headline as a headline instead of
"equals-equals-headline- equals-equals" can be very helpful to focus on the subject itself.
I participated in the Hackathon for the very first time and was quite amazed about so many people coming together and actually work productively on feature enhancements or bug fixes. I had a lot of talks with people who gave really helpful feedback about the project I'm currently working on.
You have been working on accessibility for the blind ... how did you get into this subject
I was pointed to an analysis report concerning accessibility in Wikipedia that was carried out by the Swiss initiative "Access for all". While reading this I realized that a lot of the mentioned issues were
quite easy to solve. A lot of the content available on the web seems to be designed without considering accessibility aspects, although a little tweak can always have a high impact.
How do you know what to focus on
The analysis report was quite thorough and included recommendations, so it ended up to be something like a task list.
You identified a number of issues to work on this weekend .. how did it go
The issues I was working on were quite easy to fix, whenever I had problems with something there was always somebody around to help out.
Did having all these other hackers make a difference ?
The gathering of all those experienced MediaWiki developers is a really helpful thing. That applies to having certain questions answered rightaway as well as just sharing experience in whatever topic might
come up.
Brion Vibber helped you with the parser tests ...
Brion figured out what the problems was in no time. There has been a language version related bug in another patch which he simply reverted.
Are there many more accessibility issues in MediaWiki people can help with
The accessibility analysis report mentions more issues that need to be fixed to make Wikipedia and all other projects based on MediaWiki more accessible. It is clearly written and points out lacks of accessibility very
How do you continually test for good accessibility of our software
Most of the time one seldomly notices lacks of accessibility when not being affected by disabilities. Whatever issue I fixed for improving accessibility I have to keep in mind to apply that again in a similar case.
Are there best practices for coding for accessibility
There are guidelines defined by the WAI, which should be considered when coding for accessibility.
Do you have thoughts on what the Visual Editor will do for accessibility ?
Since screen readers will read what is written on the screen it also reads the wikitext as is. That might be hard to understand, especially for newcomers. Reading out a headline as a headline instead of
"equals-equals-headline-
--- Kai

Subscribe to:
Posts (Atom)







.jpg)








