On Thu, May 3, 2012 at 9:44 AM, Dario Taraborelli
<dtaraborelli(a)wikimedia.org> wrote:
> MathJax [1] is now enabled site-wide as an opt-in preference. You can now see beautifully rendered, accessible, copy&pasteable and standard-compliant (MathML) formulas on Wikipedia, replacing the old TeX-rendered PNGs.
Thanks Dario. There are definitely still bugs in this experimental
rendering mode, so please report issues in Bugzilla against the Math
component:
https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensions…
More here:
http://www.mediawiki.org/wiki/Extension:Math/MathJax_testing
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
Hey all.
I'm a GSoC student working on a project called TranslateSvg (as astute
list followers will already know).
Since being awarded the position, I've been delighted to be able to
sort out several details about how the project is going to come
together. For example, it's clear now that my best bet is to extend
the Translate extension to allow it to cope with SVGs.
This and several other design decisions I've been making are documented at [1].
Also included on that page are a proposed workflow, an updated
roadmap/timetable and several preliminary designs. I've been grateful
to the translator community for their comments on the designs already,
but I welcome any further considerations on them or the other
sections.
Basically, if anyone has a niggling doubt about the feasibility of
some aspect of the project, I'd love to hear as soon as possible so I
can work on a solution :)
Thanks everyone!
Harry
--
Harry Burt (User:Jarry1250)
WMF GSoC student
[1] https://www.mediawiki.org/wiki/Extension:TranslateSvg/2.0
Hi Arun,
A very warm welcome to you on the I18n/L10N engineering team. We are excited about the Universal Language Selector UI/UX work that you and Pau are helping us with.
Happy to see you onboard!
Alolita
__
Alolita Sharma
Wikimedia Foundation
----- Reply message -----
From: "Subhashish Panigrahi" <subha(a)wikimedia.org>
To:
Cc: <wikitech-l(a)lists.wikimedia.org>, <wmfall(a)lists.wikimedia.org>, "Arun Ganesh" <arun.planemad(a)gmail.com>
Subject: [Wmfall] Introduction - Arun
Date: Thu, May 3, 2012 6:55 am
Congratulations Arun!
Happy that I met you a month back, now the L10n have more people from Indic
communities and it makes me happier again ;-)
On Thu, May 3, 2012 at 7:17 PM, Maggie Dennis <mdennis(a)wikimedia.org> wrote:
> Welcome, Arun! Somehow I feel sure that you are in for an interesting
> ride. :D
>
> Maggie
>
> On Thu, May 3, 2012 at 9:16 AM, Arun Ganesh <arun.planemad(a)gmail.com>wrote:
>
>> Hi everyone,
>> I wanted to introduce myself to the community and the WMF team, I'm Arun
>> Ganesh (user:planemad)[1a] from Bangalore, India and have joined as
>> contractor for the foundation's L10n team[1b] as an Interaction designer
>> along with Pau to improve the user experience of language tools and
>> features.
>>
>> I have been a longtime contributer to both commons[2] and the
>> openstreetmap[3] project and got involved with foundation work during the
>> Mumbai and Pune hackathons recently[4][5][6] where I proposed some of the
>> first ideas for the Universal Language Selector widget with Brandon, with
>> which we want to make language selection for anyone easy peasy.
>>
>> Apart from that, I love cartography and maps [7], which would explain my
>> map contributions and the occasional headline for wikipedia [8], use only
>> public transport[9] and traveling with my pocket camera[10].
>>
>> Its feels great to have this opportunity to work more seriously on a
>> project which has been an important part of my life. I'm new here, I wont
>> claim to know much, but I hope to make a difference in whichever way
>> possible. I also look forward to interacting more closely and learning from
>> the rest of the designers - Brandon, Heather and Pau to do the wonderful
>> things that designers like to do .So keep the usability bugs coming :)
>> -Arun
>>
>> [1a] http://en.wikipedia.org/wiki/User:Planemad
>> [1b] http://wikimediafoundation.org/wiki/Localization_team
>> [2]
>> http://tools.wikimedia.de/~daniel/WikiSense/Gallery.php?&wiki=commons.wikim…
>> [3]
>> http://yosmhm.neis-one.org/?zoom=4&lat=21.96627&lon=81.68268&layers=B0T&u=P…
>> [4]
>> http://www.mediawiki.org/wiki/Universal_Language_Selector#Arun_Ganesh.27s_O…
>> [5] http://commons.wikimedia.org/wiki/File:Mobile_language_selector.pdf
>> [6]
>> http://commons.wikimedia.org/wiki/File:L10n-ux-Universal_Language_Selector-…
>> [7] http://bit.ly/timesofindia-osm
>> [8]
>> http://www.guardian.co.uk/news/datablog/2010/jul/30/information-beautiful-i…
>> [9]
>> http://www.thehindu.com/todays-paper/tp-national/tp-tamilnadu/article182223…
>> [10] http://www.time.com/time/world/article/0,8599,1663025,00.html
>>
>>
>> _______________________________________________
>> Wmfall mailing list
>> Wmfall(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wmfall
>>
>>
>
>
> --
> Maggie Dennis
> Community Liaison
> WikimediaFoundation.org
>
>
> _______________________________________________
> Wmfall mailing list
> Wmfall(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wmfall
>
>
--
*Subha*
*Imagine a world in which every single human being can freely share in the
sum of all knowledge. Help us make it a reality!*
> Message: 5
>
> Date: Thu, 3 May 2012 08:33:45 +0200
>
> From: Alex Brollo <alex.brollo(a)gmail.com>
>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>
> Subject: [Wikitech-l] Full support for djvu files
>
> Message-ID:
>
> <CAH_M_mPXxD9LeMjHCm65CRAvoqN5W45O5dGO+TeH1C0f_hc4rg(a)mail.gmail.com>
>
> Content-Type: text/plain; charset=ISO-8859-1
>
>
> Djvu files are the wikisource standard supporting proofreading. They have
>
> very interesting features, being fully "open" in structure and layering,
>
> and allowing a fast and effective sharing into the web, when they are
>
> stored in their "indirect" mode. Most interesting, their text layer - which
>
> can be easily extracted - contains both the mapped text from OCR and
>
> metadata. A free library - divuLibre - allows full command line access to
>
> any file content.
>
>
> Presently, djvu files structure and features are minimally used. Indirect
>
> mode is IMHO not supported at all, there's no mean to access to mapped text
>
> layer nor to metadata, and only the "full text" can be accessed once, when
>
> creating a new page into Page namespace.
>
>
> It would be great IMHO:
>
> * to support indirect mode as the standard;
>
> * to allow free, easy access to the full text layer content from wikisource
>
> user interface.
>
>
> Alex
>
Text layer is stored in img_metadata, which means it can be retrieved
by the API (using ?action=query&prop=imageinfo&iiprop=metadata).
However when I tried to test this, it didn't seem to work. Maybe
trying to return the entire text layer hit some max api result size
limit or something. (It'd be really nice if we had some nicer place to
store information about files, especially for huge things like the
text layer which we don't generally want to load the entire thing all
the time. There's a bug about that somewhere in bugzilla land).
Indirect mode (From what I can find out from google) is when you have
an index djvu file that has links to all the pages making up the djvu
file, so you can start viewing immediately and pages are only
downloaded as needed. I'm not sure how such a format would work in
terms of uploading it. Unless we convert it on the server side, how
would we upload all the constitutiant files (I suppose we could tell
people to upload tarballs. Then we have to make sure to validate the
contents, and communicate to people that the tarball is only for
uploaded djvu files). [Of course until 5 minutes ago I'd never heard
of an indirect djvu file, so I could be misunderstanding]
-bawolff
Djvu files are the wikisource standard supporting proofreading. They have
very interesting features, being fully "open" in structure and layering,
and allowing a fast and effective sharing into the web, when they are
stored in their "indirect" mode. Most interesting, their text layer - which
can be easily extracted - contains both the mapped text from OCR and
metadata. A free library - divuLibre - allows full command line access to
any file content.
Presently, djvu files structure and features are minimally used. Indirect
mode is IMHO not supported at all, there's no mean to access to mapped text
layer nor to metadata, and only the "full text" can be accessed once, when
creating a new page into Page namespace.
It would be great IMHO:
* to support indirect mode as the standard;
* to allow free, easy access to the full text layer content from wikisource
user interface.
Alex
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/