Whole Tomato Software Forums

Whole Tomato Software Forums

All Forums

Visual Assist

You must be registered to post a reply.
Click here to register.

Screensize:

UserName:

Password:

Format:

Message:

Forum code is on.
Html is off.

Check to include your profile signature.
Check to subscribe to this topic.

T O P I C R E V I E W
Mordachai	Posted - Mar 21 2013 : 09:26:37 AM I have a block of text with some unicode literals: const wchar_t * kszDefaultTextFaceNameJapan = _T("#65325;#65331; #12468;#12471;#12483;#12463;"); const wchar_t * kszDefaultDimensionFaceNameJapan = _T("#65325;#65331; #12468;#12471;#12483;#12463;"); I highlight that, type the # key, which brings up the surround with preprocessor define, type UNICODE, hit enter, and get back #ifdef UNICODE const wchar_t * kszDefaultTextFaceNameJapan = _T("MS ????"); const wchar_t * kszDefaultDimensionFaceNameJapan = _T("MS ????"); #endif // UNICODE Hmmm... this FORUM mucks with the data (apparently it's not unicode enabled? But pretend the first block has Japanese Kanji, while the second has what you probably see: junk.
1 L A T E S T R E P L I E S (Newest First)
accord	Posted - Mar 21 2013 : 2:22:21 PM I am seeing the same effect here. Thank you for the clear description. case=5792 I was wondering about this bug for a moment, but after you pointed out that it was indeed unicode originally, it makes sense now :)