Localisation guidelines

From Betawiki
Jump to: navigation, search
Betawiki
Intro
Getting started
How to start
Translatable
Interface translation
Regional settings
Process
Other
Language project
Languages
Group statistics
Statistics
Developer log
See also
Import requests
Offline
Translator privileges
Localisation guidelines
Support
Tasks


Contents

[edit] How to identify the messages that need to be updated in your language?

  • Use Special:Translate to Review changes to your language. Update any message tagged with !!FUZZY!!. These messages have been changed since the last time they were translated and need to be updated.
  • Use Special:Translate to View all untranslated messages from your language. Translate any message that comes up in the list.

[edit] Translating namespace names

If the namespace names for your language are not localized, you can translate them via Special:Magic. You can request committing these on Translating:Tasks. The name of the project namespace (e. g. "Betawiki" on this wiki) should follow "{{SITENAME}}". If it is not possible in your language to form a valid name for the Project_talk namespace without changing sitename, please contact a developer.

Namespace aliases should only be added if pre-existing namespace names are changed. They should not be created by default. See mw:Manual:$wgNamespaceAliases about how to implement them. The $wgNamespaceAliases should be added to your MessagesXyz.php.

[edit] Sitename/project namespace on Wikimedia wikis

If the sitename at your project is not localized, you should contact the other contributors at your project and find consensus about translation, then open a request at bugzilla: that it should be changed.

[edit] other technical issues

  • There are some other functions which can be specified in the MessagesXyz.php file. These are:
  1. {{plural:}}; used by most slavic languages
  2. specify how a large number should be displayed: 1,000,000.13 or 1.000.000,13 or 1 000 000,13 etc.
  3. date formats
  4. search optimization
  5. ISBN configuration
  6. specifying linkprefix and linktrail
  7. to be continued...

[edit] actions requiring root or shell access

  • setting the project logo: upload it as Image:Wiki.png to your project, protect it, and make a Bugzilla request that it should be used as project logo.
  • to be continued ...
Google AdSense
Personal tools