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
Mb/s (hvfxsd1) [audio+video]
INFO: Converting to MP4
INFO: Tagging MP4
INFO: Downloading subtitles
ERROR: Failed to load subtitles:
:7: parser error : Char 0x0 out of allowed range
LEAGUE OF GENTLEMEN 4 - BD313601
^
:7: parser error : Premature end
xsd1) [audio+video]
INFO: Converting to MP4
INFO: Tagging MP4
INFO: Downloading subtitles
ERROR: Failed to load subtitles:
:7: parser error : Char 0x0 out of allowed range
LEAGUE OF GENTLEMEN 4 - BD313601
^
:7: parser error : Premature end of data in tag t
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
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
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
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
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
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
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
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
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
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 t
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
n 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 action?
>>
>
> PMFJI
>
> I built
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
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
ormed or maybe only a little
badly-formed XML document.
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.
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. My knowledge of Perl is not sufficient to understand
how get_iplayer.pl interacts with XML::LibXML.
I said t
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
in v3.05
because --subsfmt has been removed.
...
Does anyone have any idea what causes a parser error?
Answered by Colin; some further analysis below...
The corruption he refers to is a few spurious NUL characters in
. The subtitles themselves are in and they are
intact.
On Tue Oc
=> vpid=b09c79wx (needed later...)
Does anyone have any idea what causes a parser error?
Answered by Colin; some further analysis below...
On Tue Oct 24 21:41:54 BST 2017, RS wrote:
I'm glad I asked because I hadn't realised
that was where subtitles came from.
I had assumed there w
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
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
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
Does anyone have any idea what causes a parser error? I thought at first
that it was an AtomicParsley error, but the --verbose output seems to
indicate it didn't get that far. The programme is the editorial version of
the 1941 Hitchcock film Suspicion, b00gmlrx, from hlshd1
26 matches
Mail list logo
