[Bug 24369] New: UCS-4 trick not working with resource files
wine-bugs at winehq.org
wine-bugs at winehq.org
Sun Sep 12 08:12:14 CDT 2010
http://bugs.winehq.org/show_bug.cgi?id=24369
Summary: UCS-4 trick not working with resource files
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Windows 98
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs at winehq.org
ReportedBy: carlo.bramix at libero.it
Created an attachment (id=30717)
--> (http://bugs.winehq.org/attachment.cgi?id=30717)
Resource file for testing
Here there is an extract of my email sent to wine-devel mailing list about this
problem:
==== CUT = CUT = CUT
Let's take for example this piece of code from richedit.h:
#if defined(__GNUC__)
# define RICHEDIT_CLASS20W (const WCHAR []){
'R','i','c','h','E','d','i','t','2','0','W',0 }
#elif defined(_MSC_VER)
# define RICHEDIT_CLASS20W L"RichEdit20W"
#else
static const WCHAR RICHEDIT_CLASS20W[] = {
'R','i','c','h','E','d','i','t','2','0','W',0 };
#endif
Because the famous UCS-4 "issue", the control name is splitted in its single
letters.
While this can work in almost all situations with C/C++ sources, it is
absolutely not possible to put a richedit control in RC files.
For example, if I put a Richedit control into a dialog box, it will crash since
the letter by letter format won't be recognized by the resource compiler.
More information about the wine-bugs
mailing list