On 04/23/2013 08:52 PM, Jon Robson wrote:
Thanks for pointing out the __TOC__ magic word. Out of interest - for
what reason do we support this? It seems like a bad thing to allow
inconsistencies between page content on the same wiki.
In some list articles, where the TOC is long and where each
The things that are not the most trivial are the most challenging and fun.
I'd hate to wait for Parsoid - if anything this would help Parsoid by
defining the needs of mediawiki's parser.
I would suggest starting with just extracting table of contents and
section data into individual components...
For wider distribution!
-- Forwarded message --
From: Jon Robson jdlrob...@gmail.com
Date: Tue, Apr 23, 2013 at 5:13 AM
Subject: [WikimediaMobile] Rethinking MobileFormatter / Skins
To: mobile-l mobil...@lists.wikimedia.org
I've been playing around with skins a lot recently.
I was experimenting with using the onOutputPageParserOutput hook [1]
(running based on the current skin) and think it might be a better
approach to run the transformations on smaller chunks of data. For
instance the table of contents is known to be in the lead section so
it seems like it would be
On Tue, 23 Apr 2013 11:06:13 -0700, Yuvi Panda yuvipa...@gmail.com wrote:
For wider distribution!
-- Forwarded message --
From: Jon Robson jdlrob...@gmail.com
Date: Tue, Apr 23, 2013 at 5:13 AM
Subject: [WikimediaMobile] Rethinking MobileFormatter / Skins
To: mobile-l
Thanks for pointing out the __TOC__ magic word. Out of interest - for
what reason do we support this? It seems like a bad thing to allow
inconsistencies between page content on the same wiki. If a table of
contents is in the lead section for one article but in the third
section for another article
On Tue, Apr 23, 2013 at 2:52 PM, Jon Robson jdlrob...@gmail.com wrote:
Thanks for pointing out the __TOC__ magic word. Out of interest - for
what reason do we support this? It seems like a bad thing to allow
inconsistencies between page content on the same wiki. If a table of
contents is in
Daniel
Great to hear I'm not alone in my thoughts. Things like the edit
section link shouldn't have to be hacked in at the parser level - if
the parser returned the components of a page it would be trivial for
the skin to add these itself.
The fact you are resorting to hacks to do things which
It's an interesting idea. Though it won't be trivial. But we could start
to express the parser output of pages as high level components nested in
each other. Like a document with a TOC nested in it, as well as high-level
headers (or maybe sections), emeded image frames, etc... where things
