Showing posts with label RtL. Show all posts
Showing posts with label RtL. Show all posts

Monday, February 10, 2014

#Wikidata - About #lists, page views and #language support


I positively hate lists. They should have only two statements one should indicate that it is a list and the other should indicate what the list is about. The problem is that many Wikipedias think a list is a substitute for the real thing.

When you look at the statistics for the Reasonator, you will find that there is no interest to see the information it provides in Arabic. So far there have been only 24 page views ... How to double this and double it again, how to find an audience for information presented in Arabic.

One way is to have information that they might like, this is why I did some work on the kings of Saudi Arabia. However, it then shows that the timeline screws up in that the buttons for right and left overlap. It is open source and a solution is welcome.
Thanks,
      GerardM

Wednesday, March 14, 2012

#multilingweb - #Arabic and #Hebrew are #RTL

Amir  asked me to ask at the Multilingual Web conference in conference to people like Richard Ishida:
"How hard would it be to allow assigning element directionality according to lang.  In HTML4 and in the current draft of HTML5, <span lang="ar"> has dir="ltr", unless specified otherwise, and I find it ridiculous". 
The usual replies Amir gets is:
  • Backwards compatibility
  • Many websites already use HTML-5 even though it is not a finished product. This will break them
His reply to this:
  • If a document explicitly specifies that it's HTML5, it should have directionality assignment by default.
  • Add an attribute to the root HTML tag, something like: <html dir="bylang"> or <html dirbylang="true">
Amir has aired his view before and an answer he gets from some "standards people" is: "It would be very problematic to do it, because most web developers don't use the lang attribute". This is rather funny because this will work only when the lang attribute is used.  And anyway at some point in time the public at large do not care really about previous versions of HTML as all the websites still in use will have moved on.

What we need is proper meta data for all languages and such data can hide very nicely inside a browser. Developers of websites do not know and want to know about all the linguistic niceties necessary to support a multi lingual web. It so many ways it makes sense to provide language support from inside the browser.

At the Wikimedia Foundation we we don't just support a lot of languages, we are also well aware of the languages we support. Ours is a world-wide community of people who have the opportunity to openly complain to us about bad support for their language and they expect that their complaint is actually read and is being taken care of.
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

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

#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


Sunday, September 25, 2011

#MediaWiki #RTL support when upgrading to 1.18

Amir is a Wikimedian and a linguist who quickly gained expertise on how to support RTL languages like Arabic and Hebrew. Not only did he add many bugs in bugzilla, he provided us with a lot of fixes as well. His latest project is supporting the upgrade for RTL to release 1.18. This contains RTL fixes by him and by SPQRobin.
Enjoy,
      GerardM

Administrators can thoroughly customize every MediaWiki based wiki by editing CSS and JS files, such as MediaWiki:Common.css, MediaWiki:Common.js, MediaWiki:Vector.css etc. These customizations are usually requested by the editors community and fall into two general categories. The first category are changes to the design of the site, such as setting a different background image, a festive logo, a different font or a different color for the revision comparison (diff). The other category works around bugs until they are solved in the core code.

Customizations may need to be updated by the local site admins specially after the deployment of a new version or MediaWiki or of a customized extension. Sometimes old customizations that worked around bugs just quietly stop working after the bug is resolved. They don't affect the site much, but they fill up Common.css with now useless code that makes maintenance much harder, so it is best to remove them. Sometimes changes in the software break the customizations and the site appears broken to the users - in this case they MUST be removed or updated.

MediaWiki 1.18 was rolled out to several wikis a few days ago. Among them was mediawiki.org, the website about the software itself. MediaWiki 1.18 has many updates for the handling right-to-left (RTL) text, especially on pages where it is mixed with left-to-right text. Before the upgrade mediawiki.org had several customizations to fix the display of RTL text in the tabs on the top of the page. After the upgrade this text appeared badly until they were removed.
 All the other Wikimedia wikis will be upgraded next. If you are an administrator in any Wikimedia wiki, you should look at these customization files as soon as possible and also at the release notes of MediaWiki 1.18. Understand the purpose of the existing customizations and be prepared to remove the ones that aren't needed anymore immediately after the upgrade. A general rule of thumb is to take an especially good look at lines that have "rtl", "ltr", "right", "left" and "bidi" in them.
If you need more help understanding these files, contact Amir Aharoni preferably on IRC.
--  Amir

Sunday, July 31, 2011

SPQRobin does #Haifa

Tomorrow I am travelling with Robin to #Wikimania. We are looking forward to meet our Wiki friends irl. We will have fun meeting new and old friends and we may see the sights of another beautiful city.
Thanks,
      GerardM

- Who is SPQRobin in real life

I am Robin Pepermans and I live in Flanders, the northern part of Belgium. I just finished my secondary education, having studied Latin and modern languages. My next studies will likely be Public Administration and/or Translation Studies in Ghent. I started editing the Dutch Wikipedia in 2006 under my username SPQRobin. At that time I was very interested in Roman history and the Roman Empire. Even though my interests quickly shifted, I remained known under this nickname since then.

- You are involved in multiple projects, what are they and what role do you play

As I become more active in the wiki world, I discovered Meta, Commons, and also the Incubator. It was a relatively new project, where new language editions of existing Wikimedia projects are developed and maintained until they are active enough to have their own sub-domain. Incubator was however not maintained well, so I improved it and helped the users there. A few more people joined me, and there is now a little group who maintains the Incubator. Not only was Incubator itself not maintained, the process to start a new wiki was often slow and people kept asking when their wiki would be created (sometimes with no response). To improve communication, I became a member of the language committee in 2009. This committee is in charge of deciding which Incubator wikis are ready for creation. Incubator, being a special wiki like Commons, required some software features that are not easily available in MediaWiki. Therefore I applied for commit access so I could create a MediaWiki extension that provides these features. It took quite some time for this extension to be enabled, maybe because Incubator is a lesser-known project and not a high priority. I am working further on this extension, for example the plan (that especially I and Milos Rancic are pushing forward) is to make subdomains of non-existing wikis (e.g. xmf.wiktionary.org and yua.wikipedia.org) redirect to the respective welcome pages or main pages at the Incubator, (xmf Wiktionary and yua Wikipedia).

- Lately you have worked on bugs that have to do with RTL languages like Hebrew and Arabic. Are these patches in production and what are these patches about

Recently I became more involved in fixing bugs and making the software better. It was clear that a lot of the interface and features had poor support for right-to-left languages, even though a lot of the RTL bugs are relatively easy to fix. You don't have to be able to read an RTL language to be able to fix them :-) I noticed that ResourceLoader included CSSJanus, which automatically flips CSS, making the software A LOT better and easier to maintain for RTL interface. Even the old bug 6100 (interface direction should follow user language and not content language) would be fixed. However, the content was flipped as well, so this was disabled. I fixed this issue, along with many others, and I generally improved the directionality support of MediaWiki. These improvements are now part of the upcoming MediaWiki 1.18, and will hopefully soon be deployed on Wikimedia wikis. You can already enjoy the improvements on e.g. translatewiki.net, which always runs the latest software. If you have any bug reports or suggestions regarding RTL interface, don't hesitate to contact me :-)


- You are going to your first Wikimania, what do you expect

I am really looking forward to my first Wikimania. I hope to see a lot of people who I know from Wikimedia in real life, and to meet other people as well. I am going to the developer days, where I will talk about my RTL work and improve it even further with other developers, especially for the issues that I am not able to fix myself :) I could also talk about the Incubator improvements that I am developing, such as the welcome pages for non-existing wikis.

Since Belgium, my country is one of the few Western countries without a chapter, I might talk with other Belgians and Dutch people about a possible Wikimedia Belgium or even a possible Wikimedia Benelux.

The sad thing is that the developer days coincide with the Global South Meeting and Chapters Meeting, which both seem to be very interesting.


New wikis in 2010
- How many more languages will we support in two years time

Currently we are growing quite slowly in my opinion. There are yearly some ten to twenty new wikis opened, most of which are in European languages. Sometimes there are promising projects organised, that want to help languages in the Global South to get their Wikipedia, but then I didn't hear of them anymore. My hope is that the chapters set up such projects. For example India, Indonesia and Australia are starting to become active in helping small languages get support and get their Wikimedia wikis. South America is less active but I hope they will join too.
 -Robin

Saturday, May 14, 2011

#MediaWiki has <ref>; but look at it in #Hebrew

The #mwhack11 is an important meeting to squash bugs. As the Language committee has its meeting and as there is a large group of translatewiki.net developers, there was a dedicated session on "right to left" issues.

Some five bugs were squashed. They were the known bugs, the bugs that were documented. There were bugs that had so far not been given the attention they deserve; one bug kills the wish to actually use references in a Wikipedia article.

When you do <ref> some source </ref> you will get another entry in this nice reference section at the end of the article.


You can find the complete <ref> tag in the screen shot. For your convenience, it has been highlighted in blue. From a usability point of view, it is atrocious. It is so bad that even Mr Michael Everson himself was shocked.

Now there is a bug for this issue and there is a chance that the Hebrew community will overcome their reluctance to include sources in their articles. One lesson learned is; there is a relation between localised technology and the quality of a Wikipedia.
Thanks,
        GerardM

Saturday, March 19, 2011

Our #bugmeister makes me happy

Bug 6100 - "Allow different directionality (rtl/ltr) for user interface and wiki content" is an old one. It goes back all the way to 2006. Many people commented over time and several issues mentioned have already been overcome.

By raising the priority of this bug to "highest" and "major", a clear signal is given by the Wikimedia Foundation that support for languages like Arabic, Farsi, Hebrew is important. Actions like this and the recent work on the implementation of Narayam demonstrate this support visibly.

Support was announced in words but these actions speak for themselves and empower the words with reality.
Thanks,
     GerardM

Sunday, February 14, 2010

#StatusNet in Arabic

The localisation of StatusNet is well under way in the Arabic language; with 62.46% of the messages localised. The Persian language is only slightly behind with 60.83% and Hebrew is also there but at 17.36%.


As you can see, there is some more work to be done; when the final localisations are in, when the text is properly in the right to left direction, StatusNet will be ready for deployment in these languages.
Thanks,
     GerardM

Sunday, April 29, 2007

Orientation of text

When you have a text, you write either in a right to left direction, like in Arab or Hebrew, or you write in a left to right direction, like in English or Russian. In OmegaWiki, we are going to support the orientation for right to left once Multilingual MediaWiki is integrated in our software.

I have given SignWriting a lot of thought lately. This is a script that goes top to bottom. What I just realised is, that as as consequence a left to right word mixed into such an environment would also go top to bottom. It makes however as much sense to have a right to left word also go in the same direction.

The problem is that when you have both RTL and LTR in a top down environment, it will seem odd.

Thanks,
GerardM