Epic: Support non-en-US locales #2006

Closed
opened 2026-01-30 22:44:08 +00:00 by claunia · 3 comments
Owner

Originally created by @Dabraleli on GitHub (Jun 23, 2019).

Summary of the new feature/enhancement

I think that any software needs translation on other languages, especially Console which is used very often even by people that are not using it for administrative and programming purposes.
I should admit that English is very common and widely used language, but in not English speaking countries it's sometimes hard to understand what some buttons do.

Proposed technical implementation details (optional)

I spent some time to look at code and app's resources and I think we can make same files like en-US/Resources.resw for other languages and store all strings there.
I think it's better to implement two ways to select language:

  1. Configuration file parameter "preferredLanguage"
  2. Using system locale/language

As for me I can prepare Russian translation for buttons, labels, hints, etc.
Also I can try to implement feature like this.

Originally created by @Dabraleli on GitHub (Jun 23, 2019). # Summary of the new feature/enhancement I think that any software needs translation on other languages, especially Console which is used very often even by people that are not using it for administrative and programming purposes. I should admit that English is very common and widely used language, but in not English speaking countries it's sometimes hard to understand what some buttons do. # Proposed technical implementation details (optional) I spent some time to look at code and app's resources and I think we can make same files like en-US/Resources.resw for other languages and store all strings there. I think it's better to implement two ways to select language: 1. Configuration file parameter "preferredLanguage" 2. Using system locale/language As for me I can prepare Russian translation for buttons, labels, hints, etc. Also I can try to implement feature like this.
claunia added the Issue-FeatureNeeds-Tag-FixProduct-TerminalArea-Build labels 2026-01-30 22:44:08 +00:00
Author
Owner

@Dabraleli commented on GitHub (Jun 28, 2019):

@DHowett-MSFT, should I try to implement this feature or is it Spec-Needed?

@Dabraleli commented on GitHub (Jun 28, 2019): @DHowett-MSFT, should I try to implement this feature or is it Spec-Needed?
Author
Owner

@DHowett-MSFT commented on GitHub (Jun 28, 2019):

@Dabraleli My main concern is that we're not properly set up for resource loading because our project is a frankenstein's monster of win32 and UWP and everything else all together. It's not going to be easy, but it doesn't need a spec. If you want to dig into getting the infrastructure in place, knock yourself out. I don't know what it looks like to actually translate the project this early in its lifecycle. It may be too early.

@DHowett-MSFT commented on GitHub (Jun 28, 2019): @Dabraleli My main concern is that we're not properly set up for resource loading because our project is a frankenstein's monster of win32 and UWP and everything else all together. It's not going to be _easy_, but it doesn't need a spec. If you want to dig into _getting the infrastructure in place_, knock yourself out. I don't know what it looks like to _actually translate_ the project this early in its lifecycle. It may be too early.
Author
Owner

@zadjii-msft commented on GitHub (Dec 9, 2021):

Uh, pretty sure we've actually been doing this for a LONG time now. Gonna close this one out, thanks!

@zadjii-msft commented on GitHub (Dec 9, 2021): Uh, pretty sure we've actually been doing this for a LONG time now. Gonna close this one out, thanks!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#2006