I have some general Parsoid questions I hoped someone here might help me
with.
The background is that we are doing some preliminary work looking at how
Text-to-Speech might work on Wikipedia (there will be some info online in
the coming weeks).
One detail of this is that you might occasionally have to highlight
specific words/sentences that are dealt with differently (e.g. World War
III -> World War 3). It is still unclear how frequent such things would be
but if they are very frequent then there would likely be push-back from the
community if this is stored in the normal wikitext.
In this case we would have to store the markup outside of the wikitext and
any viewing/editing of it would have to happen in some user enabled
extension of the normal environment.
And here we come to the question.
1. If we would have to store this markup outside of the wikitext could this
be done by storing the individual parsoid-data-units?
2. Would it be possible to add these units to the existing parsoid-data
(which gets loaded from the wikitext) when loading a page?
3. Would it be possible to detect which of these units would be affected by
edits to the wikipage?
This is still in the early stages so mainly we are looking at what
possibilities exist should we need them. Using Parsoid data was something
we thought of as a light-weight solution to having to store a synced copy
of the wikitext+additional markup.
Cheers,
André
André Costa | GLAM-tekniker, Wikimedia Sverige | Andre.Costa(a)wikimedia.se |
+46 (0)733-964574
Stöd fri kunskap, bli medlem i Wikimedia Sverige.
Läs mer på blimedlem.wikimedia.se
* Do you have small, self-contained, "easy" bugs you'd love to get fixed?
(Also see https://www.mediawiki.org/wiki/Annoying_little_bugs )
* Does your documentation need improvements?
* Do your old bugs welcome some testing?
* Does your user interface have some small design issues?
* Does the Outreachy/GSoC project you finished welcome small tweaks?
* Would you enjoy helping someone port your template to Lua?
* Does your gadget use some deprecated API calls?
* Do you have some tasks that welcome some research?
Google Code-In (GCI) will take place again in Dec+Jan: a contest for
13-17 year old students to provide small contributions to free software
projects.
Wikimedia will apply again to take part in GCI. The more tasks we can
offer the likelier the changes Wikimedia will get accepted.
Unsure about quality of contributions and effort?
Read about tgr's post about Multimedia achievements in GCI 2014:
https://lists.wikimedia.org/pipermail/multimedia/2015-January/001009.html
In short:
* Add the project "GCI2015" + a comment to Phabricator tasks you'd mentor.
* Tasks are welcome in five areas: Code; Outreach/Research;
Documentation/Training; Quality Assurance; User Interface.
* Make sure the task description provides pointers to help the student.
* Add yourself to the table of mentors on the wikipage.
* "Beginner tasks" (<30 min for an experienced contributor) also welcome.
* "Generic" tasks also welcome (e.g. "Fix two user interface messages from
the "Blocked By" list in https://phabricator.wikimedia.org/T40638 ").
For all information, check
https://www.mediawiki.org/wiki/Google_Code-in_2015#Mentors.27_corner
Can you imagine providing a helping hand to someone fixing tasks?
Please ask if you have questions!
Thank you!
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/