Dimitri schrieb:
Hi,
These files don't seem to contain non-ASCII character. If so, this
can't be an encoding issue.
Maybe there's a problem with teh XML declaration, the original:
<?xml version="1.0" encoding="Windows-1252"?>
vs. the Qt output:
<?xml version = '1.0' encoding='Windows-1252'?>
What happens if you just modify the first lien with the XML prolog
to match the original?
No difference -- still fails...
Please post the file you've just tried that fails. Is the first line
looking *exactly* like (including whitespaces):
<?xml version="1.0" encoding="Windows-1252"?>
Yes, I have copied the first line from the working file version.
If so:
* It's not an encoding issue - unless I have missed some non-ASCII
character in you files?
* It's not an issue with the XML declaration.
As far as I can see Qt outputs a legal XML file. Maybe it's not a
valid Visual Studio XML file, you'll to double-check that - I didn't
look into such details. If it's a valid VisualStudio XML file, then
this is a Microdoft bug and you'll have to contact them.
I have checked what happens if I just read in with QTextStream and write
it back into another QTextStream (without setting any encodings) --
this works.
I have diffed the two files in an xml editor saying that the files do
not differ. In that editor I have changed the encoding to windows-1252
(not knowing whether only the first line or "really" the encoding gets
changed in Stylus) -- still the file is unreadable.
So You are most certainly right that the problem is that the vcproj file
"looks" like xml but Visual Studio does not use it like xml. Possibly the
attributes have to appear in a certain sequence.
Does Visual Studio display an error message?
Yes, it says the project file could not be read. No details (<g> it's MS).
--
Dimitri
--
List archive and information: http://lists.trolltech.com/qt-interest/
Thanks for the help!
Best Regards,
Peter
--
List archive and information: http://lists.trolltech.com/qt-interest/
|