I think i found solution suitable for me. I would wrap all broken texts in CDATA sections, it works perfectly.
Thanks for help On Fri, Jun 04, 2010 at 02:05:58PM -0400, Chas. Owens wrote: > On Fri, Jun 4, 2010 at 13:30, Roman Makurin <dro...@gmail.com> wrote: > > I used mostly the same things, but without uri_(un)escape it doesnt work. > > If i clearly understant, in order to parse feed i need apply escape > > methods to broken elements, am i right ? > snip > > How you fix each section that is broken is dependent on how that > section is broken. One thing that may be tripping you up is that some > XML parsers can't handle UTF-8. Can you tell us what error messages > you are getting after the substitution I suggested? > > snip > > i there any module with magic function like fixBrokenXML() ? > snip > > How would such a function work? How would it be able to tell bad XML > like "&" from a URL that hasen't been properly escaped like > "http://foo.com?x=1&=4";? In one case it would need to add a > semi-colon and in the other it would need to say > "http://foo.com?x=1&amp=4";, > "http%3A%2F%2Ffoo.com%3Fx%3D1%26amp%3D4", or something similar. > > -- > Chas. Owens > wonkden.net > The most important skill a programmer can have is the ability to read. -- If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby Digital and all the music is free...
pgpxy9ne2kpl3.pgp
Description: PGP signature
