Talk:MediaWiki localization

There might be alot of users who use Media-Wiki on rather oldfashioned hardware like me on a PIII-500 with 256 mb because it makes a fine Notepad.

Those should know that they won't be able to access Project:All_messages Page to customize their language settings because that script uses so much power that one needs to adjust alot of settings to see that page at all, let alone load several times in a row after editing it.

--Tictric 22:34, 14 Jun 2004 (UTC)

I believe the newer Special:Allmessages is slightly faster, and thus possibly address this complaint. - IMSoP 17:21, 27 Sep 2004 (UTC)

Updating messages / changing the language

I suspect this section needs updating to reflect the changes in 1.3:

• "$wgUseDatabaseMessages = false;" presumably doesn't disable the Template: namespace, now that it's explicitly different from the software l10ns
• "(This'll be cleaner in 1.3.x...)" - anyone know off-hand if it is cleaner, and in what ways?

Basically, someone who knows how the MediaWiki: namespace works under 1.3 needs to just make a note of it here. - IMSoP 23:25, 23 Jun 2004 (UTC)

It appears this is now fixed. - IMSoP 17:21, 27 Sep 2004 (UTC)

ElayaRaja S ( elayaraja.s@gamil.com )

mediawiki 1.3.5 lags wikipedia in localization

While the template-based localization is very nice, it has the drawback that localizations done for the wikipedias are no longer in the mediawiki source files, e.g. the Estonian wikipedia works fine, but the LanguageEt.php is far from complete (look at all the red in the system messages).

Another thing is that you can configure quite a lot with these files, so that for example MediaWiki:nogomatch actually adds very useful functionality that is not in mediawiki 1.3.5!

Exploration des applications et des systèmes des partenaires

Bonjour, J'ai commencé l'exploration des systèmes et des applications des partenaires. J'ignore est ce que je peux leurs demander le code pour que je puisse les voir comme des boites blanche et les installer dans mon poste ou bien je dois les voir comme des boites noires à explorer les fonctionnalités ?

Merci de me répondre. (Gilbert)

ElayaRaja S Bangalore

Language negotiation for system messages?

Is it possible (without substantial coding) for system messages to be rendered depending upon the request's Accept-Language header? It appears to me offhand that you choose a language at install time, then that's the only language used. Even if $wgUseDatabaseMessages == false, $wgLanguageCode seems to control what language is rendered. Mike Linksvayer 02:10, 2 Feb 2005 (UTC)

The newest version of the software (1.4, currently in beta, but active on this and other Wikimedia sites) allows logged in users to set the language of the UI in preferences, so it's no longer true that you're stuck with whatever the configuration file says. Negotiation with the browser might make an interesting addition to this, however - perhaps as a default for this preference. - IMSoP 22:37, 5 Feb 2005 (UTC)

Translating Messages

How can I help in translating messages? There should be a link on this page ... --zeno 08:34, 1 Jul 2005 (UTC)

Installing a mediawiki with 2 or more languages

I'm searching for help installing a mediawiki-1.5beta3 in 2 different languages. i´ve seen that the user can choose the language, but that´s only for the application, not for the content. on wikipedia they set up 2 subdomains. propably these are 2 seperate installations? but how does it work then with the interlanguage link? i would like to use the monoblock design with the language link on the left side. has wikipedia 2 complete different setups? but the users can log in both with the same account!? do i need 2 databases (de_wiki and en_wiki) or 1 database (wiki) and different table names (de_... and en_...)

thanks for infos! --patxi 08:08, 27 July 2005 (UTC)

Wikipedia has separate wikis for each language; obviously, you don't necessarily need multiple copies of the files (just use symlinks and PHP include_once directives as necessary). Nor, in fact, do you need completely separate databases, since you can specify a table prefix in the installer, so the two won't conflict. Users do, however, have to log in separately on each wiki (this may cease to be the case eventually; see Single login and the many related pages). The sub-domains are "name-based virtual folders" on Apache, and the interlanguage links are taken care of by having your Help:Interwiki linking set up correctly. I hope that covers everything - at least as far as leading you towards appropriate further reading, anyway. - IMSoP 19:49, 23 September 2005 (UTC)