Showing posts with label localisation. Show all posts
Showing posts with label localisation. Show all posts

Sunday, August 25, 2019

#Translatewiki.net the @Wikimedia movement infrastructure most people even do not know


Just consider this, there are more than 200 functioning Wikipedias and this is only possible because people localise the MediaWiki software in over 280 languages. It makes translatewiki.net, the website where all this work happens a strategic resource to the Wikimedia movement.

Internationalisation (i18n) and localisation (l10n) are an integral part of software development. It is an integral part of a continuous process and it requires constant attention. The day to day jobs are well in hand. The localisation itself is a community effort and with developers continually expanding the software base a continuous effort is needed of the translators to keep up with their language. This is hard and for many languages it is a struggle to keep up with even the "most used messages".

Managing this effort is a continuous effort, it is essential to maintain the i10n and the localisation optimally. It follows that it should be obvious what messages have the biggest impact first on the readers and then the editors of a Wikipedia. What should be in the "most used messages" changes over time and when it is considered strategic, such maintenance is to be considered a Wikimedia/MediaWiki undertaking. 

Translatewiki has always been an independent partner of the Wikimedia Foundation and it has always been firmly part of the Wikimedia movement. Given that partnerships are a key part of the strategic plans of the WMF, the proof of the partnership pudding is very much in how it interacts with a translatewiki.net. TWN does not need to be part of the WMF organisation for it to fund TWN, it is clearly a quid pro quo. The WMF should even encourage TWN and other partners to collaborate for their i18n and l10n and enable this for strategic purposes, strengthening these partners globally. 
Thanks,
     GerardM

Tuesday, June 05, 2018

#AfricaGap - Lucien Xavier Michel-Andrianarahinjaka a politician from Madagascar

Lucien Xavier Michel-Andrianarahinjaka is a politician from Madagascar with two Wikidata items that have now been merged. People at the Zulu Wikipedia expressed an interest in information on all African politicians and as a consequence they want to have all information available in Zulu.

Reasonator is a tool that makes this easy. As you can see in the screen shot, there is a lot to do; the label for "male" for instance is not even known yet. When someone who knows Zulu sees the information in this way, it is extremely easy to add a label in Zulu.

When you consider names of people, typically the spelling of a name is the same when seen in the same script. When this is true for Zulu or Xhosa or .. it is easy enough to have a bot add the missing labels in Zulu.

When labels are available, it becomes practical to have info boxes particularly when the info in these info-boxes is updated from Wikidata. In this way it becomes possible to provide information in Zulu, information that will be hard to find in Zulu elsewhere on the Internet.
Thanks,
       GerardM

Friday, June 01, 2018

#AfricaGap - maps in Yoruba, Swahili, Hausa and Zulu

As no percent of Wikipedia is about Africans, it is great to learn how "map internationalisation" works on African language Wikipedias. The original example has Africa in Russian and with two tweaks, this same map shows really well in Yoruba, Swahili, Hausa or Zulu.

My objective is to bring focus to African content. I am still adding African politicians and this new functionality is too good to miss. It works really well, the documentation is there and it becomes a matter of localising the information for it to provide the same information properly in the languages of Africa.

While adding such information it becomes painfully obvious how much is still lacking. It would be cool to have information in long lists like this in columns. It takes more expertise than I have to make this happen. I have not figured out how to get Listeria to update these lists either.. At some stage I will or probably sooner, someone else will help me out.
Thanks,
       GerardM

Sunday, October 19, 2014

#Wikidata - P1472, the #Commons #Creator #Template

The work of many artists is represented in Commons. Having great information available for all of them is a Herculean job. Having all that information and more available in all the languages that are supported by the Wikimedia Foundation is very much an aspiration.. Once Commons is wikidatified, all information needs to be understood in all our languages..

France Prešeren is one of 13,481 people who currently have a Creator template and are known as such in Wikidata. All the data in those templates can be harvested and included in an Wikidata item. For all the templates NOT known in Wikidata, an item can be found or created to make them known in Wikidata as well.
A lot is already known about Mr Prešeren in Wikidata and much of that data can be expressed in multiple languages. The same can be said for the Creator template itself; as you can see, the template already shows its labels in multiple languages. With Wikidata we can show the information in all our languages as well.

Realising this will introduce the Commons community in a positive way and reduce one obstacle that needs to be overcome during the wikidatification of Commons.
Thanks,
      GerardM

Friday, January 17, 2014

#Wikidata - making #information from #data


Wikidata contains lots of data and making this into information is a matter of giving it a place, providing a user interface, bringing some order and even visualising the data. The latest version of the Reasonator is pushing all this.

As you may recognise, the user interface is in Dutch, at this time it could also be French, German, Telugu, Malayalam. We would love to have localisation in a few hundred more languages.

When it is about a person, we can show the family tree as well as the names of the near relatives. We provide even better support for external sources and, how do you like the way we show the Wikis connected to this item?

The best way to support your language? Just start adding the missing labels. The effect of one hour of work can be really amazing..
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

Saturday, January 05, 2013

#Wikidata needs #localisation

A lot of hard work has gone in developing Wikidata. It is getting at a stage where the localisation of the "Wikibase - client" extension (only fourteen messages) needs to be done.

Of particular interest is the localisation in Hungarian; they are likely to get the Wikidata functionality implemented as one of the first.

As always, localisation of software is done at translatewiki.net. As always there is more that you can do for your language.
Thanks,
      GerardM

Monday, May 14, 2012

Benefit from the #MediaWiki Babel extension

At #translatewiki.net a Northern Sami Wikipedian asked for and was given translation rights. When a person wants to localise in a language, we ask to provide us with information about the person's proficiency in the languages he or she knows. At translatewiki.net we use the Babel extension for this.

When the Babel extension is not localised, I often ask people to localise Babel. This time the person had not provided us with the opportunity to send him an e-mail so I went to his profile on the se.wikipedia.org to ask the question.

On the profile page I found his Babel information provided by templates and as you can see to the right, many templates are missing and some like the one for Swahili and Japanese are incomplete. I copied his Babel information to my talk page. For some of the languages there is no localisation but the information is now at least readable in English.

The templates provided me with enough information to localise some of the Babel messages in Northern Sami. All that is left is for these messages to be distributed to the Wikimedia projects.
Thanks,
    GerardM

Monday, April 23, 2012

#MediaWiki #Localisation update process runs now with #GIT

Tthe #Wikimedia Foundation embarked on the migration from SVN to GIT and it proved quite an adventure. It was unclear how changes in the MediaWiki software and its extensions would end up in translatewiki.net . It was unclear how changes in the localisation would end up in GIT and from there on the production wikis.

We are now happy to report that the pipeline from new and changed messages in the MediaWiki software and its extensions resulting in new and changed localisations in all the WMF projects is working again. The messages that have been localised are now automatically moved into GIT and from there the LocalisationUpdate process makes them available in all the WMF wikis.

When you had the LocalisationUpdate process running on your wiki, it is likely that you need to update the software to reflect the change from SVN to GIT. When the latest version of LocalisationUpdate does not work for you, please create a bug in Bugzilla and ask for support.
Thanks,
    GerardM

Friday, March 16, 2012

#mlwlux - #Wikipedia, how many people do live in #Amsterdam

At the Multilingual Web conference in Luxembourg, it was mentioned that Amsterdam has a different number of people living there depending on what Wikipedia you are reading.

It needs a solution it was said. Yes it does and letting us know is part of a solution. It certainly allows the number for Amsterdam to become the same. A real solution would be one where such data is maintained centrally and served where ever it is needed.

The Wikidata project is starting and one of its objectives is to serve as a central data repository. The people at the conference will appreciate that it is not simple; 783.364 is the number quoted on the Dutch Wikipedia while an American would say that a number like 783,364 is quite a lot more.

Anyway; we do appreciate that the numbers game and the data game is very much something we have fun with in the near future.
Thanks,
      GerardM

Tuesday, March 13, 2012

#multilingweb - #i18N and #l10n testing framework

A subject for the conference about the Multilingual Web is what gaps exist in supporting a multilingual web. Obviously people who are living the multilingual web like my colleagues in the WMF localisation team suffer these gaps. Our team has been asked what to do next and one idea of Amir I love to put forward.
A testing framework for localization
I searched and I couldn't find any testing framework that is focused on localization. Many localization-specific issues must be tested, for example, grammatical correctness of generated messages, text readability in different scripts, support for encodings and fonts, etc. You can find a fuller list in Wikipedia (i wrote most of that section myself). It is possible to test all these things using the current frameworks, but much of it would be manual.
For example, i'm not familiar with any tool that would automatically or semi-automatically create screenshots of all the possible translated strings with their complete context. This would be useful for the translator, to see how to translate a message; for the developer, to see whether any message runs out of the screen or hides a button that must remain visible; and for the tester who speaks the language and wants to see whether all the generated messages are grammatically correct. Currently, a developer must do this manually;
it is time-consuming, inefficient, hard to plan and to maintain, and the fact is that the developers are hardly ever doing this.
Such a testing framework would be really great for so many organisations. At translatewiki.net we support many organisations with their internationalisation and localisation. A framework will make it easy to repeat the testing often. This will improve consistency and quality and makes for a great multi lingual experience.
Thanks,
     GerardM

Friday, March 09, 2012

Fixing #terminology in #translatewiki is easy

The most important objective of translatewiki.net is to make it easy for our localising community. Another really important objective is to make sure that we facilitate all the needs for our localisers.

When we learn that a particular community localises on their local wiki, we really want to understand why. When we do, we will look for a solution that will make localisers more efficient and preferably reconsider using translatewiki.

At this time localisation is done locally on the Sanskrit Wikipedia. The argument to do this is because a lot of work is going into deciding on the best terminology used. Once the community has decided on what word or phrase to use, the changes that reflect the decision are made locally one at a time.

Translatewiki offers an alternative that is much more efficient. It is possible to export the messages. The result is a text file in the "gettext" format and all it takes to replace the changed terminology is to use the tools available in any decent text editor. Once this is done, the updated file is uploaded to complete this task.

Every language on translatewiki.net has its portal page and the Sanskrit portal should include references to the used terminology. This will prevent a person new to localising Sanskrit from using the terminology that he or she likes best.

Obviously it is up to the Sanskrit community to do as they please. Localising in an environment dedicated to localisation makes the people involved in localisation more efficient. The benefits of  their work will be widely shared and the developers at translatewiki.net are eager to learn why their environment is not good enough. They will fix things where it is broken.
Thanks,
      GerardM

Wednesday, March 07, 2012

#Twitter does #RTL

When Twitter started to support right to left languages in earnest, they did need localisation for their software. Given the relevance of Twitter a great localisation is important; many people will actually see it, use it.

With the implementation of RTL languages like Arabic, Farsi and Hebrew, and the simultaneous localisation there are many people who are exposed to the same issues and flaws in the software. What is so wonderful that all the people localising software find each other and work together. It is as a Saudi Wikipedian wrote on the Arabic village pump: "we all have the same problems".

Amir, one of my colleagues in the WMF Localisation team, does a fair amount of localisation on other projects in his own time. The one thing we learn from him is about cool features used in other localisation platforms.



What really pleases us is how often we learn how much the community model of translatewiki.net is valid. It does make a difference when people are not working on their own little island. Many applications are localising an upcoming release and this makes all these people testers as well. People learning together about issues and working together on solutions particularly with developers involved as well make for a perfect and agile software development environment.
Thanks,
     GerardM

Wednesday, February 22, 2012

Why localise #MediaWiki at #translatewiki.net

Some of the localisations in use for MediaWiki need improvement. It can be for all kinds of reasons including bad grammar, typos, spelling errors but also because a message changed. When you are an administrator on a wiki, you can change such MediaWiki messages on your local wiki however, you should not.

When you improve a message locally, the result will be local and it will override the messages that come with the MediaWiki software. This includes the daily messages that are new or have been updated and come to you through the LocalisationUpdate process.

When you improve a message at translatewiki.net, you will find the experience much more productive compared to working on your local wiki. Tools are available to you that suggest translations, help you proofread what is already there. If anything, translatewiki.net exist to make you as a localiser as efficient as possible. You will find once you get going, you are at least ten times more productive.

For some people localising on-line is what prevents them from being productive. When the local connectivity to the servers of translatewiki.net leave a lot to be desired, it is sometimes better to work off-line.

Getting the message out why you should localise at translatewiki.net has its answer in this way. However, there is a reason why some messages need to be changed locally. It is because the message needs to be adapted to the local wiki. They may be about policies, contact information or whatever else is not standard. Only a few people need to bother with this and they are the local admins of a wiki, they are the ones who can change messages locally.
Thanks,
     GerardM

Monday, February 20, 2012

International Mother Language Day 2012

#Wikipedia is without a doubt a good example of a multilingual project. On a good day we support 280+ languages. On a sad day there are more then 6000+ languages we do not yet support.

This year a lot has happened at the Wikimedia Foundation to support languages. As we now have a Localisation team, we support quite a few languages with web fonts and input methods. We are improving our translation capability. The internationalisation for our PHP and JavaScript code supports grammatical gender and plural.

Best of all is what we aim to achieve: we make editing MediaWiki as easy as it is to edit in English.

This year we will host an "office hour" at 18:00 UTC on IRC. The subject is very much how we can help you and how you can help us support your language. We welcome any suggestions that improves the use of MediaWiki in your language:

  • web fonts
  • input methods
  • translation
  • localisation
  • support for language rules for your language in MediaWiki
  • transliteration from script to script
  • your language support team
  • your suggestion....
Thanks,
      GerardM

Tuesday, February 14, 2012

Towards a #Gujarati #Wikisource

In #India, people realise that having a Wikisource is really relevant. Recently we celebrated the start of the Marathi Wikisource and now the spotlight is on the creation of a Gujarati Wikisource.

The Marathi Wikisource is special because the Maharashtra government promised source material to be published on their new project. We can hope that this will set an example for other Indian state governments.

The information needed at the moment of creation is being collected. They already created a logo for the Gujarati Wikisource. They finished the localisation of the compulsory messages in record time and now it is time for the language committee to assess if all the requirements are met.

When the language committee is satisfied, they will ask the Wikimedia Foundation board for permission to create the new project. This formality is typically granted and it is then for the WMF operations people to create a new project. It is at this stage that several configuration options have to be available and it is great that this information is already being collected.
Thanks,
        GerardM


Thursday, December 22, 2011

Workable code is not always deployable code

The #Wikimedia #Localisation team cranks out code, workable code - every sprint. At the end of the sprint, for us a sprint lasts a fortnight, all the completed "stories" are tested against their acceptance criteria and when the tests are good, they are signed off and marked as completed.

With this jargon out of the way, it is possible to consider features.

The Translate extension needs an additional feature to help translation administrators manage their work. Pages that have been marked for translation have a life-cycle; at the start they are marked for translation but at a later stage there is no longer a need for translation. Such a status change has an impact on what translators are to see.

There are many stories that make up the Translate status feature, for instance:
  • you can watch the list
  • you can change the status on a text
  • the list is different depending on the role of a user and the status of a text
A sprint is run in a fixed amount of time. In a sprint there often are stories for multiple products. When the stories do not provide enough functionality for a feature, additional stories will make it in the next sprint. When you read this carefully, you may appreciate that "enough functionality" is not the same as "feature complete". The point is very much that with Agile we get feedback as soon as possible.

When you are interested in the stories in our current sprint, have a look in Mingle (user: guest - password: guest).
Thanks,
      GerardM

Tuesday, December 20, 2011

The return of the LocalisationUpdate

The #MediaWiki localisation is a continuous process. A continuous process because MediaWiki development is a continuous process as well. For some languages everything is done, for others the localisation is very much a work in progress.

As a lot of work is involved in getting all the localisations done, making sure that people remain motivated is a challenge. The reasons for them to localise are:

  • it is the best usability improvement available for any language
  • localisation is a requirement when new projects are requested
Such arguments are a bit abstract. What does convince many people is making the latest localisations available on a daily basis to all wikis. This is what the LocalisationUpdate extension is there for. It is why almost every day the latest localisations done at translatewiki.net are committed to SVN.

Something broke in the beginning of November but today the server admin log finally indicated: 
02:04 logmsgbot: LocalisationUpdate completed (1.18) at Tue Dec 20 02:07:54 UTC 2011
On many wikis it will be noticeable that a months worth of localisations became available. It will be good when the people who lost some of their motivation will give translatewiki.net another try. They will see again how much difference their effort makes. Not only because their work goes rapidly into production but also because it is and remains the best usability improvement for their language.
Thanks,
        GerardM

Saturday, November 26, 2011

A #translation sprint and an intro to #MediaWiki hacking

The verdict on the records is out; the day is not done yet. The biggest thing was when a Panjabi woman was thrilled to be able to just type Panjabi in the Symbiosis computer lab.

This was a revelation shared by other people in the room for other languages. Supporting many Indic languages is available for many operating systems. Never mind how cool it is to support you with Narayam and WebFonts, it is much better to have support local on your local device. This not only provides you with the support you deserve in Wikipedia but also in all the applications you might run. You know what, installing this is not that hard.

At this time 40+ new people created a profile at translatewiki.net, many people have experienced that it is not that hard to support Free Software by helping themselves make the software available in their own language.

The second part of the day, the technical part was too short but many people got a clue what MediaWiki and its infrastructure is about. For us to be in Pune has been a privilege and, it is really cool to see the functionality we are so passionate about being used in earnest.
Thanks,
      GerardM

Friday, November 25, 2011

#Translation sprint in Pune is one for the whole world

The #Wikimedia #Localisation team is in Pune #India. Tomorrow we have a translation sprint at the University and our intention is to seriously beat some records. The record for the most translations in an hour, the record for the most translations in a day, the record for the most contributions of translators in a day; they are all up for grabs and we intent to break them.

We expect some 50 people at the university.  They are going to translate and they are all going to start together. Our team is available to explain, support, authorise. But when we can do it for the people in Pune, we can also do it for the people of India who want to help us. When we are at it, we can do it for people from where-ever.

When we are done at the university, we will be flying home. Happy to see our family again but we are not the only ones who support the translatewiki.net community. It will be interesting to see how we cope, how well the server copes and how hard it will be to break the record now and in the future.

So help us today, localise for your own language and break every record we have in our book.
Thanks,
        GerardM