Mediawiki-i18n

mediawiki-i18n@lists.wikimedia.org

568 discussions

I18n deployment 2012-04-02
by Niklas Laxstrom 31 Mar '12

31 Mar '12

The next i18n deployment is on Monday 2012-04-02 17-18 UTC. * Enable WebFonts in fr.wikisource.org - https://bugzilla.wikimedia.org/35328 * Possibly enable Narayam at hi.wikipedia.org -https://bugzilla.wikimedia.org/35436 Many language names were changed: https://gerrit.wikimedia.org/r/#change,3805 - Fix language names in Names.php * ab - suggested at ab.wikipedia.org village pump. * bug - improved the name. * ike-latn - capitalized the Latin name. * inh - only the Cyrillic name is needed. * ks - consistent slash usage. * pi - fixed the native name according to the Wikipedia article and dictionaries * tg-latn - capitalized the Latin name. * tly - capitalized the Cyrillic name. * ug-latn - removed unneeded LRM. * uz - fixed the apostrophe. * vep - fixed the apostrophe. We also have group of character additions and fixes to WikiEditor's character insertion tool in the queue. They will be scheduled for deployment when they have been reviewed. * https://gerrit.wikimedia.org/r/#change,3681 - [WikiEditor] Fixes for Arabic: Added ZWNJ and ZWJ according to request at bug 30611. Split special characters from digits. * https://gerrit.wikimedia.org/r/#change,3684 - [WikiEditor] Grouped Hebrew characters and added comments. Added required punctuation characters. * https://gerrit.wikimedia.org/r/#change,3901 - [WikiEditor] RTL fix for special characters insertion links. * https://gerrit.wikimedia.org/r/#change,3902 - [WikiEditor] Moved character 25cc (dotted circle) before the diacritic. * https://gerrit.wikimedia.org/r/#change,3907 - [WikiEditor] Adding pretty quotation marks for Hebrew. -Niklas

2 1

Changing MediaWiki namespaces and testing the new CLDR user interface
by Gerard Meijssen 25 Mar '12

25 Mar '12

Hoi, There are two things I want to raise in this mail: MediaWiki namespaces and the new user interface of the CLDR. Both are extremely relevant because both influence the behaviour of the MediaWiki software. Both have a tendency to take a long time before the effect of changes become available. It is therefore important to us to give this proper attention and inform you about this. *MediaWiki namespaces* the Wikimedia developers are transitioning to a different code repository system. They are changing from SVN to GIT. As one of the results a lot of things are getting reviewed. Included is a list of changes that will change the names of MediaWiki namespaces. As you may know changing namespaces is different from changing MediaWiki messages as it is a change in the configuration of the software. It is one of those things that is done with a lot of care. The objective of pointing this out is two-fold. When one of the languages below is the language you champion, we do want you to verify it and let us know if this is what is agreed upon by your community. For some languages this may be problematic as they are working towards their first project. The second point is that you may want to have a look at the localisation of the namespaces. Possibly they need changing, possibly they still need to be done. Of relevance is that we do support gender for namespaces it is possible to indicate both male and female users. <https://gerrit.wikimedia.org/r/#patch,sidebyside,3318,1,/COMMIT_MSG> languages/messages/MessagesFrp.php<https://gerrit.wikimedia.org/r/#patch,sidebyside,3318,1,languages/messages/…> - Franco-Provençal languages/messages/MessagesIg.php<https://gerrit.wikimedia.org/r/#patch,sidebyside,3318,1,languages/messages/…> - Igbo languages/messages/MessagesMk.php<https://gerrit.wikimedia.org/r/#patch,sidebyside,3318,1,languages/messages/…> - Macedonian languages/messages/MessagesMzn.php<https://gerrit.wikimedia.org/r/#patch,sidebyside,3318,1,languages/messages/…> - Mazandarani languages/messages/MessagesNds_nl.php<https://gerrit.wikimedia.org/r/#patch,sidebyside,3318,1,languages/messages/…> - languages/messages/MessagesOr.php<https://gerrit.wikimedia.org/r/#patch,sidebyside,3318,1,languages/messages/…> - Odia languages/messages/MessagesOs.php<https://gerrit.wikimedia.org/r/#patch,sidebyside,3318,1,languages/messages/…> - Ossetian languages/messages/MessagesQug.php<https://gerrit.wikimedia.org/r/#patch,sidebyside,3318,1,languages/messages/…> - Runa Shimi languages/messages/MessagesSa.php<https://gerrit.wikimedia.org/r/#patch,sidebyside,3318,1,languages/messages/…> - Sanskrit languages/messages/MessagesSr_ec.php<https://gerrit.wikimedia.org/r/#patch,sidebyside,3318,1,languages/messages/…> - Serbian languages/messages/MessagesWar.php<https://gerrit.wikimedia.org/r/#patch,sidebyside,3318,1,languages/messages/…> - Waray Waray languages/messages/MessagesYue.php<https://gerrit.wikimedia.org/r/#patch,sidebyside,3318,1,languages/messages/…> - Yue We are going to ask on the wikis for confirmation as well and we are looking for positive feedback by April 5th. *The CLDR user interface* The CLDR or the Common Locale Data Repository is where basic and not so basic information is gathered about languages in a standard. We use this information in the MediaWiki software and we rely on it. We do not like to override any values of this standard. Sometimes we have no choice when the CLDR does not have information on one of the languages we support. Once the CLDR does have data our local information is removed. The CLDR works with periods where they welcome input from the world. *The next period starts on April 4*. At this moment they are asking for comments on the improved user interface of their data collection software. They want to know and we want to know what you think of it. If it works for you, if you can find any bugs. This means that you can test-drive the application and learn to use it as well as find any issues with it. I have copied the invitation to the CLDR Survey Took Beta below. Enjoy and let us know your experiences. Thanks, Gerard ************************************************* ** Unicode CLDR Survey Tool Beta March 21, 2012 — The Unicode CLDR<http://cldr.unicode.org/>Survey Tool is open for beta testing today. CLDR provides key building blocks for software to support the world's languages, with the largest and most extensive standard repository of locale data available. The survey tool is an online tool used by organizations and individuals to contribute data to this repository, and to vote on alternative contributions. The survey tool has undergone substantial revision, with dramatic improvements in performance and usability. We would appreciate people trying out the tool so that we can identify any remaining problems before we start data submission (currently scheduled for April 4). For more information, see http://goo.gl/7M1IG. ------------------------------ Contents Access<https://mail.google.com/mail/?ui=2&view=bsp&ver=ohhl4rw8mbn4#136392b30c40a1…> Guide<https://mail.google.com/mail/?ui=2&view=bsp&ver=ohhl4rw8mbn4#136392b30c40a1…> How you can help<https://mail.google.com/mail/?ui=2&view=bsp&ver=ohhl4rw8mbn4#136392b30c40a1…> Known issues<https://mail.google.com/mail/?ui=2&view=bsp&ver=ohhl4rw8mbn4#136392b30c40a1…> What changed?<https://mail.google.com/mail/?ui=2&view=bsp&ver=ohhl4rw8mbn4#136392b30c40a1…> Access 1. Production Survey Tool <http://st.unicode.org/cldr-apps/survey>. If you have an existing survey tool account, you can go to the production tool at Production Survey Tool <http://st.unicode.org/cldr-apps/survey>. 2. Smoke-Test Survey Tool<http://st.unicode.org/smoketest/createAndLogin.jsp?vap=isdithOif5>. If you don’t have an account, you can still try out the survey tool using the Smoke Test version. It will create a test account automatically. So that you can try out the tool as you wish, none of the data you enter during beta is saved. The Smoke Test tool may be restarted at any time, because it used for development. If you get disconnected when this happens, then refresh your browser: all of your changes should be saved. Guide If you haven’t used the survey tool before, you may want to take a quick look at: 1. http://cldr.unicode.org/index/survey-tool/guide 2. http://cldr.unicode.org/index/survey-tool/walkthrough This documentation should be updated in the next few days for some of the changes in UI. How you can help Visit and randomly vote and enter changes. 1. Pick your favorite locale 2. Visit different Sections of the locale (Code Lists, etc), and different pages in the Section. 1. Vote for different choices (including Proposed, Others, Abstain) 2. Change a value (Change column) 3. Try zooming on different columns (clicking on the following cells) 1. St (status, eg error/alert) 2. Draft (the approval status) 3. Voted (the voting status) 4. Proposed / Others (particular values) 5. (Clicking on Code shows some internals, not really user-focused item) 4. Reset your Coverage Level (at the top). (This changes how many items show). 1. Verify that data was accepted, or is rejected (appropriately) because of an error. 2. Periodically, refresh the entire page you are on and verify that items previously added remain visible. 3. Report any new issues at http://unicode.org/cldr/trac/newticket. (Skip those below). Please include the URL to the page where you found the error. Known issues Please read these over so you know what to skip: 1. Use FireFox/Safari/Chrome, not IE 8 or other browsers. 2. Some locales, such as English (en), are read-only. 3. Do not post comments in the ‘forums’ or try “Show Coverage” 4. Some generated examples use English instead of the local language, or the wrong currency. 5. The information in the “Code” column will be simplified during the beta process; some rows will move to different sections or pages. 6. There will be a bookmark on each row, for reference. 7. Other items may be added to this list during the beta period What changed? 1. Page access is 10-30 times faster, depending on the operation. 2. Items are submitted individually (with Return/Enter), instead of having to submit a whole page. 3. Pages are not broken up into multiple subpages, simplifying navigation. 4. Errors and Warnings appear when you submit an item. 5. There is no “zoom” window; instead, zooming is in-place, with separate versions depending on what part of a row you click on.

1 0

I18n deployment 2012-03-26
by Niklas Laxstrom 23 Mar '12

23 Mar '12

Next deployment is on Monday 2012-03-26, 17:00-18:00 UTC (I think, summer time changes...) Summary of planned changes: * Lohit Nepali font update -Niklas

1 0

I18ndeploy 2012-03-19
by Niklas Laxstrom 16 Mar '12

16 Mar '12

Next deployment is on Monday 2012-03-19, 17:00-18:00 UTC Only small bug fixes this time: * JavaScript issue causing compatibility issues for WebFonts with Internet Explorer older than 9 * Small fix to autosummary formatting Code changes: https://www.mediawiki.org/wiki/Special:Code/MediaWiki/tag/i18ndeploy -Niklas

1 0

I18ndeploy 2012-03-12
by Niklas Laxstrom 12 Mar '12

12 Mar '12

Next deployment is on Monday 2012-03-12, 17:00-18:00 UTC This time we are planning to update our three major extensions to latest versions. Summary of WebFonts changes visible to users: * Amiri font (NEW) (Persian, not yet enabled for Arabic) * Lohit family fonts updated to version 2.5.1 * Jomolhari (Tibetan, Dzongkha) Summary of Narayam changes visible to users: * Ahirani transliteration and InScript (NEW - only in incubator) * Bhojpuri transliteration and InScript (BETA - only in incubator) * Gurmukhi Punjabi transliteration (BETA - only in incubator) Summary of Translate changes relevant to Wikimedia users: * Translation administrator can now suggest languages translatable page should be primarily translated into with a note or preventing other language translations. * Encourage/discourage changes of translatable pages are now logged. * Help link is no longer added twice in Special:SupportedLanguages * Improved the position of help links in Monobook skin. * Group description of translatable pages can be extended by adding content to [[MediaWiki:Tp-custom-<group id>]]. * New tabbed task-based UI on Special:Translate Core change: * Show all CSS/JS pages as left-to-right r112423 -Niklas

2 2

"translating" place names in Openstreetmap
by Raul Kern 12 Mar '12

12 Mar '12

Hi, made a tool to semi-automatically translate place names in Openstreetmap using wikipedia links from OSM and interlanguage links from the Wikipedias: http://meta.wikimedia.org/wiki/User:WikedKentaur/OSM-Wikipedia_place_name_t… -- Raul

2 2

I18n deployment 2012-03-05
by Niklas Laxström 05 Mar '12

05 Mar '12

Next deployment is on Monday 2012-03-05, 18:00-19:00 UTC Summary of planned changes: * Enable WebFonts for Buginese Wikipedia https://bugzilla.wikimedia.org/34550 * Enable Cuneiforms for English Wikisource (and other projects) r112469 Code changes: https://www.mediawiki.org/wiki/Special:Code/MediaWiki/tag/i18ndeploy For the next deployment after this one, we are planning to update Translate and WebFonts extensions with latest features. -Niklas

1 1

maintaining the local messages
by Gerard Meijssen 29 Feb '12

29 Feb '12

Hoi, Many of you are actively working on the localisation of MediaWiki. In the last couple of days I blogged twice on possible maintenance jobs on your local wiki. There are two parts to it: - the part where you copy messages to translatewiki; you have to be a twn translator to do this - the part where you remove messages on your local wiki; you have to be a local admin to do this The bottom line is that messages available at translatewiki.net will be available on any Wiki. This is why you want to always localise at translatewiki. When messages exist that are the same on your wiki and on translatewiki they may cause problems in the future. This is why localising locally is typically not the thing to do. In the post a Toolserver tool is mentioned that makes it relatively easy to do all this. Thanks. Gerard http://ultimategerardm.blogspot.com/2012/02/cleaning-up-mediawiki-namespace… http://ultimategerardm.blogspot.com/2012/02/cleaning-up-mediawiki-namespace… http://toolserver.org/~robin/?tool=cleanuplocalmsgs

3 3

I18n deployment 2012-02-27
by Niklas Laxstrom 28 Feb '12

28 Feb '12

Next deployment Monday 2012-02-27, 18:00-19:00 UTC Summary of planned changes * Albanian gender namespace aliases: https://bugzilla.wikimedia.org/34192 * Narayam key mapping fixes: ** Gujarati: https://bugzilla.wikimedia.org/34056 ** Marathi: https://bugzilla.wikimedia.org/34596 * Enable Webfonts on English Wikisource: https://en.wikisource.org/wiki/Wikisource:Scriptorium#Web_fonts * Enable Narayam on Gujarati Wikipedia: https://bugzilla.wikimedia.org/33423 * Use Narayam by default on Kannada Wikipedia: https://bugzilla.wikimedia.org/34591 * Fonts for Lontara script, to be used in Incubator: r111935 r111935 Code changes: https://www.mediawiki.org/wiki/Special:Code/MediaWiki/tag/i18ndeploy -Niklas

4 5

Re: [Mediawiki-i18n] Patch submitted: authentication on Wikipedia via user_name OR user_email
by Nicolas Brouard 22 Feb '12

22 Feb '12

Le 17 févr. 2012 à 14:28, Bergi a écrit : > Bináris schrieb: >> An alternative solution to the original problem could be an extension that >> displays possible characters from several alphabets and helps to generate >> the username with mouse and put it back to the login name/password field. > > I don't think that would be a good idea. > * It sounds as it would need JavaScript (or would be difficult to implement) > * clicking is much slower than typing > * "possible characters from several alphabets"? You know, we support the full set of Unicode. Displaying all unicode blocks would need the user to remember from which block his characters are > * One version of the problem is that you try to login from a system that doesn't support your characters with any font. "displaying characters" is the heavy task. If we don't want to show pictures, the user needs to remember the individual character codes. > (or is there a usable all-unicode web font?) > > Therefore, it is a great idea to login with your email address, which usually consists of latin characters. I have that problem myself, beeing User:✓ (a great challenge for toolserver tools ;-). Usually I have: > * My browsers autologin function which fills in the username at known wikis > * My browsers "notice" function which allows me to insert various texts with the contextmenu > * Once logged in, I have a extraeditbutton above the edit form > * or can c&p the sign from the #p-personal portlet (user page, user disk, prefs...) > But when I try to login no at my home system, I'm challenged how to insert the 0x2713 char code with the keyboard. At windows Alt + num pad usually works, but... So I often end up googling for "unicode checkmark", and c&p the character from wikipedias "List of Unicode characters" :-( Thank you for your support. I just submitted a complete patch entitled "Can't authenticate using my mother language username (UNICODE) when I only have (a public) access to Wikipedia with an ASCII (english) keyboard" in about 20 languages on https://bugzilla.wikimedia.org/show_bug.cgi?id=34590 People supporting this idea, please for it. Here is the text: This is a real issue for people who have registered with a username having UNICODE and non ASCII (7 bits) characters and who want to login to Wikipedia when they are abroad with a simple English keyboard and want to edit some pages (usually English pages). The fact that Wikipedia and Mediawikis do not offer the possibility to authenticate with an e-mail is now considered, at least for me, as a bug. I recently discussed this fact on Wikitech-l ("Great idea" http://lists.wikimedia.org/pipermail/wikitech-l/2012-February/058183.html) and some tests have been made trying to answer legitimate questions (see http://lists.wikimedia.org/pipermail/wikitech-l/2012-February/058253.html) to a simple patch that I proposed. This small patch in User.php (function idFromName) is enough in most cases: $dbr = wfGetDB( DB_SLAVE ); $s = $dbr->selectRow( 'user', array( 'user_id' ), array( 'user_name' => $nt->getText() ), __METHOD__ ); if ( $s === false ) { //Start Patch $result = null; $stwo = $dbr->selectRow( 'user', array( 'user_id' ), array( 'user_email' => $nt->getText() ), __METHOD__ ); if ( $stwo === false ) { $result = null; }else { $result = $stwo->user_id; } //End Patch } else { $result = $s->user_id; } The modified Login form is: Username (or e-mail): |___________________| Password: |___________________| The full attached patch is rendering this new form in about 20 languages (that is what we need in our wikis). The patch is simply adding two new msg: - 'yournameoremail' instead of 'yourname' in Userlogin.php and - 'passwordreset-usernameoremail' instead of 'passwordreset-username' in SpecialPasswordReset.php . In order to explain this new experimental feature, we added a Hook in LocalSettings.php : function efLoginFormMessage( &$template ) { $template->set( 'header', "NEW (experimental): if you are a registered user with an authenticated e-mail, you can also log in with your e-mail address in place of your username. Your e-mail is used only during the authentication phase; if successful you will be logged with your standard username. <br />Please notice that for people owning different accounts with the same e-mail, you will be logged in with your first registered username (lowest ID). If the password entered doesn't match the password of your lowest registered ID, you can't authenticate this way and should enter your desired username."); return true; } $wgHooks['UserLoginForm'][]='efLoginFormMessage'; I hope that this patch will be visited and accept. It is changing our live here. People having been registered with accented characters or in Cyrillic can use their e-mail to get their temporary password by e-mail while still being able to sign authorship in Cyrillic or with accented characters avoiding the English transliteration. Others still prefer the English transliteration, it is a question of taste. Without this patch, people are using the English transliteration for the commodity of authentication. Regards, Nicolas > Regards, > Bergi >

1 0

← Newer
1
...
38
39
40
41
42
43
44
...
57
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Mediawiki-i18n