unicode

[vooood]

i'm making a console application and i need unicode support.. how do i
get it? the app also needs to be multiplatform (windows/linux only).. is
it possible to use unicode with pdcurses?


thanx


vooood

 

[Matthias Kaeppler]

i'm making a console application and i need unicode support.. how do i
get it? the app also needs to be multiplatform (windows/linux only).. is
it possible to use unicode with pdcurses?


thanx


vooood

glibc has been ported to C++ and has a type called Glib::ustring. IIRC,
its purpose is to support wide byte characters. It's non-standard, but
it has the same interface as std::string and also behaves like it.

 

[vooood]

glibc has been ported to C++ and has a type called Glib::ustring. IIRC,
its purpose is to support wide byte characters. It's non-standard, but
it has the same interface as std::string and also behaves like it.

can you tell me where could i find more information on this and
implementation examples?


vooood

 

[red floyd]

glibc has been ported to C++ and has a type called Glib::ustring. IIRC,
its purpose is to support wide byte characters. It's non-standard, but
it has the same interface as std::string and also behaves like it.

What's wrong with std::wstring ?

 

[Ron Natalie]

i'm making a console application and i need unicode support.. how do i
get it? the app also needs to be multiplatform (windows/linux only).. is
it possible to use unicode with pdcurses?

There's no platform independent UNICODE. Windows uses a 16 bit encoding
of UNICODE, most UNICES use 32 bits. In Windows the interfaces are
natively 16-bit unicode, while on most UNICES things are converted back
to a UTF-8 multibyte encoding.

While using wchar_t and things based on it will get you a lot of the
way, there are a lot of things that you'll have to deal with on an
implementation by impelementation basis (Part of which would be
unnecessary if C++ wasn't lacking wchar_t based interfaces to
the various important system calls like filenames and program
arguments).

 

[Rapscallion]

What's wrong with std::wstring ?

It's underspecified (i.e. no encodings specified).

 

[Ioannis Vranos]

i'm making a console application and i need unicode support.. how do i
get it? the app also needs to be multiplatform (windows/linux only).. is
it possible to use unicode with pdcurses?

You can use the largest character set of your compiler (usually Unicode) by using wchar_t,
wcin, wcout, wstring and the w facilities in general.

 

[Matthias Kaeppler]

can you tell me where could i find more information on this and
implementation examples?


vooood

http://freshmeat.net/projects/glibmm/

 

[Matthias Kaeppler]

There's no platform independent UNICODE. Windows uses a 16 bit encoding
of UNICODE, most UNICES use 32 bits. In Windows the interfaces are
natively 16-bit unicode, while on most UNICES things are converted back
to a UTF-8 multibyte encoding.

But there are platform independent wrapper implementations, that's what
he asked for. glibmm has such an implementation, and it's called
Glib::ustring. gtkmm and gdkmm use it exclusively over std::string.

See
http://www.gtkmm.org/docs/glibmm-2.4/docs/reference/html/classGlib_1_1ustring.html

 

[Ron Natalie]

But there are platform independent wrapper implementations, that's what
he asked for. glibmm has such an implementation, and it's called
Glib::ustring. gtkmm and gdkmm use it exclusively over std::string.

See
http://www.gtkmm.org/docs/glibmm-2.4/docs/reference/html/classGlib_1_1ustring.html

All that gets him is a UTF-8 string implemenation.
Won't help him at all with the bigger issue of application
portability.