docs: add learntocode RPG (#44868)
* docs: add learntocode RPG * Update how-to-translate-files.md * Update docs/how-to-translate-files.md Co-authored-by: Eric Cheng <ericcheng9316@gmail.com> * Update how-to-translate-files.md Co-authored-by: Lynn Zheng <lynnzheng08@outlook.com> Co-authored-by: Eric Cheng <ericcheng9316@gmail.com>
This commit is contained in:
nhcarrigan
GitHub
parent
71ef222473
commit
eb83f393ad
@ -122,6 +122,131 @@ Translating our contributing documentation is a similar flow to translating our
|
||||
> [!NOTE]
|
||||
> Our contributing documentation is powered by `docsify`, and we have special parsing for message boxes like this one. If you see strings that start with `[!NOTE]`, `[!WARNING]`, or `[!TIP]`, these words should NOT be translated.
|
||||
|
||||
## Translate the LearnToCode RPG
|
||||
|
||||
The LearnToCode RPG runs on Ren'Py, which uses special syntax for translated strings: (See [Ren'Py Text documentation](https://www.renpy.org/doc/html/text.html))
|
||||
|
||||
- The sentences to be translated are always between `""`. These are dialogues or UI strings. The keywords that come before or after the dialogue are game engine control keywords and will be explained in details in subsequent rules. Please note that this first rule governs all subsequent rules listed.
|
||||
- In case of `new "..."` Do not translate the `new` keyword.
|
||||
- Prefixes like `player`, `annika`, `layla`, `marco` (or variants like `player happy`, `player @ happy`) should not be translated. These are control keywords to correctly display the character sprite in the game.
|
||||
- Postfixes like `nointeract` should not be translated.
|
||||
- Do not translate things between `[]` and `{}`. These are variable interpolations and text tags. These must remain halfwidth parentheses `[]` and `{}` instead of their fullwidth counterparts `【】` and `「」`
|
||||
- Do not translate the `nointeract` keyword at the end of the sentence.
|
||||
- If we try to use fullwidth parentheses `（）`, a QA warning will show. To avoid the QA warning, use halfwidth parentheses `()`
|
||||
|
||||
### Examples
|
||||
|
||||
---
|
||||
|
||||
#### Before translation
|
||||
|
||||
```renpy
|
||||
# "[player_name]? What a coincidence! Our VIP team member {a=[vip_profile_url]}[player_name]{/a} will be honored to hear that."
|
||||
"[player_name]? What a coincidence! Our VIP team member {a=[vip_profile_url]}[player_name]{/a} will be honored to hear that." <--- this is the line that needs to be translated. see translation below
|
||||
```
|
||||
|
||||
#### After translation
|
||||
|
||||
```renpy
|
||||
# "[player_name]? What a coincidence! Our VIP team member {a=[vip_profile_url]}[player_name]{/a} will be honored to hear that."
|
||||
"[player_name]？好巧，我们的VIP队友{a=[vip_profile_url]}[player_name]{/a}会很高兴的。"
|
||||
```
|
||||
|
||||
Note: The `[]` and `{}` tags should be left intact.
|
||||
|
||||
---
|
||||
|
||||
#### Before translation
|
||||
|
||||
```renpy
|
||||
old "{icon=icon-fast-forward} Skip"
|
||||
new "{icon=icon-fast-forward} Skip" <-- translate this line, see below
|
||||
```
|
||||
|
||||
#### After translation
|
||||
|
||||
```renpy
|
||||
old "{icon=icon-fast-forward} Skip"
|
||||
new "{icon=icon-fast-forward} 跳过"
|
||||
```
|
||||
|
||||
Note: Again, the `new` prefix and the `{icon=icon-fast-forward}` tag should be left intact.
|
||||
|
||||
---
|
||||
|
||||
#### Before translation
|
||||
|
||||
```renpy
|
||||
# layla @ neutral "Hehe, [player_name], you are a fun one. I'm sure you will enjoy your work as a developer."
|
||||
layla @ neutral "Hehe, [player_name], you are a fun one. I'm sure you will enjoy your work as a developer."
|
||||
```
|
||||
|
||||
#### After translation
|
||||
|
||||
```renpy
|
||||
# layla @ neutral "Hehe, [player_name], you are a fun one. I'm sure you will enjoy your work as a developer."
|
||||
layla @ neutral "哈哈，[player_name]，你真有趣。我相信你一定会喜欢你的开发者工作的。"
|
||||
```
|
||||
|
||||
Note: `layla @ neutral` and `[player_name]` are left unchanged.
|
||||
|
||||
---
|
||||
|
||||
#### Before translation
|
||||
|
||||
```renpy
|
||||
# player "Maybe this is all a dream?" nointeract
|
||||
player "Maybe this is all a dream?" nointeract
|
||||
```
|
||||
|
||||
#### After translation
|
||||
|
||||
```renpy
|
||||
# player "Maybe this is all a dream?" nointeract
|
||||
player "也许这都是一场梦？" nointeract
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### A Note on How Crowdin Segments a Sentence
|
||||
|
||||
Pay attention to how Crowdin segments a line of dialogue wrapped between opening and closing quotes `""`. When we are translating the dialogue, we need to make sure to retain the opening and closing quotes, even if the quotes appear in different segments.
|
||||
|
||||
This is the line to be translated:
|
||||
|
||||
```renpy
|
||||
player @ surprised "{b}Full-stack{/b}... What is that? I better take notes so I can learn more about it."
|
||||
```
|
||||
|
||||
Crowdin segments it into three parts like below:
|
||||
|
||||
<img width="836" alt="Screen Shot 2022-01-23 at 10 36 43" src="https://user-images.githubusercontent.com/35674052/150693962-d3b091e5-2432-44d0-9d24-195ea7d7aeda.png">
|
||||
|
||||
```renpy
|
||||
# original
|
||||
player @ surprised "{b}Full-stack{/b}
|
||||
# translated, keeping the opening quotes `"`
|
||||
player @ surprised "{b}全栈{/b}
|
||||
```
|
||||
|
||||
<img width="750" alt="Screen Shot 2022-01-23 at 10 36 49" src="https://user-images.githubusercontent.com/35674052/150693965-15411504-791a-4db3-8b14-bc9177be6375.png">
|
||||
|
||||
```renpy
|
||||
# original
|
||||
What is that?
|
||||
# translated, no quotes on either side
|
||||
这是什么？
|
||||
```
|
||||
|
||||
<img width="857" alt="Screen Shot 2022-01-23 at 10 36 54" src="https://user-images.githubusercontent.com/35674052/150693969-062e3268-580f-4ad2-97db-cab6240b6095.png">
|
||||
|
||||
```renpy
|
||||
# original
|
||||
I better take notes so I can learn more about it."
|
||||
# translated, keeping the closing quotes `"`
|
||||
我最好做笔记，这样我可以学习更多东西。"
|
||||
```
|
||||
|
||||
## Rate Translations
|
||||
|
||||
Crowdin allows you to rate the existing proposed translations. If you attempt to save a translation, you may see a message indicating that you cannot save a duplicate translation - this means another contributor has proposed that identical translation. If you agree with that translation, click the `+` button to "upvote" the translation.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user