Exactly: The HTML to wikitext conversion is what makes Parsoid useful, and
not only for VE.
Thanks to Parsoid, ContentTranslation has a simple rich text editor with
contenteditable (not a full VE, though this may change in the future). We
are just starting to deploy it to production, but the users who tested in
beta labs loved it.
The Parsoid way of converting wikitext to HTML is useful, too, because it
allows ContentTranslation to process the article that is being translated
in a formal and expected way, understanding where are links, images,
templates, timelines, references, etc., and adapting it automatically to
the translated article. All of this is done with simple jQuery selectors
and very little effort.
בתאריך 20 בינו 2015 04:01, "Matthew Flaschen" <mflaschen(a)wikimedia.org>
כתב:
On 01/19/2015 08:15 AM, MZMcBride wrote:
Currently Parsoid is the largest client of the
MediaWiki PHP parser, I'm
told. If Parsoid is regularly calling and relying upon the MediaWiki PHP
parser, what exactly is the point of Parsoid?
Parsoid can go:
wikitext => HTML => wikitext
The MediaWiki parser can only go:
wikitext => HTML
The most important part of Parsoid is thus the HTML => wikitext conversion
(required for VisualEditor), but other parts of their architecture follow
from that.
And from this question flows another: why is Parsoid
calling MediaWiki's api.php so regularly?
I think it uses it for some aspects of templates and hooks. I'm sure the
Parsoid team could explain further.
Matt Flaschen
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l