> Hi. I'm Paginazero, an Italian user/contributor to it.wiki.
> As most of my contributions are related to the chemistry, I'm eagerly
> waiting to have the WikiTeX functions included in MediaWiki - that would
> be a great help to avoid image uploading and to define a common
> standard for writing chemical formulae and reaction schemes.
> I'm so impatient that I already began to prepare a tutorial for the Italian
> users!
> Looking forward to getting rid of ASCII-art formulae, I thank you all for
> your kind attention. If I can be of any help, let me know.
But WikiTex IS already included in MediaWiki since a year or so (at least
it's older than 1.3). Just type <math>some LaTeX</math>.
Andre Engels
Hi
I am developing a graphviz extension to mediawiki, basically it is
usefull to make graphs online
using the graphviz program , i think its very usefull , and i am using
it at my wiki (http://www.wickle.com/wikis/index.php/Graphviz_extension)
you can download and test it if you like.
there are samples on the wiki page .
best regards
--
Problems with Windows - Reboot.
Problems with Linux - Be root.
Vic (aKa CoffMan)
vic(a)wickle.com
We've been having a bit of trouble with a vandal [[User:Hi332211]] at
Wiktionary. He has been using the move function to transfer the Main
Page to silly places. I managed to get the Main Page back to where it
belongs, but lost its history in the process. By using the history link
in Recent Changes corresponding to when he made the move I find the
entire history is now at
http://en.wiktionary.org/w/wiki.phtml?title=You_are_an_idiot%21&curid=58201…
but I don't know how to put it back where it belongs.
The talk page is now at [[Wiktionary talk:Main Page]] along with its
history. Someone else had put it there in an attempt to fix the
vandalism. I hesitate to attempt correcting this lest I lose that
history as well.
The Main Page has been protected, and the vandal is now blocked.
Ec
In order to solve some conflicts between internal and external links,
wmahan rearranged Parser.php to call replaceInternalLinks() before
replaceExternalLinks(). However, this in turn broke the ability to put
external links inside image captions, since these are created in
replaceInternalLinks()
In order to cope with *internal* links inside image captions,
replaceInternalLinks() is currently called twice, the second pass
catching those images that couldn't be parsed properly because they
had internal links in them. This has always been rather a hack, but
until now, it worked. However, we really want things to be dealt with
in the order:
1 internal links
2 external links
3 images
In order to do this, we need a seperate function that parses *all*
image rendering. I have called this replaceImageLinks(), and based it
on replaceInternalLinks(), but without anything that isn't relevant to
images (including all the prefix and trail processing, for a start). I
rather suspect this may actually make it a whole lot more efficient
than the previous code; still not as efficient as doing proper parsing
in one go, but with the current structure of the code there's no way
to tell that [[foo [[bar]] baz]] is one entity (that would require
looking ahead, and remember we need to be able to process
[[Image:Foo|opts|Caption with a [[piped|link]] in]], so there's no
clever spotting pipes to be done)
Download from: http://195.137.84.82/~ron/replaceImageLinks.diff
It seems to work for me, but obviously I would welcome all comments and testing.
Note: this patch fails parserTests.php on a couple of things, but the
"Image caption with a free URL" and "Thumbnail image caption with a
free URL" tests are actually wrong themselves, so that's no surprise;
testing manually, these cases seem to have the appropriate result. The
"Image caption with a link" appears to fail (unrelatedly) because the
word "link" now appears in a comment, not just surrounded by HTML
tags, so the removal of /<*?>/ now kills it; which is a shame.
--
Rowan Collins BSc
[IMSoP]
I'm a little confused on the process whereby we make decisions about
shell access. I'm thinking right now primarily of access for a couple
of people from the German e.V. to work on their website, which doesn't
yet exist, rather than thinking of shell access to the main cluster.
Related to this, it seems sensible to me that we should buy a special
server to host things that we want to be separate, like for example
the donation pages, so that if wikipedia is blown up for some reason,
people can still donate money. This would also permit us to give
shell accounts more freely to people with a specific need on some
auxiliary website.
--Jimbo
--
"La nèfle est un fruit." - first words of 50,000th article on fr.wikipedia.org
Hello,
For the next 3 days I will be able to spend my full time on MediaWiki
development.
I am really willing to code an administration interface that will
superseed the install script and manually editing localsettings.php. My
idea so far is that the install script will just deal with things like
database and path, everything else will be available in the admin interface.
I am also willing to completly rewrite the rule system. Instead of
anonymous / logged in / Sysops / Bureaucrate, I am willing to assign
users to groups, each group having rights like "edit, move, special
page, site administration, mediawiki, protecting page ...".
Is there any dev already working on one of those two topics ? Do you
have any specific idea to share ?
Finally, should I start it now for the 1.4 release or wait for a later
release ?
cheers,
--
Ashar Voultoiz
Some time ago I wrote to this list that the local word for Nauruan
should be Nauruose, the source I quoted was the Nauruan wikipedia.
Consequently it was changed for use with interwikis. However, it has
transpired that the Nauruan wikipedia has been squated. Nobody knows
what language the content is in. I am afraid that Nauruose is propably
wrong.
Thanks,
GerardM
Hi. I'm Paginazero, an Italian user/contributor to it.wiki.
As most of my contributions are related to the chemistry, I'm eagerly waiting
to have the WikiTeX functions included in MediaWiki - that would be a great
help to avoid image uploading and to define a common standard for writing
chemical formulae and reaction schemes.
I'm so impatient that I already began to prepare a tutorial for the Italian
users!
Looking forward to getting rid of ASCII-art formulae, I thank you all for your
kind attention. If I can be of any help, let me know.
G.