The Resource Edior in MFC applications corrupts non-ANSI text in Combo-Box - by Mihai Nita

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 276957 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 5/12/2007 9:51:15 PM
Access Restriction Public


The Resource Editor used edit MFC dialog allows to add data in Combo Box.
Data outside the ANSI code page is accepted, but is currupted when saved.
Sign in to post a comment.
Posted by Mihai Nita on 5/16/2007 at 11:08 PM
Changing the OS Regional and Language Options:
- defeats the purpose or having Unicode RC files
- does not solve the multiple languages problem (setting the system code page to Japanese will still corrupt Russian and Romanian)
- will not be possible for Unicode only language (all Indic languages, others)

Posted by Microsoft on 5/16/2007 at 11:07 AM
Thank you for sending us feedback. The Visual C++ team has evaluated the bug and determined it does not meet the guidelines necessary to warrant a fix. To understand these guidelines please refer to

Unfortunately, the Visual C++ development team cannot provide workarounds for issues submitted via the Microsoft Connect interface. The MSDN forums are better suited for finding the correct answer. Visit the MSDN forums at

Comments from the triage team: Either editing the resource file directly with the correct hexadecimal numbers, or changing the OS Regional and Language Options to Japanes will workaround this issue. Given the workarounds, this bug does not meet the Orcas triage guidelines.

Thanks once again for taking the time to send us feedback,
The Visual C++ Triage Team
Posted by Microsoft on 5/13/2007 at 8:09 PM
Thanks for your feedback. We have reproduced this bug on Win2003 SP2 and OrcasBeta1VSTS, and we are sending this bug to the appropriate group within the Visual Studio Product Team for triage and resolution. Thank you, Visual Studio Product Team.
Posted by Microsoft on 5/13/2007 at 4:35 PM
Thank you for your feedback. We are currently investigating. If this issue is urgent, please call support directly (see Thank you, Visual Studio Product Team.