[Loc] ‘developer’ was localized in C++ Walkthrough page
Bug Summary and Steps to Reproduce
Environment: VSCode 1.90.2+ C/C++ Extension 1.21.0 pre-release)
More info:
- Repro platform: Windows
- Different status in different languages:
• 1st part translated and kept ‘developer’ in 3rd part: CHS, JPN, KOR, ITA
• 3rd part translated and kept ‘developer’ in 1st part: ESN
• ‘developer’ all translated: CHT, FRA, PLK, PTB, DEU, TRK • 1st and 3rd part all keep ‘developer’: RUS, CSY
Steps to reproduce:
- Open VScode and change the display language to loc languages (such as: CHS)
- Open the command palette-> Type "Welcome: Open Walkthrough..." and hit enter
- Select the "Get Started with C++ Development"
- Check the string ‘developer’ status in 1st part (Set up your c++ Environment) and 3rd part (Launch from the developer command prompt)
Expected result:
‘developer’ needn’t localized to launch Developer Command Prompt for VS
(Such as: 3rd part on CHS version)
Actual result:
‘developer’ was translated on some part
(Such as: 1st part on CHS version)
Configuration and Logs
loc issue not related to log
Other Extensions
No response
Additional context
No response
Thank you for reporting this issue, this has been filed with our internal localization team (VS: 985101). Please track this issue for updates.
@bobbrow @PhoebeTf This issue has not yet been fully resolved in the latest C++ version v1.23.0(pre-release), it has been fixed for ITA, DEU, RUS, CSY but not yet for the other languages, you can get detailed screenshots from below. I will reopen this issue. Thank you!
Different status in different languages: • 1st part translated and kept ‘developer’ in 3rd part: CHS, JPN, KOR • 3rd part translated and kept ‘developer’ in 1st part: ESN • ‘developer’ all translated: CHT, FRA, PLK, PTB, TRK • 1st and 3rd part all keep ‘developer’: RUS, DEU, ITA,CSY
CHS: Should be “developer” in quotes not translated
I spoke with the team that owns the "developer command prompt for VS" shortcuts and it looks like those won't ever be translated. It looks like they will be treated as product names going forward. I'll open a new bug to get all of these strings reverted to the product name (undoing the translations around them)