You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Person A creates an issue in their native language (Japanese).
Depending where the layer is located (app or server), the translator could translate the text and title to English.
The issue in English would be stored in GitHub's databases,
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.
The text was updated successfully, but these errors were encountered:
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: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.
The text was updated successfully, but these errors were encountered: