This has just been brought to my attention by some friends in India,
who are considering to use it to create a DVD version of Wikipedia:
http://wikifilter.sourceforge.net/
>From the description: "WikiFilter is both a wiki text parser and a web
filter. It converts wiki text stored in a wiki data-base (dump) file
into html text, and sends the html text to the web browser." The
program is written in C. There's also an indexing component. I haven't
tested it, but it looks like it could be a useful module for a DVD
edition; the parser component might also be interesting for other
purposes.
Erik
An automated run of parserTests.php showed the following failures:
Running test Table security: embedded pipes (http://mail.wikipedia.org/pipermail/wikitech-l/2006-April/034637.html)... FAILED!
Running test Link containing double-single-quotes '' (bug 4598)... FAILED!
Running test Template with thumb image (wiht link in description)... FAILED!
Running test message transform: <noinclude> in transcluded template (bug 4926)... FAILED!
Running test message transform: <onlyinclude> in transcluded template (bug 4926)... FAILED!
Running test BUG 1887, part 2: A <math> with a thumbnail- math enabled... FAILED!
Running test Language converter: output gets cut off unexpectedly (bug 5757)... FAILED!
Running test HTML bullet list, unclosed tags (bug 5497)... FAILED!
Running test HTML ordered list, unclosed tags (bug 5497)... FAILED!
Running test HTML nested bullet list, open tags (bug 5497)... FAILED!
Running test HTML nested ordered list, open tags (bug 5497)... FAILED!
Running test Parsing optional HTML elements (Bug 6171)... FAILED!
Running test Inline HTML vs wiki block nesting... FAILED!
Running test Mixing markup for italics and bold... FAILED!
Running test 5 quotes, code coverage +1 line... FAILED!
Running test HTML Hex character encoding.... FAILED!
Running test dt/dd/dl test... FAILED!
Passed 409 of 426 tests (96.01%) FAILED!
On 13/07/06, rotem(a)svn.leuksman.com <rotem(a)svn.leuksman.com> wrote:
> * Using "internationalisation" instead of "internationalization", for Rob Church.
There aren't really many responses to that I can make apart from the
following. And given that I've had just about enough, I think I'll
make it, and to hell with the consequences. I will absolutely not
allow a third person to start abusing me and get away with it
unscathed.
You. Fucking. Wanker.
Now, let me rationalise. The current method of adding i18n for
extensions is better than what we had before, but it sucks a little
bit still. It sucks 'cause people downloading the extensions still
have to download a load of shit that they aren't interested it.
You broke backwards compatibility with extensions before and you're
doing it again. Granted you aren't the only one, but your
implementation is a mess. I'm sorry to say it, but it's the bloody
truth.
How dare you start making snide remarks because I happen to use
British English spelling? How bloody dare you?
I've had enough of this, I'm going on a 3 month break.
Rob Church
I've run a cleanup script to fix uploaded image records with invalid titles,
uploaded under older, buggier versions of MediaWiki. These fell into mainly
these categories:
* Filenames with %HH hex codes
* Filenames with non-normalized Unicode sequences
* Filenames with Latin-1 encoding
* Blank database entries
* Filenames with other illegal chars ("[" and "{")
Where the file could not be located, the entry was removed from the database.
Where it was present, the filename was normalized and the record and the file
renamed. Names conflicting with existing titles have had a number appended.
Complete list of changes (be sure to view in UTF-8):
http://download.wikimedia.org/tools/bad-image-fixes.txt
-- brion vibber (brion @ pobox.com)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Language select allows users to hide foreign languages on multilingual
pages. This would, for example, allow a French reader to see only French
text on multilingual pages (though they would still see Spanish on a
Spanish-only page). (as seen from
http://meta.wikimedia.org/wiki/Meta:Language_select )
The feature's been implemented and is currently live on Meta, however,
the version control currently is happening privately on my own machine.
Since it is licensed under an open license (at least implicitly, since
it's been posted on the site), I would like to make the repository public.
I was going to open a SourceForge project, but then it occurred to me
that if it was going to be mainly deployed on Wikimedia websites, why
not store the code on Wikimedia's SVN server?
So my question is would it be feasible to store the code as an extension
Javascript file in the repository? This would mean that if multiple
projects wanted to use the code, all they would have to do is include an
extra Javascript file, rather than have the entire code copied out on
Monobook.js . And also, of course, would it happen?
- --
Edward Z. Yang Personal: edwardzyang(a)thewritingpot.com
SN:Ambush Commander Website: http://www.thewritingpot.com/
GPGKey:0x869C48DA http://www.thewritingpot.com/gpgpubkey.asc
3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFEtcKiqTO+fYacSNoRAsyzAJ9fwfZfCOFppjX77R+rtw446rVxtACfS2cC
TCpBj0/swqjx+da2eWLXBrg=
=aiUi
-----END PGP SIGNATURE-----
An automated run of parserTests.php showed the following failures:
Running test Table security: embedded pipes (http://mail.wikipedia.org/pipermail/wikitech-l/2006-April/034637.html)... FAILED!
Running test Link containing double-single-quotes '' (bug 4598)... FAILED!
Running test Template with thumb image (wiht link in description)... FAILED!
Running test message transform: <noinclude> in transcluded template (bug 4926)... FAILED!
Running test message transform: <onlyinclude> in transcluded template (bug 4926)... FAILED!
Running test BUG 1887, part 2: A <math> with a thumbnail- math enabled... FAILED!
Running test Language converter: output gets cut off unexpectedly (bug 5757)... FAILED!
Running test HTML bullet list, unclosed tags (bug 5497)... FAILED!
Running test HTML ordered list, unclosed tags (bug 5497)... FAILED!
Running test HTML nested bullet list, open tags (bug 5497)... FAILED!
Running test HTML nested ordered list, open tags (bug 5497)... FAILED!
Running test Parsing optional HTML elements (Bug 6171)... FAILED!
Running test Inline HTML vs wiki block nesting... FAILED!
Running test Mixing markup for italics and bold... FAILED!
Running test 5 quotes, code coverage +1 line... FAILED!
Running test HTML Hex character encoding.... FAILED!
Running test dt/dd/dl test... FAILED!
Passed 409 of 426 tests (96.01%) FAILED!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rob Church, please calm down. It's not good to edit war over software,
because unlike Wikis, you can't tack on a "Disputed" tag. ;-)
The internationalization is quite welcome, but perhaps the extension
developers should agree on a I18N scheme and mandate it for all
extensions? (Or, even better, have a lead developer lay down the law of
the land.)
Looking at the code, I do somewhat agree with Church's assertion.
Ideally speaking, messages should only be parsed (and defined) when they
are needed. However, they really shouldn't pollute the global namespace
(although I'm not precisely sure how you would get around that. The
MediaWiki core messages are also added to the global namespace.)
- --
Edward Z. Yang Personal: edwardzyang(a)thewritingpot.com
SN:Ambush Commander Website: http://www.thewritingpot.com/
GPGKey:0x869C48DA http://www.thewritingpot.com/gpgpubkey.asc
3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFEtwRyqTO+fYacSNoRArjtAJ9vx5XesIm5zcBQXU0YO0lxoUwqOgCeJ/ZL
cvAUV+Q3jJJH8ri6Ll2uqB4=
=HCdD
-----END PGP SIGNATURE-----
Further to the above, the 8 hex digits of *.ipt.aol.com addresses appear
simply to be their public IP addresses written in hex (0xAC = 172).
This supports the idea that these addresses are just dynamically
assigned client computer IP addresses, as their address range suggests.
This suggests that these addresses should be treated in the future in
the same way as those of cable modem accounts.
-- Neil
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rob Church wrote:
> Given our current attitude, it seems you'd get Subversion access if
> you offered to blow your nose in the name of MediaWiki.
Erm... ::offers to blow nose in the name of MediaWiki?:: Subversion
access would be very nice.
> We don't typically do per-folder permissions; we just trust people not
> to fuck up code they don't understand or touch stuff they're not
> supposed to.
I'd have no problem self-enforcing. My main trouble is remembering to
set my editor to use tabs instead of spaces when editing MediaWiki code.
> However, I'd vouch for your sanity and ability to keep your sticky
> fingers to yourself, and I want to see some proof of concept code for
> this.
Actually, the proof of concept code is already live on Meta. You can
view the Javascript at MediaWiki:Monobook.js (
http://meta.wikimedia.org/w/index.php?title=MediaWiki:Monobook.js&action=re…
, scroll down ).
- --
Edward Z. Yang Personal: edwardzyang(a)thewritingpot.com
SN:Ambush Commander Website: http://www.thewritingpot.com/
GPGKey:0x869C48DA http://www.thewritingpot.com/gpgpubkey.asc
3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFEtkFLqTO+fYacSNoRAh+aAJ9HpKuos2rPYOZ3MOTiKIkqYl+lhACeIRkj
mVOyOtUQZMSRAzzbxXkibc8=
=14vK
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> I'd love to have this in the MediaWiki core, we were discussing just a few
> days ago how much a feature like this would help Commons. Adding a
> javascript variable describing the user's currently selected language is on
> my to do list, for this exact application.
>
> I think we could put a loader stub in wikibits.js and have the bulk of the
> feature in a separate file, how does that sound?
Sounds great. Does that mean I'd get SVN access (even if it's just for
that extension folder) to maintain it?
- --
Edward Z. Yang Personal: edwardzyang(a)thewritingpot.com
SN:Ambush Commander Website: http://www.thewritingpot.com/
GPGKey:0x869C48DA http://www.thewritingpot.com/gpgpubkey.asc
3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFEtjZJqTO+fYacSNoRAk97AKCJw+row1Ny90wkdmpTUp/EYJo5EgCbBJiV
As1K7wMGw6+pPd/sgMHqbzU=
=CZTe
-----END PGP SIGNATURE-----