This repository was archived by the owner on Jul 16, 2022. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 180
Localization Support #197
Copy link
Copy link
Open
Labels
priority: NoneIssues that do not require any priority to be handledIssues that do not require any priority to be handleds: Awaiting FeedbackIssues which are awaiting additional feedback from maintainers or the community.Issues which are awaiting additional feedback from maintainers or the community.target: CommandsIssues that target Command filesIssues that target Command filestype: DiscussionIssues that discuss a topic about GAB's SourceIssues that discuss a topic about GAB's Sourcetype: EnhancementIssues that enhance an existing feature or moduleIssues that enhance an existing feature or module
Metadata
Metadata
Assignees
Labels
priority: NoneIssues that do not require any priority to be handledIssues that do not require any priority to be handleds: Awaiting FeedbackIssues which are awaiting additional feedback from maintainers or the community.Issues which are awaiting additional feedback from maintainers or the community.target: CommandsIssues that target Command filesIssues that target Command filestype: DiscussionIssues that discuss a topic about GAB's SourceIssues that discuss a topic about GAB's Sourcetype: EnhancementIssues that enhance an existing feature or moduleIssues that enhance an existing feature or module
This issue tracks the technical discussion about the proposal to integrate multiple languages into GAB's bot responses.
Currently, we're probably going to keep the web interface in English, but this could change during the course of planning this out. Of course, you'll be able to change your language settings from within the administration panel, probably on the same page as auto-translate (bonus points cuz it fits nicely under the "command-list" submenu).
When we confirm that we actually want to do this, and we have enough users who are willing to contribute translations, I'll create a PR that tracks the actual development of the integration and close this issue, this PR will then most likely merge into v4.2. Until then, happy discussing!
Here's Vlad's original announcement about it for more context if needed:
This will NOT affect extensions OR command usage! Keep that in mind! This will only affect the returning strings.