On Tue, Feb 24, 2009 at 7:31 PM, Aryeh Gregor
simetrical+wikil...@gmail.comsimetrical%2bwikil...@gmail.com
wrote:
On Tue, Feb 24, 2009 at 7:17 PM, Sergey Chernyshev
sergey.chernys...@gmail.com wrote:
How do we go about doing this? Can it be tied into Usability project (
Sergey Chernyshev wrote:
Yes, of course - I checked it out and that's why I quoted it in my original
email.
My brief overview made me feel that it wasn't enough.
I just didn't want this to be only in context of localization as performance
is more related to overall user experience then to
As mentioned already, I'm not sure if localization is the best for candidate
for being held in JavaScript, but other things mentioned, e.g. single
request, minified and infinitely cached JS is what I'm looking at for
overall MW infrastructure - so far it's a big performance problem for MW -
Hoi,
Sergey, you may also want to take a visit at the folks at
http://translatewiki.net. This is where the internationalisation and
localisation effort for MediaWiki and its extensions and all the rest is
concentrated. In the past translatewiki,net has been instrumental in
bringing best practices
On 2/24/09 4:17 PM, Sergey Chernyshev wrote:
As mentioned already, I'm not sure if localization is the best for candidate
for being held in JavaScript, but other things mentioned, e.g. single
request, minified and infinitely cached JS is what I'm looking at for
overall MW infrastructure - so
On Tue, Feb 24, 2009 at 7:17 PM, Sergey Chernyshev
sergey.chernys...@gmail.com wrote:
How do we go about doing this? Can it be tied into Usability project (
http://usability.wikimedia.org/)?
It doesn't seem usability-related. If you have commit access, you
could just start committing code
