Hi all
The first installment of the ContentHandler facility we need for Wikidata is now
on Gerrit, awyiting review:
https://gerrit.wikimedia.org/r/#change,6101
I already got a lot of useful input from several developers, and tried to
address them as well as I could. However, I would appreciate any additional
comments, so we can go ahead with this soon.
Please note that as it is, this changeset doesn't implement any new
functionality. Once it is merged in, I will submit changes to Article, EditPage,
DiffereEngine, etc. that make use of the new features introduced by the
ContentHandler facility. If you want a sneak preview, have a look at the
Wikidata branch of core:
https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/WikidataClient…
cheers
daniel
I'm happy to announce the availability of the first stable release
of the new MediaWiki 1.19 release series.
MediaWiki 1.19 is a large release that contains many new features and bug
fixes. This is a summary of the major changes of interest to users.
You can consult the RELEASE-NOTES-1.19 file for the full list of changes in
this version.
Our thanks go to everyone who helped to improve MediaWiki by testing the
beta
release and submitting bug reports.
****************************************************************
What's new?
****************************************************************
MediaWiki 1.19 brings the usual host of various bugfixes and new features.
Comprehensive list of what's new is in the release notes.
* Bumped MySQL version requirement to 5.0.2.
* Disable the partial HTML and MathML rendering options for Math,
and render as PNG by default.
* MathML mode was so incomplete most people thought it simply didn't work.
* New skins/common/*.css files usable by skins instead of having to copy
piles of
generic styles from MonoBook or Vector's css.
* The default user signature now contains a talk link in addition to the
user link.
* Searching blocked usernames in block log is now clearer.
* Better timezone recognition in user preferences.
* Extensions can now participate in the extraction of titles from URL paths.
* The command-line installer supports various RDBMSes better.
* The interwiki links table can now be accessed also when the interwiki
cache
is used (used in the API and the Interwiki extension).
Internationalization
- --------------------
* More gender support (for instance in user lists).
* Add languages: Canadian English.
* Language converter improved, e.g. it now works depending on the page
content language.
* Time and number-formatting magic words also now depend on the page
content language.
* Bidirectional support further improved after 1.18.
Full release notes:
https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/core.git;a=blob;f=RELEASE-
NOTES-1.19;hb=REL1_19
https://www.mediawiki.org/wiki/Release_notes/1.19
Frequently asked questions about upgrading:
http://www.mediawiki.org/wiki/Manual:FAQ#Upgrading
**********************************************************************
Download:
http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.0.tar.gz
GPG signatures:
http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.0.tar.gz.sig
Public keys:
https://secure.wikimedia.org/keys.html
I've written up a proposed interface between the MediaWiki parser and Lua:
<https://www.mediawiki.org/wiki/Extension:Scribunto/Parser_interface_design>
In summary: the Lua function is called with a single argument, which
is an object representing the parser interface. The object is roughly
equivalent to a PPFrame.
The object would have a property called "args", which is a table with
its "index" metamethod overridden to provide lazy-initialised access
to the parser function arguments with a brief syntax:
{{#invoke:module|func|name=value}}
function p.func(frame)
return frame.args.name --- returns "value"
end
There would be two methods for recursive preprocessing:
* preprocess() provides basic expansion of wikitext
* callTemplate() provides an API for template invocation, since I
imagine that would otherwise be a common use case for preprocess().
Using preprocess() to expand a template with arbitrary arguments would
be difficult.
Like a normal parser function, the Lua function returns text which is
not modified any further by the preprocessor.
Please see the wiki page for a more detailed description, including
rationale.
Any comments would be greatly appreciated.
-- Tim Starling
2012/4/24 Samuel Klein <meta.sj(a)gmail.com>
> Where's the latest thread on the Timed Media Handler progress?
>
> I am meeting with MIT Open CourseWare tomorrow - they want to expand
> the set of videos they released last year under CC-SA, starting with
> categories / vids that would be fill gaps on Wikipedia. Any thoughts
> on how to make that collaboration more effective would be welcome.
>
> SJ
>
>
You can upload them to Internet Archive, if Wikipedia has temporal issues
with videos. When the problems are fixed, we can move them from Internet
Archive to Wikimedia Commons.
--
Emilio J. Rodríguez-Posada. E-mail: emijrp AT gmail DOT com
Pre-doctoral student at the University of Cádiz (Spain)
Projects: AVBOT <http://code.google.com/p/avbot/> |
StatMediaWiki<http://statmediawiki.forja.rediris.es>
| WikiEvidens <http://code.google.com/p/wikievidens/> |
WikiPapers<http://wikipapers.referata.com>
| WikiTeam <http://code.google.com/p/wikiteam/>
Personal website: https://sites.google.com/site/emijrp/
Hey,
Setting up a git repo holding all extensions hosted by WMF was one of the
things on the git migration roadmap IIRC. AFAIK there is none yet - is this
being worked on?
Right now it's rather hard to get an overview of all changes made
everywhere and to do analytics on the overall codebase. You can of course
write a script to work with all the different repos, but that's rather less
convenient :)
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
Hi,
One of LibreOffice killer features is exporting documents in MediaWiki
format. It's not perfect, but it's nevertheless very useful for
converting papers written by academics and their students to Wikipedia
articles.
Unfortunately, it's broken in the latest LibreOffice releases:
https://bugs.freedesktop.org/show_bug.cgi?id=46509
Is there, by any chance, anybody here who is familiar with the world
of LibreOffice development that can help get it fixed?
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore