You can subscribe to this list here.
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2008 |
Jan
(5) |
Feb
(13) |
Mar
(7) |
Apr
(23) |
May
(1) |
Jun
(1) |
Jul
(10) |
Aug
(2) |
Sep
(6) |
Oct
(6) |
Nov
|
Dec
(7) |
2009 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
(6) |
May
(8) |
Jun
|
Jul
(5) |
Aug
(5) |
Sep
(2) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
2010 |
Jan
(12) |
Feb
(5) |
Mar
|
Apr
(4) |
May
(22) |
Jun
(3) |
Jul
(1) |
Aug
(3) |
Sep
(3) |
Oct
(1) |
Nov
(1) |
Dec
(2) |
2011 |
Jan
(10) |
Feb
|
Mar
(4) |
Apr
(2) |
May
|
Jun
(2) |
Jul
|
Aug
(3) |
Sep
(1) |
Oct
|
Nov
|
Dec
(3) |
2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(2) |
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Andy C. <an...@cy...> - 2008-01-22 02:49:17
|
siegfried wrote: > Thanks! What about the encoding argument? Can I specify null for the > systemid, publicid, and basesystemid and encoding? You should be able to leave the rest of them null, if you like. And the encoding is only necessary if 1) you are using an input stream instead of a reader; and 2) if you don't want the parser to auto-detect the character set. P.S. If you'd like to ask more questions, please join the mailing list. Because only members are allowed to post to the list, I have to personally approve every message from a non-member. |
From: siegfried <sie...@he...> - 2008-01-22 00:48:53
|
Andy, Thanks! What about the encoding argument? Can I specify null for the systemid, publicid, and basesystemid and encoding? Siegfried -----Original Message----- From: Andy Clark [mailto:an...@cy...] Sent: Monday, January 21, 2008 5:28 PM To: sie...@he... Cc: nek...@li... Subject: Re: [nekohtml-user] Wanted: Example to read from string instead of file sie...@he... wrote: > Can someone give me an example of parsing the contents of a string > instead of reading from a file? You need to wrap the string in a java.io.StringReader and then pass that into the XMLInputStream's constructor. This is the same as if you were parsing XML documents with Xerces. The publicId and systemId are only important for XML parsing when the parser needs to load an external entity. -AndyC |
From: Andy C. <an...@cy...> - 2008-01-22 00:27:56
|
sie...@he... wrote: > Can someone give me an example of parsing the contents of a string > instead of reading from a file? You need to wrap the string in a java.io.StringReader and then pass that into the XMLInputStream's constructor. This is the same as if you were parsing XML documents with Xerces. The publicId and systemId are only important for XML parsing when the parser needs to load an external entity. -AndyC |
From: <sie...@he...> - 2008-01-21 22:40:26
|
Can someone give me an example of parsing the contents of a string instead of reading from a file? I've studied the source code for neko and xerces and I cannot figure out how to create pass an input stream to the DOMParser.parse function. Apparently I can pass an XMLInputStream but the XMLInputStream constructor requires 5 constructor arguements to specify the publicid, systemid, basesystemid and encoding. What the heck do I pass as these values? Anyway, my attempts don't work: Neko complains that <HTML> is not a valid protocol (apparently it is looking for a URL). Thanks, Siegfried |
From: Stephen M. <ste...@gm...> - 2007-12-26 19:42:20
|
I am trying to remove the tag <HEAD> </HEAD> from an HTML fragment. I tried: org.cyberneko.html.filters.ElementRemover er = new org.cyberneko.html.filters.ElementRemover(); er.removeElement( "head" ); org.apache.xerces.xni.parser.XMLDocumentFilter[] filters = { er }; parser.setProperty( "http://cyberneko.org/html/properties/filters", filters ); But this seems to remove everything. Is there anyway to say accept everything except <HEAD> ? -Thanks Steve More |
From: Ahmed A. <asa...@ya...> - 2007-12-17 15:02:30
|
Dear all, Thanks a lot for reviving NekoHTML. Some cases encountered in HtmlUnit were related to parsing something like "hello there</div>", or "<a", " href=url". This happens when the end user use javascript 'document.write()', for instance: <script> document.write("<div>"); document.write("hello there</div>"); </script> I believe the solution is either to: 1- Allow injecting any string at end of 'body' by having method like parser.appendToBody(string) 2- Or parsing incomplete HTML. What do you think? Ahmed Ashour ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ |
From: Andy C. <an...@cy...> - 2007-12-15 03:17:21
|
After acouple years of inactivity, NekoHTML users wrote me to inquire about the future of the project. Thanks to their persistence, NekoHTML now has a new home and a new release! There are some major organizational changes in the new release. First and foremost, I moved the development to SourceForge and changed the license to a pure Apache 2.0 license. Another important change is the updated version number. The new version marks the fresh start at SourceForge and indicates that the project is mature and stable. In addition, the implementation was updated to be compatible with the newest version of Xerces and the latest XNI API changes. And a number of outstanding bugs were fixed. The only change that could affect users is that the minimum Java version required to run NekoHTML was increased to Java 1.3. If this causes any problems for existing users, please let us know by posting to the Users mailing list. The email address is included at the end of this message. The move to SourceForge gives the project a lot of things that were missing before including a publicly available source control system, bug tracking, mailing lists, release management, and more! In addition, I am opening up the development to more contributors to make sure that the project has a long, prosperous future. Here are some important links: Docs - http://nekohtml.sourceforge.net/ Project - http://sourceforge.net/projects/nekohtml Mail - nek...@li... Enjoy! P.S. Sorry for spamming a bunch of the Apache lists but it's been a loooong time since the last release and wanted to reach as many people as possible. -- Andy Clark - an...@cy... |
From: Andy C. <an...@cy...> - 2007-05-23 07:45:03
|
This has been a long time coming. I had hoped that the NekoHTML parser would find a home as part of the Xerces-J project at Apache. But I was looking for an adoption and they didn't want anything thrown over the wall, so to speak. So I have *finally* been pushed into creating a SourceForge project[1] by numerous users of the code. The great thing about having the project hosted at SourceForge is that we get real source control, mailing lists, issue tracking, and perhaps most importantly, I have a way to allow others to hack on the code and help me out as it continues to evolve. So far I have done the following: * Imported the source code Now all versions of the source, from release 0.1 through 0.9.5 has been checked into Subversion (SVN). The current codebase is checked in under trunk[2], and all of the releases are found in the branches[3] directory. You can browse the SVN repository[4] to see how it is setup. * Created the mailing lists We have two mailing lists[5], nekohtml-user and nekohtml-developer. The user mailing list is for questions, comments, and general usage discussions. Whereas the developer mailing list is for design and development discussions. The latter is where we will talk about design changes, releases, etc. Even though I've made a good start on the project, there is still a lot of work to do. Here is a list of the things still left to do: * Import release packages I want to upload the download packages for all of the version of NekoHTML. This is a good idea for archiving purposes as well as allowing people to get the latest version while we are working on a new release. * Update license Currently, the code is released under an Apache-style license. In other words, I took the Apache V1 license and changed "Apache" to "CyberNeko". I understand that this has caused people some problems in integrating the parser with their code due to company restrictions. So I want to change the license to vanilla Apache V2[6]. * Change directory structure Previously, the NekoHTML parser was part of a larger development project that I called the "CyberNeko Tools for XNI". As such, I had organized the directories so as to keep the source separate. For example, there was a src/dtd/ directory, a src/html/ directory, etc. Now that NekoHTML is a full-fledged project of its own, I want to clean this up and go back to just src/ as the root of the source code tree. Similar changes will be needed in other directories. * Update build script Aside from the changes required by changing the dir structure, I want to update the build script to take advantage of changes in Ant since the time I started the project; and also to follow standard Java project conventions. For example, building into build/ instead of bin/, etc. There are probably more things to be done but that's a good enough list for the moment. Anyway, welcome to the project! Links: [1] http://sourceforge.net/projects/nekohtml/ [2] https://nekohtml.svn.sourceforge.net/svnroot/nekohtml/trunk [3] https://nekohtml.svn.sourceforge.net/svnroot/nekohtml/branches [4] http://nekohtml.svn.sourceforge.net/viewvc/nekohtml/ [5] http://sourceforge.net/mail/?group_id=195122 [6] http://apache.org/licenses/LICENSE-2.0 -- Andy Clark - an...@cy... |