[Connect - C++] Problems with special danish characters in dialogbox'es

Question

HI 
 If I change the dialogtext "OptionButton2:" to "Option_&AElig;&Oslash;&Aring;&aelig;&oslash;&aring;:" in the DialogBoxDemo example, the danish characters are not displayed correctly. Please see the attached screendump. I pointed this out in the beginning of august and I was told that a couple of solutions would be provided in the final SDK... 
 Any ideas ? 
 TIA, Evan

Jan Šlegr · Accepted Answer

Hmmm ... interesting. Sounds like something I should try also using standard delivered examples. My original assumption is if a file is UTF-8 encoded, VisualStudio should process it without any warning. 
 
Off-hand I am not sure if there are some know UTF / Unicode issues in Visual Studio 2013, hoping somebody more experienced will shared some recommendations. 
 
Maybe one more test: There are two ways how UTF-8 encoded (codepage 65001) files can be stored: With signature and without signature (also called BOM - byte order mark). Can you try to compile both versions? VisualStudio and also many other editors are able to define the version in Save as. 
 
Regards, 
 
 Jan

Boogie58 · Answer

I haven't gotten to playing with unicode in the mdl dialog boxes yet, but do you have to change the encoding value in the transkit.xml file? 
 I have gotten a few errors compiling, because I changed some of my defined strings to L"Text" and they were referenced in a dialog item resource as a label. I noticed that the define for the dialog item struct is Utf8Char. 
 struct DItem_OptionButtonRsc
 {
 long synonymsId;
 UInt32 helpInfo;
 UInt32 helpSource;
 long itemHookId;
 UInt64 itemHookArg; /* The OPTNBTNATTR_... may be used here */
#if defined (resource)
 Utf8Char label[];
 char accessStr[]; // CHAR_OK
 DItem_OptionButtonItemRsc optionButtonItems[];
#else
 long labelLength;
 Utf8Char label[1];
#endif
 };
 
 I wonder if they need changed to a unicode string after the dialog is loaded using mdlDialog_rItemLabelSet() or one of the mdlDialog_ functions that are available for whichever resource type you're setting. I am pretty sure I have done it this way in the past in v8i just messing around. But I haven't done it in Connect yet. 
 Rich