1
0
mirror of https://github.com/Pomax/BezierInfo-2.git synced 2025-09-01 12:23:19 +02:00

Created localize (markdown)

Mike Kamermans
2017-02-17 11:11:51 -08:00
parent d6dd5aad05
commit 2b0ff30fce

31
localize.md Normal file

@@ -0,0 +1,31 @@
# Localization
Localizing content for the Primer is relatively straight forward:
1. fork the project
2. Each section directory in the `./components/sections/` directory contains a `content.en-GB.md` file which acts as master English document
3. create a file called `content.{locale code}.md` in the same directory (for instance, Japanese is `content.ja-JP.md`, Chinese is `content.zh-CN.md`, etc.)
4. Translate the English content to your locale
5. Form a PR to the Pomax/BezierInfo-2 repository for any translated files you make in this way.
## Typographic conventions
- Don't use spaces or the like to make text "look right" - the fonts for each locale and the presentation CSS will take care of getting the spacing right (and in cases where this is insufficient, custom JavaScript per locale can be used to ensure moderately decent presentation until the CSS specification catches up)
## Conventions for specific locales
### English
English content uses British spelling. There is an en-GB; there will not be an en-US.
### Japanese
- no specific policies (yet)
### Chinese (traditional)
- no specific policies (yet)
### Chinese (simplified)
- no specific policies (yet)