diff options
author | kwm <kwm@df743ca5-7f9a-e211-a948-0013205c9059> | 2010-06-19 04:09:32 +0800 |
---|---|---|
committer | kwm <kwm@df743ca5-7f9a-e211-a948-0013205c9059> | 2010-06-19 04:09:32 +0800 |
commit | edda531c5cd77a95b5a30e767b29a1d057f2d870 (patch) | |
tree | 280a75367589c431ad47ea0404e0cdb30aeff094 /devel/glibmm/files/patch-glib_glibmm_ustring.cc | |
parent | a66a339f6eb04c77eb4e575240b48d60d39895c2 (diff) | |
download | marcuscom-ports-edda531c5cd77a95b5a30e767b29a1d057f2d870.tar.gz marcuscom-ports-edda531c5cd77a95b5a30e767b29a1d057f2d870.tar.zst marcuscom-ports-edda531c5cd77a95b5a30e767b29a1d057f2d870.zip |
Update to 2.25.2.
git-svn-id: svn://creme-brulee.marcuscom.com/ports/trunk@14254 df743ca5-7f9a-e211-a948-0013205c9059
Diffstat (limited to 'devel/glibmm/files/patch-glib_glibmm_ustring.cc')
-rw-r--r-- | devel/glibmm/files/patch-glib_glibmm_ustring.cc | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/devel/glibmm/files/patch-glib_glibmm_ustring.cc b/devel/glibmm/files/patch-glib_glibmm_ustring.cc new file mode 100644 index 000000000..dbcfc7dde --- /dev/null +++ b/devel/glibmm/files/patch-glib_glibmm_ustring.cc @@ -0,0 +1,20 @@ +--- glib/glibmm/ustring.cc.orig 2010-06-18 21:49:11.000000000 +0200 ++++ glib/glibmm/ustring.cc 2010-06-18 22:03:33.000000000 +0200 +@@ -1361,7 +1361,7 @@ + Glib::Error::throw_exception(error); + } + +- utf8_string.assign(buf.get(), buf.get() + n_bytes); ++// utf8_string.assign(buf.get(), buf.get() + n_bytes); + + return is; + } +@@ -1392,7 +1392,7 @@ + // NUL. Given this, there doesn't seem much of a point in allowing NUL in + // formatted output. The semantics would be unclear anyway: what's the + // screen width of a NUL? +- os << reinterpret_cast<wchar_t*>(buf.get()); ++// os << reinterpret_cast<wchar_t*>(buf.get()); + + return os; + } |