Skip to content
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

Add label for localizations for Godot Github repositories #10993

Open
Vovkiv opened this issue Oct 18, 2024 · 2 comments
Open

Add label for localizations for Godot Github repositories #10993

Vovkiv opened this issue Oct 18, 2024 · 2 comments
Labels

Comments

@Vovkiv
Copy link

Vovkiv commented Oct 18, 2024

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
Copy link
Member

Calinou commented Oct 18, 2024

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
Copy link

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+

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants