i thought tag extensions can output what they want, and that it is not processed as wiki text.
R&D, Qlusters Inc.
+972-3-6081994 Fax: +972-3-6081841
www.openqrm.org - Data Center Provisioning
I have identified an organization which is willing to spend up to
about EUR 10,000 on adding support for exporting MediaWiki pages as
PDF files, and improving document management for documents consisting
of multiple pages.
My current thinking is that the functionality implemented, as a
minimum, would be as follows:
a) Using an extension, integrate of a "PDF link" on any wiki page
which would call an external library like HTMLDOC on a single wiki
b) Support filters on the rendered HTML (replacing image thumbnails
with high resolution images, filter content by regular expression,
etc.), and revision filters (export last revision edited by user on
whitelist Y, or approximating currentdate-Z)
c) Create a "PDF basket" UI which makes it possible to compile a PDF
from multiple pages easily (and rearrange the pages in a hierarchy).
The resulting structures could potentially also be stored as wikitext,
using a new <structure> extension tag, so that they can be used both
by individuals compiling PDFs for personal use, and by groups
collaborating on complex documents.
Possibly some budget could also be allocated for improving the
external PDF library used, especially if we can allocate additional
funds for this project.
I'd like to request comments on this approach, specifically:
- Besides HTMLDOC, do you know a good (X)HTML-to-PDF library which
could be used for this purpose?
- Within this budget, do you believe an alternative approach which
utilizes an intermediate format is viable (e.g.
wiki-to-Docbook-to-PDF), given the complexity of the MediaWiki syntax,
its various extensions, and the need to keep up with parser changes?
- If you are a developer, would you be interested in working on this
project, and available to do so? (If so, please contact me privately.)
Any other comments would also be appreciated.
Peace & Love,
DISCLAIMER: This message does not represent an official position of
the Wikimedia Foundation or its Board of Trustees.
I use (but don't administrate) wiki.lspace.org, which runs MediaWiki 1.9.0.
I'd like to receive an email whenever a page on my watchlist
changes. Can this be done?
I didn't see it as an option under Preferences/Watchlist. Does the
administrator need to turn on some setting to make this possible?
Can I tell by looking at "Special:Version" whether this feature is
We're just a Bunch Of Regular Guys, a collective group that's trying
to understand and assimilate technology. We feel that resistance to
new ideas and technology is unwise and ultimately futile.
I try to utilize the STSGMassMailer
(http://meta.wikimedia.org/wiki/STSGMassMailer) extension in mediawiki
When I access the dedicated special page MassMailer it pops up with no email
Does it require a special user group to work?
Does anyone have experience with that extension?
New famous last words....
"Wikipedia said it was edible"
I saw that quote as someone's signature on Slashdot a little while ago.
It made me laugh hysterically and I wanted to share.
I apologize if there are rules against submitting non-technical e-mails
like this on this forum.
The ajax TeX Editor extension
has been adapted to work on mw 1.9.0.
Viel oder wenig? Schnell oder langsam? Unbegrenzt surfen + telefonieren
ohne Zeit- und Volumenbegrenzung? DAS TOP ANGEBOT JETZT bei Arcor: günstig
und schnell mit DSL - das All-Inclusive-Paket für clevere Doppel-Sparer,
nur 44,85 inkl. DSL- und ISDN-Grundgebühr!
I'd like to set up multiple (OK, two) wiki sites running on the same
server. We can use the same version of the wiki software (one will be
1.6.3 until I get around to upgrading it, the other will be 1.6.x where
x is the latest 1.6 release), so don't need to worry about running
different PHP/MySQL versions. Now the questions:
1) It looks like the best way is to set up another wiki directory with
another copy of the wiki software etc. in it, and do whatever apache
hoodoo is needed to direct requests to that wiki copy. That sound right?
We'll probably simply use the ip number of the machine, rather than
getting a new domain name, as the new wiki will be private. But I'll
worry about that when the time comes.
2) It would seem that all I would need to worry about with MySQL is to
make sure I set up the new wiki with a new database, but otherwise not
need to fiddle with MySQL. Is this correct?
3) Biggest thing is that I need to ensure the new wiki is private--it
will contain very private stuff. (If I told you what, I'd have to kill
you. I know, an old line, but it never ceases to be funny to
double-digit IQs such as my own.) Opinions on this? Aside from the
general machine setup (which I'm as sure I can be is reasonably secure),
would it be best to use Mediawiki security features, or should I instead
go into the Apache side of things? And are there any special things I
need to look at to ensure that users of the public wiki cannot somehow
access the private wiki? (I'm guessing not, since the wiki code and
databases will be completely separate, but one wants to be sure...)
In advance, many thanks,