|
|
15.
|
|
|
Alternate languages are referred to by names which can double as python identifiers. (Starts with a letter or underscore, followed by letters, numbers, and underscores.)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/translation.rst:44
|
|
|
16.
|
|
|
Generating Translation Files
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/translation.rst:49
|
|
|
17.
|
|
|
When the project scripts are available, translation files can be generated by opening the project in the Ren'Py Launcher, and choosing "Generate Translations". The launcher will prompt you for the name of the language to generate, and will then proceed to create or update the translation files.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/translation.rst:51
|
|
|
18.
|
|
|
The translation files live in directories underneath the "tl" subdirectory of the game directory. For example, if you create a piglatin translation of the tutorial project, translation files will be placed under ``tutorial/game/tl/piglatin``.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/translation.rst:57
|
|
|
19.
|
|
|
There will be one translation file created per game script file. The common.rpy file will also be created to contain translations of strings found in the common code.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/translation.rst:62
|
|
|
20.
|
|
|
Translating Dialogue
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/translation.rst:67
|
|
|
21.
|
|
|
As Ren'Py is a visual novel engine, we expect most translation to involve dialogue. Ren'Py includes a flexible framework that allows dialogue to be split, combined, reordered, and omitted entirely.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/translation.rst:69
|
|
|
22.
|
|
|
Translation Units
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/translation.rst:74
|
|
|
23.
|
|
|
The fundamental unit of translation is a block of zero or more translatable statements, optionally followed by a single say statement. Translatable statements are the voice and nvl statements. For example take the following game::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/translation.rst:76
|
|
|
24.
|
|
|
This is broken up into multiple translation units. Each unit has an identifier assigned to it, with the identifier being generated from the label preceding the unit, and the code inside the unit. (If multiple units would be assigned the same translation number, a serial number to the second and later units to distinguish them.)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/translation.rst:90
|
