Re: Glib::ustring tradeoffs?
- From: Matthias Kaeppler <matthias finitestate org>
- To: Chris Vine <chris cvine freeserve co uk>
- Cc: gtkmm-list gnome org
- Subject: Re: Glib::ustring tradeoffs?
- Date: Sat, 29 Oct 2005 10:49:05 +0200
Thanks for that in-depth answer Chris.
I'd have another question though. First, what's the difference between
these two conversions:
std::string ascii = "text";
// what's the difference between this ...
Glib::ustring unicode = ascii;
// ... and this?
Glib::ustring unicode = Glib::locale_to_utf8(ascii);
Furthermore, do I have to wrap every line of text into a call to
Glib::locale_to_utf8()? For example if I define a widget text somewhere,
do I have to do it like this:
#define WIDGET_LABEL Glib::locale_to_utf8("BUTTON")
...
widget.set_text(WIDGET_LABEL);
and what could happen if I don't make the conversion?
Thanks,
Matthias
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]