Ren'Py Translator ToolKit  Check-in [2a6f2fe54d]

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Doc fixes
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256:2a6f2fe54d5bca8c2efc8b9abdf1538c60b731bafb2eddd332a6bdf41afc7065
User & Date: Beuc 2019-06-02 15:46:14
Context
2019-06-30
19:03
Always recompile translations as I always have a doubt check-in: 7fe90bf200 user: Beuc tags: trunk
2019-06-02
15:46
Doc fixes check-in: 2a6f2fe54d user: Beuc tags: trunk
2019-06-01
19:23
Note about not removing translation .rpy files + clarification check-in: 9775ad51f3 user: Beuc tags: trunk
Changes

Changes to README.md.

15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

Work on your Ren'Py translation using the PO format. This brings support for iterative translation:

- Translatable strings are kept in the same order as in the Ren'Py scripts, to give you context, even after an update.  You can also sort by other criteria in your PO editor if needed.

- Fuzzy matching on update, so you can e.g. update a translation after a typo fix with a single click/keystroke.

- Detect obsolete strings on update, so you don't waste time translating them.

- Ren'Py forces you to either: display empty texts when there's no translation yet; or prefill all translations using the original language but this makes it hard to see untranslated strings. Now you can have both, as untranslated strings will be empty in your .po but filled with the original language in the Ren'Py translation files.

Handle duplicates, so you can translate the same dialog line differently depending on the context.  Only duplicates get an additional context marker, so as to avoid tons of fuzzy texts when e.g. you renamed a Ren'Py label.

Up-to-date source references (file:line).

Support customized Ren'Py translations (WIP): for instance .po doesn't support splitting a translation to several Ren'Py dialogs, but if you did that in Ren'Py with a customized translation block, don't translate it in the PO file, or add a `# renpy-ttk:ignore` comment in the `translate` block before your translations.


## Install and run

### From Ren'Py (GUI)

Place this directory along with your other Ren'Py games, so it shows







|







|







15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

Work on your Ren'Py translation using the PO format. This brings support for iterative translation:

- Translatable strings are kept in the same order as in the Ren'Py scripts, to give you context, even after an update.  You can also sort by other criteria in your PO editor if needed.

- Fuzzy matching on update, so you can e.g. update a translation after a typo fix with a single click/keystroke.

- Hide obsolete strings on update, so you don't waste time translating them.

- Ren'Py forces you to either: display empty texts when there's no translation yet; or prefill all translations using the original language but this makes it hard to see untranslated strings. Now you can have both, as untranslated strings will be empty in your .po but filled with the original language in the Ren'Py translation files.

Handle duplicates, so you can translate the same dialog line differently depending on the context.  Only duplicates get an additional context marker, so as to avoid tons of fuzzy texts when e.g. you renamed a Ren'Py label.

Up-to-date source references (file:line).

Support customized Ren'Py translations (WIP): for instance .po doesn't support splitting a translation to several Ren'Py dialogs, but if you did that in Ren'Py with a customized translation block, add a `# renpy-ttk:ignore` comment in the `translate` block before your translations.


## Install and run

### From Ren'Py (GUI)

Place this directory along with your other Ren'Py games, so it shows