Thanks everyone who replied to my post.
I have proposed to change $wgSitename to ウィキペディア in Japanese
Wikipedia. A few users oppose itself. The half of users support
changing not the prefix of project namespace but only site's name, while
others support changes of both $wgSitename and project
On Wed, Sep 23, 2009 at 9:14 AM, mizusumashi mizusuma...@coda.ocn.ne.jp wrote:
I have proposed to change $wgSitename to ウィキペディア in Japanese
Wikipedia. A few users oppose itself. The half of users support
changing not the prefix of project namespace but only site's name, while
others support
On Wed, Sep 23, 2009 at 9:14 AM, mizusumashi mizusuma...@coda.ocn.ne.jp
wrote:
I have proposed to change $wgSitename to ウィキペディア in Japanese
Wikipedia. A few users oppose itself. The half of users support
changing not the prefix of project namespace but only site's name, while
others
stevertigo wrote:
See https://bugzilla.wikimedia.org/show_bug.cgi?id=18793 .
Note that ウィキペディア is not the canonical term, so people may not
want to provide such functionality. ;-|
-Stevertigo
Your answer is completely unrelated to mizusumashi request, which would
have no problem to be
2009/9/23 Platonides platoni...@gmail.com:
stevertigo wrote:
See https://bugzilla.wikimedia.org/show_bug.cgi?id=18793 .
Note that ウィキペディア is not the canonical term, so people may not
want to provide such functionality. ;-|
-Stevertigo
Your answer is completely unrelated to mizusumashi
Platonides platoni...@gmail.com:
Your answer is completely unrelated to mizusumashi request, which would
have no problem to be fulfilled (assuming there's community consensus).
Don't confuse people with your own war (aka. bug 18793).
Hm. You are right. The tokens befuddled me.
-Stevertigo
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
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}}
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?
[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
Hello,
For example, [[MediaWiki:Aboutsite]] have the default message About
{{SITENAME}}. But we have overwritten it by ウィキペディ
アについて
（translated word from about Wikipedia).
Performance-wise it is even better, if all main messages which have
{{SITENAME}} get replacements with literals.
2009/8/31 Domas Mituzas midom.li...@gmail.com:
Hello,
For example, [[MediaWiki:Aboutsite]] have the default message About
{{SITENAME}}. But we have overwritten it by ウィキペディ
アについて
（translated word from about Wikipedia).
Performance-wise it is even better, if all main messages which have
Hoi,
Changing the messages in this way may be good from a performance perspective
it really hurts the usability of our messages. Messages are localised at
translatewiki.net and this is where we do require these messages. When
messages are to have hardcoded strings as you propose you defeat the
On Mon, Aug 31, 2009 at 7:10 AM, Gerard
Meijssengerard.meijs...@gmail.com wrote:
Hoi,
Changing the messages in this way may be good from a performance perspective
it really hurts the usability of our messages. Messages are localised at
translatewiki.net and this is where we do require these
Hi!
Changing the messages in this way may be good from a performance
perspective
it really hurts the usability of our messages. Messages are
localised at
translatewiki.net and this is where we do require these messages. When
messages are to have hardcoded strings as you propose you
Hoi,
There are two opposing objectives at play. Performance is one and quality
localisation for MediaWiki in all our projects is the second. Just stating
that performance trumps our localisation is also very much a nono.
These are consequences and they have to be considered. Just breaking the way
Hoi,
Thank you for the hyperbole.. Your representation insinuates that our
systems will crash unless this change is implemented. Fact is that currently
our messages are parsed.
Thanks,
GerardM
2009/8/31 Aryeh Gregor
simetrical+wikil...@gmail.comsimetrical%2bwikil...@gmail.com
On Mon, Aug
On Mon, Aug 31, 2009 at 10:17 AM, Gerard
Meijssengerard.meijs...@gmail.com wrote:
Hoi,
Thank you for the hyperbole.. Your representation insinuates that our
systems will crash unless this change is implemented. Fact is that currently
our messages are parsed.
Thanks,
GerardM
2009/8/31
No need to have a heated debate here, I think.
I have known about this issue for high traffic MediaWiki wikis for at least
a year and a half - Domas actually made me aware of it, and based on that I
made a few changes in the Dutch language Wikipedia and notified some admins
of other larger
On Mon, Aug 31, 2009 at 8:27 AM, Gerard
Meijssengerard.meijs...@gmail.com wrote:
There are two opposing objectives at play. Performance is one and quality
localisation for MediaWiki in all our projects is the second. Just stating
that performance trumps our localisation is also very much a
On 31/08/2009, at 9:27 AM, Gerard Meijssen wrote:
Hoi,
There are two opposing objectives at play. Performance is one and
quality
localisation for MediaWiki in all our projects is the second. Just
stating
that performance trumps our localisation is also very much a nono.
These are
Domas Mituzas wrote:
Anyway, we have to ensure, that most of wikis (at least top20 ones)
have got ridden of curly braces and any other expensive parser stuff
in these messages, as that costs them up to 10 milliseconds per
pageview (if anyone writes a bot to do this automatically, I'd
Hoi,
Centralised localisation works when the resulting localised messages are
usable and useful in all environments. More exceptions to this rule make it
seem as if central localisation is not a good idea. There is already one
acknowledged exception to the rule; messages that inform about the
On Mon, Aug 31, 2009 at 3:56 AM, Domas Mituzasmidom.li...@gmail.com wrote:
I asked about this a while ago.
http://www.mediawiki.org/wiki/Project:Support_desk/Archives/Miscellaneous/007#tuning_MediaWiki
:Aboutsite
asking on-wiki doesn't really makes much sense, as I don't read it ;-p
Platonides platoni...@gmail.com wrote in message
news:h7gok4$6v...@ger.gmane.org...
1) Copy that list
2) Prepend MediaWiki: namespace
3) Post to Special:Export
4) Automate it:
...
6) Profit!!
What's step 5? :-P
--HM
___
Wikitech-l mailing
On Mon, Aug 31, 2009 at 1:01 PM, Happy-melonhappy-me...@live.com wrote:
Platonides platoni...@gmail.com wrote in message
news:h7gok4$6v...@ger.gmane.org...
1) Copy that list
2) Prepend MediaWiki: namespace
3) Post to Special:Export
4) Automate it:
...
6) Profit!!
What's step 5? :-P
Aryeh Gregor wrote:
On Mon, Aug 31, 2009 at 1:01 PM, Happy-melonhappy-me...@live.com wrote:
Platonides platoni...@gmail.com wrote in message
news:h7gok4$6v...@ger.gmane.org...
1) Copy that list
2) Prepend MediaWiki: namespace
3) Post to Special:Export
4) Automate it:
...
6) Profit!!
Hi,
In the long-term, wouldn't it be smarter to make some of these stable
and quasi-stable tokens automatically cache in their evaluated state?
We already do, we cache such simplified messages in Mediawiki:
namespace.
For something like {{SITENAME}} there is little reason to be looking
it
I was under the impression we were talking about changing the strings
at the individual Wikis, thus a custom message, not in the language
files used for all MediaWiki sites... I'm not sure, then, what the
problem is Gerard? If we alter a message locally at Wikipedia how does
that affect
Hello everyone.
I want to propose changing {{SITENAME}} in jawp. But I don't know how
to, and who can do it. Editing some pages, requesting to server
administrators or anything... Please teach me what I have to.
Thank you.
[[w:ja:User:mizusumashi]]
mizusumashi wrote:
Hello everyone.
I want to propose changing {{SITENAME}} in jawp. But I don't know how
to, and who can do it. Editing some pages, requesting to server
administrators or anything... Please teach me what I have to.
Thank you.
[[w:ja:User:mizusumashi]]
How do you want it changed?
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
36 matches
Mail list logo
