You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am a user from China, and I would like to use Mail-Archiver in my organization. However, the current version of Mail-Archiver does not support Chinese (both Simplified and Traditional), which creates significant barriers for adoption:
User experience: Team members who are not proficient in English find it difficult to navigate the interface and configure settings.
Deployment friction: Administrators need to constantly translate interface terms when explaining the system to end-users.
Wider adoption: The lack of Chinese localization limits the potential user base in Chinese-speaking regions, which represent a substantial market.
Describe the solution you'd like
I would like to propose adding Simplified Chinese (zh-CN) and Traditional Chinese (zh-TW) language support to Mail-Archiver.
The project already has a well-established localization framework using ASP.NET Core's built-in resource files (SharedResource.resx). Adding Chinese support would follow the same pattern as other existing languages (German, French, Spanish, etc.):
Create SharedResource.zh-CN.resx for Simplified Chinese
Create SharedResource.zh-TW.resx for Traditional Chinese
Add both files to the Resources/ directory in the project
I have already reviewed the SharedResource.resx file and confirmed that the localization framework is fully in place. The only missing piece is the actual translation files for Chinese.
Additional context
Manual workaround: I could fork the project and maintain a private Chinese version, but this creates maintenance overhead and prevents the broader community from benefiting.
Browser translation plugins: While technically possible, this solution is unreliable (incorrect translations, formatting issues) and degrades the user experience.
Third-party translation services: Integrating an automated translation service would add complexity and dependency without guaranteeing quality.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem?
I am a user from China, and I would like to use Mail-Archiver in my organization. However, the current version of Mail-Archiver does not support Chinese (both Simplified and Traditional), which creates significant barriers for adoption:
User experience: Team members who are not proficient in English find it difficult to navigate the interface and configure settings.
Deployment friction: Administrators need to constantly translate interface terms when explaining the system to end-users.
Wider adoption: The lack of Chinese localization limits the potential user base in Chinese-speaking regions, which represent a substantial market.
Describe the solution you'd like
I would like to propose adding Simplified Chinese (zh-CN) and Traditional Chinese (zh-TW) language support to Mail-Archiver.
The project already has a well-established localization framework using ASP.NET Core's built-in resource files (SharedResource.resx). Adding Chinese support would follow the same pattern as other existing languages (German, French, Spanish, etc.):
Create SharedResource.zh-CN.resx for Simplified Chinese
Create SharedResource.zh-TW.resx for Traditional Chinese
Add both files to the Resources/ directory in the project
I have already reviewed the SharedResource.resx file and confirmed that the localization framework is fully in place. The only missing piece is the actual translation files for Chinese.
Additional context
Manual workaround: I could fork the project and maintain a private Chinese version, but this creates maintenance overhead and prevents the broader community from benefiting.
Browser translation plugins: While technically possible, this solution is unreliable (incorrect translations, formatting issues) and degrades the user experience.
Third-party translation services: Integrating an automated translation service would add complexity and dependency without guaranteeing quality.
All reactions