New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor ally dialogue in UtBS #6158
Comments
With four potential allies in the campaign, there is a lot of dialogue duplication. This refactoring attempts to consolidate the text. Additionally, the ally ID was recorded in the variable ally_name which can be confusing, so rename it to ally_id instead.
With four potential allies in the campaign, there is a lot of dialogue duplication. This refactoring attempts to consolidate the text. Additionally, the ally ID was recorded in the variable ally_name which can be confusing, so rename it to ally_id instead.
With four potential allies in the campaign, there is a lot of dialogue duplication. This refactoring attempts to consolidate the text. Additionally, the ally ID was recorded in the variable ally_name which can be confusing, so rename it to ally_id instead.
With four potential allies in the campaign, there is a lot of dialogue duplication. This refactoring attempts to consolidate the text. Additionally, the ally ID was recorded in the variable ally_name which can be confusing, so rename it to ally_id instead.
As a translator (czech), I don't mind multiple similar text strings (because they are easy to translate), but the inappropriate use of variable names, which are difficult to incorporate into translation. And Czech still uses Latin, I can't imagine what the troubles will be in other scriptures. |
…nslated text, the use of variables adds challenges to some translations. The particular discussion which led to this reversion relates to the Czech translation. Revert "Refactor handling of allies in UtBS. Resolves wesnoth#6158." Revert "Add po hints where self-referential troll names have been replaced with variables." This reverts commit 541f0a1. This reverts commit 4a3ddfb.
Re-opening due to reversion of #6165 via d5b95e6. I suspect it's unlikely that avoiding text redundancy and avoiding variables for translation efforts can be resolved together. I want to highlight that the refactoring was not the only place where variables are used in translated text. So I consider that the question of what to do in those circumstances may also be relevant. A couple of examples: wesnoth/data/campaigns/Dead_Water/scenarios/10_The_Flaming_Sword.cfg Lines 272 to 275 in d5b95e6
wesnoth/data/campaigns/Heir_To_The_Throne/scenarios/20b_Underground_Channels.cfg Lines 612 to 613 in d5b95e6
For more background, see the discussion in hrubymar10/wesnoth-cs#209. |
Reopened due to a discussion in hrubymar10/wesnoth-cs#209. |
I think d5b95e6 reverted too much stuff, as it included reverting the variable-name change from Edit: I'd mistakenly assumed this was also affecting 1.16, hadn't expected the translation team to already be working on master. |
You previously made the point to try to make some sort of compatibility, despite the fact this was only applied to 1.17.x. That's what #6301 was supposed to include. The renaming made sense to me, but if you want to keep it then do you still require the (unfinished) 'compatibility' work to go with it? If not, it's probably better to just rename the variables separate to the text consolidation.
Pretty sure #6165 was only applied to master, not 1.16. |
@knyghtmare has put on the roadmap that he'll rewrite S12 for 1.17.5, so I'm happy if the current S12 doesn't have compatibility with 1.16.x save files. Does that finish the compatibility work with the currently-prepared code? Sorry if I'm missing details here. |
Is this still on the roadmap? ISTR him saying he'd given up on it... |
You are referring to the campaign rewrite? For this issue specifically, I recall I had to revert the consolidation effort because of translation overhead. The discussion is in my (reverted) PR and the linked Czech translation discussion. |
Well, Knyght rewriting S12 of the campaign specifically; I think it was issue #6142 (currently postponed...) |
#6155 highlights that the way the dialogue of a potential ally is handled is not good. Basically it appears in many cases strings are printed in quadruplicate to accommodate the four different potential ally characters. Suggest refactoring this not just to avoid the redundant strings and corresponding translation effort but also to avoid complications with female characters as @CelticMinstrel mentioned.
The text was updated successfully, but these errors were encountered: