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

Translate tags too #20

Closed
MrSebastian opened this issue Oct 13, 2023 · 4 comments
Closed

Translate tags too #20

MrSebastian opened this issue Oct 13, 2023 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@MrSebastian
Copy link
Member

The tags are currently only in one language:

grafik
Tags listed in the english version of the use page

I suggest to translate them too. We could use a lookup table for the tags for each language. If it has an entry the translated version is picked. When there is no entry for the selected language the native value is shown.


I am not sure if it is really necessary right now, because most of the tags should be readable (except eigentwickung oder schnittstelle).

@klml klml added the enhancement New feature or request label Oct 15, 2023
@klml
Copy link
Member

klml commented Oct 15, 2023

@MrSebastian you are right, this is el bit mixed. we should use one language for tags, imho english.

So I suggest to translate eigenentwicklung with "inhouse" and schnittstelle with "interface".

I suggest to translate them too. We could use a lookup table for the tags for each language. If it has an entry the translated version is picked. When there is no entry for the selected language the native value is shown.

Thats a good enhancement.

@MrSebastian
Copy link
Member Author

next step is to refactor all existing tags:

  • eigenentwicklung ->inhouse
  • infrastruktur -> infrastructure
  • kooperation -> cooperation
  • refarchinfrastruktur -> refarchinfrastructure
  • schnittstelle -> interface
  • webanwendung -> webapp

I guess I can do it til the end of the week.

@FabianWilms @klml are there any other issues and branches that may produce a conflict?

@FabianWilms
Copy link
Member

I think most of these are already fixed in #28

There are currently two branches that were not merged becaues of this feature in which it should be integrated afterwords:

@FabianWilms
Copy link
Member

It's done 👏

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

No branches or pull requests

3 participants