Add chinese translation #3950

Closed
opened 2025-12-29 18:32:14 +01:00 by adam · 4 comments
Owner

Originally created by @BaiYongJun on GitHub (Aug 6, 2020).

Environment

Python version: 3.7.7
NetBox version: 2.8.8

Proposed Functionality

Add chinese translation

Use Case

Netbox has a lot of Chinese users, so I think Chinese translation is necessary

Database Changes

None

External Dependencies

None

Originally created by @BaiYongJun on GitHub (Aug 6, 2020). ## Environment Python version: 3.7.7 NetBox version: 2.8.8 ## Proposed Functionality Add chinese translation ## Use Case Netbox has a lot of Chinese users, so I think Chinese translation is necessary ## Database Changes None ## External Dependencies None
adam closed this issue 2025-12-29 18:32:14 +01:00
Author
Owner

@Dzordzu commented on GitHub (Aug 6, 2020):

I don't support idea of @BaiYongJun
The official language of the current web, networking and IT overall is english. It's the most known language for people that are using tools such as Netbox.

Additionaly there are some other issues with multilingual approach:

  • translations have to be maintained
  • plugins would have to support other languages
  • another useless button
  • it encourages people to use non english descriptions, names, symbols etc. - for me it's the biggest no no
@Dzordzu commented on GitHub (Aug 6, 2020): I don't support idea of @BaiYongJun The official language of the current web, networking and IT overall is english. It's the most known language for people that are using tools such as Netbox. Additionaly there are some other issues with multilingual approach: * translations have to be maintained * plugins would have to support other languages * another useless button * it encourages people to use non english descriptions, names, symbols etc. - for me it's the biggest no no
Author
Owner

@tyler-8 commented on GitHub (Aug 6, 2020):

translations have to be maintained

Not only that, the Django-native translation framework would have to be integrated throughout the project first, which in and of itself is a massive undertaking since it's not present today in NetBox - that's not even including the actual translation aspect.

Integrating the translation framework would be a separate FR and have to be completed before any language-specific support can be viable.

Adding: I'm all for translation support, Django has pretty excellent built-ins for it, but it will require a good set of defined processes and language maintainers to keep translations up to date.

@tyler-8 commented on GitHub (Aug 6, 2020): > translations have to be maintained Not only that, the Django-native translation framework would have to be integrated throughout the project first, which in and of itself is a massive undertaking since it's not present today in NetBox - that's not even including the actual translation aspect. Integrating the translation framework would be a separate FR and have to be completed before any language-specific support can be viable. Adding: I'm all for translation support, Django has pretty excellent built-ins for it, but it will require a good set of defined processes and language maintainers to keep translations up to date.
Author
Owner

@jeffrey4l commented on GitHub (Aug 7, 2020):

I support this feature. There are lots of multi language support request long time ago, check #1068 #1795 #1854 . But we have no any approach for a long time.

I am agree with @tyler-8 , django i18n framework is great and easy to be set up. We can use it to make multi language suuport easier.

@jeffrey4l commented on GitHub (Aug 7, 2020): I support this feature. There are lots of multi language support request long time ago, check #1068 #1795 #1854 . But we have no any approach for a long time. I am agree with @tyler-8 , django i18n framework is great and easy to be set up. We can use it to make multi language suuport easier.
Author
Owner

@lampwins commented on GitHub (Aug 10, 2020):

As @tyler-8 points out, localization is a MASSIVE undertaking and requires broad-reaching, fundamental changes, and infrastructure to implement. The largest barrier for NetBox is always going to be long term ownership of the translations. Consider that anytime we implement something new, the relevant translations will have to be written which just adds to the maintenance burden.

Because there is a massive undertaking necessary before we can even attempt to take on any language-specific translations, I have to reject this request.

@lampwins commented on GitHub (Aug 10, 2020): As @tyler-8 points out, localization is a MASSIVE undertaking and requires broad-reaching, fundamental changes, and infrastructure to implement. The largest barrier for NetBox is always going to be long term ownership of the translations. Consider that anytime we implement something new, the relevant translations will have to be written which just adds to the maintenance burden. Because there is a massive undertaking necessary before we can even attempt to take on any language-specific translations, I have to reject this request.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3950