On Sat, 2007-12-08 at 07:03 -0500, Onur Tugcu wrote:
Hi,
I'm writing my strings hardcoded into the program, so I want to make
use of string literals in C++.
I think the easiest thing to do is not to use wchar_t at all but
directly encode the string literals in UTF-8.
When I use gtkmm with
-- Forwarded message --
From: Onur Tugcu [EMAIL PROTECTED]
Date: Dec 8, 2007 12:22 PM
Subject: Re: wide char string literals to Glib ustring
To: Armin Burgmeier [EMAIL PROTECTED]
On Dec 8, 2007 7:43 AM, Armin Burgmeier [EMAIL PROTECTED] wrote:
On Sat, 2007-12-08 at 07:03 -0500,
On Sat, 2007-12-08 at 12:24 -0500, Onur Tugcu wrote:
To me, easiest would be to be able to write unicode directly
into code and to not worry about the codes. Also, I imagine
multi-byte glyphs will suffer from endianness.
No, UTF-8 is composed of a series of characters (a narrow codeset), so
On Sat, 2007-12-08 at 18:20 -0500, Onur Tugcu wrote:
On Dec 8, 2007 5:55 PM, Chris Vine [EMAIL PROTECTED] wrote:
On Sat, 2007-12-08 at 12:24 -0500, Onur Tugcu wrote:
To me, easiest would be to be able to write unicode directly
into code and to not worry about the codes. Also, I imagine
Hi. I'm thinking of working on the Gst::Message class in such a way so
that when messages are sent out to the Gst::Bus they are the right type
(e.g. Gst::MessageError when an error occurs instead of just a
Gst::Message). I'm looking at things and see that Gst::Message should
inherit from
