.net 2005 beta 2 corrupts MBCS strings in resource files

I'm having trouble with a multi-project solution with several Asian Language resources. I've ported this from VC6.

It appears that VC8 and the dev studio have fundamental problems with handling MBCS resource text. Here are the easy steps to duplicate this problem:

Create an MFC dialog based project in VC8. Use all the defaults

Add some new strings to the English String table

Create a copy of the English string table, select the Japanese language for the new resource.

edit the .rc file, and replace some of the strings in the Japanese resource section with MBCS Japanese text. I've been doing this step with MSVC6, since I know it works.

re-make the project. Verify ( again, likely using MSVC6 ) that no corruption has occured in the .rc file. This step isn't really needed.

Add a new english string, and save the .rc file

Observe that the Japanese text in the .rc file is now corrupted, and replaced with ? characters

This same thing happens if you chose MBCS instead of Unicode in the project settings.

Please tell me, how are people creating multi-language solutions using VC8?
The only work around I can see is to use .net 2003 for development, and only convert a copy to .net 2005 for the actual MAKE. This since I need x64 support.

Also, are there published guidelines for .rc organization with multiple languages?

TIA

[1361 byte] By [StandbySoft] at [2007-12-16]
# 1
Well, 2005 now supports Unicode RC files, you can save the RC file as a Unicode file by choose File Save As for the RC file (highlight RC file in solution explorer then choose File Save As) then click on the Save button's down arrow, and choose Save with encoding, and choose to save the RC file as a Unicode file.

But, more importantly, MBCS should still work fine, so you should definitely file a bug at
http://lab.msdn.microsoft.com/ProductFeedback

Ted.

Ted. at 2007-9-9 > top of Msdn Tech,Visual C++,Visual C++ General...
# 2
... and please post a link to your bug report back here so we can see what the response is.

Dave

DavidLowndes at 2007-9-9 > top of Msdn Tech,Visual C++,Visual C++ General...
# 3
This is clearly a bug to me. Please open a report as Ted and David suggested.

Thanks,
Nikola
VC++

NikolaDudar at 2007-9-9 > top of Msdn Tech,Visual C++,Visual C++ General...
# 4
Hi Ted,

Great answer. This works ( I'm using Unicode code page 1200 ), and I can also convert it back if I need to edit/use the file under VC6.

StandbySoft at 2007-9-9 > top of Msdn Tech,Visual C++,Visual C++ General...