Visual Studio and .NET Framework Home
The Resource Edior in MFC applications corrupts non-ANSI text in Combo-Box
as Won't Fix
5/12/2007 9:51:15 PM
User(s) can reproduce this bug
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.
Visual Studio Code Name "Orcas" (Beta 1)
Windows XP Professional
Operating System Language
Steps to Reproduce
Create MFC Dialog Application (everything default)
In Solution Explorer find the .rc file, right-click and select View Code (answer "yes" when asked to close the already opened document).
Select "File" -> "Save <fileName>.rc As...".
Do not click the "Save" button, but click on the down-arrow and select "Save with encoding..."
Accept to override the original file and select "Unicode - Codepage 1200), and save.
Close the file, go back to "Resource View," and open the application's dialog.
Add a Combo Box, then right-click, select "Properties", and find the "Data" section.
Add some text outside the ANSI code page (ie Japanese on English US system, try "Test;Руский;日本;Română")
Save, build, and run
The Japanese and Russian text is replaced by question marks, the last Romanian character (U+0103) is replaced with lowercase a (U+0061)).
Open the .rc file in Notepad (or in VS IDE as code). The DLGINIT contains question marks:
IDC_COMBO1, 0x403, 5, 0 0x6554, 0x7473, "\000"
IDC_COMBO1, 0x403, 7, 0 0x3f3f, 0x3f3f, 0x3f3f, "\000"
IDC_COMBO1, 0x403, 3, 0 0x3f3f, "\000"
IDC_COMBO1, 0x403, 7, 0 0x6f52, 0xe26d, 0x616e, "\000"
The Unicode content should be preserved.
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
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)
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 http://blogs.msdn.com/vcblog/articles/621116.aspx.
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 http://forums.microsoft.com/msdn/default.aspx.
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
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.
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 http://support.microsoft.com). Thank you, Visual Studio Product Team.
to post a workaround.
Please enter a workaround.
© 2014 Microsoft