That's a good example of what I was proposing (although, for some
reason, I think MW loads all strings anyway, not sure...).
Anyway, I was just trying to ask you (all) to be i18n-aware while you're
developing tools from scratch, if there is someone (like me!). It will
be far easier to do it also from scratch, than having to run all scripts
to turn them i18n-ready.
Imagine um mundo onde é dada a qualquer pessoa a possibilidade de ter livre acesso ao
somatório de todo o conhecimento humano. É isso o que estamos a fazer.
Participe também: http://www.wikimedia.pt
Ter, 2011-03-29 às 19:22 +0200, Maarten Dammers escreveu:
Op 29-3-2011 17:23, Nuno Tavares schreef:
Joan, just my opinion about that: the drawback of
it is having to load
(in memory) multiple strings that will not be used anytime - if you set
your language to PT, you are still loading the strings to ES,CA, etc..
I'd go for something like:
With appropriate security wrapping, obviously. This will load only one
set of strings (the language set in $lang).
More, if you send the whole string file to translate to both PT and ES,
it might to turn in difficulties when you'll merge the translations..
usually it's best to deliver PT-only to PT people, ES-only to ES people,
etc etc and so on.
Let's not reinvent the wheel again. At
you can see how it's done in MediaWiki.
I suggest we stick to that :-)
Wiki Loves Monuments mailing list