-
Notifications
You must be signed in to change notification settings - Fork 10.5k
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
[NEW] Informal German translations #9984
Conversation
Please add a second language option for that. |
@marceloschmidt we discussed this quite some time ago. Just seen the PR is still open. |
When I think about formal vs informal in Portuguese, formal Portuguese sounds very inadequate for a software, while informal Portuguese may sound as poorly built, so we use a mix between the two, whatever "sounds" best. I say use your best judgement. Does formal sound too weird in that context? If so, try less formal... in Portuguese, we use a lot of English words, because translating them would be very weird, such as "Online" and "Logout" for example. |
@marceloschmidt in German, the differentiation is not as huge. It's mainly a formal article for "you". |
@mrsimpson It’s may a pain in the arse to have two german translations, but we use RC in an enterprise environment and we definitely don’t want to use informal german on our installation :) And it’s not just about the “You”. Sometimes the hole structure of a sentence can change when you use formal/informal german. |
bf55e67
to
23b4c41
Compare
@kaiiiiiiiii Finally, I managed to provide a second language option for informal german in Rocket.Chat (with TAPi18n as translation framework) 🎉
However, at least on my local build, the language variant is not accepted in TAPi18n! I could use some help from the TAPi18n-warriors around here (looking at you, @sampaiodiego ;) ) |
that's cool. we have to check if lingohub also supports language variations like this. |
Yup, also thought about Lingohub. But even if it didn’t: there are other (direct) ways of contributing to the informal translations. Sent with GitHawk |
The IETF language specification compliant suffix "informal" did not work with the i18n library used
@sampaiodiego I fought some more fights with TAPi18n - and kind of lost: I could not get it accept the IETF compliant language name |
all my fights against TAPi18n ended as lost 😢 I'll give it a try and merge it 😉 |
* Provide a dedicated informal german language option * Use a "virtual" language code de-IN for informal german The IETF language specification compliant suffix "informal" did not work with the i18n library used
Liebe Deutsche 🇩🇪 Anwender, wir kennen euch nun besser. Ab sofort wollen wir "Du" zu einander sagen