On 8/31/09 4:34 PM, Gregory Maxwell wrote:
Greetings.
Can anyone provide a status update regarding flaggedrevs.labs.wikimedia.org ?
In the future perhaps it would be better to import simple english
Wikipedia for enwp testing: The lack of templates makes the site look
extensively vandalized
On 8/31/09 1:12 PM, Ilmari Karonen wrote:
Platonides wrote:
You get a request for page Foo:Bar. It could be a page name, or Foo
could mean Special in Bantu. How do you check (efficiently) over 300
languages?
With array_key_exists(), surely? It's (AFAIK) a (nearly) constant-time
hash
Perhaps I am misunderstanding, but simple shouldn't be locked into some sort
of 'testing' agreement with enwp unless there is some sort of consensus on
both sites, and I have little doubt that consensus will not exist for such
an action.
As I say, perhaps I am misunderstanding.
- Chris
Domas Mituzas wrote:
For something like {{SITENAME}} there is little reason to be looking
it up every single time the message loads, so why not teach Mediawiki
to pre-evaluate that and similar items before putting it in the
message cache?
There is little reason to keep {{SITENAME}} in
Hi,
The point is, then it won't get automatically updates from
translatewiki.
Enwiki will be really really sad by not have pagetitle constantly
translated by translatewiki :)
On the other hand, one could support branching of messages at
translatewiki - isn't that what we do with
On Tue, Sep 1, 2009 at 5:39 PM, Gregory Maxwellgmaxw...@gmail.com wrote:
Seems my concern was moot in any case... Every time I loaded it I've
only seen trashed pages like this:
http://flaggedrevs.labs.wikimedia.org/wiki/Super_Smash_Bros._Melee
But I guess this is just a result of the import
2009/9/1 Domas Mituzas midom.li...@gmail.com:
Enwiki will be really really sad by not have pagetitle constantly
translated by translatewiki :)
That's not the point. If a message is customized by replacing
{{SITENAME}} with Wikipedia, updates to *that message* (not to the
site name) from
On Tue, Sep 1, 2009 at 7:06 PM, Roan Kattouwroan.katt...@gmail.com wrote:
2009/9/1 Domas Mituzas midom.li...@gmail.com:
Enwiki will be really really sad by not have pagetitle constantly
translated by translatewiki :)
That's not the point. If a message is customized by replacing
{{SITENAME}}
pouvez vous m'envoyer les documents en francais
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Salut Ameth,
vous n'avon pas traduire les manuels, ils sont disponible seulement en
anglais.
Mais tu peux trouver des page de l'aide pour Wikipedia et en modifier le wiki
en francais dans la Wikipedia francaise:
http://fr.wikipedia.org/wiki/Aide:Sommaire
Cordialement,
Manuel
Am Dienstag,
We should support shadow wiki copies of mediawiki.
Something like copying the page table and have mediawiki look at the
revision table of the original wiki when needed.
Obviously, the labs login should have read-only access to the production
wiki (it's labs, after all) except perhaps to the user
On Tue, Sep 1, 2009 at 2:03 AM, K. Peacheyp858sn...@yahoo.com.au wrote:
On Tue, Sep 1, 2009 at 5:39 PM, Gregory Maxwellgmaxw...@gmail.com wrote:
Seems my concern was moot in any case... Every time I loaded it I've
only seen trashed pages like this:
Hello,
That's not the point. If a message is customized by replacing
{{SITENAME}} with Wikipedia, updates to *that message* (not to the
site name) from TranslateWiki (or changes to the message in
MessagesEn.php , in the case of English) will not get through because
the local customization
Hello,
Domas suggested the top 20 wikis, but I think the top 10 of these
should be the wikis where optimisations takes precedence over
translations.
I restricted myself to top20 because I think there's more work to
maintain more.
Every wiki which does not have these messages fixed will be
Domas Mituzas midom.li...@gmail.com wrote:
[...]
By the way, how did you come up with top10 number? Why do you think it
is better, than, say, top20?
Anyone else has any opinions? Should that be top5? Top20? Top100?
Why not *all* that haven't been changed on translatewiki in
the past x weeks?
On Tue, Sep 1, 2009 at 5:03 AM, K. Peacheyp858sn...@yahoo.com.au wrote:
On Tue, Sep 1, 2009 at 5:39 PM, Gregory Maxwellgmaxw...@gmail.com wrote:
Seems my concern was moot in any case... Every time I loaded it I've
only seen trashed pages like this:
Dear developers, publishers and users,
we have fixed the time for our second developers meeting of the openZIM
project, a meeting for all users, developers and publishers of software or
works using the ZIM file format.
== Time ==
It will take place over the weekend from November 20th to 22nd
[snip]
I'd like to ask that folks leave this thread aside for the moment other
than useful replies to the original poster's request about how and where
to propose changing $wgSitename for ja.wikipedia.org.
If the code paths for setting up and running the parser to do brace
substitution in
On 9/1/09 6:56 AM, Platonides wrote:
We should support shadow wiki copies of mediawiki.
Something like copying the page table and have mediawiki look at the
revision table of the original wiki when needed.
Obviously, the labs login should have read-only access to the production
wiki (it's
Domas Mituzas wrote:
Performance-wise it is even better, if all main messages which have
{{SITENAME}} get replacements with literals. Otherwise you're adding
up 5ms of page load time to each page. :)
I'm not very familiar at all with the new LocalisationCache system, but
it seems to me
2009/9/1 Ilmari Karonen nos...@vyznev.net:
Domas Mituzas wrote:
Performance-wise it is even better, if all main messages which have
{{SITENAME}} get replacements with literals. Otherwise you're adding
up 5ms of page load time to each page. :)
I'm not very familiar at all with the new
-- Forwarded message --
From: Brion Vibber br...@wikimedia.org
Date: Tue, Sep 1, 2009 at 11:48 AM
Subject: Re: [Wikitech-l] how to chang {{SITENAME}}
To: Wikimedia developers wikitech-l@lists.wikimedia.org
[snip]
I'd like to ask that folks leave this thread aside for the moment
Duplicate thread of
http://lists.wikimedia.org/pipermail/wikitech-l/2009-September/044984.html
?
Roan Kattouw (Catrope)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Tue, Sep 1, 2009 at 1:40 PM, Roan Kattouwroan.katt...@gmail.com wrote:
Duplicate thread of
http://lists.wikimedia.org/pipermail/wikitech-l/2009-September/044984.html
?
Roan Kattouw (Catrope)
___
Wikitech-l mailing list
Roan Kattouw wrote:
Duplicate thread of
http://lists.wikimedia.org/pipermail/wikitech-l/2009-September/044984.html
?
Not exactly, I think. Folding constant magic words when setting up the
localization cache and speeding up the parser in general would be fairly
orthogonal improvements, even
On Tue, Sep 1, 2009 at 2:34 PM, Domas Mituzasmidom.li...@gmail.com wrote:
Hello!!!
If anyone is interested in actually looking into the costs of Parser
setup and invocation for brace replacement in messages and optimizing
this code path, that would be great, but please follow up in a new
Chad,
I personally haven't, but if you've got some good profiling data from
WMF usage of this stuff it would certainly be helpful :)
Well, in simple micro-benchmarking, wfMsg(pagetitle) took 0.5ms on
enwiki and 5ms on frwiki (thats _without_ any initialization overhead).
First call to
Hello,
What other people have objected is your position that the only way to
regain them is to manually replace {{SITENAME}} on all messages.
I didn't say manually ;-) One could have an automated solution :)
Parser-transformMsg() could replace many well-known {{something and
only call
Domas Mituzas wrote:
Anyone, one can see, lion's share is Parser-preprocess, which doesn't
do any initialization here, pure parser magic (though it probably has
some revisits to magic words and Title code that could be removed).
So yes, parser init adds about 5ms, so does message cache,
Gregory Maxwell wrote:
And it's different now than it was last night, last night the
templates weren't there yet and it looked like a car hit it. :)
You know, when you point to a broken page, people^W wikipedians tend to
do absurd things like fixing them :)
It was me who fixed it, by importing
Domas Mituzas wrote:
Hello,
What other people have objected is your position that the only way to
regain them is to manually replace {{SITENAME}} on all messages.
I didn't say manually ;-) One could have an automated solution :)
An admin bot template subster
Parser-transformMsg() could
On Tue, Sep 1, 2009 at 2:16 PM, Domas Mituzasmidom.li...@gmail.com wrote:
Hello,
What other people have objected is your position that the only way to
regain them is to manually replace {{SITENAME}} on all messages.
I didn't say manually ;-) One could have an automated solution :)
On Wed, Sep 2, 2009 at 7:02 AM, Platonidesplatoni...@gmail.com wrote:
You know, when you point to a broken page, people^W wikipedians tend to
do absurd things like fixing them :)
I was going to fix some up, but import is restricted and i was too
lazy to do copy/paste imports.
-Peachey
On Tue, Sep 1, 2009 at 7:17 PM, K. Peacheyp858sn...@yahoo.com.au wrote:
On Wed, Sep 2, 2009 at 7:02 AM, Platonidesplatoni...@gmail.com wrote:
You know, when you point to a broken page, people^W wikipedians tend to
do absurd things like fixing them :)
I was going to fix some up, but import is
I bring this old issue up because I want to know if (or if not) progress (or
plans) are made to update the static HTML version of Wikipedia.
BH photos just leaked the next generation of Archos portable media players.
Unbelievably, the rumors of a 500GB version is true! This is already
tempting
Hello,
I am interested in using the Wiktionary API (located at
en.wiktionary.org/w/api.php) and was having trouble finding any information
on what is acceptable commercial use. If there are any controlling
documents on the subject, can you please direct me to them? In particular,
I would like to
2009/9/1 James Richard james.richard...@gmail.com:
Hello,
I am interested in using the Wiktionary API (located at
en.wiktionary.org/w/api.php) and was having trouble finding any information
on what is acceptable commercial use. If there are any controlling
documents on the subject, can you
Chengbin Zheng wrote:
I bring this old issue up because I want to know if (or if not) progress (or
plans) are made to update the static HTML version of Wikipedia.
BH photos just leaked the next generation of Archos portable media players.
Unbelievably, the rumors of a 500GB version is true!
I think it would...
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Tue, Sep 1, 2009 at 8:31 PM, Chengbin Zheng chengbinzh...@gmail.comwrote:
BTW, does anyone know what is the size of the current static HTML English
Wikipedia version uncompressed? Thanks.
Based on some quick extrapolation (the smaller dumps seem to be compressed
at ~21-22x), it seems like
You can try to work with the parsed Wiktionary database (now only a
part of Russian Wiktionary, English Wiktionary is planning for the
next year).
See http://code.google.com/p/wikokit
Good luck!
On Wed, Sep 2, 2009 at 5:01 AM, Platonidesplatoni...@gmail.com wrote:
I think it would...
On Tue, Sep 1, 2009 at 9:47 PM, Benjamin Leesemufarm...@gmail.com wrote:
On Tue, Sep 1, 2009 at 8:31 PM, Chengbin Zheng chengbinzh...@gmail.comwrote:
BTW, does anyone know what is the size of the current static HTML English
Wikipedia version uncompressed? Thanks.
Based on some quick
42 matches
Mail list logo
