-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
Update translation priorities in Localization contributing page #10319
Conversation
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.
not sure if the word count is needed anyway
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.
I'm not sure whether the word count is useful or should be dropped. If it is, maybe we should add one of those UPDATE
comments here so try to remember?
Maybe it's best to drop it, yeah. If people want to see the count is right there on Weblate. The actual numbers are only going to grow and cannot be maintained accurate every time. |
It seems reasonable to drop the word count entirely. I do think there is some value in knowing the scale of the text to translate, to at least an order of magnitude, as well as the relative sizes of the three subcategories. This PR is updated to remove the counts entirely, which we seem to have reasonable consensus on. As an alternative, we could list the total word count which right now is ~1,000,000, but not the subcounts. |
53d500f
to
55b0851
Compare
This seems fine to me :) Thank you, merged. |
Updated the word counts to roughly match the current "All strings" count on Weblate.
Also changed the recommended priority of translations to editor interface, then class reference, then manual. As I don't have first-hand experience with translation, I'm not 100% sure about that order. I asked in the translation RC and got a couple agreements, but I'm not sure how unanimous that is. It does match the concept of treating the class reference as more of a source of truth, since it's in the main repo and included in the engine itself.