I have just joined, I am from mumbai, india. I would like to get the
articles translated in marathi, my mother tongue. Looking at the effort
and no of volunteers, this will not be usable in any reasonable amount
That has made me think of alternatives - machine translation. A state
funded institute has a software available but I don't have access to it
Pl. comment about this approach. Has this been tried for any other
Thanks & regards,
Yahoo! India Matrimony: Find your life partner online
Go to: http://yahoo.shaadi.com/india-matrimony
As wikipedia is slow at the busy time, I propose to get some new servers for our cluster.
- Some new web servers(3 or 4), P4 2,8Ghz with 2Go of RAM
- A server which could be a backup for nfs server, zwinger, with bigger disk, 80Go is very low, maybe 200 or 250Go
- Upgrading disk of zwinger to 200 or 250Go (or add a new one)
- A db server in 64 bits mode with 4Go of RAM (if we cant make working geoffrin), like this one :
With raid 10 disk system, 4 or 6 drives in raid and 1 stand-by. I prefer 15000rpm disk, but I can understand that they are more expensive
- Maybe another squid server
What do you think of that ?
Firstly, I'm disappointed Erik chose to characterise my stated
motivation as "false pretenses", as if I had some kind of bias towards
Klingon and I deliberately tried to mislead the list. I mistakenly
created Klingon, I did not try to pull a swiftie on the Wikimedia
community. I hope that Erik's choice of words was in error.
Jimbo issued one statement against Klingon and one statement in favour
of Klingon. His opinion was thus sufficiently ambiguous that my pretext
was removed. However he later clarified his position by withdrawing his
initial statement -- both on wikitech-l and on #wikipedia. I would have
been happy to re-enable the wiki as soon as he did this, however he
asked me to wait for the discussion to pan out.
The compromise agreed to by Erik and Timwi is to allow the Klingon
Wikipedia, but to avoid interlanguage links. Accordingly, I have
commented out the Klingon entry in $wgLanguageNames. This means that
markup of the form [[tlh:wIqIpe'DIya]] will create an external link
rather than an interlanguage link, just like links to meta or sep11.
Otherwise the wiki is fully functional.
-- Tim Starling
[[de:Benutzer:Joma]] has written a fast search engine for a Wikipedia mirror
which can handle complex search queries. He emphasises that it's meant as a
supplement to an existing SQL database, not a replacement. He is willing to put
the code under GPL if we are interested.
I think this might be useful for us, could one of the German speaking developers
please take a look at
and - if we want to give it a try - get in contact with Joma?
http://leihnetzwerk.de -- Teile Bücher, Videos und CDs mit anderen!
http://wikipedia.de -- Arbeite mit bei der freien Enzyklopädie!
Kurt Jansson, Wiener Str. 7, 10999 Berlin, http://jansson.de
Some time ago, I requested to turn off the capitalisation for
nk:wiktionary. From things that I read on the en:wiktionary I was led to
believe that for a sysop it is an easy little time consuming
manipulation. The big thing is to get things right afterward.
Can someone please turn the capitalisation off. The longer the wait the
more there is to fix.
-> PLEASE TRANSLATE THIS MESSAGE INTO YOUR LANGUAGE AND SEND A COPY TO
YOUR LOCAL PROJECT MAILING LIST. THANK YOU!
MediaWiki is a great software package, but in one department it is
lacking: documentation. In spite of the collaborative power of wiki, so
far there exists no single user documentation. Instead, each project
maintains its own fork, and the Meta pages are one big mess (although the
English documentation has become a bit better with the introduction of the
I have just taken live some code changes which allow us to finally
systematically document MediaWiki. I have added code to allow custom
namespaces, so that any wiki can have any number of namespaces beyond the
ordinary ones. Using this, I have then created namespaces in the largest
languages (for which I had translations of "Help" and "Help talk") on
http://meta.wikimedia.org . See
for a list of available namespaces.
That means you can now edit Hilfe:Inhalt or Aide:Aide like the English
users have been editing Help:Contents. Why is that important? Because it
allows us to easily export all the help files in one language, and import
them into another wiki.
Any wiki may want to make custom changes to the help pages. This is best
done using custom header and footer templates. Interlanguage links should
also be passed to a template as a parameter, so that users who only import
one translation can hide them easily (by removing the parameter).
I have laid out some basic editorial guidelines for working on pages in
the Help: namespace of your language:
This also includes a modified Template:Hc which shows how interlanguage
links can work.
The gist of it is that we must make sure that the pages in the namespace
can be imported by *any project*, Wikimedia or not, without changes
(except to a handful of templates).
Once the pages have stabilized, we should clean out the Help: namespaces
of all Wikimedia projects and import the meta pages instead. We can then
upgrade them regularly (even daily) and automatically on all wikis.
The project namespace ("Wikipedia:", "Wikisource:" etc.) should then be
used strictly for policy.
I propose that the Help: namespace be used both for user and
administration documentation (installation guidelines etc.), so we can
move towards a single neatly integrated handbook.
I invite all interested parties to participate in consolidating our
If I wanted to get a new sister project started off of the home page,
who would I talk to? What would I do? The project I have in mind doesn't exactly
fit any of the categories listed, yet I feel it would be a useful addition.
so - do I write a proposal? Discuss it on this mailing list? Go through meta-wiki?
Or some other method?
similar bug as in "watch this page" (this being now solved in 1.3.2):
* Situation: being on a page of user X
* after having sent an "E-Mail this user" an acknowledgment page appears
and returns to Main_page
* However, it is proposed to automatically return to last relevant page
(i.e. the page of User_X) instead
* After deleting a page (as Admin), the wiki returns to the Main_Page
* It is suggested to return to the previous relevant page (in this case,
the page visited _before_ the now-deleted page)
iI was wondering if anyone was working on the following features for mediawiki. Or
if they existed already, and I don't know about them:
1) ability to upload a gnuplot data file, and have it turn into an associated
PNG graph inside mediawiki.
2) ability to do polling/data collection based off of IP.
If nobody is working on these, I'd like to add them. It would also be cool to
add an integrated mailing list creator for projects through interface to majordomo,
although I'm a little bit hazy on implementation of this one.
ps - for images, how does mediawiki get around the inode limit? I noticed
in the LocalSettings.php that there was a directory for images, but I'd
think that images/files being stuffed into one directory would ultimately be
cause for trouble..
(1) Is there a simple way to bulk copy (clone) the whole
MediaWiki:namespace from one wiki to another wiki (on the same server) ?
(2) Is there a simply way to extract let's say five MediaWiki:pages so
that I can put it together with a patch into the CVS ?
In my case, the coming e-mail notification patch for 1.3.2 (see my
recent (pre)documentation pages on the MetaWiki) uses a couple of
MediaWiki:namespace pages for composing the notification mails and other
purposes and I want to publish these important pages together with the
program patch in one "package".
But I don't know, how.