simetrical(a)svn.wikimedia.org wrote:
> (bug 6873) When viewing old revisions, add link to diff to current version.
[snip]
> -'old-revision-navigation' => 'Revision as of $1; $5<br />($6) $3 | $2 | $4 ($7)',
> +'old-revision-navigation' => 'Revision as of $1; $5<br />($6) $3 | $2 ($8) | $4 ($7)',
A note: changing the existing message this way means that customized
versions will not show the new functionality.
If it's important to add, it may be more appropriate to rename the message.
Actually this message should probably be broken up anyway; it seems
badly factored to me, mixing a line of text and what should probably be
a programmatic line of links into a single HTML message.
-- brion vibber (brion @ pobox.com)
On Sat, Nov 18, 2006 at 02:17:46AM +0800, Tian-Jian Barabbas Jiang@Gmail wrote:
> http://taipedia.info/mediawiki/index.php/Template:Languages
So, who wants to petition ICANN to start the .pedia TLD?
Cheers,
-- jr 'http://en.wiki.pedia' a
--
Jay R. Ashworth jra(a)baylink.com
Designer Baylink RFC 2100
Ashworth & Associates The Things I Think '87 e24
St Petersburg FL USA http://baylink.pitas.com +1 727 647 1274
"That's women for you; you divorce them, and 10 years later,
they stop having sex with you." -- Jennifer Crusie; _Fast_Women_
Sun Microsystems will make all the Java code they own available under the GPL:
http://www.sun.com/software/opensource/java/
This is a very major step. IMHO we should now make Java core part of
our own strategy, as it's one of the best ways to deliver interactive
content (high quality animations, learning tools, etc.). There are
large numbers of free applets that we can potentially use, esp. in
Wikipedia and Wikiversity.
My main question is: Are there security considerations with enabling
the upload and embedding of Java Applets? According to
http://java.sun.com/sfaq/
one of the capabilities of applets is to open a connection to the
originating host. Could this be used, e.g., to create auto-vandalism
applets and if so, can we somehow protect against it?
If security is a major issue, might it be feasible to maintain a
whitelist of certificates (to allow applets from trusted authority to
be uploaded directly), and to flag all other applets as
"non-embeddable" until a sysop flips a switch, so they can be reviewed
for security? We could add a big fat warning on the file description
page.
--
Peace & Love,
Erik
Member, Wikimedia Foundation Board of Trustees
DISCLAIMER: Unless otherwise stated, all views or opinions expressed
in this message are solely my own and do not represent an official
position of the Wikimedia Foundation or its Board of Trustees.
Rob Church says use Special:Prefixindex.
However that will work no better than the Special:Allpages I mentioned
in the bug report, i.e., not at all, as my thousand plus categories
are all "empty pages".
So please don't brush Bug 7951 off as INVALID so fast.
An automated run of parserTests.php showed the following failures:
Reading tests from "/home/brion/src/wiki/phase3/maintenance/parserTests.txt"...
Running test TODO: Table security: embedded pipes (http://mail.wikipedia.org/pipermail/wikitech-l/2006-April/034637.html)... FAILED!
Running test TODO: Link containing double-single-quotes '' (bug 4598)... FAILED!
Running test TODO: Template with thumb image (with link in description)... FAILED!
Running test TODO: message transform: <noinclude> in transcluded template (bug 4926)... FAILED!
Running test TODO: 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 TODO: HTML bullet list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML ordered list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML nested bullet list, open tags (bug 5497)... FAILED!
Running test TODO: HTML nested ordered list, open tags (bug 5497)... FAILED!
Running test TODO: Parsing optional HTML elements (Bug 6171)... FAILED!
Running test TODO: Inline HTML vs wiki block nesting... FAILED!
Running test TODO: Mixing markup for italics and bold... FAILED!
Running test TODO: 5 quotes, code coverage +1 line... FAILED!
Running test TODO: dt/dd/dl test... FAILED!
Running test TODO: Images with the "|" character in the comment... FAILED!
Running test TODO: Parents of subpages, two levels up, without trailing slash or name.... FAILED!
Running test TODO: Parents of subpages, two levels up, with lots of extra trailing slashes.... FAILED!
Running test TODO: Don't fall for the self-closing div... FAILED!
Running test TODO: Always escape literal '>' in output, not just after '<'... FAILED!
Reading tests from "/home/brion/src/wiki/phase3/extensions/Cite/citeParserTests.txt"...
Passed 449 of 469 tests (95.74%)... FAILED!
Spilling out of my unblock-en-l experience...
It would be useful for block messages that blocked users receive to
display some sort of block-unique ID number to the user (say, the
ipb_id value), so that if they report it to admins (say, via
unblock-en-l) we can go search on that key and not have to wallow
around for a while figuring out what IP block or autoblock bit the
person.
I was wandering around trying to understand the blocking code to
suggest diffs, but it's given me a worse headache, so I'm just going
to suggest it for now rather than trying to impliment...
--
-george william herbert
george.herbert(a)gmail.com
I realize full well that obsessing about one's edit summaries is
a sign of, well, obsession, and I'm not about to propose a way of
editing them, but given that their formatting rules are subtly
different from normal wikitext (special treatment of /* */,
evidently no treatment of ''...'', automagic insertion of
the → character, etc.), it seems like it would be nice (but also
benign) to show a preview of the edit summary along with the rest
of the page when doing Show Preview. Is this too goofy an idea?
An automated run of parserTests.php showed the following failures:
Reading tests from "/home/brion/src/wiki/phase3/maintenance/parserTests.txt"...
Running test TODO: Table security: embedded pipes (http://mail.wikipedia.org/pipermail/wikitech-l/2006-April/034637.html)... FAILED!
Running test TODO: Link containing double-single-quotes '' (bug 4598)... FAILED!
Running test TODO: Template with thumb image (with link in description)... FAILED!
Running test TODO: message transform: <noinclude> in transcluded template (bug 4926)... FAILED!
Running test TODO: 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 TODO: HTML bullet list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML ordered list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML nested bullet list, open tags (bug 5497)... FAILED!
Running test TODO: HTML nested ordered list, open tags (bug 5497)... FAILED!
Running test TODO: Parsing optional HTML elements (Bug 6171)... FAILED!
Running test TODO: Inline HTML vs wiki block nesting... FAILED!
Running test TODO: Mixing markup for italics and bold... FAILED!
Running test TODO: 5 quotes, code coverage +1 line... FAILED!
Running test TODO: dt/dd/dl test... FAILED!
Running test TODO: Images with the "|" character in the comment... FAILED!
Running test TODO: Parents of subpages, two levels up, without trailing slash or name.... FAILED!
Running test TODO: Parents of subpages, two levels up, with lots of extra trailing slashes.... FAILED!
Running test TODO: Don't fall for the self-closing div... FAILED!
Running test TODO: Always escape literal '>' in output, not just after '<'... FAILED!
Reading tests from "/home/brion/src/wiki/phase3/extensions/Cite/citeParserTests.txt"...
Passed 449 of 469 tests (95.74%)... FAILED!
I've reverted r17507 and r17518 after getting massive complaints
immediately after they went live in today's site update.
I'd like to ask that people please try to refrain from changing core
styles like this without testing it against the actual site usage; for
instance the prominent main pages of English and German Wikipedia and
their site-specific CSS/JS.
We've gone through this dance enough times in the last few weeks I think
we should all be able to realize that it's kind of disruptive and should
be avoided.
-- brion vibber (brion @ pobox.com)