RC file with characters outside ANSI code page is saved without warning, corrupting characters - by Mihai Nita

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<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 276954 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 5/12/2007 9:42:37 PM
Access Restriction Public


Resource Editor accepts text outside the ANSI code page, saves the RC without warning or error message, but the text is replaced by question marks.

This is a VS 2005 bug, still present in Orcas beta.
See also http://www.mihai-nita.net/article.php?artID=20051030a
Sign in to post a comment.
Posted by Microsoft on 5/25/2009 at 1:11 PM
The Visual C++ team has triaged the issue you reported. The issue has been resolved during triage with the following message:

The next release of Visual Studio produces resource files encoded in UTF-16LE which solve encoding problems. If you still use ANSI encoding and you want to use characters from outside ANSI code page you should convert resource file encoding to UTF-16LE. Thank you for your feedback.

For further information, you may want to consult one of these resources:
1. Visual C++ triage guidelines:
2. MSDN forums:

Thank you for taking time to send us feedback,
The Visual C++ Team
Posted by Mihai Nita on 5/14/2007 at 10:51 PM
The important part is "Save, build, and *run*"

The text shows in the resource editor, but is not present in the .rc file (and at runtime).

The corect Unicode characters are in the .aps file.
Posted by Microsoft on 5/13/2007 at 8:25 PM
Thanks for your feedback. We were unable to repro the bug with the steps provided using Win2003 SP2 and OrcasBeta1VSTS. At the dialog section of the .rc file, we replaced the text in the default label with the text ‘ 日本’. (LTEXT “日本”, IDC_STATIC,42,26,114,8) It was shown in the dialog correctly. If you still see this issue occurring we would like to investigate this issue again. Please provide a ZIP of an example project and more detailed steps, and we will re-investigate. Thank you, Visual Studio Product Team.
Posted by Microsoft on 5/13/2007 at 4:21 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.