“long-term we are trying to
make template nesting more sane.”
for now, do you have a list that which templates should emit properly
nested output?
On Thu, Sep 19, 2013 at 8:01 PM, <wikitext-l-request(a)lists.wikimedia.org>wrote;wrote:
Send Wikitext-l mailing list submissions to
wikitext-l(a)lists.wikimedia.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.wikimedia.org/mailman/listinfo/wikitext-l
or, via email, send a message with subject or body 'help' to
wikitext-l-request(a)lists.wikimedia.org
You can reach the person managing the list at
wikitext-l-owner(a)lists.wikimedia.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Wikitext-l digest..."
Today's Topics:
1. Re: Wikitext-l Digest, Vol 36, Issue 6 (C. Scott Ananian)
----------------------------------------------------------------------
Message: 1
Date: Wed, 18 Sep 2013 10:34:34 -0400
From: "C. Scott Ananian" <cananian(a)wikimedia.org>
To: Parsoid and wikitext discussion <wikitext-l(a)lists.wikimedia.org>
Subject: Re: [Wikitext-l] Wikitext-l Digest, Vol 36, Issue 6
Message-ID:
<CAK5kH3xtBdkd4MEKCV2wgxnZNoZws=
Fa+LWahncb4tZ--hKdYQ(a)mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
On Wed, Sep 18, 2013 at 7:51 AM, Feng Yi <zlfengyi(a)google.com> wrote:
I have another two question:
1. According to the roadmap, you will research the “HTML-only wiki
support” and “DOM-based templating”. Does it mean that if you launch
these
functions, wikitext will no longer be supported,
even the round-trip
doesn’t work?
At least initially, HTML-only wiki support will mean that it is *possible*
to install an HTML-only wiki, not that it is required.
DOM-based templating is an orthogonal issue; long-term we are trying to
make template nesting more sane.
2. In “MediaWiki_DOM_spec” there are a lot of discussing and implemented
status. Will the parsoid output change a lot in
the future? What is the
approximate percentage?
Sections which are not explicitly marked w/ discussion or 'implementing'
are expected to remain stable. We reserve the right to change the spec if
needed, but most of it is in production use and working satisfactorily and
is not expected to change. The most in-flux bits are the bits which are
not currently implemented and/or supported by Visual Editor. Our process
is to work out a spec proposal with the Visual Editor team, implement it in
Parsoid, then implement support for the new feature in Visual Editor.
During these stages the spec is often found deficient in some way and is
fixed. Once the feature lands in Visual Editor and is deployed, we have
reasonable confidence that the spec is correct and will not need to be
changed further.
--scott
--
(
http://cscott.net)