-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Put translation strings in multiple files #23434
Comments
The open source game 0.A.D is a good example of doing this. Their developers split strings into different categories and put them in separate PO files, such as 'In-Game UI', 'Tutorials', 'Buildings', 'Maps', 'Units'. Someone who is willing to do this could have a look at how they do it technically. |
Yes, I was exactly thinking of something along the lines of 0. A.D. |
Would it cause the need to translate everything again in Transifex? Even using its own repository of already translated strings it would be no joke to re-link over 24.000 of them, and could revert all teams translation effort to tile one. |
Obviously this must be done in a non-destructive manner, otherwise we lose months of work. |
You can search Transifex for occurrence in each json file. I think it applies to C++ files as well. For example, to search all strings from |
Is there any progress on this issue? The translation resource just continue to grow and grow and grow. It's barely managable anymore. I think splitting off the file on a per-mod basis would be a huge improvement already. I suspect the base game will still be huge but at least you can focus on it now. It would help translators to priotize their time. It's not good that after you managed to reach 90%, you might still have lots of missing strings in the base game because everything is mixed together … |
I second what Wuzzy2 wrote. 0.E went as a huge hit on us, especially when we have a small group of translators. |
I add my voice to this concern. Transifex is painful to use most of the time, and I've spent more time trying to update translation with file upload than I was actually translating. |
I think moving to Weblate and then tagging up the strings with different labels would help, short of dividing up files. Anything you do on Transifex removes translator credits, which makes that mess of a platform even harder to handle. Translated a 16k line document by hand once, 24k is just on another planet. ;) |
It would, as suggested, also help to split mods at least. These would easy up translating the base game content as a priority for new languages, or the mods in some order. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Please do not bump or comment on this issue unless you are actively working on it. Stale issues, and stale issues that are closed are still considered. |
Currently, almost all strings of the game are stored in one giant PO. It has over 24,000 strings. This is a big problem as it is not always easy to figure out the context, and the string list in general is pretty chaotic and impossible to navigate. Scrolling over a list of 24,000 strings is not fun, especially not in Transifex.
It would make life a lot easier for translators if the massive amount of strings is at least moved into different PO files. The idea is that breaking down the list of strings in smaller, context-based lists makes it more managable.
I propose the strings be moved in categories like this:
This would also make it possible to priotirize resources on Transifex. The core mods and the core GUI are obviously top priority while other non-core mods should get a lower priority. The benefit of this is that translators can more quickly come to an useful result.
More ideas welcome! :-)
If someone is willing to do this, please do so in a non-destructive way. No existing translation must get broken because of this. The transition must be done smoothly. If you can't do this, don't do it at all. Maybe even temporarily lock down Transifex during the transition to make sure no translator work is destroyed.
The text was updated successfully, but these errors were encountered: