Create a VisualEditor plugin to integrate with ProofreadPage
OpenPublic

Description

Page: pages are not plain wikitext pages but are split into three textareas: header, footer and body and a proofreading level tag (note 1).
So, an adaptation of the VisualEditor to these pages is needed in order to make edition of the pages work.

The UI need to be tweaked in order to allow the splitting of the main textarea into three and the edition of the Proofreading level at the save of page as it works currently for wikitext editing (example: https://en.wikisource.org/w/index.php?title=Page:La_Fontaine_-_The_Original_Fables_Of,_1913.djvu/20&action=edit ).

An other useful (but less important thing) things is to add modules to the Visual Editor to support specific tags used by Wikisource like <pages>, <section> and <poem>.

note 1: structure of the page as save in the database:
<noinclude><pagequality level="LEVEL" user="LAST PROOFREADER" />HEADER<div class="pagetext">BODY<noinclude>FOOTER</noinclude>


Version: unspecified
Severity: enhancement

bzimport added a subscriber: wikibugs-l.
bzimport set Reference to bz46580.
Tpt created this task.Via LegacyMar 26 2013, 8:31 PM
Billinghurst added a comment.Via ConduitMar 27 2013, 9:49 AM

How would we go with looking to put the user into the API? That information would be useful to present through the 'page information' so it is presentable via 'action=info'. At the moment one has to pull the page data to get the user info, while the proofread status is already captured. Well that is my limited understanding of the data.

MZMcBride added a comment.Via ConduitMar 28 2013, 5:50 AM

(In reply to comment #0)

note 1: structure of the page as save in the database:
<noinclude><pagequality level="LEVEL" user="LAST PROOFREADER" />HEADER<div
class="pagetext">BODY<noinclude>FOOTER</noinclude>

This data should be in a queryable format. The current format sucks and should be abandoned. If there's not already a bug filed about this, please file one.

(In reply to comment #1)

How would we go with looking to put the user into the API? That information
would be useful to present through the 'page information' so it is
presentable via 'action=info'. At the moment one has to pull the page data to
get the user info, while the proofread status is already captured. Well that
is my limited understanding of the data.

action=info is part of index.php, not api.php. That is, the info action is part of the (graphical) user interface, not part of the MediaWiki API. This bug should just be about a single issue. Adding this type of information to the info action can be a dependent bug of this bug. There may be such a page filed already, maybe.

Basically, once the data is queryable, both the info action and the MediaWiki API modules can pull the data out easily. But that's at least three separate bugs (and probably many more).

Tpt added a comment.Via ConduitMar 30 2013, 3:33 PM

(In reply to comment #2)

This data should be in a queryable format. The current format sucks and should
be abandoned. If there's not already a bug filed about this, please file one.

Done (bug 46724). But before doing anything on this direction, a refactoring of the wikitext edition interface is needed because the current system is closely based on this storage format (bug 46578).

Add Comment

Column Prototype
This is a very early prototype of a persistent column. It is not expected to work yet, and leaving it open will activate other new features which will break things. Press "\" (backslash) on your keyboard to close it now.