It would also be great for me to have Unicode controls under
win32.
On 2006-05-12 at 19:58,
Felipe Monteiro de Carvalho ([EMAIL PROTECTED]) wrote:
> What is missing is adding support for utf-8 on the win32 interface.
> It would probably have to be something like this:
> If Windows 9x, then convert utf-8 to adequate iso
> If Windows NT, then convert utf-8 to utf-16 and call the Wide version
> of Windows API.
I agree - this is also my understanding after the recent
thread. It seems that it would be highly inefficient on
native utf-16 machines (such as WinNT+), but it should work,
in principle. I have not tried it (yet), but I am browsing the
code from time to time (when I find some time).
Let me quote two other posts on the subject, just for the
sake of completeness...
On 2005-11-18 at 00:02,
Marc Weustink ([EMAIL PROTECTED]) wrote:
> The LCL consists of 2 parts, one which implements a class hierarchy
> compatible with the VCL and one that communicates to the various widgets
> of the various platforms. The communication between the 2 parts is done
> by a abstract class TWidgetset. Each widgetset is implemented by its own
> derived class form TWidgetset. Where the GTK widgetset is the oldest. In
> this widgetset the string encoding is determined by the LANG environment
> var. If it is a UTF8 variant, all strings from and to native
> controls/widgets are UTF8 encoded. However utf8 may affect keyboard
> handling for gtk1. On gtk2 this problem is solved, but not implemented
> yet, the keyboard routines still rely on gtk1 code there.
> The win32 interfaces is iirc setup with ansi widgets, so you wont get
> unicode there.
> In the new OSX interface we decided to make it UTF8 internally, since
> there is a movement to make the LCL UTF8 aware.
> Back to your question. IMO it doesn't make much sense to add new
> unicode controls, since the native controls should support that (I read
> UTF8 here as unicode) in the future.
> It is not like delphi where you must add new unicode aware controls
> since you cannot change the creation of the VCL controls.
On 2006-05-01 at 14:16,
roozbeh gholizadeh ([EMAIL PROTECTED]) wrote:
> Well i read your mail fast,although i shouldnt for this reply on it,but
> here are few things just to remind.
> Currently all windows apis are mapped to *A version,as far as i know like
> c headers there arent define words like unicode which you can alter
> that,so you have to change all of them-or only those you require-to be
> unicode versions.
> Secondly using getwindowtextw or getwindowstexta when your window is
> created by createwindowa,doesnt differ.
> So you have to change all window creation too,to make them really unicode.
> Not doing that and using *W version is just like using *A version and then
> converting that string to widestring.
> If you have time-which should be more than normal :)-take a look at tnt
> components and see how they have implemented everything,and whats the
> diffrence between them and vcl,the same will apply here too.
Regards,
Borut
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
