Am 13.02.2013 17:55, schrieb אנטולי קרסנר:
> Can I use std::u16string, std::u32string or std::string (with u8 string
> literals) with gettext and get perfect UTF-8 i18n-alized strings just
> like I would get by using Glib::ustring and gettext (including
> glibmm/i18n.h in source files and mark stri
Glib::ustring; they would handle hebrew, no problem. Take advantage of
> C++11 new features!
>
>
>
>
> > - Original Message -
> >
> > From: tomback...@gmail.com
> >
> > Sent: 02/12/13 01:13 PM
> >
> > To: gtkmm-li
Take advantage of
C++11 new features!
- Original Message -
From: tomback...@gmail.com
Sent: 02/12/13 01:13 PM
To: gtkmm-list@gnome.org
Subject: Glib::ustring move constructor and C++11 features
Hi everybody,
I've been writing an application which loads a possibly long
Glib:
you could use std::u16string or std::u32string instead of Glib::ustring; they
would handle hebrew, no problem. Take advantage of C++11 new features!
- Original Message -
From: tomback...@gmail.com
Sent: 02/12/13 01:13 PM
To: gtkmm-list@gnome.org
Subject: Glib::ustring move constructor and
Hi everybody,
I've been writing an application which loads a possibly long
Glib::ustring from a file and stores it as a data member of a c++ class
I wrote. I wanted to use a move-constructor to pass that string to the
class constructor by rvlaue reference, but Glibmm doesn't use C++11
features.
A
