Wikitech-l October 2010

wikitech-l@lists.wikimedia.org

95 participants
67 discussions

MediaWiki to Latex Converter
by Hugo Vincent 18 Jun '12

18 Jun '12

Hi everyone, I recently set up a MediaWiki (http://server.bluewatersys.com/w90n740/) and I need to extra the content from it and convert it into LaTeX syntax for printed documentation. I have googled for a suitable OSS solution but nothing was apparent. I would prefer a script written in Python, but any recommendations would be very welcome. Do you know of anything suitable? Kind Regards, Hugo Vincent, Bluewater Systems.

6 13

Commons ZIP file upload for admins
by Erik Moeller 25 Nov '10

25 Nov '10

Hello all, for some types of resources, it's desirable to upload source files (whether it's Blender, COLLADA, Scribus, EDL, or some other format), so that others can more easily remix and process them. Currently, as far as I know, there's no way to upload these resources to Commons. What would be the arguments against allowing administrators to upload arbitrary ZIP files on Wikimedia Commons, allowing the Commons community to develop policy and process around when such archived resources are appropriate? An alternative, of course, would be to whitelist every possible source format for admins, but it seems to me that it would be a good general policy to not enable additional support for formats that aren't officially supported (reduces confusion among users about what's permitted -- there's only one file format they can't use). Thoughts? Thanks, Erik -- Erik Möller Deputy Director, Wikimedia Foundation Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate

13 16

ResourceLoader, now in trunk!
by Trevor Parscal 07 Nov '10

07 Nov '10

MediaWiki Developers, Over the past couple of months, Roan Kattouw and I (Trevor Parscal) have been working on a JavaScript and CSS delivery system called ResourceLoader. We're really excited about this technology, and hope others will be too. This system has been proving itself to be able to seriously improve front-end performance. Just for starters, we're talking about taking the Vector skin from 35 requests @ 30kB gzipped to 1 request @ 9.4kB gzipped (see http://www.mediawiki.org/wiki/ResourceLoader/Benchmarks) We are looking to make this the standard way to deliver Javascript, CSS, and small images in MediaWiki and on Wikimedia projects, and we're seeking your comments and help. == Background == The goals of the project were to improve front-end performance, reduce the complexity of developing JavaScript libraries and user-interfaces, and get the ball rolling on a rewrite/refactoring of all JavaScript and CSS code in MediaWiki. What's wrong with things as they are now? * Too many individual requests are being made. All JavaScript, CSS and image resources are being loaded individually, which causes poor performance on the cluster and users experience the site as being slow. * We are wasting too much bandwidth. We are sending JavaScript and CSS resources with large amounts of unneeded whitespace and comments. * We are purging our caches too much. Many user interface changes require purging page caches to take effect and many assets are unnecessarily being purged from client machines due to the use of a single style version for all assets * We are sending people code they don't even use. Lots of JavaScript is being sent to clients whose browsers will either crash when it arrives (BlackBerry comes to mind), just not use it at all (older versions of many browsers) while parsing it unnecessarily (this is slow on older browsers, especially IE 6) or isn't even being completely utilized (UsabilityInitiative's plugins.combined.min.js for instance) * Internationalization in JavaScript is a mess. Developers are using many different ways -- most of which are not ideal -- to get their translated messages to the client. * Right-to-left support in CSS is akward. Stylesheets for right-to-left must to be either hand-coded in a separate stylesheet, generated each time a change is made by running CSSJanus, or an extra style-sheet which contains a series of over-rides. * There's more! These and other issues were captured in our requirements gathering process (see http://www.mediawiki.org/wiki/ResourceLoader/Requirements ) What does ResourceLoader do to solve this? * Combines resources together. Multiple scripts, styles, messages to be delivered in a single request, either at initial page load or dynamically; in both cases resolving dependencies automatically. * Allows minification of JavaScript and CSS. * Dramatically reduces the number of requests for small images. Small images linked to from CSS code can be automatically in-lined as data URLs (when the developer marks it with a special comment), and it's done automatically as the file is served without requiring the developer to do such steps manually. * Allows deployment changes to all pages for all users within minutes, without purging any HTML. ResourceLoader provides a short-expiry start-up script which then decides to continue loading more JavaScript or not, and if so has a complete manifest of all scripts and styles on the server and their most recent versions, Also, this startup script will be able to be inlined using ESI (see http://en.wikipedia.org/wiki/Edge_Side_Includes ) when using Squid or Varnish, reducing requests and improving performance even further. * Provides a standard way to deliver translated messages to the client, bundling them together with the code that uses them. * Performs automatic left-to-right/right-to-left flipping for CSS files. In most cases the developer won't have to do anything before deploying. * Does all kinds of other cool tricks, which should soon make everyone's lives better What do you want from me? * Help by porting existing code! While ResourceLoader and traditional methods of adding scripts to MediaWiki output can co-exist, the performance gains of ResourceLoader are directly related to the amount of software utilizing it. There's some more stuff in core that needs to be tweaked to utilize the ResourceLoader system, such as user scripts and site CSS. We also need extensions to start using it, especially those we are deploying on Wikimedia sites or thinking about deploying soon. Only basic documentation exists on how to port extensions, but much more will be written very shortly and we (Roan and I) be leading by example by porting the UsabilityInitiative extensions ourselves. If you need help, we're usually on IRC. (See http://www.mediawiki.org/wiki/ResourceLoader/Getting_Started ) * Help writing new code! While wikibits.js is now also known as the "mediawiki.legacy.wikibits" module, the functionality that it and basically all other existing MediaWiki JavaScript code provide is being deprecated, in favor of new modules which take advantage of jQuery and can be written using a lot less code while eliminating the current dependence on a large number of globally accessible variables and functions (see http://www.mediawiki.org/wiki/ResourceLoader/JavaScript_Deprecations ) * Some patience and understanding... Please... While we are integrating into trunk, things might break unexpectedly. We're diligently tracking down issues and resolving them as fast as we can, but help in this regard is much needed and really appreciated. But most of all, we're sorry if something gets screwed up, and we're trying our best to make this integration smooth. * Enthusiasm! Documentation is coming online as fast as we can write it. There's a very detailed design specification document at http://www.mediawiki.org/wiki/ResourceLoader/Design_Specification and more information in general at http://www.mediawiki.org/wiki/ResourceLoader , where we will be adding more and more documentation as time goes on. If you can help with documentation, please feel free to edit boldly - just try not to modify the design specification unless you are also modifying the software :) While this project has been bootstrapped by Roan and myself in a branch, we're really excited about bringing it to trunk and hope the community can start taking advantage of the new features right away. Tracking bug for tracking things that ResourceLoader will fix: http://bugzilla.wikimedia.org/show_bug.cgi?id=24415 Bugzilla Component: https://bugzilla.wikimedia.org/buglist.cgi?query_format=advanced&bug_status… - Trevor (and Roan, who's committing the merge to SVN right now)

19 56

API vs data dumps
by Paul Houle 07 Nov '10

07 Nov '10

I know there's some discussion about "what's appropriate" for the Wikipedia API, and I'd just like to share my recent experience. I was trying to download the Wikipedia entries for people, of which I found about 800,000. I had a scanner already written that could do the download, so I got started. After running for about I day, I estimated that it would take about 20 days to bring all of the pages down through the API (running single-threaded.) At that point I gave up, downloaded the data dump (3 hours) and wrote a script to extract the pages -- it then took about an hour to the extraction, gzip compressing the text and inserting into a mysql database. Don't be intimidated by working with the data dumps. If you've got an XML API that does streaming processing (I used .NET's XmlReader) and use the old unix trick of piping the output of bunzip2 into your program, it's really pretty easy.

3 3

Backups
by Eugene 07 Nov '10

07 Nov '10

Hi everyone, Are there any updates regarding Wikipedia's backup systems? I've created a bug to track this at https://bugzilla.wikimedia.org/show_bug.cgi?id=18255. Cheers, Eugene

4 5

Cross wiki script importing
by Junaid P V 04 Nov '10

04 Nov '10

Hi, How to perform cross-wiki script importing? I tried with *importScript('w:Mediawiki:rules.js‎');* on ml.wikibooks, but not working. Thank you. -- Junaid P V http://junaidpv.in

4 4

Fwd: [Mediawiki-l] about requiring PHP 5.2
by Chad 03 Nov '10

03 Nov '10

Forwarding to wikitech-l, needs more audience. I've no love for outdated software, so I'm firmly in the +1 camp. -Chad ---------- Forwarded message ---------- From: Ashar Voultoiz <hashar+wmf(a)free.fr> Date: Tue, Sep 28, 2010 at 3:39 PM Subject: [Mediawiki-l] about requiring PHP 5.2 To: mediawiki-l(a)lists.wikimedia.org Hello, Looking at INSTALL it seems we are still supporting PHP version 5.1 which is 5 years old in a couple of weeks. This is getting old and prevents developers from using some new features. Ideally we could raise it to 5.3 to get Namespace support, closures but that might be to early since most webhost probably still use 5.2.x. Would it be possible to consider raising the requirement to at least 5.2.0 ? This would give us native JSON support and most probably the filter extension enabled by default. The later can be used to speed up the input validation. cheers, -- Ashar Voultoiz _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

5 7

org-mediawiki.el
by Bastien 02 Nov '10

02 Nov '10

Dear list, if there are Emacs people among you, they might be interested in testing org-mediawiki.el -- a library for Emacs org-mode to convert Org files to mediawiki-syntax formatted files: http://lumiere.ens.fr/~guerry/u/org-mediawiki.el org-mediawiki.el uses this experimental export engine: http://repo.or.cz/w/org-mode.git/blob_plain/HEAD:/EXPERIMENTAL/org-export.el 1. Load Emacs 2. Edit an Org file and save it 3. Load org-export.el 4. Load org-mediawiki.el 5. M-x org-mw-export Thanks for any feedback, PS: sorry if such announcements are a bit off-topic. Let me know. -- Bastien

3 2

removing 1.5 upgrader
by Ashar Voultoiz 31 Oct '10

31 Oct '10

Hello, We still have a the 1.4 -> 1.5 upgrader in trunk. It was used to handle both the schema changes and the encoding changes that occurred in 1.5. According to code review on r72865 [1], it is broken since r22580 [2] from May 2007. Can we please remove it for 1.17 ? I am not sure we still have to support an upgrade from 1.4 which is like 5 years old and probably not used anywhere nowadays. [1] http://www.mediawiki.org/wiki/Special:Code/MediaWiki/72865 [2] http://www.mediawiki.org/wiki/Special:Code/MediaWiki/22580 -- Ashar Voultoiz

5 4

cruise control long build
by Ashar Voultoiz 30 Oct '10

30 Oct '10

Hello, I fixed a bug today following a failed Cruise control build. I noticed the build time was roughly 14 minutes, most of it spend by phpdoc building the documentation. The xml log file is 6MB and 13800 lines are phpdoc related. _ is there any reason to use phpdoc instead of doxygen ? _ can we build the api separately ? This will let us run tests more often. _ Is there any human log file (HTML, text) beside XML ? I could process it with XSLT but I am getting old :-) -- Ashar Voultoiz

2 1

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 October 2010