starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Colum headlines in dashboard are not translated in foreign languages #9738

New Issue
Closed
opened 2025-12-29 21:21:52 +01:00 by adam · 7 comments
adam commented 2025-12-29 21:21:52 +01:00
Owner
Copy Link

Originally created by @chbally on GitHub (May 24, 2024).

Deployment Type

Self-hosted

NetBox Version

v4.0.3

Python Version

3.10

Steps to Reproduce

  1. Make a screenshot of the English Dashboard.
  2. Goto User Preferences and Change Language to what ever
  3. Go back to the Dashboard: The Headlines will not have been translated

Expected Behavior

Headlines shown as translated.

Observed Behavior

Only native english language is shown
The content is shown in the right translation

Originally created by @chbally on GitHub (May 24, 2024). ### Deployment Type Self-hosted ### NetBox Version v4.0.3 ### Python Version 3.10 ### Steps to Reproduce 1. Make a screenshot of the English Dashboard. 2. Goto User Preferences and Change Language to what ever 3. Go back to the Dashboard: The Headlines will not have been translated ### Expected Behavior Headlines shown as translated. ### Observed Behavior Only native english language is shown The content is shown in the right translation
adam added the type: bugstatus: needs ownerpending closureseverity: low labels 2025-12-29 21:21:52 +01:00
adam closed this issue 2025-12-29 21:21:53 +01:00
adam commented 2025-12-29 21:21:53 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (May 24, 2024):

DEFAULT_DASHBOARD strings aren't internationalized.

@arthanson commented on GitHub (May 24, 2024): DEFAULT_DASHBOARD strings aren't internationalized.
adam commented 2025-12-29 21:21:54 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 28, 2024):

The widget titles aren't translated because they're meant to be user-generated; the default configuration is just a placeholder. We could add translation support, but understand that it's going to be of very limited utility, because translation is accomplished via static string mappings. For example, if a user creates a widget with the title "My custom widget," NetBox won't know how to translate it.

@jeremystretch commented on GitHub (May 28, 2024): The widget titles aren't translated because they're meant to be user-generated; the default configuration is just a placeholder. We could add translation support, but understand that it's going to be of very limited utility, because translation is accomplished via static string mappings. For example, if a user creates a widget with the title "My custom widget," NetBox won't know how to translate it.
adam commented 2025-12-29 21:21:54 +01:00
Author
Owner
Copy Link

@chbally commented on GitHub (May 28, 2024):

I don't agree with you @jeremystretch .
For Organiszation, Tenants and so on, they are normaly following the translation and I would expect that for the dashboard as well.
Only for custom widgets you are right. But if I create a custom widget as native german speaker, i wouldn't name it "Custom Widget" but "Benutzerdefiniertes Widget" and only because there is no german word for widget.

We do the translationen stuff to raise the acceptance of Netbox in the use of foreign languages - most of us work with english speaking systems every day.
In 25 years of implemanting software in companys, I've seen quite some software projects fail, because the users didn't recognize their regular wording in the first occasion the see the software.
From the same perspective I would also recommend, to have some system defined translation for major objects - such as site, location, system and tenant.
In the german translation we haven't found an agreement for the translation of "Location" yet, because almost everybody has a different translation and usage to it.
For tenant we agreed on "Mandant" but even "Kunde" (client), "Abteilung" (department) could be a personal choice vor companys installation.

@chbally commented on GitHub (May 28, 2024): I don't agree with you @jeremystretch . For Organiszation, Tenants and so on, they are normaly following the translation and I would expect that for the dashboard as well. Only for custom widgets you are right. But if I create a custom widget as native german speaker, i wouldn't name it "Custom Widget" but "Benutzerdefiniertes Widget" and only because there is no german word for widget. We do the translationen stuff to raise the acceptance of Netbox in the use of foreign languages - most of us work with english speaking systems every day. In 25 years of implemanting software in companys, I've seen quite some software projects fail, because the users didn't recognize their regular wording in the first occasion the see the software. From the same perspective I would also recommend, to have some system defined translation for major objects - such as site, location, system and tenant. In the german translation we haven't found an agreement for the translation of "Location" yet, because almost everybody has a different translation and usage to it. For tenant we agreed on "Mandant" but even "Kunde" (client), "Abteilung" (department) could be a personal choice vor companys installation.
adam commented 2025-12-29 21:21:54 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 28, 2024):

Yes, that's what I mean by "very limited utility:" Only the words NetBox knows can be translated.

@jeremystretch commented on GitHub (May 28, 2024): Yes, that's what I mean by "very limited utility:" Only the words NetBox knows can be translated.
adam commented 2025-12-29 21:21:54 +01:00
Author
Owner
Copy Link

@chbally commented on GitHub (May 28, 2024):

Sorry, we don’t get together here yet.
A newly crated user, will find on the dashboard in a totally translated software not translated items such as organization, tenant, site location and so on, when he firstly opens the software.
For the users point of view, that doesn’t make sense.
If you sit yourself on the chair of this user without knowing any code, you know, I’m right.
And to use your own argument: Netbox can translate oranization, tenant, site and location and so on.

@chbally commented on GitHub (May 28, 2024): Sorry, we don’t get together here yet. A newly crated user, will find on the dashboard in a totally translated software not translated items such as organization, tenant, site location and so on, when he firstly opens the software. For the users point of view, that doesn’t make sense. If you sit yourself on the chair of this user without knowing any code, you know, I’m right. And to use your own argument: Netbox can translate oranization, tenant, site and location and so on.
adam commented 2025-12-29 21:21:55 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 27, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 27, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 21:21:55 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 27, 2024):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Sep 27, 2024): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pending closure severity: low status: needs owner type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9738
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?