Fwd: Re: Save files with correct character set
- From: Spazzatura.Live <kharhonte hotmail com>
- To: gtkmm-list gnome org
- Subject: Fwd: Re: Save files with correct character set
- Date: Thu, 22 Mar 2012 20:11:31 +0100
You're right, the content is UTF-8, so my problem is that i don't need
one like that.
I thought the casting from Glib::ustring to std::string also made a
conversion of the content (from unicode char) so the file has wrong
extended character so that was the issue...
Probably, instead, is the tool i use after which doesn't support Unicode
file (i mean files with Unicode character encoding).
So the new question is that: How can i convert the Glib::ustring from
Unicode to ASCII (ISO-8859-1) and save to file?
That slightly depends what the OP meant by "a non-unicode file". It
will write the file with the contents of the Glib::ustring, which is
UTF-8. The resulting file will be an unembellished UTF-8 file, which a
lot of Micro$oft tools will declare to be plain ASCII because it
explicitly isn't UCS-2. Of course, if that's what he means then it's
not Glib that's broken....
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]