Note: This policy page is not community-approved yet. These rules hold no value yet.

Advtrains is formed of a diverse worldwide community. This means that a large portion of the people working on advtrains are multilingual. If you wish to work on translations:

• Keep to pages which should not change over time, such as those in Events. Try to find the most past-tense pages
• Put the language code in square brackets before the name of the article, for example ''[zh-hans]
• Keep the translation as accurate to the original as possible; translation should be an invisible art
• Provide English and your language translations of any discussion about page content as a whole, across languages

The reason not to translate documentation is that there are no systems in place to allow easy syncing of language-versions, resulting in one version potentially becoming outdated and potentially even inferior to English, resulting in a reader migration away (using machine translation to access updated text) from that version, only making the problem worse.