Hi!
I wrote:
> As I mentioned, I even tried explicit conversion. But the
> latin-1/unicode converter doesn't convert anything :(
That was wrong: It does convert strings properly. But when the file is
written, it's automagically converted back to the character set for the
locale. :-(
Simple to fix, however, once you know what's going on:
- stream << doc.toString(); // <- converts
+ stream << doc.toCString(); // <- doesn't convert
So, from now on, the contents of dvbcut project files will *always* be
UTF-8 encoded, as they should be. Besides that, dvbcut now writes a
proper XML declaration to the beginning of the file:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE dvbcut>
...
Backwards compatibility is maintained, but since the change affects the
parser, older versions of dvbcut will not accept new-style project files
any longer (they require a "<!DOCTYPE" at the beginning of the first
non-empty line).
Since Michael's patch went in yesterday, we're at revision 70 now.
Happy dvbcutting,
--
Michael "Tired" Riepe <[EMAIL PROTECTED]>
X-Tired: Each morning I get up I die a little
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
DVBCUT-user mailing list
DVBCUT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dvbcut-user
