search

godotengine / godot-proposals

Godot Improvement Proposals (GIPs)
MIT License
1.16k stars 97 forks source link

Add label for localizations on Godot GitHub repositories #10993

Open Vovkiv opened 1 month ago

Vovkiv commented 1 month ago

Describe the project you are working on

(I don't know if this are good place for this, but, well... I also tried to look if there are already exists proposals for this, and it doesn't seems to be a case). I (and there probably more) often visit Godot proposals and main repos, browsing for issue/proposals/pulls about something that interest me the most. In my case, I often interested in changes around localization parts of engine, gettext, remapping, new localization functions, etc, but there is no label that focused around localization need, making it easier to miss some issue/pull/proposal.

Describe the problem or limitation you are having in your project

There is currently no easy way to track localization related issues pulls or or proposals. There many pulls/issues that address various localization needs in different parts of engine: csv files, gettext system, pot generation, gdscript code/functions, C#, performance issues with auto-localization, issues with translation remappers, pseudolocalization, etc, etc.

Just looking for "localization" not enough, depending on how issue/proposal/pr were filled, same for looking for gettext related tasks (for example, some people might know gettext as "POT/PO" system).

Describe the feature / enhancement and how it helps to overcome the problem or limitation

Having Github label for localization needs should make tracking proposals or issues or pulls about localization much easier.

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

You will be able to click "Labels" in proposals or main Godot repositories and pick "Localization". (Label could me named similarly to already existing labels: "core:localization")

If this enhancement will not be used often, can it be worked around with a few lines of script?

Go to https://github.com/godotengine/godot-proposals or https://github.com/godotengine/godot and use search function and other labels to try and locate localization related issues/pulls/proposals.

Is there a reason why this should be core and not an add-on in the asset library?

It should be core since this is about Github repositories of Godot.

Calinou commented 1 month ago

Note that localization (l10n) refers to the actual translation process done by translators, while making software localizable is a process referred to as internationalization (shortened "i18n" because of the 18 omitted letters in that form).

Calling the label internationalization or i18n would make more sense to me.

tetrapod00 commented 1 month ago

If you're going to use the short forms anyway, topic:i18n/l10n or topic:i18n-l10n fits well in a topic label.

There aren't a necessarily a large number of open issues (only searching for the two terms and omitting "translation" due to false positives): https://github.com/godotengine/godot-proposals/issues?q=is%3Aissue+is%3Aopen+localization+OR+internationalization+

tetrapod00 commented 1 day ago

Update: I would also like this, for labeling issues in the docs repo. Can we come to some agreement on the name, between candidates: topic:localization topic:internationalization topic:i18n topic:l10n topic:i18n-l10n <- my favorite