-
-
Notifications
You must be signed in to change notification settings - Fork 5.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
Add german translation guidelines #14283
Add german translation guidelines #14283
Conversation
|
||
Genauer definiert: | ||
* "falsch" anstatt "nicht korrekt/inkorrekt" | ||
* Benutzerkonto oder Konto? Oder Account? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dazu gab es irgendwann vor viel zu langer Zeit eine Diskussion im Discord, ich glaube das hatten wir nie so richtig geklärt? Auch wenn ich das jetzt nur ungern wieder aufkochen will, sollten wir das vielleicht mal so langsam entscheiden.
Ein bisschen Diskussion gab es auch schon in crowdin: https://crowdin.com/project/gitea/discussions/4 |
I think this is probably good information to have, I'm just not sure it makes sense to put in the developer section of the English documentation. What about a link to the gist in the localization page, or maybe a German page and then linking that in the localization page? |
@jolheiser I think a dedicated page in this repo would be better suited than the gist since everyone could do a PR to update it but that's not possible with a gist. I didn't see the localization page, only looked for a page named "Translation" which ofc does not exist 🙂 I still think it should be visible in the menu somehow since that would make it far more discoverable when just skimming manually through the docs. What do you think about creating a new section "Localization" and moving the existing localization page and this new page to it? |
why not add a translation page into docs witch each lang can have it's own "translation" with additional stuff ... ?Warum nicht eig. eine eigene Seite/Topic "Translation"/"Übersetzen" in die docs einfügen. Dort könnte man spezifisch für jede sprache was machen - so wie die info dieses pulls ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Blocking per @6543 as I agree we should have a separate section in docs for translations as we can then add more pages for other languages
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hopefully it'll get merged someday
|
||
## Trennungen | ||
|
||
* Pull-Request |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ich weiß nicht, aber meiner Meinung nach gehört da kein "-" zwischen Pull-Request (Pull Request).
Bei Time-Tracker und E-Mail-Adresse stimme ich hingegen zu.
@kolaente hab die Vorschläge angewandt ... |
solved |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ping @6543
Co-authored-by: kolaente <k@knt.li>
Co-authored-by: kolaente <k@knt.li>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* master: (358 commits) [skip ci] Updated translations via Crowdin Use caddy's certmagic library for extensible/robust ACME handling (go-gitea#14177) Redirect on changed user and org name (go-gitea#11649) chore: bump minio to RELEASE.2021-01-16T02-19-44Z (go-gitea#14445) [skip ci] Updated translations via Crowdin CI: skip build steps for cron update works (go-gitea#14443) [skip ci] Updated licenses and gitignores [skip ci] Updated translations via Crowdin just overload to not get it by mistake again ... (go-gitea#14440) [skip ci] Updated translations via Crowdin Add link to packages in openSUSE build service (go-gitea#14439) Improve Description in new/ edit Project template (go-gitea#14429) Don't show "Reference in new issue" when issues unit is globally disabled (go-gitea#14437) CI: Update license & gitignore by cron (go-gitea#14419) Fix close/reopen with comment (go-gitea#14436) Add german translation guidelines (go-gitea#14283) [skip ci] Updated translations via Crowdin Fix lfs preview bug (go-gitea#14428) [skip ci] Updated translations via Crowdin Bump gsap from 3.5.1 to 3.6.0 (go-gitea#14410) ...
* master: (542 commits) [skip ci] Updated translations via Crowdin Use caddy's certmagic library for extensible/robust ACME handling (go-gitea#14177) Redirect on changed user and org name (go-gitea#11649) chore: bump minio to RELEASE.2021-01-16T02-19-44Z (go-gitea#14445) [skip ci] Updated translations via Crowdin CI: skip build steps for cron update works (go-gitea#14443) [skip ci] Updated licenses and gitignores [skip ci] Updated translations via Crowdin just overload to not get it by mistake again ... (go-gitea#14440) [skip ci] Updated translations via Crowdin Add link to packages in openSUSE build service (go-gitea#14439) Improve Description in new/ edit Project template (go-gitea#14429) Don't show "Reference in new issue" when issues unit is globally disabled (go-gitea#14437) CI: Update license & gitignore by cron (go-gitea#14419) Fix close/reopen with comment (go-gitea#14436) Add german translation guidelines (go-gitea#14283) [skip ci] Updated translations via Crowdin Fix lfs preview bug (go-gitea#14428) [skip ci] Updated translations via Crowdin Bump gsap from 3.5.1 to 3.6.0 (go-gitea#14410) ...
Because I kept seeing the same common questions over and over again (as a proofreader for the german translation) I figured I might as well document the answer properly to have something to point people to. For way too long, this has been a gist which is not really ideal because not everyone has access to it. Also this is mostly what I think it should be, most of it is distilled from discussions and my own work of translating gitea.
I didn't really know where to put it so I just put it under "development" - maybe it would make sense to add a "translation" section? I think this could be useful for other languages as well. And we don't have any documentation about the translation at all at the moment.
Pinging @jonasfranz @6543 @silverwind for review
Das hier sind im wesentlichen nur Notizen von mir in einen docs-Artikel kopiert, guckt daher bitte nochmal drüber um das in eine vernünftige Form zu bringen. Ein paar Dinge davon sollten wir vielleicht vorher noch Diskutieren (und deshalb ist dieser Satz hier auch auf deutsch).