Wikitech-l January 2010

wikitech-l@lists.wikimedia.org

91 participants
68 discussions

CSS/javascript injection for AJAX requests
by Carl (CBM) 08 Jan '10

08 Jan '10

I noticed today that livepreview does not pick up the dynamically-generated CSS from the SyntaxHighlight_Geshi extension. The same problem occurs in liquidthreads: when you add a comment with a Geshi call in it, the CSS will not be picked up when the comment is initially saved. The first full reload of the page will pick up the css correctly neither case. After some investigation, this is really an issue in core and will apply to any extension that needs to add CSS and/or javascript to the output HTML. To fix the bugs with livepreview, we would need some mechanism where AJAX calls receive not only new HTML, but also new CSS and/or javascript, and can add that CSS and javascript to the current page without a reload. Adding the CSS and javascript dynamically may be tricky from a compatibility standpoint, but having library functions in our site javascript would help with that. I have not investigated the cause of the problem in liquidthreads. The code in EditPage.php shows scars from similar problems, in a commented-out call to send a list of categories back to an AJAX preview request. - Carl

2 1

Flagged revs on en:wp?
by David Gerard 06 Jan '10

06 Jan '10

Do we have any time frame for flagged revisions on en:wp? - d.

6 12

Re: [Wikitech-l] jQuery and extensions
by Chad 04 Jan '10

04 Jan '10

I'd suggest going ahead and bundling it. It's easy to do that and it promotes people using it instead of sajax. I'd love to see the old ajax stuff removed in favor of using jQuery, but that can't happen til jQuery is bundled in a semi-stable way. -Chad On Jan 4, 2010 6:19 AM, "Bryan Tong Minh" <bryan.tongminh(a)gmail.com> wrote: On Mon, Jan 4, 2010 at 8:06 AM, Max Semenik <maxsem.wiki(a)gmail.com> wrote: > On 04.01.2010, 0:02 Sie... Can't we just add jQuery to 1.16 even though no core scripts use it yet? Is there a reason not to? Would it need a security review before it is included? Bryan _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia....

2 1

jQuery and extensions
by Sergey Chernyshev 04 Jan '10

04 Jan '10

I remember it was mentioned that jQuery is going to be bundled with MediaWiki soon (1.16?). I wonder what would be the best approach for extensions that use jQuery and package it up within itself to use global jQuery and do that in backwards compatible way (e.g. to make sure that prior versions of MediaWiki don't get broken). Is there a good How-To for developers to rewrite their extensions? Thank you, Sergey -- Sergey Chernyshev http://www.sergeychernyshev.com/

4 4

Bugzilla Weekly Report
by reporter＠isidore.wikimedia.org 04 Jan '10

04 Jan '10

MediaWiki Bugzilla Report for December 28, 2009 - January 04, 2010 Status changes this week Bugs NEW : 283 Bugs ASSIGNED : 18 Bugs REOPENED : 39 Bugs RESOLVED : 138 Total bugs still open: 4145 Resolutions for the week: Bugs marked FIXED : 66 Bugs marked REMIND : 0 Bugs marked INVALID : 13 Bugs marked DUPLICATE : 18 Bugs marked WONTFIX : 24 Bugs marked WORKSFORME : 10 Bugs marked LATER : 8 Bugs marked MOVED : 0 Specific Product/Component Resolutions & User Metrics New Bugs Per Component Video player 4 Site requests 4 Images and files 3 Bugzilla 3 server 2 New Bugs Per Product MediaWiki 11 Wikimedia 9 MediaWiki extensions 8 Wikipedia Mobile 2 mwEmbed 4 Top 5 Bug Resolvers gpaumier [AT] wikimedia.org 32 markus [AT] semantic-mediawiki.org 10 roan.kattouw [AT] gmail.com 10 sergey.chernyshev [AT] gmail.com 4 innocentkiller [AT] gmail.com 3

2 1

Re: [Wikitech-l] jQuery and extensions
by Sergey Chernyshev 03 Jan '10

03 Jan '10

Thanks, Siebrand. It gives us a bit more time to write such documentation. Sergey On Sun, Jan 3, 2010 at 4:02 PM, Siebrand Mazeland <s.mazeland(a)xs4all.nl>wrote: > Just a little roadmap info: mwEmbed[1], contaning jQuery, will not be part > of > MediaWiki 1.16. It will be added in a later version. Tim Starling pulled it > from trunk a few weeks ago and Michael Dale has continued working on it in > a > branch. > > I expect it will be added again after the branching/tagging of 1.16, and be > part of 1.17 after a thorough shake down during the 1.17 alpha period. > > Siebrand > > [1] http://www.mediawiki.org/wiki/MwEmbed > > -----Original Message----- > From: wikitech-l-bounces(a)lists.wikimedia.org > [mailto:wikitech-l-bounces@lists.wikimedia.org] On Behalf Of Sergey > Chernyshev > Sent: Sunday, January 03, 2010 9:42 PM > To: Wikimedia developers > Subject: [Wikitech-l] jQuery and extensions > > I remember it was mentioned that jQuery is going to be bundled with > MediaWiki soon (1.16?). > > I wonder what would be the best approach for extensions that use jQuery and > package it up within itself to use global jQuery and do that in backwards > compatible way (e.g. to make sure that prior versions of MediaWiki don't > get > broken). > > Is there a good How-To for developers to rewrite their extensions? > > > > > _______________________________________________ > Wikitech-l mailing list > Wikitech-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l >

1 0

Re: [Wikitech-l] Reminder: move your projects off stable -Geohack
by Tim Landscheidt 02 Jan '10

02 Jan '10

Magnus Manske <magnusmanske(a)googlemail.com> wrote: >> perhaps this would be a good moment to transfer Geohack to a regular >> mediawiki-extension on the main servers. >> I hear this was also the plan of brion vibber before he go. >> Who we need to ask now for this? > I asked Brion on the Paris meeting and he said he'd have a look. But, > I didn't hear anything back, so I assume he didn't. > wikimedia.org doesn't list an official CTO, so for the time being, I > guess Tim Starling is the person to ask. > Last time I had a long look at the code, the extension part seemed to > be in good condition. One half is using it as a special page (just a > wrapper around the current code calls), and getting the wiki template > from the cache instead of the http rendering. > Compatability might have deteriorated since then, though. > [...] I had a look at the code one or two years ago, and started a small DWIM-and-nothing-more extension "Mapsources" along the lines of "Booksources" that "called" a template with the co- ordinates as parameters so that you could use all of Media- Wiki's parser functions & Co. in it. The idea would have been to extend it eventually to have the list of map sources ordered by the region of the individual coordinate and by user preference (Swiss coordinates: Swisstopo, British coor- dinates: Ordnance Survey, etc.) with a timeout so that if you don't react within x seconds the first map source is chosen. But #1, then I stumbled upon a post of yours where you pointed out that Special:TemplateLink would be much more suitable to replace the whole Geohack shebang, and I think you were right. But #2, with all the work going on with OSM and the Maps extension, wouldn't it be wiser to integrate Geohack's func- tionality with the later? Tim (f'uping to wikitech-l)

1 0

An update on localisation in MediaWiki (2009)
by Siebrand Mazeland 02 Jan '10

02 Jan '10

On 31 December 2007 and 1 January 2008 I sent an e-mail to which this is a follow up[1,2]. First things first, because not everyone reads e-mails completely: * MediaWiki localisation (that is the translation of English source messages to other languages) depends on you! If you speak a language other than English, care about your language in MediaWiki and Wikimedia and like translating, go to http://translatewiki.net, register a user and start contributing translations for MediaWiki and MediaWiki extensions. When your localisation is complete, keep coming back regularly to re-complete it and do quality control. Thank you in advance for all your contributions and effort. * The i18n and L10n area of MediaWiki requires continuous efforts. If this area of FOSS has your interest: we need your help. Please offer your development skills to further MediaWiki's i18n, L10n and translation capabilities[3,4]. All statistics are based on MediaWiki 1.16 alpha, SVN version r60527 (31 December 2009). Comparisons are to MediaWiki 1.14 alpha, SVN version r45277 (1 January 2009). See http://translatewiki.net/wiki/MediaWiki_2009 for a wiki version of this message. ==Introduction== * Localisation or L10n - the process of adapting the software to be as familiar as possible to a specific locale (topic of this message) * Internationalisation or i18n - the process of ensuring that an application is capable of adapting to local requirements (out of scope of this message) MediaWiki has a user interface definition for 362 languages (up from 348). Of those languages at least 39 language codes are duplicates and/or serve a purpose for usability[5]. Reporting on them, however, is not relevant. So MediaWiki in its current state supports 323 languages (up from 322). MediaWiki has 346 core language files (up from 326), of which 27 are redirects from the duplicates/usability group or just empty[6]. So MediaWiki has an active in-product localisation for 308 languages (up from 299). The MediaWiki core product has several areas that can be localised: * regular messages that can and should be localised (2,369 - up 9% from 2,168) * optional messages that can be localised, which is mostly used for languages not using a Latin script (187 - up 8% from 173) * ignored messages that should not be localised (152 - up 2% from 149) * namespace names and namespace aliases (17 - no change) * magic words (142 - up 8% from 132) * special page names (88 - up 2% from 86) * other (directionality, date formats, separators, book store lists, link trail, and others) Localisation of MediaWiki revolves around all of the above. Reporting is done on the regular messages only. MediaWiki is more than just the core product. On http://www.mediawiki.org/wiki/Category:All_extensions 1500 extensions (up 25% from 1200) have some kind of documentation. This analysis only takes the code currently present in svn.wikimedia.org/svnroot/mediawiki/trunk into account. The source code repository contains give or take 445 extensions (up 25% from 370). Most extensions in the MediaWiki Subversion repository now use the reference implementation for i18n. Currently 8,200 messages for MediaWiki extensions can be localised in a consistent way (up 37% from 6,000). ==MediaWiki localisation in practice== MediaWiki localisation has moved further to a centralised collaborative process in translatewiki.net in the past year. Where in 2008 some wikis were still translating in their own MediaWiki: namespace, the introduction of the LocalisationUpdate extension[7], especially in the Wikimedia Foundation wikis, has taken away the last hurdle for local translation against centralised translation: instant gratification. Translations that are committed to Subversion can be added to wikis without requiring software updates, as often as desirable. Little to no translations are submitted through the Bugzilla ticketing system or directly by SVN committers. Exceptions are the localisations of Hebrew, Cantonese, Simplified Chinese, Traditional Chinese, Classical Chinese and Persian, that are still actively maintained in SVN, next to regular contributors from the centralised system. ==The past, the present and the future== MediaWiki localisation has always been a volunteer effort, and expect that it will remain so. 2009 brought a successful Google Summer of Code project, executed by Niklas Laxstrom [8,9] and the Wikimedia Foundation is supporting the localisation that takes place at translatewiki.net[10]. Not only MediaWiki, but all Open Source projects that are supported there[11] benefit from these developments. We want to keep using the Translate extension technology and expand on it, as well as nourish our translator base of nearly 2,000 translators by providing them with better tooling and more projects in 2010. Vereniging Wikimedia Nederland[12], the Dutch Wikimedia Chapter has granted 2,000 Euro to Stichting Open Progress[13] for the translatewiki.net Translation Rallies, that motivated its translators to make more than 60,000 new translations for MediaWiki and its extensions in August and December 2009. New opportunities lie in better support of Translation Memory technology and more supported projects to grow the community and allow the translators to spend their time as productive as possible, while still allowing all the socialising and collaboration features of MediaWiki. At the Google Summer of Code Mentor Summit there was interest from the KDE Documentation Project[14], the PHP Documentation Project, Pidgin, wxWidgets, and other projects. For translatewiki staff this was a confirmation that our approach works. The Translate extension however needs more development. If you want to work on an exciting extension that makes a difference in multi language support for Open Source software and MediaWiki content pages that require structured translation, check out the Translate extension and help us make it better. Your help *is* needed and most welcome! The Wikimedia Strategic Planning process that is currently taking place also allows for a broader perspective on the localisation of MediaWiki in a Wikimedia context[15]. Support for several dozen MediaWiki extension in the Wikia code repository is expected within the next few weeks. Wikimedia is, or will soon be including a localisation score for language projects in their statistics, so that in a year we expect to be able to analyse if localisation is a requirement for a rise in usage or if it is a consequence[16]. ==MediaWiki localisation statistics== Daily statistics for MediaWiki and extension localisation have been available for the past two years[17]. For the past two years (arbitrary) milestones have been set for four collections of MediaWiki related messages. For the usability of MediaWiki in a particular language, the group 'core most used' is the most important. A language must qualify for MediaWiki to have 'minimal support' for that language in the first group. Reaching further milestones indicates the maturity of a localisation: * core most used (469): 98% * core (2,369 messages): 90% * Wikimedia extensions (2,700 messages): 90% * extensions (8,200 messages): 65% Currently the following numbers of languages have passed the above milestones[18]: * core most used: 147 (45.6% of supported languages - up 35% from 109 - goal of 130 passed) * core: 82 (21.1% of supported languages - up 21% from 68 - goal of 90 missed by 203 translations) * Wikimedia extensions: 44 (13.6% of supported languages - up 22% from 36 - goals of 50 missed by 1,500 translations) * extensions: 39 (12.1% of supported languages - up 86% from 21 - goal of 30 passed) I think the changes in the past year are very satisfying. MediaWiki localisation has again improved enormously in the past year. Two of the four goals I set in last years' e-mail have not been reached (only one of four goals was reached for 2008). We nearly got there, though. Currently MediaWiki core contains 377,394 messages (up 24% from 303,863 ultimo 2008). ==Conclusion== So... Is MediaWiki doing well on localisation? Just like the past two years, my personal opinion is that we do a proper job, but can still do a lot better. After all, MediaWiki is the engine that runs a top 5 site in the world committed to creating "a world in which every single human being can freely share in the sum of all knowledge." Observing that there are also an estimated hundred thousand MediaWiki installations out there, more than 250 Wikipedias that all use the Wikimedia Commons media repository, and that 147 languages out of 323 have a minimal localisation, there is a lot of room for improvement; more realistically: the work will never be done, we the least we can do is try to get there :). Last year I mentioned languages from Africa performing way below average. I am sad to conclude that this has not changed considerably. In an overview with a weighted score for the localisation level of MediaWiki in a Wikimedia context[19], the largest African languages have the lowest score (52 out of 100). Large languages spoken on multiple continents and large languages from Europe are doing best (100 and 99 out of 100 respectively). Languages like Oriya, Zulu, Burmese and Urdu are the large languages with the worst localisation score. It is my personal aim to work towards an average L10n score of 83 for the 50 largest languages in the world by the end of September 2010. We have all the tools to successfully localise MediaWiki into any of the 7,000 or so languages that have been classified in ISO 639-3. We only need one person per language to make and effort and make it happen. Reaching the first milestone (core most used) takes about six hours of work. Using translatewiki.net or the Gettext file, little to no technical knowledge is required. Knowledge of MediaWiki is a plus. This was the pitch, basically the same as in 2007 and 2008, with even more experience and data. Goals for MediaWiki localisation per end of 2010 are ambitious, but still realistic with the right effort: * core most used: 170 languages with 98% or more localised * core: 105 languages with 90% or more localised * wikimedia extensions: 65 languages with 90% or more localised * extensions: 50 languages with 65% or more localised I would like to wish everyone involved in any aspect of MediaWiki a wonderful 2010. Cheers! Siebrand Mazeland [1] http://lists.wikimedia.org/pipermail/translators-l/2007-December/000571.html [2] http://translatewiki.net/wiki/User:Siebrand/An_update_on_localisation_in_Me… [3] https://bugzilla.wikimedia.org/buglist.cgi?query_format=advanced&component=… [4] http://translatewiki.net/wiki/User:Siebrand#Bugs [5] als, be-x-old, ckb, crh, de-at, de-ch, de-formal, dk, en-gb, fiu-vro, gan, got, hif, kk, kk-cn, iu, kk-kz, kk-tr, ko-kp, ku, ku-arab, nb, ruq, simple, sr, tg, tp, tt, ug, zh, zh-classical, zh-cn, zh-sg, zh-hk, zh-min-nan, zh-mo, zh-my, zh-tw, zh-yue [6] als, be-x-old, bh, ckb, ckb-latn, crh, de-at, dk, en-rtl, fiu-vro, gan, hif, hif-deva, ii, iu, kk, kk-cn, kk-kz, kk-tr, ko-kp, ks, ku, nb, pi, ruq, simple, st, tg, tp, tt, ug, zh-classical, zh-cn, zh-min-nan, zh-mo, zh-my, zh-sg, zh-yue [7] http://www.mediawiki.org/wiki/Extension:LocalisationUpdate [8] http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2009/wikime… [9] http://laxstrom.name/blag/2009/09/01/gsoc-wrap-up-translate-extension/ [10] http://techblog.wikimedia.org/2009/10/supporting-translatewiki-net/ [11] http://translatewiki.net/wiki/Project_list [12] http://nl.wikimedia.org [13] http://www.openprogress.org/Stichting_Open_Progress [14] http://translatewiki.net/wiki/Project:KDE_Documentation [15] http://strategy.wikimedia.org/wiki/Localisation [16] http://stats.wikimedia.org/EN/TablesCurrentStatusVerbose.htm [17] http://translatewiki.net/wiki/Translating:Group_statistics [18] http://translatewiki.net/wiki/Translating:Group_statistics_in_time [19] http://translatewiki.net/wiki/Project:MediaWiki_localisation_in_the_50_most…

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l January 2010