2005 Resource Editor trashes non-English languages when you edit any dialog

2005 Resource Editor trashes non-English languages when you edit any dialog

• LateNightDBA

  Not that I'm aware of but right now it's highly important that this issue is put up at the product feedback center (and possibly request a fix as a QFE through product support - should be free incident because it's a bug).  

  From past experience having a fix made into a QFE makes it much more likely for it to make a service pack.  There are literally thousands of issues up on the product feedback center competing for attention, so only a small fraction of these issues will make SP1.  It's much less likely for it to make even Orcas unless there is sufficient pressure put on the team.   There were bugs in the resource editor that lasted for 4 years, working fine in 6.0, introduced in 2002 and not fixed until recently). 

  So getting these types of problems marked as high priority is something that I would try to do, and soon, because from my experience, the cutoff for a service pack is months before it's actually released. 

  P.S. For switching languages easily to change resources, just use the Applocale utility (available for download from Microsoft) it will save you from having to change the "language for non-Unicode programs" and rebooting.

   

  
  

• SpinWebs

  Microsoft has issued a KB article on this issue, and I just tested the hotfix and it works fine. Chinese, Hungarian and Polish no longer get garbled when you edit resources.
  
  The KB article (not posted yet) will be at http://support.microsoft.com/ kbid=917327
  

• maniac

  I have the same problem and would like to try the patch. Where can I get it
  
  

• Steve1031

  Bill, just to let you know, I called Microsoft PSS and they sent me the hotfix VS80-KB917327-X86-ENU.exe and it works great! (but it took quite a while to install)

  Thanks again for going through this whole process,

  Ted.

  
  

• Dickin

  Let me ask the person at Microsoft with whom I have been in contact to see if they would like another person (you) to test the patch before they release it. In my eyes it would be smart on their part to have as many testers verify the patch as possible. I'll give them your email address.
  
  If you do not hear from them in a few days email me directly. I would rather they approve and give it to you directly if possible.
  
  
  

• Thieme

  Thanks, validated and voted.
  

• yuvald

  hello

  I am having the same problem.

  where can i get the fix

  thanks!!!

  
  

• Bharathi Raja

  Bug submitted, along with a trivial dialog app that demonstrates the issue. Happens every time.
  
  

  http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx feedbackId=FDBK46637

  
  
  

• Deepakgg

  Thanks for the update Bill,

  Ted.

  
  

• Eddy-kun

  Looking at the bug you reported on product feedback, I see now that they have already fixed this problem - you may want to request a QFE now.  See:

  http://www.codeproject.com/scrapbook/semicolon_1.asp print=true

  for more information about the QFE process (warning: the above article is a bit dated, but a lot of it is still valid today)  I believe this may be considered a candidate as there's no real workaround. 

  P.S.  Microsoft, thanks for fixing this quickly,

  Ted.

  
  

• Mandhadi

  A hotfix is being created as we speak. I've tested the initial patch and it works fine. I think (but I'm not sure) that the final fix will be QFE4134.
  
  
  

• I Love Burger

  Delete your APS file(s), restart, and try again, to see if it still happens. I've heard about APS files eventually causing corruptions.

  While not really the same problem as yours, the APS file has been known to cause similar problems, see

  http://www.mihai-nita.net/20051030a.shtml

  
  

• shongalolo

  Thanks Bill,

  I do not have your mail address but please send your email address to my hotmail (obrynild@...).

  OleM

  
  
  

• V3M4

  Interesting article, definitely a related concept, but doesn't 100% directly deal with my issue. And deteting the APS file as you suggested didn't do it (I had high hopes...). It almost seems like the Resource Editor has decided that "oh you have multiple code pages so you must need Unicode whether you want it or not...."
  
  The article does raise the issue that has bothered me for years: I have never been able to merely cut and paste the translations for Chinese / Polish / Hungarian into my resource file. The translations get munched that way too. I have to go to a system running e.g. Windows Chinese, save the translations to a flat text file on that system (so it writes using the correct code page), and THEN I can cut and paste the (seemingly garbled) translations into my RC file. What a chore. If I had gone Unicode in the beginning this might not have been the case, but then the Resource Editor didn't support Unicode until now, so I would have had troubles either way.
  
  But it seems like this "improvement" of supporting Unicode has broken the support for my MBCS app, even though I have "Use MBCS" selected in my project settings.
  
  Does anyone know of a way to tell the Resource Editor to knock it off and go back to the old MBCS-supporting behavior
  
  
  
• 2005 Resource Editor trashes non-English languages when you edit any dialog