Re: [xmltv-users] Parser crash today

[Robert E. <rm...@ya...>]

Yea --dropbadchar removes unencoded high-ASCII.  The problem today is
with & and bad & codes in the data.  No easy way to separate out the
bad/good from the data.

It's been reported to Tribune and I think they fixed it already.

Robert

--- steve childress <st...@sa...> wrote:

> Same error with --dropbadchar
>   _____  
> 
> From: xml...@li...
> [mailto:xml...@li...] On Behalf Of steve
> childress
> Sent: Sunday, September 09, 2007 10:37 AM
> To: xml...@li...
> Subject: [xmltv-users] Parser crash today
> 
>  
> 
> NO DATA FOR ME - worked OK since day one, I made no changes. Perl
> parser
> Error is data dependent:
> 
>  
> 
> using config filename ./.xmltv/tv_grab_na_dd.conf
> 
> Fetching from Schedules Direct     Fetched 3014 k/bytes in 8 seconds
> 
> loading data: #######################
> 
> WARNING: error parsing DD xml:
> 
> not well-formed (invalid token) at line 40397, column 28, byte
> 1459810 at
> /PerlApp/XML/Parser.pm line 187
> 
>  
> 
>  
> 
> ERROR: Bad XML from DD, cannot continue. Consider using --dropbadchar
> or
> Capture
> 
>  xml with --dd-data
> 
>  
> 
> ----------
> 
> Provider: Time Warner analog cable, zip code 92130
> 
>  
> 
> >
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/>
_______________________________________________
> xmltv-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmltv-users
> 



       
____________________________________________________________________________________
Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. 
http://answers.yahoo.com/dir/?link=list&sid=396545433