- Jun 10, 2017
- 11,017
- 16,307
You can't avoid it, just deal with it.How can I avoid that?
Like you said, the problem come from the change in the label name. The "reference ID" used to design the string isn't the same anymore because of this
There's theis there any way for renpy to notice if the text is the same instead of the label name? (I seem to remember that in the menu options it does, I'm not sure).
translate LANGUAGE strings
statement, which is more generic, but I think that it apply only for screens. Anyway it would slow down the game since Ren'py would have to compare the strings instead of just searching for the right label.It should works yes. When looking at the two example you provided, only the part of the reference regarding the label changed, but I don't have looked deep enough to the translation part to ensure that the rest of the reference (the "b472194a" in your example) effectively describe the string and not it's position into the label.Or maybe generate the translation ("tl/english/patch.rpy"), make a copy/paste of the other translation ("tl/english/meg.rpy") and make a substitution of the label "meg_intro" for "meg_intro_p"?
I think this last option would work, but if there's any easier one I'd like to know
It all depend of what I said right above.Note: Could it be easier using the new function "config.allow_duplicate_labels"?
If the "b472194a" describe the string, then yes it would be easier since the actual translation file would works without problem. But if it describe the position of the string, then the problem would stay the same. The start of the reference would be "meg_intro_" for both, but it's the rest of the reference that would change.
The ideal would be to have a script that use the comment (or
old
property) to rebuild the translation file.