<commit_before>---
title: Translate Code.org
rightbar: blank
---


# Help us translate Code.org

We want help translating the Code.org web site, tutorials, and videos. To sign up, please [fill out this form](http://eepurl.com/Im_In).

## Tips for Translating
The Code.org drag-drop tutorials are based on the Blockly language. Many of the tips below are loosely based on the wiki article [Translating:Blockly](http://translatewiki.net/wiki/Translating:Blockly)

### Use Informal Style
The tone is informal and conversational, and we prefer short phrases to long ones, such as "if path ahead" instead of "if there is a path ahead". Translations do not need to be exact.

### Be Gender Neutral
The target audience for drag-drop programming is individual or small groups of children, aged 8+. Please use gender-neutral forms if possible in your language.

### Avoid Technical Jargon
Our tutorials are meant for beginners, so please avoid technical jargon. It is **far** more important that language be clear to beginners than for it to match what experienced programmers might use. For example, Blockly uses the term "text" instead of "string", and we use "list" instead of "array". Also, Blockly uses 1-based indexing instead of the more common 0-based indexing.

### Review The CrowdIn Glossary
Consistency is important. In English, for example, we have gone back and forth on whether to use the term "function" or "procedure". What is more important than which term is chosen is that the same term is used throughout. Inside the CrowdIn interface, click the "Terminology" tab to see what the key terms are. These are the ones that need to be translated consistently within each language.

### Untranslatable Symbols
If any mathematical (or other) symbols are inappropriate in your language but are not offered for customization, please let us know by contacting <EMAIL>.

### Translate Text, Not Code
Code that shows up in peach or green like `var x = 2;`, `&quot;`, `%{keyword}` should not be translated. There is also the case when you might see text such as `{ outside text { inside text } outside text }`. Notice the two sets of curly braces. Translate the inside text, but do not translate the outside text. And for consistency, leep the same capitalization and punctuation of our strings.

## How to Use CrowdIn

<embed src="/files/crowdin.swf" width=800 height=550 />

See a larger version of the [demo video](/files/crowdin.swf).

## Ready to Translate?

1. Sign up [here](http://eepurl.com/Im_In) to stay up to date on what we need translated.
2. Create an account on CrowdIn, join the [Code.org project](http://crowdin.net/project/codeorg/invite), and start immediately!

---
<commit_msg>changed text on translate page<commit_after>---
title: Translate Code.org
rightbar: blank
---


# Help us translate Code.org

We want help translating the Code.org web site, tutorials, and videos. 

1. Sign up [here](http://eepurl.com/Im_In) to stay up to date on what we need translated.
2. Create an account on CrowdIn, join the [Code.org project](http://crowdin.net/project/codeorg/invite), and start immediately!

## Tips for Translating
The Code.org drag-drop tutorials are based on the Blockly language. Many of the tips below are loosely based on the wiki article [Translating:Blockly](http://translatewiki.net/wiki/Translating:Blockly)

### Use Informal Style
The tone is informal and conversational, and we prefer short phrases to long ones, such as "if path ahead" instead of "if there is a path ahead". Translations do not need to be exact.

### Be Gender Neutral
The target audience for drag-drop programming is individual or small groups of children, aged 8+. Please use gender-neutral forms if possible in your language.

### Avoid Technical Jargon
Our tutorials are meant for beginners, so please avoid technical jargon. It is **far** more important that language be clear to beginners than for it to match what experienced programmers might use. For example, Blockly uses the term "text" instead of "string", and we use "list" instead of "array". Also, Blockly uses 1-based indexing instead of the more common 0-based indexing.

### Review The CrowdIn Glossary
Consistency is important. In English, for example, we have gone back and forth on whether to use the term "function" or "procedure". What is more important than which term is chosen is that the same term is used throughout. Inside the CrowdIn interface, click the "Terminology" tab to see what the key terms are. These are the ones that need to be translated consistently within each language.

### Untranslatable Symbols
If any mathematical (or other) symbols are inappropriate in your language but are not offered for customization, please let us know by contacting <EMAIL>.

### Translate Text, Not Code
Code that shows up in peach or green like `var x = 2;`, `&quot;`, `%{keyword}` should not be translated. There is also the case when you might see text such as `{ outside text { inside text } outside text }`. Notice the two sets of curly braces. Translate the inside text, but do not translate the outside text. And for consistency, leep the same capitalization and punctuation of our strings.

## How to Use CrowdIn

<embed src="/files/crowdin.swf" width=800 height=550 />

See a larger version of the [demo video](/files/crowdin.swf).

---

{'fraction_non_alphanumeric': 0.07362885048835462, 'fraction_numerical': 0.004507888805409466, 'mean_word_length': 4.378787878787879, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5619784', 'n_tokens_mistral': 1442, 'n_tokens_neox': 1371, 'n_words': 785}