Bug 4682 - WINDRES generates unusable dialog resource when multibyte characters exist
Summary: WINDRES generates unusable dialog resource when multibyte characters exist
Status: RESOLVED INVALID
Alias: None
Product: binutils
Classification: Unclassified
Component: binutils (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-21 14:55 UTC by crlf0710
Modified: 2007-06-29 00:16 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description crlf0710 2007-06-21 14:55:56 UTC
When there are multibyte characters(Chinese characters, for example) in the 
text of controls(for example: Label) in dialog resources, WINDRES generates 
corrupted and unusable output. English characters won't cause this problem.

Steps to Reproduce:
1. Create a resource script file, insert a dialog, put a Label on it, and 
modify its text to a sentense in Chinese. 
2. Use DialogBox API to show the dialog.
3. Build the code.

Actual Result:
The dialog won't appear up.

Build Platform:
Windows XP SP2 (and other Win32 platforms)
---------------------------------------------------------------
Sorry for my bad English
Comment 1 Kai Tietz 2007-06-27 13:14:39 UTC
(In reply to comment #0)
> When there are multibyte characters(Chinese characters, for example) in the 
> text of controls(for example: Label) in dialog resources, WINDRES generates 
> corrupted and unusable output. English characters won't cause this problem.
> Steps to Reproduce:
> 1. Create a resource script file, insert a dialog, put a Label on it, and 
> modify its text to a sentense in Chinese. 
> 2. Use DialogBox API to show the dialog.
> 3. Build the code.

Have you used the -c option of windres to specify your language codepage ? You 
can do this also within the rc-file by using the code "#pragma code_page(<your-
used-codepage>)".
Comment 2 crlf0710 2007-06-29 00:16:46 UTC
I updated binutils and found it has been fixed.

Sorry.