<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: State of the language selection in MediaWiki and Wikipedia</title>
	<atom:link href="http://www.gpaumier.org/blog/633_state-of-language-selection-mediawiki-wikipedia/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gpaumier.org/blog/633_state-of-language-selection-mediawiki-wikipedia/</link>
	<description>open knowledge, design &#38; technology</description>
	<lastBuildDate>Wed, 16 Mar 2011 20:05:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Henk van Deelen (HenkvD)</title>
		<link>http://www.gpaumier.org/blog/633_state-of-language-selection-mediawiki-wikipedia/comment-page-1/#comment-6182</link>
		<dc:creator>Henk van Deelen (HenkvD)</dc:creator>
		<pubDate>Sun, 27 Jun 2010 08:59:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.gpaumier.org/blog/?p=633#comment-6182</guid>
		<description>I compliment on the nice overview.

Regarding &quot;Autotranslate&quot; it should be mentioned that it uses Fallback languages instead of just one default language. 

See the list at http://strategy.wikimedia.org/wiki/Template:GetFallback. 

For instance if the user language is af (Afrikaans) the /af subpage will be displayed if it exists. The fallback language is nl (Nederlands). If the /nl subpage does not exist the defaul language page (English) will be displayed. 

An other example would be any of the chinese languages that will fallback to zh.</description>
		<content:encoded><![CDATA[<p>I compliment on the nice overview.</p>
<p>Regarding &#8220;Autotranslate&#8221; it should be mentioned that it uses Fallback languages instead of just one default language. </p>
<p>See the list at <a href="http://strategy.wikimedia.org/wiki/Template:GetFallback" rel="nofollow">http://strategy.wikimedia.org/wiki/Template:GetFallback</a>. </p>
<p>For instance if the user language is af (Afrikaans) the /af subpage will be displayed if it exists. The fallback language is nl (Nederlands). If the /nl subpage does not exist the defaul language page (English) will be displayed. </p>
<p>An other example would be any of the chinese languages that will fallback to zh.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean-Fred</title>
		<link>http://www.gpaumier.org/blog/633_state-of-language-selection-mediawiki-wikipedia/comment-page-1/#comment-6181</link>
		<dc:creator>Jean-Fred</dc:creator>
		<pubDate>Sun, 27 Jun 2010 00:34:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.gpaumier.org/blog/?p=633#comment-6181</guid>
		<description>Though {{Multilingual description}} is indeed scarcely used on Commons, its behaviour could easily be massively deployed by adding two lines to {{Information}}.

(Absolutely no idea of the impacts of such a modification, though :-)</description>
		<content:encoded><![CDATA[<p>Though {{Multilingual description}} is indeed scarcely used on Commons, its behaviour could easily be massively deployed by adding two lines to {{Information}}.</p>
<p>(Absolutely no idea of the impacts of such a modification, though :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guillaume Paumier</title>
		<link>http://www.gpaumier.org/blog/633_state-of-language-selection-mediawiki-wikipedia/comment-page-1/#comment-6180</link>
		<dc:creator>Guillaume Paumier</dc:creator>
		<pubDate>Sat, 26 Jun 2010 17:46:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.gpaumier.org/blog/?p=633#comment-6180</guid>
		<description>Hi Siebrand. I didn’t address the RTL support because my article was specifically about language &lt;em&gt;selection&lt;/em&gt;, and not a general article about language &lt;em&gt;support&lt;/em&gt;. But you’re totally right that MediaWiki isn’t RTL-friendly enough. I experienced the very example you took (trying to add a wiki link inside brackets) a few times when I tried to illustrate articles on the Hebrew or Arabic Wikipedia with pictures from Commons. It was extremely confusing.</description>
		<content:encoded><![CDATA[<p>Hi Siebrand. I didn’t address the RTL support because my article was specifically about language <em>selection</em>, and not a general article about language <em>support</em>. But you’re totally right that MediaWiki isn’t RTL-friendly enough. I experienced the very example you took (trying to add a wiki link inside brackets) a few times when I tried to illustrate articles on the Hebrew or Arabic Wikipedia with pictures from Commons. It was extremely confusing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Siebrand Mazeland</title>
		<link>http://www.gpaumier.org/blog/633_state-of-language-selection-mediawiki-wikipedia/comment-page-1/#comment-6175</link>
		<dc:creator>Siebrand Mazeland</dc:creator>
		<pubDate>Sat, 26 Jun 2010 10:43:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.gpaumier.org/blog/?p=633#comment-6175</guid>
		<description>Nice overview, Guillaume. One issue - major as far as I&#039;m concerned - that you have left unaddressed, is language directionality of the user interface, compared to language directionality of the content.

Even with the &#039;uselang&#039; parameter, this is not resolved. Nice examples are the main pages of the Arabic[1] and Hebrew[2] Wikipedias with an English user interface. You can imagine that navigating &#039;&#039;our&#039;&#039; Western Europan language wikis is like hell to everyone who is used to reading Right to Left, instead of Left to Right. A fun example is the behaviour of the inline text editor. Try to add a wiki link inside brackets ([[link]]) while looking at the text entry screen :).

Not addressing this issue in this context, too, means in my opinion that the gap between left to right and right to left languages increases, in turn decreasing chances of Wikimedia playing a major part in the internet future of the countries where the affected languages are used.

[1] &lt;a href=&quot;http://ar.wikipedia.org/wiki/%D8%A7%D9%84%D8%B5%D9%81%D8%AD%D8%A9_%D8%A7%D9%84%D8%B1%D8%A6%D9%8A%D8%B3%D9%8A%D8%A9?uselang=en&quot; rel=&quot;nofollow&quot;&gt;Arabic Wikipedia main page with English uses Interface&lt;/a&gt;
[2] [1] &lt;a href=&quot;http://he.wikipedia.org/wiki/%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99?uselang=en&quot; rel=&quot;nofollow&quot;&gt;Hebrew Wikipedia main page with English user interface&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Nice overview, Guillaume. One issue &#8211; major as far as I&#8217;m concerned &#8211; that you have left unaddressed, is language directionality of the user interface, compared to language directionality of the content.</p>
<p>Even with the &#8216;uselang&#8217; parameter, this is not resolved. Nice examples are the main pages of the Arabic[1] and Hebrew[2] Wikipedias with an English user interface. You can imagine that navigating &#8221;our&#8221; Western Europan language wikis is like hell to everyone who is used to reading Right to Left, instead of Left to Right. A fun example is the behaviour of the inline text editor. Try to add a wiki link inside brackets ([[link]]) while looking at the text entry screen :).</p>
<p>Not addressing this issue in this context, too, means in my opinion that the gap between left to right and right to left languages increases, in turn decreasing chances of Wikimedia playing a major part in the internet future of the countries where the affected languages are used.</p>
<p>[1] <a href="http://ar.wikipedia.org/wiki/%D8%A7%D9%84%D8%B5%D9%81%D8%AD%D8%A9_%D8%A7%D9%84%D8%B1%D8%A6%D9%8A%D8%B3%D9%8A%D8%A9?uselang=en" rel="nofollow">Arabic Wikipedia main page with English uses Interface</a><br />
[2] [1] <a href="http://he.wikipedia.org/wiki/%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99?uselang=en" rel="nofollow">Hebrew Wikipedia main page with English user interface</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
