[Idea] Better terminology for certain words (Better translations) #10381

New Issue

GiteaMirror · 2025-11-02T09:05:48-06:00

GiteaMirror commented

2025-11-02 09:05:48 -06:00

Originally created by @Andre601 on GitHub (Mar 3, 2023).

Feature Description

This has originally been suggested on forgejo/forgejo @Codeberg but I was told it would be a good idea to propose this to the upstream repository forgejo is based of, so here we go.

I love the fact that Gitea allows translations for the UI, as it makes understanding certain things a lot easier.
However, certain words cannot be translated that easily, either because there isn't a translation available, or the translation wouldn't be as suitable.

Take for example "Issues". In german, my native language, would it translate to "Probleme", which has more of a negative tone to it, which is why the word is used untranslated in german. And while issues are mainly for... well... issues, have issue tracker gone way beyond their initial purpose and are now also used for feature requests (Such as this one), but also questions or even general feedback.

The term "issues" is therefore not really that up-to-date anymore and a suitable replacement should be considered.
My personal suggestion would be "Tickets" as a ticket is more neutral than an issue.
Also, given my usage of Forgejo, which to my knowledge is mostly the same as gitea in terms of design, does the Activity history you can see already use "Ticket" as a word in translations, to refer to issues, which means that a change could make it more consistent.

Of course, there are a few other terms that aren't translated and used as-is for various reasons, so it should be considered to look into this and see what words and/or phrases can be improved to make translations that little bit better for everyone.

Screenshots

No response

Originally created by @Andre601 on GitHub (Mar 3, 2023). ### Feature Description This has originally been suggested on [forgejo/forgejo @Codeberg](https://codeberg.org/forgejo/forgejo/issues/330) but I was told it would be a good idea to propose this to the upstream repository forgejo is based of, so here we go. I love the fact that Gitea allows translations for the UI, as it makes understanding certain things a lot easier. However, certain words cannot be translated that easily, either because there isn't a translation available, or the translation wouldn't be as suitable. Take for example "Issues". In german, my native language, would it translate to "Probleme", which has more of a negative tone to it, which is why the word is used untranslated in german. And while issues are mainly for... well... issues, have issue tracker gone way beyond their initial purpose and are now also used for feature requests (Such as this one), but also questions or even general feedback. The term "issues" is therefore not really that up-to-date anymore and a suitable replacement should be considered. My personal suggestion would be "Tickets" as a ticket is more neutral than an issue. Also, given my usage of Forgejo, which to my knowledge is mostly the same as gitea in terms of design, does the Activity history you can see already use "Ticket" as a word in translations, to refer to issues, which means that a change could make it more consistent. Of course, there are a few other terms that aren't translated and used as-is for various reasons, so it should be considered to look into this and see what words and/or phrases can be improved to make translations that little bit better for everyone. ### Screenshots _No response_

GiteaMirror added the type/proposal modifies/translation labels 2025-11-02 09:05:48 -06:00

GiteaMirror commented

2025-11-02 09:05:48 -06:00

@jolheiser commented on GitHub (Mar 3, 2023):

Our translations are currently done via crowdin, if you have specific ideas we could probably add them there and have them reviewed.

Changing them in code or across languages might be a bit larger of an undertaking, however.

@jolheiser commented on GitHub (Mar 3, 2023): Our translations are currently done via [crowdin](https://crowdin.com/project/gitea), if you have specific ideas we could probably add them there and have them reviewed. Changing them in code or across languages might be a bit larger of an undertaking, however.

GiteaMirror commented

2025-11-02 09:05:48 -06:00

@jolheiser commented on GitHub (Mar 3, 2023):

Interestingly, crowdin seems to suggest Probleme for a no-context Issues, however for something like Create Issue it suggests Ticket erstellen.

(I know precisely zero German, I just found it interesting given your feedback above Probleme vs Tickets)

@jolheiser commented on GitHub (Mar 3, 2023): Interestingly, crowdin seems to suggest `Probleme` for a no-context `Issues`, however for something like `Create Issue` it suggests `Ticket erstellen`. (I know precisely zero German, I just found it interesting given your feedback above `Probleme` vs `Tickets`)

GiteaMirror commented

2025-11-02 09:05:49 -06:00

@Andre601 commented on GitHub (Mar 3, 2023):

Interestingly, crowdin seems to suggest Probleme for a no-context Issues, however for something like Create Issue it suggests Ticket erstellen.

(I know precisely zero German, I just found it interesting given your feedback above Probleme vs Tickets)

Yep. I found it interesting to see that "Issues" was used for the tab, while the overview (Page showing past activities) is using "Ticket".
It confused me and made me consider this proposal to have the word changed to Ticket in general (And by that I don't just mean translations, but source itself. That kinda was missed out in my OP) for the previously mentioned points of issues no longer being "just for issues".

Also, other software for bug-report and feature request management - like Jira - also use Tickets as their main words (Tho, Idk if that is also the case in original and not just translations), which for me makes sense.

@Andre601 commented on GitHub (Mar 3, 2023): > Interestingly, crowdin seems to suggest `Probleme` for a no-context `Issues`, however for something like `Create Issue` it suggests `Ticket erstellen`. > > (I know precisely zero German, I just found it interesting given your feedback above `Probleme` vs `Tickets`) Yep. I found it interesting to see that "Issues" was used for the tab, while the overview (Page showing past activities) is using "Ticket". It confused me and made me consider this proposal to have the word changed to Ticket in general (And by that I don't just mean translations, but source itself. That kinda was missed out in my OP) for the previously mentioned points of issues no longer being "just for issues". Also, other software for bug-report and feature request management - like Jira - also use Tickets as their main words (Tho, Idk if that is also the case in original and not just translations), which for me makes sense.

GiteaMirror commented

2025-11-02 09:05:49 -06:00

@lunny commented on GitHub (Mar 4, 2023):

We also have a German channel in discord, maybe you can find more German native speaker to discuss how to translate it well.

@lunny commented on GitHub (Mar 4, 2023): We also have a German channel in discord, maybe you can find more German native speaker to discuss how to translate it well.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#10381