Looking for an article in Delphi Magazine
-
Does @SAKryukov or maybe anybody other knows where following article is available, maybe as PDF? S. A. Kryukov, ‘Unicode Controls: What Can VCL Do?’, The Delphi Magazine, 116 (April 2005), p. 33-43 Thank you very much in advance. Bruno
-
Does @SAKryukov or maybe anybody other knows where following article is available, maybe as PDF? S. A. Kryukov, ‘Unicode Controls: What Can VCL Do?’, The Delphi Magazine, 116 (April 2005), p. 33-43 Thank you very much in advance. Bruno
The Delphi Magazine was discontinued after I published this article. I may need considerable time to dig it out. But let me tall you: this is not actual anymore. At that time, it was really a cunning trick, to enable Unicode for VCL. which was not designed to support it; and the source code wasn't available. It was to avoid re-writing VCL controls, but to pin-point some methods in certain controls which had to be overridden or added. The problem was solved, but in later versions of Delphi, Unicode versions have been introduced. And look at modern Free Pascal with Lasarus. It gives you true cross-platform UI, very nice, and yet majorly compatible with old VCL. You just won't need my work. If you have any questions, I'll try to answer. One point for you: if you want to address to some member, you have to comment on any of one's posts, such as answer of comment. I did not get any notifications on your question. Somebody somehow notified me.
—SA
Sergey A Kryukov
-
The Delphi Magazine was discontinued after I published this article. I may need considerable time to dig it out. But let me tall you: this is not actual anymore. At that time, it was really a cunning trick, to enable Unicode for VCL. which was not designed to support it; and the source code wasn't available. It was to avoid re-writing VCL controls, but to pin-point some methods in certain controls which had to be overridden or added. The problem was solved, but in later versions of Delphi, Unicode versions have been introduced. And look at modern Free Pascal with Lasarus. It gives you true cross-platform UI, very nice, and yet majorly compatible with old VCL. You just won't need my work. If you have any questions, I'll try to answer. One point for you: if you want to address to some member, you have to comment on any of one's posts, such as answer of comment. I did not get any notifications on your question. Somebody somehow notified me.
—SA
Sergey A Kryukov
Dear Sergey First of all, thank you very much that you responded. Sorry, I thought if I write "@SAKryukov " in the message, that the CP system will send a notification to you. Now your article I think, is more than enough actual for me. I need to do a "crazy" thing, means: I need to migrate an bcb6 application from Interbase to MSSQL. More or less an easy thing, ADO works still fine with the old bcb6. I did most of these work already. But now I'm asking me also, whether I should also go the way to save the data in Unicode and I'm looking for a confirmation whether my thinkings concerning all the consequences are correct. And for this I think your article could be a very great help. Thank you very much again. Kind regards Bruno [Edit] My imagination... At present everything in bcb6 is done with MBCS. That means: - "Windows-ControlPanel-RegionalSetting-UniCode incompatible" needs to be setup correctly. - Queries from DB do use TStringField. DBControls manage to show the data correctly (according to above mentioned regional settings) New: Moving to UniCode DB - All Queries using TStringField needs to be modified to use TWideStringField. - While passing TWideStringField to DBControls, all WideStrings (Unicode) will implicitely converted to AnsiString (MBCS), by the "help" of WideString/AnsiString cooperation given by bcb6/VCL. - Because of the point mentioned just above, still "Windows-ControlPanel-RegionalSetting-UniCode incompatible" needs to be setup correctly. This so that the above mentioned implicit conversion Wide/Ansi does work correctly. [/Edit]
-
Dear Sergey First of all, thank you very much that you responded. Sorry, I thought if I write "@SAKryukov " in the message, that the CP system will send a notification to you. Now your article I think, is more than enough actual for me. I need to do a "crazy" thing, means: I need to migrate an bcb6 application from Interbase to MSSQL. More or less an easy thing, ADO works still fine with the old bcb6. I did most of these work already. But now I'm asking me also, whether I should also go the way to save the data in Unicode and I'm looking for a confirmation whether my thinkings concerning all the consequences are correct. And for this I think your article could be a very great help. Thank you very much again. Kind regards Bruno [Edit] My imagination... At present everything in bcb6 is done with MBCS. That means: - "Windows-ControlPanel-RegionalSetting-UniCode incompatible" needs to be setup correctly. - Queries from DB do use TStringField. DBControls manage to show the data correctly (according to above mentioned regional settings) New: Moving to UniCode DB - All Queries using TStringField needs to be modified to use TWideStringField. - While passing TWideStringField to DBControls, all WideStrings (Unicode) will implicitely converted to AnsiString (MBCS), by the "help" of WideString/AnsiString cooperation given by bcb6/VCL. - Because of the point mentioned just above, still "Windows-ControlPanel-RegionalSetting-UniCode incompatible" needs to be setup correctly. This so that the above mentioned implicit conversion Wide/Ansi does work correctly. [/Edit]
Do you really have to work with that badly obsolete Delphi where VCL was non-Unicode? I doubt it. At that time my work was a real saver, but right now all Delphi and Pascal libraries are all with proper Unicode support. My work did not do anything beyond the VCL UI, it has nothing to do with databases, etc. And it is inapplicable to modern Delphi libraries. Instead, I can try to answer your questions, but I haven't use Delphi for a long time. I have Free Pascal with Lazarus and recently worked with it and thing it's great. And I seriously advise you to port code to Free Pascal. With Lazarus, it makes great cross-platform library and tools. (If not .NET with C#, of course. There is nothing closer to Object Pascal then C#. And yet, Delphi has some unique features non implemented in .NET; one of them is its fully-fledged metaclasses, a feature much more advanced then .NET reflection.)
—SA
Sergey A Kryukov
-
Dear Sergey First of all, thank you very much that you responded. Sorry, I thought if I write "@SAKryukov " in the message, that the CP system will send a notification to you. Now your article I think, is more than enough actual for me. I need to do a "crazy" thing, means: I need to migrate an bcb6 application from Interbase to MSSQL. More or less an easy thing, ADO works still fine with the old bcb6. I did most of these work already. But now I'm asking me also, whether I should also go the way to save the data in Unicode and I'm looking for a confirmation whether my thinkings concerning all the consequences are correct. And for this I think your article could be a very great help. Thank you very much again. Kind regards Bruno [Edit] My imagination... At present everything in bcb6 is done with MBCS. That means: - "Windows-ControlPanel-RegionalSetting-UniCode incompatible" needs to be setup correctly. - Queries from DB do use TStringField. DBControls manage to show the data correctly (according to above mentioned regional settings) New: Moving to UniCode DB - All Queries using TStringField needs to be modified to use TWideStringField. - While passing TWideStringField to DBControls, all WideStrings (Unicode) will implicitely converted to AnsiString (MBCS), by the "help" of WideString/AnsiString cooperation given by bcb6/VCL. - Because of the point mentioned just above, still "Windows-ControlPanel-RegionalSetting-UniCode incompatible" needs to be setup correctly. This so that the above mentioned implicit conversion Wide/Ansi does work correctly. [/Edit]
Bruno, Finally, I got to my old archives and dug out this old Delphi article, with full source code and the article, will gladly deliver it to you. Please respond; probably, one way would be if you ask a formal question. The article title and publication data: "Unicode Controls: What Can VCL Do?", The Delphi Magazine, 116 (April 2005), p. 33-43 —SA
Sergey A Kryukov
-
Dear Sergey First of all, thank you very much that you responded. Sorry, I thought if I write "@SAKryukov " in the message, that the CP system will send a notification to you. Now your article I think, is more than enough actual for me. I need to do a "crazy" thing, means: I need to migrate an bcb6 application from Interbase to MSSQL. More or less an easy thing, ADO works still fine with the old bcb6. I did most of these work already. But now I'm asking me also, whether I should also go the way to save the data in Unicode and I'm looking for a confirmation whether my thinkings concerning all the consequences are correct. And for this I think your article could be a very great help. Thank you very much again. Kind regards Bruno [Edit] My imagination... At present everything in bcb6 is done with MBCS. That means: - "Windows-ControlPanel-RegionalSetting-UniCode incompatible" needs to be setup correctly. - Queries from DB do use TStringField. DBControls manage to show the data correctly (according to above mentioned regional settings) New: Moving to UniCode DB - All Queries using TStringField needs to be modified to use TWideStringField. - While passing TWideStringField to DBControls, all WideStrings (Unicode) will implicitely converted to AnsiString (MBCS), by the "help" of WideString/AnsiString cooperation given by bcb6/VCL. - Because of the point mentioned just above, still "Windows-ControlPanel-RegionalSetting-UniCode incompatible" needs to be setup correctly. This so that the above mentioned implicit conversion Wide/Ansi does work correctly. [/Edit]
Bruno, I got your message. I would prefer publishing at CodeProject. I can simply upload it to my area, so you could copy it all, but what do you think, would it be appropriate to publish it as a normal article, despite the pure historical value of it. :-) I have it formatted to CodeProject style... Perhaps with added appropriate preface... —SA
Sergey A Kryukov
-
Dear Sergey First of all, thank you very much that you responded. Sorry, I thought if I write "@SAKryukov " in the message, that the CP system will send a notification to you. Now your article I think, is more than enough actual for me. I need to do a "crazy" thing, means: I need to migrate an bcb6 application from Interbase to MSSQL. More or less an easy thing, ADO works still fine with the old bcb6. I did most of these work already. But now I'm asking me also, whether I should also go the way to save the data in Unicode and I'm looking for a confirmation whether my thinkings concerning all the consequences are correct. And for this I think your article could be a very great help. Thank you very much again. Kind regards Bruno [Edit] My imagination... At present everything in bcb6 is done with MBCS. That means: - "Windows-ControlPanel-RegionalSetting-UniCode incompatible" needs to be setup correctly. - Queries from DB do use TStringField. DBControls manage to show the data correctly (according to above mentioned regional settings) New: Moving to UniCode DB - All Queries using TStringField needs to be modified to use TWideStringField. - While passing TWideStringField to DBControls, all WideStrings (Unicode) will implicitely converted to AnsiString (MBCS), by the "help" of WideString/AnsiString cooperation given by bcb6/VCL. - Because of the point mentioned just above, still "Windows-ControlPanel-RegionalSetting-UniCode incompatible" needs to be setup correctly. This so that the above mentioned implicit conversion Wide/Ansi does work correctly. [/Edit]
Bruno, I got your message. I would prefer publishing at CodeProject. I can simply upload it to my area, so you could copy it all, but what do you think, would it be appropriate to publish it as a normal article, despite the pure historical value of it. :-) I have it formatted to CodeProject style... Perhaps with added appropriate preface... Anyway, I don't want to delay you at this moment of time. You can take article and code here: S. A. Kryukov, UnicodeControls.zip, from: The Delphi Magazine, 116 (April 2005), p. 33-43 (54.1 KB). Please send me some feedback, ask if you have any questions. Again, remember that you can re-do all your old Delphi code to Free Pascal with Lazarus and get rid of all these problems.
—SA
Sergey A Kryukov
-
Bruno, I got your message. I would prefer publishing at CodeProject. I can simply upload it to my area, so you could copy it all, but what do you think, would it be appropriate to publish it as a normal article, despite the pure historical value of it. :-) I have it formatted to CodeProject style... Perhaps with added appropriate preface... Anyway, I don't want to delay you at this moment of time. You can take article and code here: S. A. Kryukov, UnicodeControls.zip, from: The Delphi Magazine, 116 (April 2005), p. 33-43 (54.1 KB). Please send me some feedback, ask if you have any questions. Again, remember that you can re-do all your old Delphi code to Free Pascal with Lazarus and get rid of all these problems.
—SA
Sergey A Kryukov
Dear Sergey Thank you so much for your help. Meanwhile I posted a question, please answer if you like. BTW: Publish it as an article would be very nice. I don't think I'm the only one who has to fight with something like this.... recognizing this in Praxis ;) Bruno