At 09:43 24/11/2003 -0500, you wrote:
>We cannot allow spelling bots unless:
>A. The bot is registered
>B. The bot draws from an approved list
>A word like /thier/ can safely be changed to "their", since it's almost
>always a misspelling. However, there are many misspellings which can't
>be automatically corrected.
>I don't mind HUMANS whiling away their time doing a bit of spell-check
>work; I do it myself, when I want to relax.
>But if a machine can do it, then it probably shouldn't be done as a
>logged-in contributor (robot or "bot"). Rather, let's have our zealous
>programming staff write a custom spell-check program.
When I get my search engine converted to the wiki db, it comes with a
moderated spell checker
the result should be a fast search and a table full of typos for bots and
humanbots to play with.
>Wikitech-l mailing list
The say it is no spam :-)
The are not listmembers so the will not get the responds.
Quim Gil wrote:
> Please forward this message to the WikiMedia project cordinator or
> anyone assuming such role. This is not spam, is a real message addressed
> to the core WikiMedia developers. Thank you!
> Quim Gil
> Invitation: how will be MediaWiki in 2004?
> Quim Gil <qgil(a)interactors.coop>
> Mon, 24 Nov 2003 15:24:28 +0100
> Dear colleagues,
> We invite you to participate indirectly in a speech that we will offer
> in Barcelona on December 9th to 700 Internet related professionals. This
> will happen in the context of the Next'04 -
> http://www.infonomia.com/eventos/next04/ . This is one of the main &
> classic Internet events in Spain and it has a very special format: 10
> selected speakers have 5 minutes each to explain which they think will
> be the most relevant fact of the next year, and why.
> Our speech will bet for the consolidation of free software as an option
> known and recognized out of the usual specialized spheres, gaining
> attention from the media, businesses, institutions and society. We
> believe that this will happen partially thanks to projects like yours
> and this is why we want to include you in our speech.
> We ask you just for some lines explaining the main developments your
> project is plaining to release next year and how can this affect its
> context, the users and also the similar projects developed as
> proprietary software. This last element will help the audience of the
> event (mainly MS Windows / Mac users) to have references and understand
> by themselves how close these free software developments are related to
> their needs and their work.
> We ask you to send those lines to next04(a)interactors.coop. There is a
> dummy example in http://interactors.coop/next04/ (sorry but this working
> website is only in Spanish). Here we will also publish the other answers
> we are receiving.
> We will enhance the speech with screenshots, taking advantage from the
> fact that the venue has a cinema screen. We wont get into details about
> the screenshots, they will serve as background images in order to help
> the audience to visualize the concept of "free software" that may sound
> too abstract to many of them. The idea is to obtain this surprise effect
> so usual between Linux newcomers: "But it looks just like Windows?!". If
> you want that we add your screenshots please send them to us, preferably
> at 1024x768. Or you can just send us the URLs and we make the captures,
> as you prefer.
> We hope that you find this experience interesting. We'll see how the
> experiment turns out and thank you very much in advance for your
> Looking forward for your answer,
We cannot allow spelling bots unless:
A. The bot is registered
B. The bot draws from an approved list
A word like /thier/ can safely be changed to "their", since it's almost
always a misspelling. However, there are many misspellings which can't
be automatically corrected.
I don't mind HUMANS whiling away their time doing a bit of spell-check
work; I do it myself, when I want to relax.
But if a machine can do it, then it probably shouldn't be done as a
logged-in contributor (robot or "bot"). Rather, let's have our zealous
programming staff write a custom spell-check program.
For some reason $wgDynamicDates was being set on in DefaultSettings
(after being set to off, the correct default). This option corrupts
output for languages other than English. It's now set to off.
-- brion vibber (brion @ pobox.com)
Staying so long with ISO 8859 was a mistake.
So I propose converting all Wikipedias that aren't using UTF-8 yet to UTF-8.
Procedure should be like that:
1. new LanguageXX.php prepared and put under some name
2. make backups
3. create tables curutf8 and oldutf8
4. disable write access
5. convert all data - numeric HTML codes are going to be replaced by UTF-8 characters too.
6. rename tables cur and old to cur88591 and cur88591
7. rename tables curutf8 and oldutf8 to cur and old
8. replace old LanguageXX.php with utf8-enabled version
9. reenable write access
The conversion script should be tested on test.* Wikipedia first.
During step 5 Wikipedia is going to be read only. It may take some time,
especially with English Wikipedia, so it's better to do conversion of each Wikipedia
separately. During steps 6-8 Wikipedia may not work at all, but it's going to
take less than a minute.
Does anybody have any really good reason why shouldn't I proceed ?
These reasons aren't good enough:
* broken URLs - all old URLs are going to work after upgrade
* size increase - size is going to stay about the same
* broken browsers - they should be upgraded, if someone has browser so old
that it doesn't grok UTF-8, it's not going to grok CSS,
PNGs, and other things we're using either.
Unless we want to remove all CSS and PNGs, there's
no point in not using UTF-8.
* ISO 8859-N is good enough - no, it's not. Not if someone wants to write about
people and places from countries where non-8859-1 Latin
characters are used, or about linguistics, or math, etc.
This is a patch for one of the tasks on Brion's todo
list he sent some days ago. Currently, MediaWiki
requires the setting of
register_globals = On
in php.ini, which causes some trouble for people
trying to install MediaWiki and which might cause
some security problems. The attached patch enables
MediaWiki to run with register_globals=Off.
There's a test server running this code at
I wasn't sure about Evan's new colour scheme -- I think people would be
confused by broken links that look like stubs and stubs that look like
visited links. So I committed the new style sheets in an "alternate"
directory. That also required a minor change to the installer.
Setting the default style for <a> tags caused all headings to turn
bright blue, on pages with TOCs. So I commented that line out.
While I was at it, I noticed that ordinary internal links were
underlined regardless of the user preferences. Brion took out the
class=internal from ordinary links a while ago, putting it back in
seemed to fix the problem.
The only other change I made to Evan's stuff was adding the ability to
disable the cookie check in LocalSettings.php
-- Tim Starling.
Arwel Parry wrote:
>I've just noticed an oddity on cy.wikipedia.org -- if a logged-in
>user goes to the main page, NUMBEROFARTICLES shows that
>we have (currently) 174 articles, but a non-logged-in user
>going to the same page is told that we only have 75 articles !
I suspect this is due to page caching (anon users see cached versions of pages
while logged-in users don't). The last time the cy.wikipedia main page was
chached (when it was last edited) cy.wikipedia probably had 75 articles. Edit
the main page (adding whitespace at the end of line if need be) and then see
if the number of articles gets updated.
Every time I see an announcement that xx.wikipedia has reach # milestone, I
edit their main page to update the cache.
-- Daniel Mayer (aka mav)
(I apologize if people are receiving this message twice -- I sent it
out earlier, but I don't think that it was posted to the list.)
I am looking to create my own wikiwiki website using the MediaWiki
software, but I'm uncertain as to how I should proceed, because I do
not have access to the command line. I first attempted to have my
host's support people run the install.php script for me, but they ran
into errors and told me that they ran into errors when they ran the
script from the backend, and to look for errors in the code. (You'll
have to forgive my ignorance here -- I'm pretty good with websites, but
server management isn't something I know anything about yet!)
So, I'm looking for a way to install MediaWiki and set up my site using
nothing but FTP upload, phpMyAdmin access (full admin/dba permissions),
and a normal Web browser. Can anyone provide some assistance with