pmrowla
commented
4 years ago So basically for games like AGLS where text lines are not manually broken up (and speaker info is handled via NAMELABEL as an image in the message box instead of a text line), you would get something like:
(syntax borrowed from renpy here, but probably not exactly what pylm syntax would look like)
# 00000623.lsb.pylm.translation
...
# NAMELABEL: 名前_リンネ
translate 070f_603912e6:
# "「ああ、これがフォン・ブラウン………憧れの、フォン・ブラウンに、ついに………」<PG>"
e '"Ah, this is Von Braun... the Von Braun I've longed for, finally..."'where 070f is the TpWord block from 0623.lsb, and 603912e6 is the first 4 bytes of the sha256 hash for the original JP. Everything after the e is what the translator would add themselves
For games that manually do line breaks, you'd get something like:
# 00001.lsb
translate 0009_a18577af:
# 【 教師 】<BR>
# え～、最近の研究では、次元断裂の際に現れる敵性生物たちは<BR>
# 一緒に転移してくる遺跡などから異世界の文明によって作られた<BR>
# 兵器である、と考えられていて……<PG>
e "[Sensei]"
e "<translation line 1>"
e "<translation line 2>"
e "<translation line 3>"
e "[Sensei]"
e "<translation line 4>……"This hypothetical also shows how we would handle the case where the msg box height is 4 lines including the speaker name, and the translated version would be more than 4 lines long.
We also assume that our tool for patching the translations back into an lsb will be smart enough to use <PG> at the end of the final e "..." line for a translation, and <BR> at the end of all the other ones, so that translators no longer have to add in the line breaks themselves. (Although for the 2nd case it may actually be required for the translator to manually add the hard page break between lines 3 and 4 to get the desired scroll/pagination behavior)
Stefan311
akanetr
Working off of extracted .lns scripts is better than nothing, but given that
it would be ideal to have a better way of extracting text lines for one lsb (into a single file), translating them, and automatically patching those translations back into an lsb.
I'm currently thinking it would be nice to have something that looks similar to ren'py's translation units, where each "translation unit" would just be text up to a page break (
<PG>). This would give the translator a good idea of what was originally supposed to fit into one message box screen (or was originally safe to rely on the game to scroll automatically).Certain system event info (like
NAMELABEL) probably still needs to be included as well, not sure about any other system events though.