Hi everyone,
I recently set up a MediaWiki (http://server.bluewatersys.com/w90n740/)
and I need to extra the content from it and convert it into LaTeX
syntax for printed documentation. I have googled for a suitable OSS
solution but nothing was apparent.
I would prefer a script written in Python, but any recommendations
would be very welcome.
Do you know of anything suitable?
Kind Regards,
Hugo Vincent,
Bluewater Systems.
Hi,
today we came over 10k HTTP requests per second (even with inter-squid
traffic eliminated). Especially thanks to Mark and Tim, who've been
improving our caching, as well as doing lots of other work, and
achieved incredible results (while I was slacking). Really, thanks!
Domas
Hey,
I've put together an extension for rating articles if anyone is
interested. It's just a first version and hasn't been tested much, but
the details can be found here:
http://www.wikihow.com/WikiHow:RateArticle-Extension
You can see an example here on our development server:
http://wiki16.wikidiy.com/Get-a-Better-Deal-on-a-Home-Loan
(username password wikihow / wikihow2006) - scroll down to the bottom
of the page for the checkmarks.
I'd appreciate feedback if anyone has any. If someone wants to add
this to extensions in svn, that'd be great.
Thanks,
Travis
Anthere wrote:
> Hello Mike,
>
> Apologies, but it was unclear to me whether there is a wiki page set up
> for the 2007 hacking days.
> If there is no such page, can you set up one so that it is easier to
> follow plans and discuss programmes ?
>
> One feedback I had from hacking days 2006 was that it was necessary to
> have more cool time in small groups, and less "academic-type"
> presentations in front of 20 people. In short, they need not only a room
> with some presentations going on, but also a nice and cosy place to sit,
> with drinks etc...
Indeed there was a strong feeling that the hacking days were
overproduced last year, with too many outsiders, too heavy scheduling,
too many talks.
The hacking days are meant to be informal and, hopefully, productive. :)
Some really nice points did get made in the middle of it, but I and
others found the overall experience rather frustrating. In contrast, in
2005 we really weren't organized enough, and while there was good
socializing which helped build team spirit we didn't come out with much
directly productive.
My recommendation: don't invite too many people, don't have lots of
talks. Talks would be more appropriate for a tech track during Wikimania
proper.
A few small workshop-type sessions to let people strategize, socialize,
roadmap, experiment, and accept tasks to work on for the coming months
would be a lot nicer, and would better justify having a distinct
"hacking days" period before/after the main conference.
-- brion vibber (brion @ pobox.com)
I need this extension:
http://meta.wikimedia.org/wiki/Chr2syl
installed on the Cherokee Wikipedia. Is there a page somewhere on meta
for this purpose to request Brion to install the
extension for editing in Sequoyah Syllabary? I did not see a page for
requesting extensions installed. I know when I install
extensions, I have to do it from the unix login and its not normally
possible to install them from the web interface.
Any assistance would be appreciated.
Thanks
Jeff
Hi,
Would it be possible to improve the post-move page text to actually
show the double redirects, rather than just asking the mover to check
for them? In particular, could it show *just* the double redirects,
and not all the other links? It's not very obvious, particularly to
the novice, which of the following links are "bad":
Rank of hands (poker) (redirect page)
* Draw poker
* Poker
* Poker/Hands (redirect page)
o Talk:Poker
* Bug (poker)
* Ace-to-six low (redirect page)
o Draw poker
o Stud poker
o Five-card stud
* Deuce-to-seven low (redirect page)
o Draw poker
o Kansas City
o List of poker terms
o Deuce
o Jennifer Harman
o Dewey Tomko
o Billy Baxter (poker player)
A trimmed-down display like the following would be much more helpful:
* Poker/Hands (linked 1 time)
* Ace-to-six low (linked 3 times)
* Deuce-to-seven low (linked 7 times)
Or if we really want to go the whole hog, could the move page just fix
the double redirects automatically? Or maybe at least add them to some
list that a bot is constantly monitoring?
Steve
[This is in response to all the bitching and whining that's taken
place since December 24th, on mailing lists, bug trackers, village
pumps and sleazy little back-alley forums...I apologise for the
crossposting. As ever, please feel free to forward this to other
appropriate parties or lists, but keep responses and/or discussion on
one.]
All right, this bickering has gone far enough. The fact of the matter
is that we're under constant pressure to keep the site alive and
introduce new features and fixes on a regular basis. I can well
understand that a lot of people will object to each change, and we do
our best to make things non-intrusive.
When this feature was first introduced, some bright spark on the
English Wikipedia edited the global CSS and made the numbers bright,
garish green and red, and emboldened them - I didn't agree with that,
but whatever. However, there were a huge number of not-too-polite
complaints blaming us for doing it, and some of these failed to
subside when it was pointed out that this had nothing to do with the
development team.
We might not implement their letter, but the spirit of the ideas of
keeping civil and assuming good faith *are* applied at the development
level; we just reserve the right to be blunt. If I've been
particularly rude to anyone over this issue, I do apologise for it -
and I'm sure anyone else who may have been apologises too.
If we're to implement certain tweaks for this in user preferences,
then we need some co-operation from the user base to allow us time to
determine a clean means of doing so (we want to avoid duplication of
code when generating changes list items), and we want people to
remember that politeness goes both ways.
Just because user A dislikes a feature, it doesn't mean that user B
will, and it is not fair to scream and rant and rave over it because
we tried to implement something that was useful. I would like to note
also that the numbers, as with the "minor edit" flag, and the whole
concept of edit summaries, are advisory - what we provide is a factual
statement of who changed what, and how much they changed, and we allow
that user to present justification for their changes. If that user
chose to lie in their edit summary, or deliberately mis-labelled a
minor edit, then there is nothing any of us can do - and you (the
users) have coped with that well enough over (at least) the past four
years or so.
I will open a fresh feature request, giving an opportunity for Brion
to say "yes" or "no" definitively, and I will avail myself to Leon or
anyone else who would then wish to implement the outcome should they
want any input.
I point-blank refuse, however, to work with any user who feels that it
is acceptable to assume bad faith on the part of the development team.
That attitude could very well lose you a lot of the behind-the-scenes
supporting cast one day, without whom you wouldn't even *have* a
website.
Rob Church
> Could I trouble you to elaborate on this point a little?
$ lynx -dump http://localhost/mediawikibus/index.php?title=Special:Recentchanges\&uselan… -44
1. Odd, uselang=en didn't clean up this part:
本頁跟蹤中公內最新的更改。 [6]歡迎,新來者! 請參見這些頁面:[7]中公常見問題解答、 [8]中公守則 (特別是[9]命名常規、
[10]中立觀點) 和[11]最常見失禮行為。
如果您希望中公成功,那麼請您不要增加受其它[12]版權 限制的材料,這一點將非常重要。相關的法律責任會傷害本項工程,所以請不要這樣做。
2.
* ([29]Move log); 12:45 . . [30]WikiSysop ([31]Talk | [32]contribs)
@ (討論:020移動到討論:020a)
* ([33]Move log); 12:45 . . [34]WikiSysop ([35]Talk | [36]contribs)
@ (020移動到020a)
* (diff) ([37]hist) . . N [38]分類討論:綠川東站; 12:03 . . [39]MediaWiki
default ([40]Talk) (Importing text file)
* ([41]Deletion log); 12:03 . . [42]Delete page script ([43]Talk)
(已刪除“分類討論:綠川東站”)
* (diff) ([44]hist) . . N [45]分類:綠川東站; 12:02 . . [46]MediaWiki
default ([47]Talk) (Importing text file)
No links on the lines I marked with @. Thus one needs to visit the
move log to click on the newly born page "020a"
And not only moveBatch.php, but moving pages via the main web
interface too.