silverstripe-framework/docs/en/misc/contributing/translation.md

## Contributing Translations for the User Interface

[« Back to Contributing page](../contributing)

The content for UI elements (button labels, field titles) and instruction texts shown in the CMS and
elsewhere is stored in the PHP code for a module (see [i18n](/topics/i18n)). 
All content can be extracted as a "language file", and uploaded to an online translation editor interface.
SilverStripe is already translated in over 60 languages, and we're relying on native speakers
to keep these up to date, and of course add new languages. 
Please [register](translation-process) a free translator account to get started, 
even if you just feel like fixing up a few sentences.
See [our translation workflow](translation-process) for more details.
Broke up contributing docs into 4 sections and unified code contribtion guide. The guidelines for contributing code were scattered across a section of contributing.md and collaboration-on-git.md. I've updated this to have separate contributing/code.md page with all the content in a single cohesive page. We also have contributing/documentation.md, contributing/issues.md and contributing/translation.md. 2012-10-09 01:32:22 +02:00			`## Contributing Translations for the User Interface`

			`[« Back to Contributing page](../contributing)`

			`The content for UI elements (button labels, field titles) and instruction texts shown in the CMS and`
			`elsewhere is stored in the PHP code for a module (see [i18n](/topics/i18n)).`
			`All content can be extracted as a "language file", and uploaded to an online translation editor interface.`
			`SilverStripe is already translated in over 60 languages, and we're relying on native speakers`
			`to keep these up to date, and of course add new languages.`
			`Please [register](translation-process) a free translator account to get started,`
			`even if you just feel like fixing up a few sentences.`
			`See [our translation workflow](translation-process) for more details.`