Unicode vs Non-Unicode

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I understand that the unicode versions of the com components support foreign characters, but I wanted to know other than characterset implementation, is there any other differences between the two versions, particularly with the CommandBars and TaskPanel?  We localize our applications and would prefer to use the unicode controls, but we have implemented everything so far using the ANSI controls.  What impact would switching to the unicode controls have, if any? 

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
griswald88 Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 16 May 2008 Status: Offline Points: 27	Post Options Post Reply Quote griswald88 Report Post Thanks(0) Quote Reply Topic: Unicode vs Non-Unicode Posted: 26 June 2008 at 1:16pm
	I understand that the unicode versions of the com components support foreign characters, but I wanted to know other than characterset implementation, is there any other differences between the two versions, particularly with the CommandBars and TaskPanel? We localize our applications and would prefer to use the unicode controls, but we have implemented everything so far using the ANSI controls. What impact would switching to the unicode controls have, if any?

Oleg Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 21 May 2003 Location: United States Status: Offline Points: 11234	Post Options Post Reply Quote Oleg Report Post Thanks(0) Quote Reply Posted: 27 June 2008 at 1:27am
	Hi, Don't think you will notice any difference instead of charset support. Main difference that Unicode version don't work with win9x.
	Oleg, Support Team CODEJOCK SOFTWARE SOLUTIONS

nighthawk Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 11 June 2004 Status: Offline Points: 167	Post Options Post Reply Quote nighthawk Report Post Thanks(0) Quote Reply Posted: 27 June 2008 at 4:24pm
	I don't know how unicode works from a technical level but is it possible for you to combine the unicode and non-unicode versions. Either make it auto-detect whether or not unicode is supported or else have a setting which will turn it on and off? Right now I'm using the non-unicode version because I need to support Win9x but I also would like to also support other languages for those who have a newer OS.

Baldur Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 22 November 2006 Location: Germany Status: Offline Points: 244	Post Options Post Reply Quote Baldur Report Post Thanks(0) Quote Reply Posted: 11 July 2008 at 10:25am
	Normaly it's no problem, if you use the ActiveX-Versions. The CLSID's and Typelib-Id from both versions are the same. If you run the CJ COM-Registrator you can switch between this versions without any effect. So for Win9X you can deliver the non-unicode and for other you can deliver the unicode-versions. Your Application can ask the Unicode-Property of CJ's control. Because COM-interfaces use BSTR for Strings, this are always Unicode (for windows also named WideChar). Only the UI's of windows himself doesn't support WideChar in 9X.

nighthawk Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 11 June 2004 Status: Offline Points: 167	Post Options Post Reply Quote nighthawk Report Post Thanks(0) Quote Reply Posted: 11 July 2008 at 11:15pm
	I'll have to test out using both unicode and non-unicode versions of the ocxs. I'm not going to create a seperate installation package for both versions so I will have to bundle them together, which will increase the size of my installation program by several MB. Not ideal but if it works smoothly, I may still go with that option.