Thread: [Htmlparser-user] Lexer differences between 1.4 and 1.6
Brought to you by:
derrickoswald
From: Vincent M. <vm...@gm...> - 2006-03-01 00:47:06
|
Hello, I have some code that uses htmlparser 1.4 and I am looking at upgrading it to the latest 1.6 integration build. However, I am seeing differences in the way the input is processed that make the work more difficult. Given the input (note it's missing a quote): Hello <a href=3D"http://www.foo.com>World</a> With htmlparser 1.4, I get the following nodes: Text: Hello Begin tag: a href=3D"http://www.foo.com" Text: World End tag: a With htmlparser 1.6, I get these: Text: Hello LinkTag: link to http://www.foo.com>link</a> The 1.6 behavior makes error recovery a lot more difficult. Is there a way to have 1.6 behave like 1.4 in this case? Thanks for your help, Vince. |
From: Derrick O. <Der...@Ro...> - 2006-03-01 01:58:44
|
No, sorry, there is no 'backwards compatibility' switch. Vincent Mallet wrote: >Hello, > >I have some code that uses htmlparser 1.4 and I am looking at >upgrading it to the latest 1.6 integration build. However, I am seeing >differences in the way the input is processed that make the work more >difficult. > >Given the input (note it's missing a quote): >Hello <a href="http://www.foo.com>World</a> > >With htmlparser 1.4, I get the following nodes: >Text: Hello >Begin tag: a href="http://www.foo.com" >Text: World >End tag: a > >With htmlparser 1.6, I get these: >Text: Hello >LinkTag: link to http://www.foo.com>link</a> > >The 1.6 behavior makes error recovery a lot more difficult. Is there a >way to have 1.6 behave like 1.4 in this case? > >Thanks for your help, > > Vince. > > > > |
From: Vincent M. <vm...@gm...> - 2006-03-01 17:34:51
|
Thanks Derrick. Are "changes.txt" and "release.txt" all the documents about the evolution o= f htmlparser between 1.4 and 1.5/1.6, or is there something else that would talk about changes in concepts and design between the different releases? Thanks, Vince. On 2/28/06, Derrick Oswald <Der...@ro...> wrote: > > > No, sorry, there is no 'backwards compatibility' switch. > > Vincent Mallet wrote: > > >Hello, > > > >I have some code that uses htmlparser 1.4 and I am looking at > >upgrading it to the latest 1.6 integration build. However, I am seeing > >differences in the way the input is processed that make the work more > >difficult. > > > >Given the input (note it's missing a quote): > >Hello <a href=3D"http://www.foo.com>World</a> > > > >With htmlparser 1.4, I get the following nodes: > >Text: Hello > >Begin tag: a href=3D"http://www.foo.com" > >Text: World > >End tag: a > > > >With htmlparser 1.6, I get these: > >Text: Hello > >LinkTag: link to http://www.foo.com>link</a> > > > >The 1.6 behavior makes error recovery a lot more difficult. Is there a > >way to have 1.6 behave like 1.4 in this case? > > > >Thanks for your help, > > > > Vince. > > > > > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > that extends applications into web and mobile media. Attend the live > webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat= =3D121642 > _______________________________________________ > Htmlparser-user mailing list > Htm...@li... > https://lists.sourceforge.net/lists/listinfo/htmlparser-user > |
From: Derrick O. <Der...@Ro...> - 2006-03-02 02:35:59
|
Those are the primary resources. Mostly it's the Javadocs, for example there's a good summary piece of the most major difference (underlying lexer) in the lexer package: http://htmlparser.sourceforge.net/javadoc/org/htmlparser/lexer/package-summary.html Vincent Mallet wrote: > Thanks Derrick. > > Are "changes.txt" and "release.txt" all the documents about the > evolution of htmlparser between 1.4 and 1.5/1.6, or is there something > else that would talk about changes in concepts and design between the > different releases? > > Thanks, > > Vince. > > On 2/28/06, *Derrick Oswald* <Der...@ro... > <mailto:Der...@ro...>> wrote: > > > No, sorry, there is no 'backwards compatibility' switch. > > Vincent Mallet wrote: > > >Hello, > > > >I have some code that uses htmlparser 1.4 and I am looking at > >upgrading it to the latest 1.6 integration build. However, I am > seeing > >differences in the way the input is processed that make the work > more > >difficult. > > > >Given the input (note it's missing a quote): > >Hello <a href="http://www.foo.com>World</a> > > > >With htmlparser 1.4, I get the following nodes: > >Text: Hello > >Begin tag: a href="http://www.foo.com" > >Text: World > >End tag: a > > > >With htmlparser 1.6, I get these: > >Text: Hello > >LinkTag: link to http://www.foo.com>link</a> > > > >The 1.6 behavior makes error recovery a lot more difficult. Is > there a > >way to have 1.6 behave like 1.4 in this case? > > > >Thanks for your help, > > > > Vince. > |