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
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
Matthew Flaschen wrote:
On 01/19/2015 08:15 AM, MZMcBride wrote:
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.
I've been discussing
After 18 months of MediaWiki release management handled externally by
Markus Glaser and Mark Hershberger, we have agreed to bring the
MediaWiki release work back to the Wikimedia Foundation. From now on,
the Release Engineering team coordinated by Greg Grossmeier, which is
responsible for the WMF
On 19 January 2015 at 01:46, Jay Ashworth j...@baylink.com wrote:
Aha! Sorry; I was behind on Parsoid, was the problem. Yeah, if there's
a way to edit in MWtext, both for humans and programs, then that serves the
use cases I would be concerned about. Thanks for the prompt clarification,
Tim Starling wrote:
Note that feature parity with Wikipedia has not been possible in pure
PHP since 2003, when texvc was introduced. And now that we have
Scribunto, you can't even copy an infobox template from Wikipedia to a
pure-PHP hosted MediaWiki instance. The shared hosting environment has
I felt I should respond to this...
I run about a dozen MediaWiki wikis singlehandedly. I've been using
MediaWiki since 2005, and I think only once did I run into a substantial
problem doing an upgrade. Upgrading has only gotten easier over the
years, too... and I use a lot of extensions,
(Combining pieces of Jay's thread and pieces of the shared hosting thread.)
Daniel Friesen wrote:
Parsoid can do Parsoid DOM to WikiText conversions. So I believe the
suggestion is that storage be switched entirely to the Parsoid DOM and
WikiText in classic editing just becomes a method of
Il 19/01/2015 19:00, Tyler Romeo ha scritto:
On Wed, Dec 17, 2014 at 11:57 AM, Ricordisamoa ricordisa...@openmailbox.org
wrote:
* Given that the W3C Validator can also parse HTML files, would it be
useful to validate wiki pages as well? Even if sometimes the
validation errors appear
On Wed, Dec 17, 2014 at 11:57 AM, Ricordisamoa ricordisa...@openmailbox.org
wrote:
* Given that the W3C Validator can also parse HTML files, would it be
useful to validate wiki pages as well? Even if sometimes the
validation errors appear to be caused by MediaWiki itself, they can
If I might weigh in, I concur with MZMcBride. If Parsoid is absolutely needed
regardless, that's one thing, but if a VE editing interface can be set up that
doesn't need Parsoid, that would reduce dependence on third party software,
make installation easier for all parties concerned, and not be
Hey,
On my local wiki I have a page with the name File:Blue marker.png. The
following code returns false:
$title = Title::makeTitle( NS_FILE, $file );
$title-exists();
That used to return true in the past. Not sure what is broken - my wiki or
MediaWiki itself.
What I want to do is go from
Somebody can correct me, but:
$title = Title::makeTitle( NS_FILE, $filename );
$file = wfLocalFile( $title );
$file-getUrl();
// $file-getFullUrl();
// ...
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
On Mon, Jan 19, 2015 at 1:45 PM, Jeroen De
Don't know, if that's the correct way, but it is done in SRF for the
excel format:
https://github.com/SemanticMediaWiki/SemanticResultFormats/blob/master/formats/excel/SRF_Excel.php#L249
On 19 January 2015 at 19:45, Jeroen De Dauw jeroended...@gmail.com wrote:
Hey,
On my local wiki I have a
14 matches
Mail list logo