UNICODE newbie

Thread View: borland.public.cppbuilder.nativeapi

6 messages

[T] Back to Threads [V] Tree View [G] Group Articles

6 total messages Started by SmartDude Wed, 20 Jun 2007 23:50

#1703

Author: SmartDude
Date: Wed, 20 Jun 2007 23:50

9 lines
1358 bytes

I recently discovered that filenames on windows XP can have special unicode 
characters in their filenames.  Now it looks like i need to support unicode 
in my programs.  they say that if you define UNICODE it automaticly makes 
all TCHAR and LPCTSTR parameters for win32 funcions take in wide char(which 
is what i want).  defining UNICODE give me errors but _UNICODE dosn't.  Do 
the ANSIStrings given by TOpenDialog have a unicode representation if you 
use the .WideChar and .WideCharBufSize?

Thanks.

Re: UNICODE newbie

#1704

Author: Remy Lebeau (TeamB)
Date: Thu, 21 Jun 2007 04:14

22 lines
1651 bytes

"SmartDude" <smartdude81@comcast.net> wrote in message
news:4679bd3d$1@newsgroups.borland.com...

> defining UNICODE give me errors but _UNICODE dosn't.

Please be more specific.

> Do the ANSIStrings given by TOpenDialog have a unicode
> representation if you use the .WideChar and .WideCharBufSize?

No.  Most VCL components do not have any Unicode support at all, as
the Win32 VCL is primarily written for Ansi usage only.  If you want
to use Unicode, then you need to either use third-party
Unicode-capable components, such as TntWare, or else access the Win32
API directly instead of using VCL wrappers.  For instance, TOpenDialog
calls the Win32 API GetOpenFileName() function internally.  You can
call that directly, though you will have to set up its values and
callbacks manually in your own code.


Gambit

Re: UNICODE newbie

#1721

Author: SmartDude
Date: Thu, 21 Jun 2007 22:26

28 lines
2028 bytes

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:4679fb6f$1@newsgroups.borland.com...
>
> "SmartDude" <smartdude81@comcast.net> wrote in message
> news:4679bd3d$1@newsgroups.borland.com...
>
>> defining UNICODE give me errors but _UNICODE dosn't.
>
> Please be more specific.
>
>> Do the ANSIStrings given by TOpenDialog have a unicode
>> representation if you use the .WideChar and .WideCharBufSize?
>
> No.  Most VCL components do not have any Unicode support at all, as
> the Win32 VCL is primarily written for Ansi usage only.  If you want
> to use Unicode, then you need to either use third-party
> Unicode-capable components, such as TntWare, or else access the Win32
> API directly instead of using VCL wrappers.  For instance, TOpenDialog
> calls the Win32 API GetOpenFileName() function internally.  You can
> call that directly, though you will have to set up its values and
> callbacks manually in your own code.
>
>
> Gambit
>
>
I was afraid of that!

Re: UNICODE newbie

#1722

Author: Remy Lebeau (TeamB)
Date: Fri, 22 Jun 2007 02:02

26 lines
1852 bytes

"SmartDude" <smartdude81@comcast.net> wrote in message
news:467afb12$1@newsgroups.borland.com...

> I was afraid of that!

Or you could wait until 2008.  Borland's roadmap shows a fully Unicode
VCL being available by then:

    Delphi and C++Builder Roadmap
    http://dn.codegear.com/article/36620

    Codename: Tibur�n
    Time Frame: First Half 2008
    Theme: Delphi and VCL development with Unicode and Generics

    - Delphi Win32 Unicode
    This means that the IDE, the VCL, and all types of development
should be made fully Unicode-compatible. The standard string in the
Delphi language will become a Unicode string, meaning that the IDE,
the VCL - that is, the entire product - will be Unicode-based.
Developers around the world will be able to develop applications for
use in any language using the Unicode standard.


Gambit

Re: UNICODE newbie

#1735

Author: poojo hackma
Date: Mon, 25 Jun 2007 21:19

31 lines
2101 bytes

Interesting.

I notice the site is not Borland. Does this mean Borland is owned by someone 
else? I heard rumors a year or two ago that it being bought out was not 
unlikely.


Gambit wrote:
>
> Or you could wait until 2008.  Borland's roadmap shows a fully Unicode
> VCL being available by then:
>
>    Delphi and C++Builder Roadmap
>    http://dn.codegear.com/article/36620
>
>    Codename: Tibur�n
>    Time Frame: First Half 2008
>    Theme: Delphi and VCL development with Unicode and Generics
>
>    - Delphi Win32 Unicode
>    This means that the IDE, the VCL, and all types of development
> should be made fully Unicode-compatible. The standard string in the
> Delphi language will become a Unicode string, meaning that the IDE,
> the VCL - that is, the entire product - will be Unicode-based.
> Developers around the world will be able to develop applications for
> use in any language using the Unicode standard.
>
>
> Gambit
>
>

Re: UNICODE newbie

#1738

Author: Remy Lebeau (TeamB)
Date: Mon, 25 Jun 2007 22:56

22 lines
1643 bytes

"poojo hackma" <poojo.com/mail> wrote in message
news:46803151$1@newsgroups.borland.com...

> I notice the site is not Borland.

Yes, it is.  CodeGear is the new company that Borland created to
manage its developer tools.

> Does this mean Borland is owned by someone else?

No.  CodeGear is owned by Borland.

> I heard rumors a year or two ago that it being bought out
> was not unlikely.

Borland tried to sell off its developer tools, but it couldn't find a
buyer that it was happy with, so a new child company named CodeGear
was created instead.


Gambit

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads