Mediawiki-i18n June 2013

mediawiki-i18n@lists.wikimedia.org

10 participants
10 discussions

MediaWiki Language Extension Bundle launches
by Niklas Laxström 09 Feb '23

09 Feb '23

The Wikimedia Language Engineering team is pleased to announce the first release of the MediaWiki Language Extension Bundle. The bundle is a collection of selected MediaWiki extensions needed by any wiki which desires to be multilingual. This first bundle release (2012.11) is compatible with MediaWiki 1.19, 1.20 and 1.21alpha. Get it from https://www.mediawiki.org/wiki/MLEB The Universal Language Selector is a must have, because it provides an essential functionality for any user regardless on the number of languages he/she speaks: language selection, font support for displaying scripts badly supported by operating systems and input methods for typing languages that don't use Latin (a-z) alphabet. Maintaining multilingual content in a wiki is a mess without the Translate extension, which is used by Wikimedia, KDE and translatewiki.net, where hundreds of pieces of documentation and interface translations are updated every day; with Localisation Update your users will always have the latest translations freshly out of the oven. The Clean Changes extension keeps your recent changes page uncluttered from translation activity and other distractions. Don't miss the chance to practice your rusty language skills and use the Babel extension to mark the languages you speak and to find other speakers of the same language in your wiki. And finally the cldr extension is a database of language and country translations. We are aiming to make new releases every month, so that you can easily stay on the cutting edge with the constantly improving language support. The bundle comes with clear installation and upgrade installations. The bundle is tested against MediaWiki release versions, so you can avoid most of the temporary breaks that would happen if you were using the latest development versions instead. Because this is our first release, there can be some rough edges. Please provide us a lot of feedback so that we can improve for the next release. -Niklas -- Niklas Laxström

3 3

Report on WebFonts deployment
by Siebrand Mazeland (WMF) 20 Jan '14

20 Jan '14

Dear all, My apologies up front for the long e-mail that follows. In this e-mail you will find a comprehensive status overview of the recent WebFonts deployment. On Monday December 12 at 18:00 UTC we deployed the extension WebFonts[1] to 40 wikis in 11 Indic languages and Wikimedia Incubator -- all wikis in Assamese, Bengali, Gujarati, Hindi, Kannada, Marathi, Nepali, Oriya, (Eastern) Punjabi, Sankrit and Telugu have WebFonts now. WebFonts was not deployed on Malayalam and Tamil projects. The reason for this was that community members had requested us not to. We are confident that in time, the communities will request that WebFonts is enabled on their projects. WebFonts aims to resolve the issue that users see incomplete web pages, because the fonts to properly render the page is not present in the local system by downloading the font through the browser. One of our great challenges developing this functionality is the multitude of scripts and the low availability of freely licensed fonts that may be modified and redistributed. Over the past few months we have tried to build out a collection of fonts in the extension mainly for Indic languages, and we have performed many tests. We have solicited community involvement through messaging in village pumps, e-mails on mailing lists, blog posts on personal blogs as well as on the Wikimedia Foundation blog, at developer events, through personal e-mails and through our bug tracker, and gotten some feedback, although unfortunately not for all the languages we would like to have gotten it for. We will of course continue our efforts in this area. Next to the community involvement, we have had a two day session with the Red Hat Localisation team in Pune, India. Since the deployment, we have been criticised for not communicating enough -- or not through the right channels, not with the right people, not in time, or too soon, or not with the right messages. I'm not really sure how to respond to that, except for uttering a general "mea culpa, mea maxima culpa". We are working really hard in continuously improving the work that we do, and the way that we do it. We make mistakes, we are human after all, and when we become aware of our mistakes, we will do everything in our power to make it better. With our team we support the mission of the Wikimedia Foundation to "imagine a world in which every single human being can freely share in the sum of all knowledge." I care about that -- a lot. We all care, and I am pretty certain that we're not ignorant, dismissive or incapable. I acknowledge that we as the Localisation team are a relatively new entity within the MediaWiki development community and within the Wikimedia Foundation, with a very wide scope, and that we are dealing with a lot of technical details on which we are simply not able to assess the final quality; there are after all 7.500 languages in this world of over 7 billion people that we theoretically all cover, some 350 of those languages are supported in MediaWiki, and 280 within Wikimedia. I accept that we cannot keep everybody happy -- doesn't keep us from trying, though. I want to try and work with as many people as possible in a constructive way. With these numbers, that's not always easy to coordinate. To channel the input on languages, we have set up "Language Support Teams"[2]. We do not yet have a language support team for every language. Please sign up if you care about the technical facilitation of your language in the Wikimedia movement. Let's use the mediawiki-i18n mailing list[3] to have constructive discussions about language support. Let's use the #mediawiki-i18n IRC channel[4] on Freenode to have real-time discussions. Let's use bugzilla.wikimedia.org to report bugs[5]. Link [5] explains the bug reporting procedure. If you already know how, report issues quickly using this link: http://ur1.ca/6ov9a . Since the deployment, we have been made aware of about 17 issues. Some very serious in nature, others not requiring immediate attention. Yesterday an issue with web fonts not loading in Firefox was resolved in the infrastructure. Today around 15:30 UTC, we have deployed fixes for an additional hand full of issues[6]: functionality disabled in IE6, IE8 on Windows XP, selection buttons not working properly in IE7 and hiding the Samyak fonts in the font selector. During our current sprint, we are working on a framework for multi-lingual and localised user documentation as well as feature based feedback functionality for WebFonts, Narayam and Translate. In the future we will also explore what is known as "dark launch" by some, a kind of hidden live deployment of a feature, only usable be for example manipulating a URL. This would allow us to deploy a feature in a live environment, without having the "full deployment" impact. Thanks for reading through this. I am looking forward to working with you! Please read on for details on all the issues that were reported on WebFonts recently. Cheers! Siebrand Mazeland Product Manager Localisation Wikimedia Foundation ======================================= Links ======================================= [1] https://www.mediawiki.org/wiki/Extension:WebFonts [2] https://translatewiki.net/wiki/Language_support_team [3] https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n [4] https://translatewiki.net/wiki/Special:WebChat [5] https://www.mediawiki.org/wiki/Bugzilla [6] https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106204 ======================================= Open issues ======================================= https://bugzilla.wikimedia.org/33004 -- Old cached pages do not have web fonts enabled Priority: HIGH -------------------------------------------------------------------------------------- Wikimedia is able to serve this many pages with relative few servers because of very aggressive caching strategies, especially for anonymous users. WebFonts requires the addition of JavaScript for anonymous users, which is not being done for pages that are in the squid cache at the moment WebFonts was enabled. All squid cache objects for wikis on which WebFonts was deployed need to be purged. An internal RT ticket created for the Wikimedia Operations team to get anonymous squid caches purged. This may take up to a week or longer to be resolved. https://bugzilla.wikimedia.org/33018 -- Firefox 5 on Windows XP has script time-outs Priority: MEDIUM -------------------------------------------------------------------------------------- The Localisation team has tested this report, and was not yet able to confirm the observation. The reason for using a non-recent version of Firefox for the report was the alleged lower memory usage. Brion noted that Mozilla has been actively working on lowering memory usage over the last year, so the reporter may be better off with the current versions than the old ones. https://bugzilla.wikimedia.org/33110 -- Google Crome on Windows XP dispays gibberish Priority: LOW -------------------------------------------------------------------------------------- Observed very rarely on a page on Wikimedia Incubator, and we have not been able to reproduce this observation, let alone reproduce it reliably. A screenshot is present in the bug report. Except for reporting upstream, no action is being taken on this issue at this point in time. https://bugzilla.wikimedia.org/33054 -- Hinting issues in Lohit fonts Priority: MEDIUM -------------------------------------------------------------------------------------- Confirmed in Windows XP. We can do something to the font by adding hinting, but this is a lot of work if it needs to be done manually. The stem of the Lohit glyphs could do with more width and darkness. This may not be desirable for platforms (Linux) which render it perfectly, because it already has hinting and anti-aliasing on an operating system level. Same goes got Windows 7. https://bugzilla.wikimedia.org/33100 -- Page crashes on Webkit browsers with WebFonts enabled. Priority: MEDIUM (could be HIGH if we find many occurances) -------------------------------------------------------------------------------------- A page in Nepali Wikipedia makes a tab on Mac OS X 10.7.2 with Google Crome crash. This behaviour was also reported for Mac OS X 10.7.2 (11C74) with Safari 5.1.1 (7534.51.22, r102522) [This is a webkit nightly build] by thedj. This is most probably related to the WebFonts code, because if, as a logged in user, web fonts is disabled in preferences, the page does not crash Chrome. Developer Derk-Jan Hartman was asked to report this bug in the WebKit. Please make us aware of any additional pages that would cause this behaviour in any wiki. https://bugzilla.wikimedia.org/33102 -- OSX 10.7.2/Opera 11.60 has no fallback for Latin characters Priority: MEDIUM -------------------------------------------------------------------------------------- This is a bug that needs to be reported upstream. No technical measures have been taken so far to mitigate this issue. One of the Localisation team members has been in contact with a high level executive of Opera, and will contact that person again. We're going to wait for a few days for an outcome -- if there is no expectation of a relatively quick fix, we might disable WebFonts for Opera completely. Opera unfortunately does not have a public bug tracker. https://bugzilla.wikimedia.org/33027 -- Narayam and WebFonts both loading slows down page Priority: MEDIUM -------------------------------------------------------------------------------------- The reporter claims that the functionality is quicker on translatewiki.netthan it is in Wikimedia wikis. A commenter states that more functionality usually means more code, means more data that needs to be transferred, and without changing bandwidth, that causes longer load times. This currently isn't our highest priority, but eventually we will look into this a little deeper. We're inviting volunteers to do some of the data gathering and analysis for us. What is needed in our opinion is insight in the data volume added by WebFonts, as well as an assessment of the code quality with regards to size optimisation. All referenced properly, of course :). There are alternate EOT conversion tools that have a good compression ratio. Needs to be explored, but EOT is not required for modern browsers since they started using WOFF fonts which are compressed OpenType fonts. https://bugzilla.wikimedia.org/33085 -- Integration of updated Lohit-Tamil Font Priority: MEDIUM -------------------------------------------------------------------------------------- Request to update WebFonts with a font that is updated upstream. This is something the Localisation team checks regularly. Will probably be closed this week, pending issues the have a higher priority. https://bugzilla.wikimedia.org/32942 -- Provide help page and bug report link for WebFonts Priority: HIGH -------------------------------------------------------------------------------------- More recently developed tools by the Wikimedia Foundation have often included feedback mechanisms. The Localisation team plans on implementing these for the functionality of the WebFonts, Narayam and Translate extension. Besides that, we also want to provide multi-lingual and localised documentation. This needs some thinking and some work to provide in a structured and navigable way. We'll keep you posted. It will most probably involve translatable *user* documentation on MediaWiki.org and hopefully it is possible to have one feedback location per feature across the multiple Wikimedia wikis -- this is something we're going to contact the ArticleFeedback and MoodBar teams for. ======================================= Closed issues ======================================= https://bugzilla.wikimedia.org/33025 -- When changing to a non-default web font, the content does not -------------------------------------------------------------------------------------- This issue was a side effect of a feature to allow multiple web fonts to be used using the "lang" attribute. It was resolved in https://www.mediawiki.org/wiki/Special:Code/MediaWiki/105980 and has been deployed. https://bugzilla.wikimedia.org/33034 -- Web fonts not loading in Firefox -------------------------------------------------------------------------------------- Duplicate reports were 33038 and 33044. This issue originated from http://www.w3.org/TR/css3-fonts/#same-origin-restriction. Almost all browsers except for Firefox ignore that specification. A fix was designed and deployed: https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106092, https://gerrit.wikimedia.org/r/1501. Thanks to Roan, Brion and Ryan for their help. https://bugzilla.wikimedia.org/32775 -- Gibberish in Internet Explorer 8 on Windows XP -------------------------------------------------------------------------------------- This is an unexplained phenomenon only observed in Internet Explorer on Windows XP. It is also hard to reproduce. One of the developers was able to make something somewhat reproducible on a clean, fully patched installation of Windows XP with Internet Explorer 8. See bug report for details. Based on these observations we think it is a bad idea to keep supporting WebFonts in Internet Explorer 8 on Windows XP and we have disabled it in https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106172. This fix has been deployed. https://bugzilla.wikimedia.org/33096 -- Internet Explorer 6 does not have font fallback -------------------------------------------------------------------------------------- IE6 not having font fallback causes Latin characters to display as squares when a web font is loaded that does not contain glyphs for the Latin script. A screenshot is available at http://media.crossbrowsertesting.com/users/34057/screenshots/window/z669002…. Based on this observation, we think it is a bad idea to keep supporting WebFonts in Internet Explorer 6 and we have disabled it in https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106172. This fix has been deployed. https://bugzilla.wikimedia.org/33024 -- WebFonts menu buttons not working in IE7 -------------------------------------------------------------------------------------- This was caused by the JavaScript $( '<input type="radio" />' ) . attr( "name" ,"font"); not working in IE6 and IE7. Updating name attributes once they have been created is not possible. We think there may be more occurances of this in our code (one occurance in jQuery has already been identified: resources/jquery/jquery.validate.js:59). A fix was made in https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106175. This fix has been deployed. https://bugzilla.wikimedia.org/33040 -- Overlap in Samyak font for Hindi and Sanskrit -------------------------------------------------------------------------------------- This issue occurs in Windows XP and Windows 7 (possibly also in Windows Vista) when using Google Chrome. It is not observed when using Chrome with Mac OS X 10.7.2 or several Linux distributions (Debian and Fedora). Samyak Devanagari is available as a non-default web font in Hindi, Marathi, and Sanskrit. Samyak Gujarati is available for Gujarati as a non-default font. This font needs to be corrected. The maintainers will be notified of the observed issues, and mean while, the fonts will be removed from the WebFonts selection list (but can still be used using the font-family property. A fix was made in https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106179. This fix has been deployed. https://bugzilla.wikimedia.org/33039 -- Overlap in Madan font for Nepali -------------------------------------------------------------------------------------- This report was invalid. The reporter was not aware of the correct glyph for the Nepali script. Comments on this bug report resulted in two odd observations (Crome crash, Opera font fallback), that have been split off into separate bug reports: https://bugzilla.wikimedia.org/33100 and https://bugzilla.wikimedia.org/33102. https://bugzilla.wikimedia.org/33095 -- WebFonts menu can expand off the screen -------------------------------------------------------------------------------------- If the translations for "Select font" and "Login / Register" are really short, like in http://mr.wiktionary.org, expanding the WebFonts menu for anonymous users will display a menu that is partially off the screen. It was resolved in http://www.mediawiki.org/wiki/Special:Code/MediaWiki/106186, http://www.mediawiki.org/wiki/Special:Code/MediaWiki/106197, http://www.mediawiki.org/wiki/Special:Code/MediaWiki/106201, http://www.mediawiki.org/wiki/Special:Code/MediaWiki/106202. These revisions also depend on a few small UI changes of both WebFonts and Narayam, and will be deployed on December 19, 2011. <no bugzilla report> -- WebFonts menu expands under the control for customised input method in IE6 on transliteration -------------------------------------------------------------------------------------- There are issues with the z index in IE6. Because of https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106172, WebFonts is no longer available in IE6, so this issue is obsolete. Observing that the Hindi projects Wikipedia and Wiktionary are using an custom input methods tool, we would like to invite them to test Narayam which contains many input methods in a MediaWiki extension. We are very open to having the Hindi input method InScript tested and add a transliteration input method with some community representatives, as we have done with other Indic languages. We hope this will eventually lead to Narayam being adopted by the Hindi community, and the custom input method being abandoned.

8 8

Making inter-language links shorter
by Pau Giner 04 Sep '13

04 Sep '13

As multilingual content grows, interlanguage links become longer on Wikipedia articles. Articles such as "Barak Obama" or "Sun" have more than 200 links, and that becomes a problem for users that often switch among several languages. As part of the future plans for the Universal Language Selector, we were considering to: - Show only a short list of the relevant languages for the user based on geo-IP, previous choices and browser settings of the current user. The language the users are looking for will be there most of the times. - Include a "more" option to access the rest of the languages for which the content exists with an indicator of the number of languages. - Provide a list of the rest of the languages that users can easily scan (grouped by script and region ao that alphabetical ordering is possible), and search (allowing users to search a language name in another language, using ISO codes or even making typos). I have created a prototype <http://pauginer.github.io/prototype-uls/#lisa> to illustrate the idea. Since this is not connected to the MediaWiki backend, it lacks the advanced capabilities commented above but you can get the idea. If you are interested in the missing parts, you can check the flexible search and the list of likely languages ("common languages" section) on the language selector used at http://translatewiki.net/ which is connected to MediaWiki backend. As part of the testing process for the ULS language settings, I included a task to test also the compact interlanguage designs. Users seem to understand their use (view recording<https://www.usertesting.com/highlight_reels/qPYxPW1aRi1UazTMFreR>), but I wanted to get some feedback for changes affecting such an important element. Please let me know if you see any possible concern with this approach. Thanks -- Pau Giner Interaction Designer Wikimedia Foundation

11 15

MediaWiki Language Extension Bundle 2013.06 release‏‏
by Amir E. Aharoni 29 Jun '13

29 Jun '13

Hallo, I would like to announce the release of MediaWiki language extension bundle 2013.06. * https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.06.tar… * sha256sum: 6df32382ddec91ab61e3e74f2ede6c043220d5c1252ee3baf8efd1d6403b4d82 Quick links: * Installation instructions are at https://www.mediawiki.org/wiki/MLEB * Announcements of new releases will be posted to a mailing list: https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n * Report bugs to https://bugzilla.wikimedia.org * Talk with us at #mediawiki-i18n @ freenode Release notes for each extension are below. Amir E. Aharoni == Babel == Only localization updates. == cldr == Initial support for CLDR currency was added. == CleanChanges == Only localization updates. == LocalisationUpdate == The default values for $wgLocalisationUpdateCoreURL and $wgLocalisationUpdateExtensionURL were changed to point to Wikimedia's new Git repo server https://git.wikimedia.org . == Translate == * The option to hide the MediaWiki sidebar while translating was added * Translations identical to the current translation are not suggested any more from translation memory * Suggestion in the source language is no more shown in the "in other languages" section * Edit section links are not shown anymore for translation pages * Only local files can now be upload using Special:ImportTranslations * Groups that are not marked as a priority for the current language are not shown in Special:LanguageStats == UniversalLanguageSelector == == Highlights == The feature of showing the ULS trigger as a cog icon in the sidebar was completed. Many other bugs were fixed. Internet Explorer 6 and 7 (and newer if they are in compatibility mode) are explicitly not supported. == Notable feature changes == * ULS is completely disabled in browsers that don't run JavaScript. * Several bugs in the font and language selection panels were fixed. * The functionality of the Cancel and Apply buttons in the keyboard selection panel were clarified: Apply saves the settings and closes the panel and Cancel undoes the changes. * The wiki content language is now the default language for input methods * Bugs in several input methods were fixed. == Font changes == * Added: UnifrakturMaguntia, Linux Libertine, Charis SIL, Doulos SIL * Lohit Tamil is updated to 2.5.3 * System font is now the default font for Tamil == Notable design changes == * Button style is updated according to the MediaWiki Agora style. * Smooth scrolling is used on every change in display. * A floating tooltip ("Tipsy") in used on the "Language settings" trigger

1 0

Shrinking level of MediaWiki extensions localisation
by Federico Leva (Nemo) 25 Jun '13

25 Jun '13

Most of our messages are in MediaWiki extensions. I checked the localisation stats as of now and two years ago for the extensions used on Wikimedia projects: many languages are lagging behind development, with only 14 over 90 % translated (was 40) and 22 over 80 % (was 52).* Do we need more recruitment? Some examples of affected languages: Russian went from 100 % to 80 % messages translated, pl 98 -> 80, pt 100 -> 64, hu 94 -> 67, nb 94 -> 72, cs 93 -> 77, ar 92 -> 64. Nemo (*) <https://translatewiki.net/w/i.php?title=Translating:Group_statistics&oldid=…>, sort by 3rd column <https://translatewiki.net/w/i.php?title=Translating:Group_statistics&oldid=…>, sort by 4th

2 2

removing messages from core
by S Page 20 Jun '13

20 Jun '13

https://gerrit.wikimedia.org/r/#/c/67233/ remotes the old-style login and create account forms from core. The new forms have different messages, e.g. no more colons in English labels and there's no more use of the combined "Log in / create account". So I removed the old messages from MessagesEn.php, MessagesQqq.php and messages.inc. Raimond pointed out that the 'userlogin' message is still used by the OpenID extension. Maybe more of these very old messages are used by other extensions.Needs investigation, partly revert recommended in the meantime. Good point, it's also used by MobileFrontEnd (!), I'll submit a patch restoring this message and ask on the i18n mailing list for guidance. FWIW mw.org's I18n page and Manual:System_message#Creating_new_messages don't say anything about extensions reusing core messages. I think they should caution extension writers about relying on messages in core, and instead define their own messages with a {{same}} template in Qqq. Or we need to somehow identify "reliable" or "deprecated" messages in core. -- =S Page software engineer on E3

3 3

Why why /** Message documentation (Message documentation)?
by S Page 17 Jun '13

17 Jun '13

Almost every extension's i18n.php file has /** Message documentation (Message documentation) * @author Some Person */ $messages['qqq'] = array( ... Why repeat it? Is it because the header for each language section is "/** French (français)" , so Qqq is being consistent? But the English header is just /** English. Does some undocumented tool in maintenance/language rely on the format of these headings? Thanks for any insight. -- =S Page software engineer on Editor Engagement Experiments

2 3

Language Engineering office hour on 2013-06-12 at 17:00 UTC/10:00 PDT
by Siebrand Mazeland (WMF) 12 Jun '13

12 Jun '13

Event Details # Date: 2013-06-12 # Time: 1700-1800 UTC, 1000-1100 PDT #IRC channel: #wikimedia-office on irc.freenode.net The Wikimedia Language Engineering team [1] invites everyone to join the team’s monthly office hour on June 12, 2013 (Wednesday) at 1700 UTC/1000 PDT in #wikimedia-office. During this session we would be talking about some our recent activities and updates from the ongoing projects. The provisional agenda is outlined below. See you all at the IRC office hour! Siebrand Mazeland Product Manager Language Engineering Wikimedia Foundation Agenda # Introductions # Universal Language Selector - Phase 1 deployment was on Tuesday 2013-06-11 [2,3,4] # Universal Language Selector - Phase 2 and later # Q/A - We shall be taking questions during the session. Questions can also be sent to "siebrand at wikimedia dot org" before the event, and will be addressed during the office hour. [1] http://wikimediafoundation.org/wiki/Language_Engineering_team [2] https://www.mediawiki.org/wiki/Universal_Language_Selector [3] https://www.mediawiki.org/wiki/Universal_Language_Selector/FAQ [4] https://www.mediawiki.org/wiki/Universal_Language_Selector/Design

1 1

Pre-releasing translatewiki.net iOS App
by Or Sagi 11 Jun '13

11 Jun '13

Hi Everyone, We are working on a mobile application for translatewiki.net, as a part of our BSc final project in the Tel-Aviv Uni. We try to do our best effort to make the perfectly handy, simple and professional way to use translatewiki.net on the go. We are super close to launch it publicly to the iOS app store. If you have an iOS device (iphone, iPod or iPad), you are invited to be among the first to see and test it, via "TestFlight". click this invitation<http://tflig.ht/17EJVFz> and you'll be approved. You can also find our project on Github<https://github.com/orsa/TranslateWikiApp-iOS> . Please send us your feedback. Thanks, Tomer T. Or S.

1 0

[X-POST] Universal Language Selector(ULS) Deployment - Phase 1
by Runa Bhattacharjee 06 Jun '13

06 Jun '13

Hello, The Universal Language Selector (ULS)[1] provides a flexible way to configure and deliver language settings like interface language, fonts, and input methods (keyboard mappings). It combines the features of two earlier Mediawiki extensions Narayam[2] and WebFonts[3]. From June 11, 2013 on, ULS will be made available to all Wikimedia wikis in 5 phases[4]. # Phase 1: In the first phase, ULS will replace the Narayam and WebFonts extensions on 84 wikis[5]. User preferences from the replaced extensions will not be preserved. Affected communities will be informed by the Wikimedia Language Engineering team of the upcoming change. # Phase 2: In the 5 weeks that follow, ULS will be deployed on Wikipedias in size 11-20, # Phase 3: All projects without language versions # Phase 4: English language Wikipedia # Phase 5: All other wikis The ULS can be visible in two ways: 1. In the sidebar for wikis with language versions, like Wikipedia, or 2. In the personal toolbar at the top of wiki pages for wikis without language versions, like Wikimedia Commons and Meta-Wiki. Based on the geographic location of users, the initial set of language preferences is presented. Users can set the input methods and fonts to that they want to use. Logged-in users can also change the language for the MediaWiki menu items. ULS is already available on several Wikimedia wikis like Wikimedia Commons[6] and Meta-Wiki[7]. The beta installation of English Wikipedia on Wikimedia Labs[8] shows what will be available as the look and feel. A cog icon is present in the “Languages” section of the sidebar menu. Clicking the cog icon opens the Language settings panel that can be used to set the display and input settings. Please have a look at the Universal Language Selector feature description[9] or the Frequently Asked Questions[10] for more detailed information. Thank you. regards Runa [1] https://www.mediawiki.org/wiki/Extension:UniversalLanguageSelector [2] https://www.mediawiki.org/wiki/Extension:Narayam [3] https://www.mediawiki.org/wiki/Extension:WebFonts [4] https://www.mediawiki.org/wiki/UniversalLanguageSelector/Deployment/Planning [5] https://www.mediawiki.org/wiki/UniversalLanguageSelector/Deployment/Plannin… [6] https://commons.wikimedia.org/wiki/ [7] https://meta.wikimedia.org/wiki/Main_Page [8] http://en.wikipedia.beta.wmflabs.org/ [9] https://www.mediawiki.org/wiki/Universal_Language_Selector [10] https://www.mediawiki.org/wiki/Universal_Language_Selector/FAQ -- Language Engineering - Outreach and QA Coordinator Wikimedia Foundation https://meta.wikimedia.org/wiki/User:Runab_WMF

5 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Mediawiki-i18n June 2013