http://www.lua.org/wshop12.html
"the main goal of the workshop is to allow the Lua community to get
together and meet in person and talk about the Lua language, its uses,
and its implementation.... We shall have a plenary talk by Roberto
Ierusalimschy (Lua's chief architect) and several contributed talks....
If you'd like to speak at the workshop, please send a tentative title
and a short abstract to the organizers."
If you think it would be useful for Wikimedia to make an appearance, go
ahead and submit an abstract or suggest someone to go.
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
Dear all,
today I did some changes to simplify the math plug in a little bit and
as a preparation to the LaTeXML integration:
Please review and comment at:
https://gerrit.wikimedia.org/r/#/c/28824/
Best regards
Moritz
PS: I had some problems with the commit messages. They were not
accepted so the text is lost.
What I basically did that I separated the code of the divers ways of
rendering into separate classes that extend a common base class.
On Mon, Oct 15, 2012 at 12:13 AM, Moritz Schubotz
<physik(a)physikerwelt.de> wrote:
> HI DJ,
>
> first of all thanks a lot for your helpful comments.
>
> On Sun, Oct 14, 2012 at 10:31 PM, Derk-Jan Hartman
> <d.j.hartman+wmf_ml(a)gmail.com> wrote:
>> On 14 okt. 2012, at 17:45, Moritz Schubotz <physik(a)physikerwelt.de> wrote:
>>
>>> Summary: I'm looking for people to discuss about the parsing of math.
>>
>> The last person who really did some work on the extension was Brion Vibber. Almost all of the (limited) work that has gone into the extension over the last 1,5 year was actually based on the efforts of User:Nageh on the English wikipedia and his MathJax userscript. Beyond these MathJax changes, the extension has not seen much developer involvement for quite some while.
>>
>>> I came up with a proposal for a new version of the rendering of the
>>> <math> tag. I proposed to use LaTeXML to convert the LaTeX expressions
>>> in the math tag to MathML. If the browser is not capable of displaying
>>> MathML I use MathJaX to display the MathML output in the browser.
>>> My implementation (the LaTeXML branch) has only a few very little
>>> differences in contrast to the master branch. I have the feeling that
>>> the php code of the math extensions could be improved. For example I'd
>>> suggest to put all the texvc related stuff to another class.
>>> Furthermore I was thinking about an asynchronous rendering of the
>>> formula, which would speed up page loading time especially for major
>>> edits.
>>> At
>>> http://wiki.physikerwelt.de/images/text_math_search.pdf
>>> you find the draft of a paper where I describe in detail what
>>> I changed and why it is an improvement. The paper will appear soon in
>>> the postconference proceedings of CICM2012.
>>> Now I want to figure out, who is working on the development of the
>>> math extension, and who wants to discuss with me about our ideas.
>>> I'm open to any kind of suggestions and questions.
>>
>> Discussion is always welcomed and in this case probably best on the mailinglist.
>>
>> You seem to propose switching our current texvc -> image converter (by some users extended by using MathJax) with a LaTeX -> MathML presentational renderer that would use MathJax as a backup. The renderer would also output Content MathML to make the content easier to index and search. In general I would support this, definitely morally.
>
> I see MathJaX rather as a renering engine that supports browsers that
> do not such a good job in displaying MathML, rather than a fall back
> alternative.
>
>>
>> There are however some problems here as well.
>> - If a browser does not support MathML and not support (have enabled) Javascript, you would see nothing reading the article.
>>
>
> MathML is also capable of producing images. However this feature is
> more designed for the rendering of whole documents rather than for
> small latex snippets. So this would require a little customization.
>
>> - Browser support for MathML is still spotty. It would be nice if we can gather some actual numbers on this. There are apparently also significant bugs in rendering implementations. I believe this is one of the reasons that the default of MathJax is HTML+CSS now, and not MathML.
>>
>> - You are determining support serverside right now ? This would require fragmenting the cache when we move forward.
>
> I'm nor sure if I understand, what you mean by that. The math table
> becomes much larger as it is if you use texvc, since the matml column
> contains all the mathml code which is not really optimized with regard
> to space.
>
>>
>> - I think that currently a large group of users would fall into your MathJax group. Especially those with older browsers. However, we don't particularly like MathJax for that usergroup. It is incredibly slow on the client side and this greatly affects the userbase with less capable computers (of which we have quite a lot). This is one of the main reasons why we are not particularly pushing for this solution as a default right now (let alone as the primary backup method). I would seriously consider just skipping MathJax (at least by default) and just show images for the fallback option.
>
> MathJaX is slow if you want to display LateX stuff. If you want to
> display MathML with the help of MathJaX- that's what I propose-
> MathJaX is reasonably fast.
>>
>> - In order to provide proper MathML support, a proper font is required. Many Operating Systems do not yet have this font support. This is something that possibly could be solved with WebFonts, but will require a bit of work.
>>
>> - MathML does not, I believe, provide everything that is possible with texvc. This is another issue that we are currently seeing with MathJax, though we (Nagheh actually) has added most of them to MathJax by now. For MathML the solution seems not so simple however. This probably means we either need to phase out part of what we currently support (always complicated) or fragment the implementation for these particular situations.
>
> This would be really interesting to see which are those things, that
> can not be displayed with MathML.
>
>>
>> - I'm not aware of the current quality of LaTexML. Is there some information about the 'completeness' of the capabilities and quality of the implementation? Comparisons with other implementations ? That would be useful information.
>
> I'll provide some information soon.
>>
>> - Outputting both Presentational and Content MathML into the HTML will significantly increase the page size.
>
> This is true. I saw that in my experiments.
>
>>
>> - LaTeXML will have to be reviewed by one of the developers of the security team.
>>
>
> Yes. I think the major advantage of LaTeXML in contrast to texvc is
> that it can be run on a separate machine, with very restricted rights.
>
>> These would be the issues that I think would require assessment and solving at some point before a full solution can be deployed on Wikipedia. But of course, we can just start and expose the functionality at a later time.
>>
>> DJ
>>
>>
>> P.S. Seems that MathJax 2.1 will be released soon: http://www.mathjax.org/2012/10/01/news/mathjax-v2-1-beta-now-available-on-t…
>> _______________________________________________
>> MediaWiki-l mailing list
>> MediaWiki-l(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
> Thanks again for the feedback.
>
> Best regards
> Moritz
>
> --
> Mit freundlichen Grüßen
> Moritz Schubotz
>
> Telefon (Büro): +49 30 314 22784
> Telefon (Privat):+49 30 488 27330
> E-Mail: schubotz(a)itp.physik.tu-berlin.de
> Web: http://www.physikerwelt.de
> Skype: Schubi87
> ICQ: 200302764
> Msn: Moritz(a)Schubotz.de
--
Mit freundlichen Grüßen
Moritz Schubotz
Telefon (Büro): +49 30 314 22784
Telefon (Privat):+49 30 488 27330
E-Mail: schubotz(a)itp.physik.tu-berlin.de
Web: http://www.physikerwelt.de
Skype: Schubi87
ICQ: 200302764
Msn: Moritz(a)Schubotz.de
Moritz, thanks for your note. Forwarding to the wikitext-l list, which
is specifically interested in MediaWiki's parsing.
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
On 10/14/2012 11:45 AM, Moritz Schubotz wrote:
> Summary: I'm looking for people to discuss about the parsing of math.
>
> Dear all,
>
> I came up with a proposal for a new version of the rendering of the
> <math> tag. I proposed to use LaTeXML to convert the LaTeX expressions
> in the math tag to MathML. If the browser is not capable of displaying
> MathML I use MathJaX to display the MathML output in the browser.
> My implementation (the LaTeXML branch) has only a few very little
> differences in contrast to the master branch. I have the feeling that
> the php code of the math extensions could be improved. For example I'd
> suggest to put all the texvc related stuff to another class.
> Furthermore I was thinking about an asynchronous rendering of the
> formula, which would speed up page loading time especially for major
> edits.
>
> At
> http://wiki.physikerwelt.de/images/text_math_search.pdf
> you find the draft of a paper where I describe in detail what
> I changed and why it is an improvement. The paper will appear soon in
> the postconference proceedings of CICM2012.
> Now I want to figure out, who is working on the development of the
> math extension, and who wants to discuss with me about our ideas.
> I'm open to any kind of suggestions and questions.
>
> Best regards
> Moritz
>
> --
> Mit freundlichen Grüßen
> Moritz Schubotz
>
> Telefon (Büro): +49 30 314 22784
> Telefon (Privat):+49 30 488 27330
> E-Mail: schubotz(a)itp.physik.tu-berlin.de
> Web: http://www.physikerwelt.de
> Skype: Schubi87
> ICQ: 200302764
> Msn: Moritz(a)Schubotz.de
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Sorry for the spam, but the ContentHandler changes especially may affect
you -- if you have any time this weekend or next week to do some
testing, we'd appreciate it. Thanks.
-Sumana
-------- Original Message --------
Subject: Please notice and report big glitches - changes coming
Date: Fri, 12 Oct 2012 17:14:05 -0400
From: Sumana Harihareswara <sumanah(a)wikimedia.org>
Organization: Wikimedia Foundation
To: Coordination of technology deployments across languages/projects
<wikitech-ambassadors(a)lists.wikimedia.org>
On Monday we start deploying a new version of MediaWiki, 1.21wmf2, to
the sites, starting with mediawiki.org and 2 test wikis
(https://www.mediawiki.org/wiki/MediaWiki_1.21/Roadmap). 1.21wmf2 will
have 3 big new things in it and we need your help to test on the "beta"
test site http://deployment.wikimedia.beta.wmflabs.org/wiki/Main_Page
now to see if there are any really critical bugs.
1) The new ContentHandler (
https://www.mediawiki.org/wiki/ContentHandler ) might affect handing of
CSS and JavaScript pages, import/export (including PDF export), and API
stuff, especially when rendering and editing. I'd suggest we also look
out for issues in template rendering, images and media handling,
localisation, and mobile device access. (merged on Oct 9)
2) High-resolution image support. This work-in-progress will try to
give higher-res images to high-density screens that can support it, like
new Retina displays. More info at
https://gerrit.wikimedia.org/r/#/c/24115/ . One of the bigger risks of
the high res stuff is load-based, since we may see substantial new load
on our image scalers. So *all* image scaling might be impacted. (merged
on Oct 11)
3) "Sites" is a new backend to represent and store information about
sites and site-specific configuration. This code is meant to replace
the current interwiki code, but does not do so just yet. Still, keep an
eye out for site-specific configuration or interwiki issues.
Right now the version of MediaWiki on the beta cluster dates from 9 Oct
and thus has ContentHandler but not the high-res image support or Sites.
So please test on the beta sites now and look out for these issues on
your sites in the weeks ahead.
https://www.mediawiki.org/wiki/Category:MediaWiki_test_plans has some
ideas on how to find errors.
Thanks! With your help we can find bugs early and get them fixed before
they affect lots of readers and editors.
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
On 08.10.2012 19:12, Siebrand Mazeland (WMF) wrote:
> On Mon, Oct 8, 2012 at 6:33 PM, Daniel Kinzler <daniel(a)brightbyte.de> wrote:
>> As discussed last week with Rob, I have no prepared a merge request that
>> introduces the ContentHandler into MediaWiki core. This is a major building
>> block for the Wikidata project. I hope the merge will be completed soon, since
>> this will grow stale fast.
I would like to add a heads up:
This change deprecates some heavily used core functions and hooks, like
Revision::getText() and the ArticleSaveComplete hook. They are replaced with
equivalent functions that use Content objects instead of text. This means that a
lot of extensions will generate warnings and thus fail tests as soon as this is
in core. Once it is merged, we can start fixing these problems.
-- daniel
PS: The deployment target for this is, as far as i know, 1.21wmf2. Please check
with RobLa.