Showing posts with label Meta. Show all posts
Showing posts with label Meta. Show all posts

Monday, March 26, 2012

Translate reports of the #Hungarian #Wikimedia chapter

Like so many chapters, the Hungarian chapter writes monthly reports. Their main audience are the members of the chapter and for them Hungarian is a must. Many of the international partners and relations need the same report in English.

The Hungarian monthly reports are really needed in two languages. Having them translated in other languages would certainly be appreciated; the German WikimediaWoche for instance refers regularly to newly published chapter reports. This is a great argument for having reports translated in German. When people want to translate the Hungarian reports in another language, adding that language is only a click away.

Obviously many more chapters post their monthly reports you can also find them on chaptersplanet.org . Having the reports both in English and in the language of the land seems obvious. When more chapters translate their reports, it becomes relevant to translate the pages on Meta that point to these reports as well. This in turn will promote the translation of the reports of other chapters even more.
Thanks,
     GerardM

Saturday, March 03, 2012

New templates for new #Wikimedia projects

People do request new languages on Meta. When a new language is requested, people will have to comply with a series of requirements. They are things like the localisation of messages, the writing of a few hundred articles that allow us to assess if what is written is really in that language..

When the requirements are met, when the members of the language committee are happy with the results, an e-mail is send to the chair of the board of the Wikimedia Foundation with the recommendation to approve the new project. Typically these recommendations are followed.

The next step in this workflow is the creation of a bug in bugzilla requesting the creation of the new Wiki. At that time specific technical information is needed. This information is needed by the Wikimedia engineers to create the project.


Robin made changes to the template and, we have changed the request for the Gujarati Wikisource. This request is in the final stage and we want to learn if the changes to the template make it easier to complete the necessary information.
Thanks,
      Gerard

Friday, February 03, 2012

#betacowork ; a great place to work in #Brussels

In time for #FOSDEM; #Wikimedia people were looking for a place to work, have great connectivity and talk shop. At BetaGroup Coworking we found a warm welcome, and experienced how its customers are provided with what they need. For us it was a white board and guess what, someone brought chocolate cake..

We found a quiet spot where we discussed the usability and the user interface of the Translate functionality. Having Jon Harald with us proved to be a boon. He did the project management for the Fundraiser localisations and brought us a large amount of observations and suggestions.


Having a white board allowed us to easily visualise our ideas and as easily replace them with something else, something better. Once we achieved a common understanding, Jon Harald's input was translated in a "user story" by Siebrand and this will eventually end up as more work for Niklas.

PS According to Jon Harald it is not cold ... not cold enough to wear a coat.
Thanks,
      GerardM

Friday, November 11, 2011

#Wikimedia highlights for October

Many people are eager to know how the Wikimedia Foundation is doing. Every month there is a long publication in English with everything you want and do not want to know. It can be translated, but it is considered too much of a burden on our translator community. In order to get the main message out anyway, there are highlights that are available for translation at Meta.

Once a translation is ready, the highlights can be referred to on the local village pumps of the projects for a language.


The latest Wikimedia highlights, the one for October, are looking for translators. When you make a request for translation, the translator should easily be guided to what needs doing. Two improvements to the original request have been implemented;
  • When you click on the article link, you will see the text in the language you prefer
  • When you click on the translate link, you will be shown the text fragments for your language
Meta is a multi-lingual project and it can be expected that people have set their user preferences to their mother tongue. When they do, we can provide them with translations when we have them.
Thanks,
     GerardM

Wednesday, October 12, 2011

To #Translate on #Wikimedia Meta

Providing adequate tools at Meta has been a holy grail for the developers of the Translate extension. To get to this stage a page translation mode was developed a long time ago. This has been in use successfully at KDE for the translation of its user documentation.

Having tools to manage texts that need translation is extremely valuable when the message can and does alter. This has always been the case for the Wikimedia Fundraiser and it was more or less managed with templates. The Translate extension brings the kind of functionality that cannot be managed with templates.

Making use of the Translate extension also unifies the skills needed for the translation and localisation of the fund raiser. One other and essential part of the fundraiser is the software that has always been localised at translatewiki.net.

At this time Translate has just been implemented and everybody is granted the privilege to translate. Only some people can enable a page for translation. As a consequence the only page currently available for translation is a test page explaining page translation.

It was important to get the software ready as soon as possible because the annual fundraiser is already quite near. Thanks to Niklas, Siebrand, Roan and Sam it has been realised. Testing at Meta materialised a final bug that will be fixed before Translate will be used in earnest.
Thanks,
       GerardM


Sunday, March 13, 2011

Give us proper translation tools at #Wikimedia Meta

While #MediaWiki is excellent for writing encyclopaedic articles; it is not the right tool for all text jobs. We are asked to translate the Editor survey. It consists of a long list of short sentences, often repetitive. When translating these sentences, it would be useful to see the original text and existing translations to other languages. Add to this comments that make the context clear and the process of translation becomes easy and efficient.

The Translate extension developed for translating and localising at translatewiki.net provides all of these things in one convenient screen. Plain MediaWiki doesn't provide any of this and the translator has to laboriously move between screens.

Reviewing translated messages is a breeze with Translate. MediaWiki has this long list of translated questions which is very distracting. The Translate extension by comparison has a review mode that shows the translations juxtaposed with the original strings.

The Translate extension automatically offers translation for repeated sentences from its Translation Memory and automatic translations are suggested from Google and Microsoft. This is very efficient, but sadly MediaWiki doesn't have this either.

Modern browsers provide spell-checking functionality, which is very helpful for getting the translated text right. Mixing several languages in one editing box confuses the spell-checker and having a very long text in an editing box makes the spellchecker slow. With the Translate extension this is not a problem.

The Translate extension applies proper directionality to each language: Left-to-Right for English, Russian and Hindi; Right-to-Left for Hebrew, Arabic and Urdu. Translating using plain MediaWiki puts the original language - usually English - and the target language in one editing box and mixes up the directionality.

Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
"We're living in pieces,
 I want to live in peace." - T. Moore

Sunday, November 01, 2009

Karachay-Balkar

A request was made for the localisation of the  Karachay-Balkar language at translatewiki.net. As this was a new language, some technical bits had to be done, and Iltever was given translator rights.


In record time, within a day, all the localisation necessary for a first project were completed. Only after the localisation was the language added to the "Request for new languages" list. The request has the status of "open" because the language committee has to consider the eligibility of the request, but it is likely that this is another Wikipedia that is waiting to happen soon.
Thanks,
      GerardM

Tuesday, October 20, 2009

When the only tool you have is a hammer ...

Some time ago, I presented my answers to the question "What benefit of translatewiki.net as a WMF project". Today I found another fine reason why the Wikimedia Foundation would benefit from an infusion of some translatewiki.net usability.

As it is that time of year again, it is time to prepare for our fundraiser and as usual, in order to get the message out, the faithful are asked to translate texts into their language.



The screenshot of the Macedonian texts clearly shows that it is one page where all the texts are to be translated. A template has to indicate the status of the translation.

There are several reasons why this situation needs a review:
  • As it is one blob, it is not easy to tune the text and communicate the difference
  • Progress is to be indicated by changing a template
  • There is no percentage indicating the work that is left to be done
  • The translator effort is split between meta and translatewiki.net
  • The software developed at translatewiki is "not invented here"
When the Meta translations have to be translated at Meta, there is nothing stopping the powers that be to use the Translate extension. MediaWiki is a tool, the Translate extension builds upon it, there is nothing preventing the WMF to use the best of breed solution for its translations. If anything, the translatewiki.net crowd would be happy to help with its implementation.
Thanks,
GerardM

Saturday, July 05, 2008

Lingála

Lingala is a language spoken in both the Democratic Republic of the Congo and in the Republic of Congo by some 2.1 million people. This language uses the Latin script for its writing and has some additional characters. Two examples are found in "nyɔ́nsɔ" and "Kɛndɛ"́. Sadly not all fonts show these characters correctly.


In order to fix this problem, in the CSS of the Lingala Wikipedia some changes have been added indicating what fonts show these characters correctly. Given that the purpose of pro
jects like Commons, Meta and Betawiki is to support all languages properly, I would suggest that it makes sense to adopt these changes on a wider scale.
Thanks,
     GerardM

Wednesday, April 30, 2008

Extension of the week: Global blocking

Global blocking is the extension of the week at Betawiki. According to its technical documentation it has a beta status and according to the info on Meta it is life on all the WMF projects.

According to the Meta documentation, I should be one of the lucky few that can use this tool. However it is not clear to me at all how to use it; I have not yet found any documentation. What I understand is, that it only works for IP-numbers and that is really useful to prevent a lot of vandalisation. I think Werdna has done a fine job by creating "Global blocking".

What I find interesting is that the discussion about who will be able to use this tool and how it affects the autonomy of projects is still ongoing. There have been postings on the Foundation mailing list and there is a lot that can be found on Meta.

Sadly we do not have a project or volunteer council, IMHO it would be the obvious place where these things should be discussed / determined.

Some nice factoids:
  • In a conference in Beijing Denny reported that Semantic MediaWiki has been successfully localised in Betawiki.
  • We are deleting the Babel templates and use the Babel extension in stead
Thanks,
Gerard

Sunday, April 06, 2008

Ndonga and Dzongkha

Ndonga and Dzongkha are two languages. One is from Africa the other from Asia. Both still have a Wikipedia, one is officially closed the other is in the process of being closed. The dz.wikipedia is officially closed but has not been closed. The localisation effort is well under way and currently 78.12% of the most used messages have been localised. The ng.wikipedia has eight articles has no localisation and the usual people object to the closure of this project. On the talk page of Drini I found an anonymous coward indicating that something may be done soon ....

When projects are voted to be closed, they are not closed. This means that people like Drini have to continue their fight against spammers. There are two parts to the problem as I see it.
  • When the time of stewards like Drini is free and infinite and when they do not object to doing this work there seems to be no problem. We should however value the time of people like him and make sure that it is used sparingly and well
  • When policies lead to resolutions and these resolutions have no effect, what is the point of having these policies, these resolutions and all the time spend?
When policies have no effect, when nobody cares either the policies are wrong or we have to do a cost benefit analysis of the policies. When we find that the cost of having dead projects is less then the cost of blocking these projects we should abandon the policy for closing projects.
Thanks,
GerardM

PS I do not think it wise to close the Dzongkha wikipedia at this time.