When politics has its way, this year will be the last year when Muslims are allowed to celebrate Eid al-Adha in the traditional way. Traditionally a sheep is butchered, its meat is shared with the poor. According to a one issue political party, the "party of the animals" butchering animals in the halal way should not be allowed.
The law that effectively prevents the eating of meat by both Muslims and Jews still needs to go through the Dutch senate. My fear is that this law that may be well intentioned, will effectively have quite nasty results. At present animals are slaughtered in slaughter houses. With this law in place I am convinced that many animals will be butchered wherever because people will celebrate their festivals and they want to celebrate it in the traditional way.
Thanks,
GerardM
PS Ied mubarak
Sunday, November 06, 2011
Old #Hebrew shown as it should
In Hebrew, signs may be added to a text that indicate how a text is to be chanted. Such signs are not well supported in most operating systems. Amir has added a default font created by the Culmus Project for texts in old Hebrew (language code hbo).
Testing the waters in this way, a next addition for old Hebrew may be a font that will do justice to manuscripts like the Dead Sea scrolls. It means that our digital text will resemble closely what the manuscript looks like. Having all the characters show properly and in the old style will add respect to the original text.
Once a transcribed text shows visibly the same, it will give added validity to the use of our digital text for comparative research. A project transcribing the Dead Sea scrolls is the kind of project that will make Wikisource shine.
Thanks,
GerardM
#WCN11 - Uploading files to #Wikimedia #Commons
A hard nut is being cracked; selecting multiple files that are to be uploaded to Commons. There is a call out for testing this new functionality
Not only multiple file upload but other things have changed in the upload process. Read what needs testing, give it a go and see how you like it..
Please do create a profile but also change the language of the user interface to your language..
Thanks,
GerardM
#WCN11 - Attribution is what a #GLAM needs, what #Wikipedia can provide
In Wikipedia we add a
reference to the facts mentioned in an article. This is best practice
in many Wikipedias. The argument for adding references is as
applicable for pictures. Our pictures are freely licensed and
consequently they are open to abuse by people who “improve” on
the original. It is allowed. Many pictures improve as an illustration
and this becomes clear only when you compare it with the original.
The original is not on
Commons. Many original pictures are kept in museums and archives.
Wikipedia will improve not only its references but also its relations
with GLAMs when access to the original picture is made easy. To
realise this we need to remove all the unnecessary layers between the picture as
it is used on a Wiki and the GLAM.
Using images from
Commons is something we know how to do well. What we need to do is
add enough of the meta-data to provide more information and a link to
the original at the GLAM website.
It will make us friends
and it will help us clean up our act; we can include the license
information. This will get us closer to what the intention of
the creative commons license is.
Thanks,
GerardM
#WCN11 - #MediaWiki gadgets
At the #Wikimedia Conference 2011, one of the best bits of news was in the presentation of Roan and Timo. They have been working on the rejuvenation of our JavaScript support, this brought us a lot of improvements in the past and now they have their sites firmly on the MediaWiki gadgets.
In summary, the syntax to support gadgets is worse then wikisyntax on steroids, the same gadget may exist in a gazillion manifestations on any of the 800 Wikis, internationalisation is a joke, gadgets as they are are awful. Awful because its infrastructure sucks not because of a lack of hard work by a community of people fulfilling a need.
Consequenrly the syntax has to be cleaned up, gadgets are to be shared among the many wikis, it should be able to use all the JavaScript improvements and as gadgets are to be shared, internationalisation is necessary in order for it to work well on all those Wikis.
The best news; Roan and Timo are already testing gadgets with many of the improvements in place. The gadgets are able to use MediaWiki messages and Siebrand and Roan are talking about implementing gender and plural support for JavaScript.
Thanks,
GerardM
In summary, the syntax to support gadgets is worse then wikisyntax on steroids, the same gadget may exist in a gazillion manifestations on any of the 800 Wikis, internationalisation is a joke, gadgets as they are are awful. Awful because its infrastructure sucks not because of a lack of hard work by a community of people fulfilling a need.
Consequenrly the syntax has to be cleaned up, gadgets are to be shared among the many wikis, it should be able to use all the JavaScript improvements and as gadgets are to be shared, internationalisation is necessary in order for it to work well on all those Wikis.
The best news; Roan and Timo are already testing gadgets with many of the improvements in place. The gadgets are able to use MediaWiki messages and Siebrand and Roan are talking about implementing gender and plural support for JavaScript.
Thanks,
GerardM
#WCN11 #Tropenmuseum knows the stories of expeditions
As colonial powers
extended their reach, they send expeditions to those parts of the
world where they might find an “el dorado”. Many of these
expeditions had a dual purpose and expanding the knowledge of the
world was one. When you were lucky, you lived to tell the tale. You
arrived home heavy with notes, artefacts both human, animal, plant
and inanimate. These artefacts were analysed and when done, they
ended up in depots of museums. Museums like the Tropenmuseum.
The Dutch
anthropological museums all got “their” part of these expeditions
and now is the time when thanks to digitisation all the notes and
artefacts can come together. Just bringing them together is already a
lot of fun but it is only by telling the story to the public that it
gains in relevance.
The Tropenmuseum is
really happy with many of the results of their donations of
Indonesian materials; it is the Indonesian Wikipedia where their
material is used most. A project about expeditions may become as
relevant as they are when the first systematic references occur in a
written language.
Digitising the
documents, the photos and combining them in Wikipedia articles is
worthwhile in itself however this is not telling the stories of the
expeditions and the stories of the collections. Telling the stories
is what will make all the material come alive.
The pictures go into
Commons, the subjects in Wikipedia, the sources in Wikisource. Can we
have a Wikistories to tell the story and have a framework for all the
content of the expeditions ?
Thanks,
GerardM
Thursday, November 03, 2011
Learning the gender of Dutch words
It is hard to learn the gender of all the nouns of the Dutch language. There are so many nouns. There are three genders; masculine, feminine and neutral but practically masculine and feminine are mostly the same.
People who are not originally Dutch can be recognised because they always get "de and het" wrong. A really simple program could make reading a Wikipedia article a training exercise. All it has to do is to remove the words "de" and "het" and make it a toggle for the reader.
The objective; having more readers for the Dutch Wikipedia AND giving them an additional reason to do so. Many people are learning to write Dutch and they are often subject matter experts in areas where this Wikipedia is weak.
Thanks,
GerardM
People who are not originally Dutch can be recognised because they always get "de and het" wrong. A really simple program could make reading a Wikipedia article a training exercise. All it has to do is to remove the words "de" and "het" and make it a toggle for the reader.
The objective; having more readers for the Dutch Wikipedia AND giving them an additional reason to do so. Many people are learning to write Dutch and they are often subject matter experts in areas where this Wikipedia is weak.
Thanks,
GerardM
Tuesday, November 01, 2011
#Chrome #security is a bit too much
The logo for the Hindi #Wikipedia is used as an illustration on a previous post. Illustrations like this can be saved from the "page view info" that is available by right clicking a web page.
Chrome apparently does not like the Hindi Wikipedia; it does not only prevent me from accessing the page view info, the information is incorrect as well.
I did use Chrome before today. I am quite happy for Chrome to provide me with a security warning; I hate it when it prevents me to do my job.
Particularly nasty is the warning:
Thanks,
GerardM
Chrome apparently does not like the Hindi Wikipedia; it does not only prevent me from accessing the page view info, the information is incorrect as well.
I did use Chrome before today. I am quite happy for Chrome to provide me with a security warning; I hate it when it prevents me to do my job.
Particularly nasty is the warning:
The site uses SSL, but Google Chrome has detected either high-risk insecure content on the page or problems with the site’s certificate. Don’t enter sensitive information on this page. Invalid certificate or other serious https issues could indicate that someone is attempting to tamper with your connection to the site.Such warnings should be taken seriously and reported but I am quite happy to use Firefox in stead.
Thanks,
GerardM
A #Wikipedia article in #Hindi about the Hindi language
To illustrate how WebFonts will work for Hindi Wiki projects, I looked for an article on the Hindi Wikipedia about the Hindi language. Apparently there is no such article; at least there is no interwiki link to the Hindi Wikipedia.
It really amazed me.
As the objective is to have a sizeable article, I copied the article in Hindi about India to the test page on the Hindi portal at translatewiki.net. A similar exercise is needed for all the official languages of India.
We are very much interested in learning how using WebFonts is received by the communities of the associated Wiki projects. Having a sizeable article allows people to test reading and editing in their language with the latest version of the WebFonts software.
Thanks,
GerardM
It really amazed me.
As the objective is to have a sizeable article, I copied the article in Hindi about India to the test page on the Hindi portal at translatewiki.net. A similar exercise is needed for all the official languages of India.
We are very much interested in learning how using WebFonts is received by the communities of the associated Wiki projects. Having a sizeable article allows people to test reading and editing in their language with the latest version of the WebFonts software.
Thanks,
GerardM
Sunday, October 30, 2011
We know David Shankbone
#Commons is where photographers like David post many original pictures. David is based in New York where the "occupy Wallstreet" movement has its origin.
Good had a nice thing to say about David. This was mentioned on the mailing lists and many people pointed to other places where some good news is really welcome.
It is good news. I do know David and I am happy to be just another place where you can learn how photographers like David make a difference.
Thanks,
GerardM
Good had a nice thing to say about David. This was mentioned on the mailing lists and many people pointed to other places where some good news is really welcome.
It is good news. I do know David and I am happy to be just another place where you can learn how photographers like David make a difference.
Thanks,
GerardM
A new #Wikipedia for #Africa
A new Wikipedia in the Northern Sotho language has been created. Northern Sotho is spoken in South Africa and, the South African chapter has shown its interest in the creation of this new project.
The project has just been created, the content is still to be transferred from the Incubator. A mail has been send to have the traffic for this new project included in the statistics. Everything is new and we wish this project well.
With the current focus on the Northern Sotho language, it will be cool when people volunteer to be its language support team. Many open source projects including MediaWiki will be able to support this language properly when we know for sure that the CLDR information for Northern Sotho is correct and complete.
Given the interest of the South-African chapter, it will be so cool when they are motivated to ensure that the languages of South Africa are all well documented in the standards.
Thanks,
GerardM
The project has just been created, the content is still to be transferred from the Incubator. A mail has been send to have the traffic for this new project included in the statistics. Everything is new and we wish this project well.
With the current focus on the Northern Sotho language, it will be cool when people volunteer to be its language support team. Many open source projects including MediaWiki will be able to support this language properly when we know for sure that the CLDR information for Northern Sotho is correct and complete.
Given the interest of the South-African chapter, it will be so cool when they are motivated to ensure that the languages of South Africa are all well documented in the standards.
Thanks,
GerardM
Saturday, October 29, 2011
A #Font as a luxury
#Halloween will be celebrated soon; even in my part of the world there are pumpkins, grizzly costumes and other Halloween paraphernalia to be had.
Being spoiled for choice to celebrate Halloween on the Internet is good fun. I can imagine that Wikipedia main pages will join in such fun once the WebFonts extension is live on all the WMF projects.
Thanks,
GerardM
Thursday, October 27, 2011
#HTML5 and language support
The technology behind the Internet #matures; and consequently HTML 5 is becoming ever more established. HTML 5 is an open standard and the W3C is the organisation where HTML 5 is defined..
Amir went to a conference, HTML5FEST in Ramat-Gan, he met people from Google, Mozilla, the W3C. Going to a conference is where you can learn about how language support can be achieved in the future.
For Amir it is clear that improvements to the HTML 5 specifications can do with some tweaking. Going to a conference, learning how things are done and how to get suggestions in can be more effective then writing code for a month, maybe more.
Thanks,
GerardM
Amir went to a conference, HTML5FEST in Ramat-Gan, he met people from Google, Mozilla, the W3C. Going to a conference is where you can learn about how language support can be achieved in the future.
For Amir it is clear that improvements to the HTML 5 specifications can do with some tweaking. Going to a conference, learning how things are done and how to get suggestions in can be more effective then writing code for a month, maybe more.
Thanks,
GerardM
Wednesday, October 26, 2011
Just another day
As I will be going to India, I have to have a visa. It can be a one day affair,
Thanks,
GerardM
- I forgot my mobile
- It was a public holiday in India.. I have to come back another time
- I decided to visit a friend in hospital, yesterday he was released
- Leaving a good conversation made me come late for my training
Thanks,
GerardM
The original script of the #Philippines was not #Latin
At #translatewiki.net we have portal pages for the languages our community indicates they know. For some languages all we have is Babel information, others are used to provide a starting off place for every localisation and translation we do at translatewiki.
When people are new to us, we welcome them and particularly when their language is not yet supported by the Babel extension, we ask people to localise it as a matter of urgency. At the same time attention is given to that particular portal.
The Ilokano language is one of the bigger languages on the Philippines and when you check its Wikipedia, you will find a reference to the Babayin script. This script known as Tagalog or Tglg by the ISO-15924, was used in the past not only by Ilokana but also by Tagalog. .. obviously.
The problem with this script is that it is not yet fully ratified by Unicode and consequently it is not possible to use it at all in MediaWiki. MediaWiki insists on their being a Unicode compliant font. As the technical aspects of the Unicode specification have not been ratified, creating a font is a speculative affair. Theoretically at least. Some of the gurus at Unicode can develop a font based on the existing specification and amend and append the font when need be when the script definition has some unforeseen changes.
Many of the hundreds of languages supported at translatewiki.net can do with a lot more tender loving care. When a script was used for a language, it makes sense to have the orginal transliterations in that script. This proves the authenticity of the transcription effort. A follow up transcription to the modern script makes it readable. However, transcription gets you the original orthography and that is a good thing too.
Thanks,
GerardM
When people are new to us, we welcome them and particularly when their language is not yet supported by the Babel extension, we ask people to localise it as a matter of urgency. At the same time attention is given to that particular portal.
The Ilokano language is one of the bigger languages on the Philippines and when you check its Wikipedia, you will find a reference to the Babayin script. This script known as Tagalog or Tglg by the ISO-15924, was used in the past not only by Ilokana but also by Tagalog. .. obviously.
The problem with this script is that it is not yet fully ratified by Unicode and consequently it is not possible to use it at all in MediaWiki. MediaWiki insists on their being a Unicode compliant font. As the technical aspects of the Unicode specification have not been ratified, creating a font is a speculative affair. Theoretically at least. Some of the gurus at Unicode can develop a font based on the existing specification and amend and append the font when need be when the script definition has some unforeseen changes.
Many of the hundreds of languages supported at translatewiki.net can do with a lot more tender loving care. When a script was used for a language, it makes sense to have the orginal transliterations in that script. This proves the authenticity of the transcription effort. A follow up transcription to the modern script makes it readable. However, transcription gets you the original orthography and that is a good thing too.
Thanks,
GerardM
Monday, October 24, 2011
#Language options looking for an iteration II
When you expect a user to understand a language, you can be wrong. Everyone has no experience for most of the languages we have Wikipedias in.
Niklas experimented using data from the browser to suggest an appropriate interface. Obviously more needs to be done but as it is such an obvious improvement to our usability. The experiment was happily received with not too many words :)
Thanks,
GerardM
Niklas experimented using data from the browser to suggest an appropriate interface. Obviously more needs to be done but as it is such an obvious improvement to our usability. The experiment was happily received with not too many words :)
Thanks,
GerardM
Sunday, October 23, 2011
#Language options looking for an iteration
At #translatewiki.net we live at the #MediaWiki edge.. Living at the edge brings you surprises. It brings us for instance a language drop down thingie with weird options. Dutch, British English, English and American English.
Typically my user interface is set to English so I changed it to Dutch to see if it would pick up the fact that there is Belgian Dutch, formal Dutch and Dutch. It did not; it only translated these "language options" into Dutch and it did not sort them properly.
I then checked the options for English only to find that it did not pick up on Canadian English as being a valid option. American English is not even an option.
This fun event will be mentioned at the "stand up" meeting of the Localisation team. It will be interesting how the "product owner" will evaluate this new functionality and if and how our team will deal with it. Whatever the result, I do not expect that too many words will be used.
Thanks,
GerardM
Typically my user interface is set to English so I changed it to Dutch to see if it would pick up the fact that there is Belgian Dutch, formal Dutch and Dutch. It did not; it only translated these "language options" into Dutch and it did not sort them properly.
I then checked the options for English only to find that it did not pick up on Canadian English as being a valid option. American English is not even an option.
This fun event will be mentioned at the "stand up" meeting of the Localisation team. It will be interesting how the "product owner" will evaluate this new functionality and if and how our team will deal with it. Whatever the result, I do not expect that too many words will be used.
Thanks,
GerardM
#Mobile traffic is what makes #Wikipedia grow
It is great when a plan comes together; improved mobile access was made part or our strategy. Traffic from mobile devices has grown briskly for quite some time and the statistics for Wikipedia show this clearly. Total traffic based on our current methods of collecting data show an overall growth of eight percent.
When you compare the traffic for the English Wikipedia, without mobile traffic it would have decreased by five percent on a year on year basis. With mobile traffic its reduction is only one percent.
When you compare these two screens, it shows that the overall growth in traffic is an additional three percent because of mobile traffic.
Mobile traffic in the bigger languages is doing really well with a 109% growth on a year on year basis. English is the biggest language and its growth of 80% suggests that other languages have at least the same potential and therefore deserve proper attention.
One challenge with mobile devices will be in making sure that the "other" languages will benefit from this mobile growth. To accomplish this, we may have to tweak functionality we aim to deliver like WebFonts. Input methods are different anyway so there is plenty of work left that will ensure that you can do MediaWiki in any language on any device with equal ease.
Thanks,
GerardM
#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
Saturday, October 22, 2011
#Fundraising is a growth path for a #Wikimedia chapter
The Dutch chapter is meeting. First line of business, providing some clarity about the existing fundraising situation. The current situation materialised because the American authorities require the Foundation to ensure a consistent world-wide practice.
As a consequence there are now chapters that have a fundraising agreement and chapters with a grant agreement. Several pains were mentioned; the Foundation was not present in Vienna at a conference on fundraising and, WMF officers are found not to have room to negotiate.
Currently the Dutch chapter has a grant agreement. The question raised is, what does this mean for the chapter and its activities. Fundraising takes a lot of effort and it takes away from the activities these funds are needed for. On the other hand a chapter involved in fund raising will grow its ability to run projects.
The biggest issue raised however is who decides what is strategic in a specific area. The Dutch chapter has been very active in GLAM and Wikimedia loves Monuments. This is not that much in line with the published WMF strategy but the effect has been stellar. The autonomy of a chapter to have local strategies and projects is why we are a Wikimedia movement and not a single organisation.
The question is, how will we ensure that we remain effective and a grass roots movement.
Thanks,
GerardM
As a consequence there are now chapters that have a fundraising agreement and chapters with a grant agreement. Several pains were mentioned; the Foundation was not present in Vienna at a conference on fundraising and, WMF officers are found not to have room to negotiate.
Currently the Dutch chapter has a grant agreement. The question raised is, what does this mean for the chapter and its activities. Fundraising takes a lot of effort and it takes away from the activities these funds are needed for. On the other hand a chapter involved in fund raising will grow its ability to run projects.
The biggest issue raised however is who decides what is strategic in a specific area. The Dutch chapter has been very active in GLAM and Wikimedia loves Monuments. This is not that much in line with the published WMF strategy but the effect has been stellar. The autonomy of a chapter to have local strategies and projects is why we are a Wikimedia movement and not a single organisation.
The question is, how will we ensure that we remain effective and a grass roots movement.
Thanks,
GerardM
Subscribe to:
Posts (Atom)

























