| Author |
Message |
| Registered: March 13, 2007 | Reputation:  |  Posts: 2,005 |
| |
| Registered: March 13, 2007 | | Posts: 55 |
| |
| Registered: March 13, 2007 | | Reputation: | | Posts: 2,005 |
| |
| Registered: March 13, 2007 | Reputation:  | | Posts: 2,216 |
| | Posted: | | | | Quoting TomGaines: Quote:
I just tried to parse the new XML export file with MSXML and get this error: Me too! It's seems to affect only studios, everythink else looks fine on first glance. As soon as I throw all Studios away [1] xsltproc parses the file without further trouble. cya, Mithi [1] grep -v '<Studio>' collection.xml > collection-new.xml | | | | Mithi's little XSLT tinkering - the power of XML --- DVD-Profiler Mini-Wiki |
|
| Registered: March 13, 2007 | | Reputation: | | Posts: 2,005 |
| | Posted: | | | | Yes, as far as I can tell, it only affects studios. I had about 30 studios to fix (24 of those were A&E  ). Now I do not have any parsing errors. | | | 
 |
|
| Registered: March 10, 2007 |  Posts: 4,282 |
| | Posted: | | | | It seems a fix to a late-breaking bug has broken encoding of some fields.
I plan to put out a 3.0.1 very soon, with the first beta in about a week. | | | | Invelos Software, Inc. Representative |
|
| Registered: March 13, 2007 | | Reputation: | | Posts: 2,005 |
| |
| Registered: March 13, 2007 | | Reputation: | | Posts: 2,005 |
| |
| Registered: March 13, 2007 | | Reputation: | | Posts: 2,005 |
| |
| Registered: March 14, 2007 | | Reputation: | | Posts: 1,029 |
| | Posted: | | | | The new comment field for "Watched" events is not exported. | | | | Matthias |
|
| Registered: March 13, 2007 |  Posts: 350 |
| | Posted: | | | | In DVDP 2.x, the overview field had all non-printable characters (including CR and LF) encoded as &#xxx;
In DVDP 3.0, the non-printables are left as 8-bit characters. I'm just wondering if this is intentional (it definitely screws up the XML parser that I'm using, but I'm not enough of an XML guru to know if there is a right and a wrong here; it could simply be two different ways of doing things (that would be my guess) | | | | -fred |
|
| Registered: March 14, 2007 | | Reputation: | | Posts: 1,029 |
| | Posted: | | | | Usually, you tell the parser how it should handle whitespace in certain tags (preserve, collapse, replace). | | | | Matthias | | | | Last edited: by goodguy |
|
| Registered: March 14, 2007 | | Reputation: | | Posts: 1,029 |
| | Posted: | | | | Also not exported: FeatureOther from the Features group. | | | | Matthias |
|
| Registered: March 14, 2007 | | Reputation: | | Posts: 1,029 |
| | Posted: | | | | More missing fields, from the Discs/Disc group:
LabelSideA
LabelSideB
DualSided (may have been dropped due to DescriptionSideA/B)
Flipper (may have been dropped since it doesn't appear in the UI either) | | | | Matthias |
|
| Registered: March 13, 2007 | | Reputation: | | Posts: 2,216 |
| | Posted: | | | | Quoting FredLooks: Quote:
(it definitely screws up the XML parser that I'm using, It shouldn't, the XML is correctly[1] marked as <?xml version="1.0" encoding="windows-1252"?> cya, Mithi [1] Well, apart from the & in Studios of course  | | | | Mithi's little XSLT tinkering - the power of XML --- DVD-Profiler Mini-Wiki |
|
| Registered: March 13, 2007 | | Posts: 350 |
| | Posted: | | | | Quoting Mithi: Quote:
Quoting FredLooks:
Quote:
(it definitely screws up the XML parser that I'm using,
It shouldn't, the XML is correctly[1] marked as
<?xml version="1.0" encoding="windows-1252"?>
cya, Mithi
[1] Well, apart from the & in Studios of course Correct, of course. I should have said that it definitely screws up the parsing methodology that I'm using  XML_OPTION_SKIP_WHITE in the php parser elides the newlines. Now if I could easily determine why the parser is un-encoding the xml primitives (< etc.) then I'd understand how the parsing is working (I think  ) | | | | -fred |
|