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
[1.16] SoF S09: A few extra translation hints #6633
Conversation
po: In SoF S09, many strings involving Krawg (a gryphon) assumed that Krawg was the only flying unit. Similar texts have been added that are used when the player has gryphon riders too; most of these will be marked as fuzzy versions of the Krawg-only strings.
I guess, is there a benefit to doing it this way rather than regular hints that show up in poedit? |
The idea of putting it in the commit message is that it's useful for a translator who had an up-to-date 1.16.2 file and is looking at the new strings, but would just be excess info for a translator who's starting with a very out-of-date or never-translated file. |
I'd say this should include the (I assume python) script to do this as well then. |
I wasn't planning to automate it, at least not in the near future. The plan is just to pipe the output of The idea being that it's something that's collated, edited, and sent to the i18n list when the pot-update is done. |
Well, I would say that his example is extremely unsuitable as a general translation comment:
This only makes sense if the translator is comparing two versions. It's nonsensical for a generic po file, especially a newly-generated one. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just remarking on the hints specifically, this seems good to me.
Also an idea for the translators' changelog: put a paragraph starting with
po:
in the commit message, so that someone can generate the translators' changelog from the Git changelog.Example covering this and 2581ab6 / f82079b :