I've just committed a bunch of new stuff to CVS:
1) "Edit this section". If you enable the user preference "Show links for
editing individual sections", you get little "edit" links under each
article section. These can be used to fetch just the text of that section,
and edit it. No more scrolling through 30 K articles to edit a typo. No
more wading through long discussion threads to add a short comment
(provided they are organized using headlines).
2) Automatic table of contents. If the option "Show table of contents for
articles with more than 3 headings" is enabled, a small TOC is added on
top of the page with navigation links to the individual sections. From
this it follows logically that we now have
3) Anchors for each article section (named after the section title, e.g.
"External links" becomes "External_links"). So you can link to these from
Tim Starling wrote:
>I've written some PHP code to convert date formats from those typed to a
>user preference. A demonstration is now available at:
>There's also some information at:
>Any comments would be appreciated. There's just a few minor things left to
>do: for example I want to have an option in LocalSettings.php to disable it.
I haven't seen your code, but if you haven't already done so I highly
recommend putting the guts of this into Language.php, so it doesn't
clutter up the common code, and so other languages that want such an
option can adapt it cleanly.
The user option should also override the sitewide setting in
Language::date() ($wgAmericanDates true or false -- incidentally,
although there were terrible flame wars a few months ago when it was
suggested to change the date format used to display timestamps from
American to British order, I've not heard a peep since the default got
flipped during the server upgrade over a month ago.)
>Can I please have whatever access is necessary to enable me to install this
>on test.wikipedia.org, and ultimately on the live server?
I'll see about setting up a login for you. (Erik probably should get
-- brion vibber (brion @ pobox.com)
I just wondered whether ppl think it's a good idea to copy wiki.png to
the installation path when calling the update script ("php4
update.php"). IMHO it isn't. A working setup will likely have a
customized logo that it doesn't want overwritten. IMHO only code should
Alternatively we could just change the copyfile method so it doesn't
abort if a file can't be written.
Any comments, criticism, ideas, hints, objections? Else I'll just
comment the concerning line out.
For quite some time, we've been outputting HTML pages with a
half-doctype declaration, with no DTD specified:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
Browsers interpret such a doctype as not quite reliable, and render
pages in so-called "quirks" mode for backwards compatibility with the
parsing and rendering bugs of earlier versions. It's been occasionally
suggested that it's superior to include also a URL to the DTD, which
will put browsers into a stricter, standards-compliant mode:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
A couple days ago I slipped this in. All well and good in Mozilla, but
in Internet Explorer 6.0 (I haven't tried 5.x) this triggers a selection
bug, such that trying to select text with the mouse selects everything
from the beginning of the document to the point where you've got the
mouse, instead of the portion of text you're dragging over. Not very
Since, unfortunately, a lot of people use this dreadful program, and
this is a _really_ annoying browser bug, I've temporarily taken the DTD
reference back out, so we're back to quirks mode, where selection works.
-- brion vibber (brion @ pobox.com)
OK, preliminary version running at test.wikipedia.org.
I suggest starting at
which already has the categories Biology and Medicine (see top bar). Following such a link, you'll go to "Category:Biology" / "Category:Medicine", which are normal articles, except they have an automatically generated list of articles in that category at the end.
I still worry that we'll create a mess like we did with the interlanguage links. But, here, you go anyway.
P.S.: This time I'll try to outsmart you all; unless I hear about some real problems with this scheme in the next few days, I'm going to put this into the CVS! Be warned!! ;-)
in response to Brion Vibber's reply to my posting to the wrong mailing
list (apologies), I'm attaching here a patch of what I think fixes the
bug that five apostrophes produce invalid HTML.
This takes care of quite a lot of weird cases and nestings. However, of
course I'm aware that it is not perfect. I can construct cases where it
will still fail, but those are cases that I don't think will ever
actually come up in an encyclopedia article (or if they do, the author
was feeling fancy and deserves to be shot ;-) ).
Here's the patch:
--- includes/OutputPage-old.php Sun Jun 29 04:06:12 2003
+++ includes/OutputPage.php Sat Jun 28 19:04:42 2003
@@ -675,6 +675,15 @@
/* private */ function doQuotes( $text )
+ /* prevent invalid HTML (<strong><em>...</strong></em>) */
+ $text = preg_replace( "/'''''(.+)'''(.*)''/mU", "<em><strong>\$1</strong>\$2</em>", $text );
+ $text = preg_replace( "/'''''(.+)''(.+)'''/mU", "<strong><em>\$1</em>\$2</strong>", $text );
+ $text = preg_replace( "/'''(.*[^'])''([^'].*)'''''/mU", "<strong>\$1<em>\$2</em></strong>", $text );
+ $text = preg_replace( "/''(.+)'''(.+)'''''/mU", "<em>\$1<strong>\$2</strong></em>", $text );
+ $text = preg_replace( "/(<strong>.*)'''(.+)'''(.*<\\/strong>)/mU", "\$1</strong>\$2<strong>\$3", $text );
+ $text = preg_replace( "/(<em>.*)''(.+)''(.*<\\/em>)/mU", "\$1</em>\$2<em>\$3", $text );
$text = preg_replace( "/'''(.+)'''/mU", "<strong>\$1</strong>", $text );
$text = preg_replace( "/''(.+)''/mU", "<em>\$1</em>", $text );
How do you usually handle casual programmer contributions? Are they
usually posted to this mailing list? Or do you have a BugZilla
installation somewhere where I should upload this as a patch? Or is
there an actual chance I might get write access to the repository?
Currently, it's possible to create a new article by editing the URL in
the title bar of ones browser. This method is even described in the
Wikipedia help text.
Why don't we put a link into the "sorry, your search didn't produce any
results" text that is displayed after a search fails? This link could
point directly to the keyword the user searched for and, thus, make the
creation of a new article much easier (i.e. "click to create article").
Sure, this method will create a new orphan, but this is already allowed
Go to upload file on en: wikipedia.
Choose a file, fill in description, check "copyright" box.
Click "upload", wait ....
The browser returns to the SAME page. Fields are blank except for the
Second attempt successfully uploads the file.
Textbook-l is not yet listed on gmane.orghttp://mail.wikipedia.org/mailman/listinfo/textbook-l
If no objections I will ask gmane to add Textbook-l
Now all wikipedia lists are using the gmane.science.linguistics.wikipedia*
Whit the new "wikimedia" name i propose to use the gmane.org.wikimedia.*
hierarchy for all wikimedia lists.
So for Textbook-l gmane.org.wikimedia.textbook
The other lists can become like this;
(but this move will have to wait until the winter afther a software change
Contact: walter AT wikipedia.be
Ook een artikeltje schrijven? WikipediaNL, de vrije GNU/FDL encyclopedie
ok guys, I'm in!
what's the correct etiquette?
should I commit the changes to LanguageFr.php from the fr: wiki, or let
you know first?
what about stylesheet changes?
what's the procedure for code travelling from the CVS repository to the
test server, to the actual live pedias?
(PS I'll write replies up into the docs on Meta!)