Showing posts with label Localisation team. Show all posts
Showing posts with label Localisation team. Show all posts

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

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

Friday, January 20, 2012

#Testing, 123, testing, testing

Testing #MediaWiki is fun. There are many, many Wikis and they are all different. Yes, we can create tests for a plain vanilla WMF Wiki. In reality they are all different. They are different because most have their specific modifications, their own gadgets. All have the potential to fail what passed the integration tests for plain vanilla wikis.

To known this, you have to have tests in the first place and the WMF Localication team is getting to grips with the testing platforms and building the tests that enable continuous integration.

Building tests is fun. You start with software that seems to be working perfectly and the tests prove that it has issues. This may sound odd, because it is not as if the software was not tested. A test that can be automated is validated in different ways. When a browser shows characters only a little bit different when comparing output, an automated test will catch this when it compares it to what is defined as correct. In many ways, automated tests test on a lower level then what humans do.

It is just that we do not have the humans to test over and over again.
Thanks,
     GerardM

Wednesday, December 14, 2011

WebFonts update

The initial deployment of #MediaWiki WebFonts has resulted in a large number of reports of large and small issues. Many of them have been fixed they are bug 33025, 33034, 32775, 33096, 33024, 33040 and 33039.  Others have to do with the fonts themselves. During a thorough analysis; the reported issues were recreated in the various browsers and were discussed among the members of the Wikimedia Localisation team. A lot of hard work has followed to fix, review and deploy as a team.

The results have been deployed to the live Wikimedia wikis. A full report was posted to the I18n mailing list. A special word of thanks goes to Bala Yeyaraman and Srikanth L who have been awesome in testing and reporting bugs for several Indic languages.

Please continue testing and give us your feedback.
Thanks,
      GerardM

Monday, November 21, 2011

#Agile is about getting functionality out

Many software development projects fail to get functionality in a timely manner. Often all functionality is released all together and it has to function to the nth degree. Usually it doesn't and usually the users of the new functionality grumble and object. The Wikimedia Localisation team does not produce everything in one go. What it does is produce functionality that is described in a story
Alolita wants to edit to localise the translatewiki.net user interface in Hindi and uses the Narayam functionality to mimic a Devanagari keyboard. She is not able to type blind and she uses a mock-up of the keyboard to find the keys she needs to press
In Agile this is called an "user story" and for us it is part of the Narayam "epic story". This story is analysed, it is divided in tasks, they are given points and every fortnight it is decided what stories to implement in the next sprint. Those stories can be quite rough around the edges consider; a story that takes as a premise that the user can type Hindi blindly is already in production.

The point of the stories is that they describe precise functionality and this is what is realised in a limited time frame. These stories are selected at the beginning of a sprint and consequently not only does new functionality get frequently realised and implemented, priorities for what the language team is to do are also constantly re-assessed.

Our hope is that our users; the Wiki communities will find us responsive. Our aim is to make the gap  between the user-experience in English and any other language as small as we can make it.
Thanks,
      GerardM

Sunday, November 20, 2011

Typing made easier for six languages

The #MediaWiki Narayam extension provides keyboard mapping. This means that when you have an International keyboard the keystrokes will be mapped to what it would be on a keyboard with another layout. This is a great help when you can type blind.


The Mumbai Hackathon has provided us with new keyboard methods for Urdu, Panjabi, Gujarati, Bodo, German and Marathi. All these keyboard methods are available now for testing in translatewiki.net.

Photo Victor Vigras
These keyboard methods are a step towards making it as easy to use MediaWiki in these languages as it is to use MediaWiki in English. This challenge is one for the Localisation team. The challenge to enhance the usability for English is outside its remit; this is what all the other developers are working on but keeping up with their good work will keep the team occupied.
Thanks,
       GerardM

Friday, November 18, 2011

WebFonts are ready for your comments


At the WikiConference #India, one of the main topics is support for the languages of India. The government of India acknowledges in its best practices that not everybody speaks English. MediaWiki may not be used by the Indian government, but it certainly aspires to bring these best practices in reality. In summary, we aim to make Wikipedia and all its sister projects as easy to edit in for instance Malayalam or Orya as English.

One of the stumbling blocks for us is that many of the computers sold did not come with support for the Indic fonts or with the keyboard mappings for Indic languages. The "Localisation team" worked hard to overcome these two very basic issues. For many languages the Narayam extension is now live and allows people to type. The next phase is providing WebFonts. Web fonts are fonts send to your computer with the data for the articles. 

Providing web fonts can only happen by us when fonts are available for a language and when these fonts are freely licensed. Luckily the fonts used by the Linux operating system are freely licensed and we are happy to provide these as well as other fonts to you.

At this time we are testing the use of WebFonts at translatewiki.net and we intent to bring WebFonts in production for all Wikimedia projects in Indic languages on December 12. We will start off with WebFonts for the Indian languages and other languages will follow at a later date. In the run-up to production day, we need you to assess the fonts for us. the questions we have are:
  • do these fonts represent the script as defined in the latest Unicode specification
  • are the characters readable
  • are you comfortable with the user interface that allows you to configure WebFonts
  • is the default we have chosen for your language the best freely licensed font available
Given that our aim is to bring information to everyone, you will appreciate that our prime objective is to enable more readers and help more people to find their way to our projects. We are quite happy to use any font that meets with our technical requirements when it is freely licensed. 

To help you assess the options available to your language, there should be a page called WebFonts that contains a copy of the India article in your language. 
Thanks,
      GerardM

Monday, November 14, 2011

#MediaWiki code review leads to refactoring

Once software is written, it needs review. When you get a great review, it may include both specific instructions and general suggestions. Krinkle did a wonderful job reviewing the current iteration of the WebFonts extension and his instructions and suggestions equally apply to other applications we are working on.

This realisation that instructions and suggestions are equally relevant in other code is powerful; it also indicates that the existing code is written in a consistent way. For the Localisation Team it is not that surprising as it does its part in the development and the maintenance of coding standards particularly for internationalisation and localisation.

Given that all Wikimedia developers are reviewing each others code and given that every one has its strenghts and weaknesses, quality is achieved by reviewing widely. For many Wikimedia developers reviewing code of other developers is a reminder that they grew into their role because of the people who mentored them and reviewed their code.
Thanks,
       GerardM

Tuesday, November 01, 2011

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

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

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

Saturday, October 22, 2011

#Wikipedia is seen in other languages

Slowly but surely, the "other languages" are getting traction. October 2011 is when the top 10 Wikipedias are likely to leave more then 10% of the page views to the other Wikipedias.

The popularity of Wikipedia is growing nicely for many languages; the Chinese Wikipedia for instance grew 289% on a yearly basis. For many languages the growth rate is in the double digits and together they more then offset the lack of growth for the English Wikipedia.

When the Localisation team will introduce its functionality in production, it is likely to boost the usability for many languages. When the general public starts to perceive this in a positive way, we will get more readers and editors. All these people will be making a difference for their language and culture; they make freely licensed encyclopaedic information in their language on the Internet their own.
Thanks,
      GerardM

Monday, October 17, 2011

Having #Babel level 0 available is best practice

On many a #Wikipedia, people come along to do some admin work or leave a message. I have the good fortune to invite people to become part of a "language support team" for their language because the "Localisation team" I am part of do not know enough of all the languages we aim to support.


My user page looks practically the same on all the projects where I have a user for my WMF persona. The example above indicates that I do not know Catalan. The message I leave is also the same for all languages, the one I left on the Catalan Wikipedia can be found here. Obviously it is not in Catalan.

We hope to channel the communications between a language community and us through the people who can help us and who are willing to help us. It is simple, proper support for a language requires expertise and together we can provide proper support for all our languages.
Thanks,
       GerardM

Sunday, October 16, 2011

Another use for a #font

The Bengali script is not only used for the Bengali language. The Bishnupria Manipuri language is as far as we know written exclusively in this script.

The best way to explain what the Localisation team can do for a language community is to implement known solutions. Adding the support for the Lohit Bengali font for Bishnupria Manipuri is easy and obvious.


We do not know if there is a need for an input method that is specific for Bishnupria Manipuri. For that we need to be advised by people who know the language. When they work together in a language support team, we can build the framework that they can implement solutions for their language on.
Thanks,
    GerardM

Wednesday, October 12, 2011

#Google, #Acehnese is not #Indonesian

The Acehnese #Wikipedia is recognised by the Google Chrome browser as Indonesian. It even offers to translate it into English.


However, in the html, there is a tag identifying the language as "ace" or Acehnese.
<html lang="ace" dir="ltr" class="client-nojs" xmlns="http://www.w3.org/1999/xhtml">
When you check the bar, there are options, one of them is to report an incorrect language detection. There is a drop down list of languages to select from with an option at the bottom to specify a language that is not in the list.


For Google to provide a translation service is wonderful. There is however a reason why we specify a language. It is because we want everyone to know what language a text is in.

Adding this is best practice for a website but sadly many if not most websites get it wrong. It is intended to allow services like the Google translation service to know  what language a text is in. The Localisation team will go a step further for MediaWiki; it will provide services based on the language indicated by this tag. Services like WebFonts, keyboard mappings and appropriate text direction settings.

Identifying a language is relevant, many services rely on it and it is what gives visibility to a language on the Internet.
Thanks,
      GerardM

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


Tuesday, October 11, 2011

#RTL support in #Wikimedia #Commons

The screenshot below shows splendidly how #MediaWiki has improved its support for languages like Arabic and Hebrew. The sidebar is to the right, the labels used for the image are in Arabic and the descriptions are in the direction of the language indicated.

As you can see, the "Summary" is a text in English and it is displayed in the wrong direction for English. This is probably the consequence of the software not knowing that this text is in English.


This is clearly a bug and it needs to be reported. The obvious way is to report this in Bugzilla. A bug reported in Bugzilla ensures that there is a record of this issue. It is likely that more issues like this bug exist where support for the use of RTL languages breaks.

In the Localisation team we are exploring the known RTL bugs. This is the best time to experiment with the combination or RTL languages and LTR languages because at this time we are extremely receptive and are able to resolve them relatively quickly.
Thanks,
       GerardM

Wednesday, October 05, 2011

What is in a name

This #translatewiki.net user localises for the Sinhala language. As you can see, his name is something that will be hard to recognise even for native speakers of the Sinhala language. One character is completely lacking and, that character is probably to be used together with the third language.

When our friend from Sri Lanka localises one of several projects he is interested in, it will be obvious that we do not and cannot verify any work done in Singhalese. A computer needs to have a functional font for Sinhala or alternatively web fonts need to be provided..

What we hope for is people who know their language well will be joining the Language support teams we are setting up and become an ambassador for their language. We really need knowledgeable support for Sinhala because these pesky boxes are not going away when I have a Sinhala font selected.



What gives, why does the font not work. What other issues need to be addressed?
Thanks,
       GerardM

#MediaWiki 1.18; RTL is no longer like Mr Bean driving in France

Support for right to left scripts is one of those un-holy grails that everybody seems to be looking for. The objective is for readers and editors to easily read and write.

When it is wrong, it feels like driving in Great Britain where nobody will drive on the right side of the road. Everything is where you do not expect it and, it looks awkward.

With release 1.18 MediaWiki many bugs that have to do with mixing and matching scripts with different directions have been tackled. On Commons and any other wiki, the sidebar will be on the side where it makes sense for the language of your preference. For languages like Urdu, Persian, Arabic and Hebrew, it will be on the right side. The content itself, in the text box will show as it should for the "content" language.

The Localisation team has been tasked to crush the rest of the RTL bugs. Guess, what we KNOW about the bugs is in bugzilla, so when there are more bugs for us to crush, this is the time to identify them to us .... and bugzilla is where we are looking for them.
Thanks,
      GerardM


Tuesday, October 04, 2011

This is on the same #Wikipedia main page

The Malayalam language can be written in many writing styles, most people prefer the traditional style while others opt for the modern style. The modern style was developed to enable typewriters and printing and as such it has been hugely important to bring knowledge to the people of Kerala.

With modern digital technology the restrictions of the previous technology no longer apply. Wikipedia can be in either style because with WebFonts it needs to be no more then a matter of preference. In Linux you will be provided with the traditional fonts by default while Windows tries to be more modern.

WebFonts are a MediaWiki extension that can be applied in many ways and for many reasons. For Wikis we have identified six user scenarios so far. The bet within the Localisation team is that the community will come up with more/less then three additional user scenarios. We expect however that these scenarios can be happily accommodated with the functionality we are currently writing specifications for.
Thanks,
      GerardM