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

[Suggestion; Discussion] Add Support for I18n #74

Open
ghost opened this issue Nov 10, 2022 · 0 comments
Open

[Suggestion; Discussion] Add Support for I18n #74

ghost opened this issue Nov 10, 2022 · 0 comments

Comments

@ghost
Copy link

ghost commented Nov 10, 2022

Overview

I like how GitSpeak is built to be a "better way to discuss code." Although I have not used the app before (I have a Windows machine), I think what would be a big help for international communities would be a an i18n layer. The i18n layer would allow developers to communicate without a language barrier, and would allow other developers to join the conversation more easily; both of those could be done without using English as the "official" language.

How the i18n layer works

Let's say that Person A is fluent in Japanese (ja-JP), Person B is fluent in Spanish (es-MX), and neither of them are fluent in another language, such as English. With the i18n layer, the process below could occur for writing an issue:

  1. Person A creates an issue in their native language (Japanese).
  2. Depending where the layer is located (app or server), the translator could translate the text and title to English.
  3. The issue in English would be stored in GitHub's databases,
  4. When Person B reads the issue on GitSpeak, Steps 1-3 would be reversed, and the target language would be Spanish.

The same process would occur for PRs Comments, notifications, etc.


I am open for feedback on this discussion, and on a personal note, I think other devs would wish this was baked into GitHub already.

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

No branches or pull requests

0 participants