Re: parser error

2017-12-12 Thread Ralph Corderoy
Hi Graham, > ERROR: Failed to load subtitles: > :7: parser error : Char 0x0 out of allowed range ... > It is still a small % but frequent enough to be annoying if you rely > on subtitles to fully follow the speech. I haven't tried this, and I'm looking at 3.06 rather than 3.07, but if you find t

RE: parser error

2017-12-12 Thread Graham Temple Personal
Of RS Sent: 10 November 2017 11:44 To: get_iplayer@lists.infradead.org Subject: Re: parser error From: Vangelis forthnet Sent: Friday, November 3, 2017 6:59 PM >by opening >http://www.bbc.co.uk/iplayer/subtitles/ng/modav/bUnknown-5df25dc8-d38f- >43e5-93a2-38b6c778f852_b09c79wx_15096254

RE: parser error

2017-12-12 Thread Graham Temple Personal
: 10 November 2017 11:44 To: get_iplayer@lists.infradead.org Subject: Re: parser error From: Vangelis forthnet Sent: Friday, November 3, 2017 6:59 PM >by opening >http://www.bbc.co.uk/iplayer/subtitles/ng/modav/bUnknown-5df25dc8-d38f- >43e5-93a2-38b6c778f852_b09c79wx_1509625417009.xml

Re: parser error

2017-11-10 Thread RS
From: Vangelis forthnet Sent: Friday, November 3, 2017 6:59 PM by opening http://www.bbc.co.uk/iplayer/subtitles/ng/modav/bUnknown-5df25dc8-d38f-43e5-93a2-38b6c778f852_b09c79wx_1509625417009.xml one can read: Created on 2/11/2017 at 12:23:23 so this was just fixed at noon yesterday (most r

Re: parser error

2017-11-03 Thread Vangelis forthnet
On Fri Nov 3 12:19:35 GMT 2017, RS wrote: but is seems more likely that the BBC would respond to something causing an error in the iPlayer. The BBC does correct errors. Hi Richard :-) by opening http://www.bbc.co.uk/iplayer/subtitles/ng/modav/bUnknown-5df25dc8-d38f-43e5-93a2-38b6c778f852_b09c

Re: parser error

2017-11-03 Thread RS
From: Ralph Corderoy Sent: Friday, November 3, 2017 12:50 PM Don't use Firefox to view XML. XML is plain text. Download it to a file and then use a text editor to view it. Firefox is trying to be helpful, but fails. Hi Ralph Sorry, yes. I have confused myself by looking at one in Brackets

Re: parser error

2017-11-03 Thread Ralph Corderoy
Hi Richard, > http://www.bbc.co.uk/iplayer/subtitles/ng/modav/bUnknown-5df25dc8-d38f-43e5-93a2-38b6c778f852_b09c79wx_1509625417009.xml ... > I may be slightly wrong about that. The problem subtitles file began > That's fine. https://www.w3.org/TR/xml/#NT-XMLDecl > - > where - is a dash charac

Re: parser error

2017-11-03 Thread RS
From: Vangelis forthnet Sent: Friday, November 3, 2017 1:41 AM On Fri Oct 27 22:16:03 BST 2017, Ralph Corderoy wrote: If the BBC haven't already been informed that a particular URL serves broken XML then that's the first thing to change, including pointing out the NUL bytes that are causing

Re: parser error

2017-11-02 Thread Vangelis forthnet
On Fri Oct 27 22:16:03 BST 2017, Ralph Corderoy wrote: If the BBC haven't already been informed that a particular URL serves broken XML then that's the first thing to change, including pointing out the NUL bytes that are causing the problem. I'm sure they'd like to work out what went wrong, and

Re: parser error

2017-10-28 Thread Bernard Peek
On 27/10/2017 21:47, RS wrote: On 27/10/2017 19:06, Bernard Peek wrote: It is then up to the calling script (get_iplayer.pl) to decide what action to take in response the action taken by the parser. It is not adequate just to allow XML::LibXML to display "parser error" and take no further ac

Re: parser error

2017-10-28 Thread Jeremy Nicoll - ml gip
On 2017-10-27 21:47, RS wrote: If you are both right about the strictness of the standard, and I have to defer to your superior knowledge, why does XML::LibXML have options for recovery and validation? According to http://search.cpan.org/dist/XML-LibXML/lib/XML/LibXML/Parser.pod#PARSER_OPTIONS a

Re: parser error

2017-10-27 Thread Ralph Corderoy
Hi Richard, > As I shall be saying in another reply, I suspect it may be possible to > configure XML::LibXML to be more error tolerant. get_iplayer should fail hard if the XML parser it uses complains as there's no good reason for it to expect poor XML and to recover from errors. If the BBC hav

Re: parser error

2017-10-27 Thread RS
On 27/10/2017 19:06, Bernard Peek wrote: It is then up to the calling script (get_iplayer.pl) to decide what action to take in response the action taken by the parser.  It is not adequate just to allow XML::LibXML to display "parser error" and take no further action. Even though that's what t

Re: parser error

2017-10-27 Thread RS
On 27/10/2017 16:31, Vangelis forthnet wrote: so if you find programmes whose subtitles can't be processed with the new implementation, report them in the forums. I suspect it's now too late, since the "new" implementation has been the only one since 3.02+, but I suspect it wouldn't hurt to le

Re: parser error

2017-10-27 Thread Alex
I think the real issue is not to fix gIp ('cos it ain't broke), or break gIp (to introduce a workaround for non-standard data), but to get the BBC to fix their subtitles. If the poor subs feed can be shown to cause issues with iPlayer, then the BBC should fix them (I can't say that they are obliga

Re: parser error

2017-10-27 Thread Bernard Peek
It is then up to the calling script (get_iplayer.pl) to decide what action to take in response the action taken by the parser.  It is not adequate just to allow XML::LibXML to display "parser error" and take no further action. Even though that's what the XML standard says IS the correct ac

Re: parser error

2017-10-27 Thread Vangelis forthnet
On Thu Oct 26 00:51:15 BST 2017, RS wrote: I have received an email from someone who told me the Suspicion subtitles download fine on his XP installation with v3.01. When I use v3.01 I still get the problem. He also mentioned that there was something in the v3.01 release notes about changes to s

Re: parser error

2017-10-27 Thread Jeremy Nicoll - ml gip
On 2017-10-27 11:33, RS wrote: On 26/10/2017 01:27, Jeremy Nicoll - ml gip wrote: On 2017-10-26 00:51, RS wrote: The corruption he refers to is a few spurious NUL characters in .  The subtitles themselves are in and they are intact. But you're a human looking at the file.  XML files have

Re: parser error

2017-10-27 Thread RS
On 26/10/2017 01:27, Jeremy Nicoll - ml gip wrote: On 2017-10-26 00:51, RS wrote: The corruption he refers to is a few spurious NUL characters in .  The subtitles themselves are in and they are intact. But you're a human looking at the file.  XML files have a tightly defined syntax (defined

Re: parser error

2017-10-25 Thread Jeremy Nicoll - ml gip
On 2017-10-26 00:51, RS wrote: The corruption he refers to is a few spurious NUL characters in . The subtitles themselves are in and they are intact. But you're a human looking at the file. XML files have a tightly defined syntax (defined by a formal grammar called a DTD). When a program

Re: parser error

2017-10-25 Thread RS
From: Vangelis forthnet Sent: Wednesday, October 25, 2017 6:14 AM On Tue Oct 24 20:35:11 BST 2017, RS wrote: The resultant .mp4 file can be played in VLC, but MediaInfo shows no metadata. Hello Vangelis Many thanks for a very thorough explanation. If you ended up, for whatever reason, wi

Re: parser error

2017-10-24 Thread Vangelis forthnet
On Tue Oct 24 20:35:11 BST 2017, RS wrote: The resultant .mp4 file can be played in VLC, but MediaInfo shows no metadata. Hello Richard :-) If you ended up, for whatever reason, with an untagged file, you can always (re-)tag post download with the --tag-only switch: get_iplayer --type=video -

Re: parser error

2017-10-24 Thread RS
From: Jeremy Nicoll - ml gip Sent: Tuesday, October 24, 2017 8:54 PM The problem doesn't lie with g_ip, but with a corrupted(?) file on the bbc server. This is the first time I have seen this error, so it must be rare. For that reason it is not worth bothering with. If it happened more ofte

Re: parser error

2017-10-24 Thread RS
From: Colin Law Sent: Tuesday, October 24, 2017 8:44 PM If you download the xml file the error refers to and look at it, it can be seen that there are lots of null characters (hence the error Char 0x0 out of range). The file is corrupt. Thanks for the explanation. I'm glad I asked because I h

Re: parser error

2017-10-24 Thread Colin Law
If you download the xml file the error refers to and look at it, it can be seen that there are lots of null characters (hence the error Char 0x0 out of range). The file is corrupt. Colin On 24 October 2017 at 20:35, RS wrote: > Does anyone have any idea what causes a parser error? I thought at