Menu
▾
▴
jtidy-devel — JTidy mailing list for developers
You can subscribe to this list here.
| 2004 |
Jan
(29) |
Feb
(1) |
Mar
(6) |
Apr
(31) |
May
(2) |
Jun
(2) |
Jul
(13) |
Aug
(31) |
Sep
(41) |
Oct
(12) |
Nov
(13) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(17) |
Feb
(3) |
Mar
(3) |
Apr
|
May
(1) |
Jun
(2) |
Jul
(1) |
Aug
(3) |
Sep
(3) |
Oct
(1) |
Nov
(2) |
Dec
(6) |
| 2006 |
Jan
(4) |
Feb
(6) |
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
(21) |
Aug
(7) |
Sep
(5) |
Oct
(4) |
Nov
(2) |
Dec
(2) |
| 2007 |
Jan
(1) |
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
(1) |
Aug
(2) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
(1) |
| 2008 |
Jan
(1) |
Feb
(1) |
Mar
(7) |
Apr
(2) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(2) |
Dec
(8) |
| 2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(2) |
Jul
(5) |
Aug
(24) |
Sep
(16) |
Oct
(8) |
Nov
(42) |
Dec
(3) |
| 2010 |
Jan
(8) |
Feb
(8) |
Mar
(14) |
Apr
(29) |
May
(2) |
Jun
(1) |
Jul
(11) |
Aug
(47) |
Sep
(4) |
Oct
(16) |
Nov
(18) |
Dec
|
| 2011 |
Jan
(5) |
Feb
(4) |
Mar
(2) |
Apr
|
May
|
Jun
(10) |
Jul
(50) |
Aug
(4) |
Sep
(4) |
Oct
(1) |
Nov
(4) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(8) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: boxed <bo...@ki...> - 2004-08-18 20:11:22
|
I get the "DOM method not supported" error on normalize() in JTidyTask, and if I comment that out I get it when trying to serialize. I use java5 and I'm wondering if this might have something to do with it. I saw in the forum on sf.net that I am not the only one with this issue... I'm working on a change to the Ant task to support fileset so you can tidy multiple files in one go, but this issue has stopped my progress. I believe my change is complete but I can't test it. -- Anders Hovmöller Research & Development bo...@ki... / soft.killingar.net SK Soft |
|
From: SourceForge.net <no...@so...> - 2004-08-18 16:24:59
|
Bugs item #1011557, was opened at 2004-08-18 09:24 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=1011557&group_id=13153 Category: Tidy functionality Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Ant task throws NPE if you don't set "log" attribute Initial Comment: java.lang.NullPointerException at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.<init>(FileOutputStream.java:176) at java.io.FileOutputStream.<init>(FileOutputStream.java:70) at java.io.FileWriter.<init>(FileWriter.java:46) at org.w3c.tidy.ant.JTidyTask.execute(JTidyTask.java:188) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193) at org.apache.tools.ant.Task.perform(Task.java:341) at org.apache.tools.ant.Target.execute(Target.java:309) at org.apache.tools.ant.Target.performTasks(Target.java:336) at org.apache.tools.ant.Project.executeTarget(Project.java:1339) at org.apache.tools.ant.Project.executeTargets(Project.java:1255) at org.apache.tools.ant.Main.runBuild(Main.java:609) at org.apache.tools.ant.Main.start(Main.java:196) at org.apache.tools.ant.Main.main(Main.java:235) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=1011557&group_id=13153 |
|
From: Fabrizio G. <fg...@gm...> - 2004-08-17 22:53:00
|
thanks for the patches, Pablo. I just committed your fixes in cvs. I also recently committed a fix from the c version of tidy for the duplicate attribute bug (it also allows to join "style" and "class" attributes instead of dropping duplicates). Xml output should now be a lot more stable, you can try it in a rc8 nightly build. Any other patch and bugfix is welcome, I recommend you to use the sourceforge bugtracker to submit them, instead of posting to the mailing list, and if possible also add a junit testcase which shows what the patch does (this takes only a few minutes, since you will simply need to provide an input, expected output, and configuration files - see http://cvs.sourceforge.net/viewcvs.py/jtidy/jtidy2/src/test/org/w3c/tidy/JTidyBugsTest.java?view=markup as an example). fabrizio On Thu, 12 Aug 2004 12:47:25 -0400, Mayrgundter, Pablo <pma...@do...> wrote: > > Here's a similar fix that drops invalid numeric entities from XML mode (entities that map to invalid XML chars): > |
|
From: Mayrgundter, P. <pma...@do...> - 2004-08-12 16:50:29
|
Here's a similar fix that drops invalid numeric entities from XML mode =
(entities that map to invalid XML chars):
if ((this.configuration.xmlOut || this.configuration.xHTML)
&& !((ch >=3D 0x20 && ch <=3D0xD7FF) // Check the =
common-case first. =
=20
|| ch =3D=3D 0x9 || ch =3D=3D 0xA || ch =3D=3D 0xD // =
Then white-space. =
=20
|| (ch >=3D 0xE000 && ch <=3D0xFFFD))) {
this.lexsize =3D start;
return;
}
This should be inserted into Lexer.parseEntity(short), right after:
str =3D getString(this.lexbuf, start, this.lexsize - start);
ch =3D EntityTable.getDefaultEntityTable().entityCode(str);
Using both of these fixes and the duplicate attribute fix I posted =
earlier on this list, I'm getting fairly robust conversion to XHTML.
Cheers,
Pablo
-----Original Message-----
From: jti...@li... on behalf of Mayrgundter, =
Pablo
Sent: Thu 8/12/2004 12:20 PM
To: jti...@li...
Subject: RE: [Jtidy-devel] Tidying doc with null char to XHTML outputs =
invalid XML entity.
=20
Here's my fix:
// Allow only valid XML characters. See:
// http://www.w3.org/TR/2004/REC-xml-20040204/#NT-Char
if ((this.configuration.xmlOut || this.configuration.xHTML)
&& !((c >=3D 0x20 && c <=3D0xD7FF) // Check the common-case =
first.
|| c =3D=3D 0x9 || c =3D=3D 0xA || c =3D=3D 0xD // Then =
white-space.
|| (c >=3D 0xE000 && c <=3D0xFFFD) // Then high-range =
unicode.
|| (c >=3D 0x10000 && c <=3D0x10FFFF))) {
return; =
=
=20
}
Not sure where best to put this. I've got it as the first statement in =
Lexer.addCharToLexer(int) currently.
|
|
From: Mayrgundter, P. <pma...@do...> - 2004-08-12 16:22:03
|
Here's my fix:
// Allow only valid XML characters. See:
// http://www.w3.org/TR/2004/REC-xml-20040204/#NT-Char
if ((this.configuration.xmlOut || this.configuration.xHTML)
&& !((c >=3D 0x20 && c <=3D0xD7FF) // Check the common-case =
first.
|| c =3D=3D 0x9 || c =3D=3D 0xA || c =3D=3D 0xD // Then =
white-space.
|| (c >=3D 0xE000 && c <=3D0xFFFD) // Then high-range =
unicode.
|| (c >=3D 0x10000 && c <=3D0x10FFFF))) {
return; =
=
=20
}
Not sure where best to put this. I've got it as the first statement in =
Lexer.addCharToLexer(int) currently.
|
|
From: Mayrgundter, P. <pma...@do...> - 2004-08-12 13:47:41
|
Hi again, Looks like my last message was munged (at least for me) when I tried to = include the #0 entity. Anyways, JTidy converts a null char in source HTML to an invalid XML = entity on output, thus breaking the XHTML and XML output modes for = documents with that char. In fact, many control characters shouldn't be = allowed into output XML documents. Here's my planned fix. If in XML or XHTML output mode, allow only valid = XML characters through the Lexing stage, and drop everything else. The = valid ranges for XML chars is: Char ::=3D #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | = [#x10000-#x10FFFF] (see: http://www.w3.org/TR/2004/REC-xml-20040204/#NT-Char) XML entities follow the same rule; they can only represent chars in this = range. Since invalid XML chars don't really have any purpose in well-formed XML = and were probably included in the source document as a mistake (e.g. the = null char), dropping them seems fine. I'll be preparing the patch soon and will make it available on this = list. Cheers, Pablo Mayrgundter |
|
From: Mayrgundter, P. <pma...@do...> - 2004-08-11 22:37:15
|
Using jtidy-r8-SNAPSHOT I get a bug when tidying an HTML doc with a null = char. JTidy turns it into a numeric entity, namely=20 |
|
From: Fabrizio G. <fg...@gm...> - 2004-07-26 19:27:35
|
thanks for the contribution, Pablo
the duplicate attribute bug is the most important I'm planning to fix
before the next release: I'm actually trying to follow the
implementation from the c version of tidy, since it also allows to
join attributes (when possible) instead of aways dropping them.
fabrizio
----- Original Message -----
From: Mayrgundter, Pablo <pma...@do...>
Date: Mon, 26 Jul 2004 12:08:08 -0400
Subject: [Jtidy-devel] Fix for the duplicate attribute bug
To: jti...@li...
In org/w3c/tidy/PPrint.java
Rename the existing printAttrs method to "printAttrsReal", and
change its body to refer to this new name in the recursive call:
if (attr.next != null)
{
// Was printAttrs(...)
printAttrsReal(fout, indent, node, attr.next);
}
And then add this method:
private void printAttrs(Out fout, int indent, Node node, AttVal attr) {
if (this.configuration.dropDuplicateAttributes) {
final java.util.Map attrMap = new java.util.HashMap();
while (attr != null) {
attrMap.put(attr.attribute.toLowerCase(), attr);
attr = attr.next;
}
final java.util.Iterator attrItr = attrMap.values().iterator();
AttVal last = null;
while (attrItr.hasNext()) {
attr = (AttVal) attrItr.next();
attr.next = null;
if (last != null)
attr.next = last;
last = attr;
}
}
printAttrsReal(fout, indent, node, attr);
}
This requires also adding the "dropDuplicateAttributes" field to Configuration.
The idea is that if you want duplicate attributes dropped, simply put each
attribute in a hashtable, and then build a new linked list from its values
afterwards. This will ensure that each attribute occurs only once.
In general, it would be a bit of a speed improvement to store the attributes
in a hash, as the current scheme seems to be O(n^2): in Node and AttVal,
there's a check which does a linear search of all attrs for a match, for each
attr.
This change works for a number of test files I'm working on. Furthermore, this
was the only problem I had with converting wild HTML to XHTML using JTidy. I'm
using the latest Xerces SAXParser to check the output for correctness.
My configuration settings to get this working are:
tidy.setUpperCaseTags(true);
tidy.setDocType("omit");
tidy.setXHTML(true);
tidy.setNumEntities(true);
tidy.setFixComments(true);
tidy.setShowWarnings(true);
Not sure which of these were strictly needed for conformance.
Thanks for starting the project up again. Hope this helps.
Cheers,
Pablo Mayrgundter
|
|
From: Mayrgundter, P. <pma...@do...> - 2004-07-26 16:08:17
|
In org/w3c/tidy/PPrint.java
Rename the existing printAttrs method to "printAttrsReal", and
change its body to refer to this new name in the recursive call:
if (attr.next !=3D null)
{
// Was printAttrs(...)
printAttrsReal(fout, indent, node, attr.next);
}
And then add this method:
private void printAttrs(Out fout, int indent, Node node, AttVal attr) {
if (this.configuration.dropDuplicateAttributes) {
final java.util.Map attrMap =3D new java.util.HashMap();
while (attr !=3D null) {
attrMap.put(attr.attribute.toLowerCase(), attr);
attr =3D attr.next;
}
final java.util.Iterator attrItr =3D =
attrMap.values().iterator();
AttVal last =3D null;
while (attrItr.hasNext()) {
attr =3D (AttVal) attrItr.next();
attr.next =3D null;
if (last !=3D null)
attr.next =3D last;
last =3D attr;
}
}
printAttrsReal(fout, indent, node, attr);
}
This requires also adding the "dropDuplicateAttributes" field to =
Configuration.
The idea is that if you want duplicate attributes dropped, simply put =
each
attribute in a hashtable, and then build a new linked list from its =
values
afterwards. This will ensure that each attribute occurs only once.
In general, it would be a bit of a speed improvement to store the =
attributes
in a hash, as the current scheme seems to be O(n^2): in Node and AttVal,
there's a check which does a linear search of all attrs for a match, for =
each
attr.
This change works for a number of test files I'm working on. =
Furthermore, this
was the only problem I had with converting wild HTML to XHTML using =
JTidy. I'm
using the latest Xerces SAXParser to check the output for correctness.
My configuration settings to get this working are:
tidy.setUpperCaseTags(true);
tidy.setDocType("omit");
tidy.setXHTML(true);
tidy.setNumEntities(true);
tidy.setFixComments(true);
tidy.setShowWarnings(true);
Not sure which of these were strictly needed for conformance.
Thanks for starting the project up again. Hope this helps.
Cheers,
Pablo Mayrgundter
|
|
From: SourceForge.net <no...@so...> - 2004-07-19 08:24:40
|
Bugs item #991469, was opened at 2004-07-15 11:56 Message generated for change (Comment added) made by pkuzel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=991469&group_id=13153 Category: Tidy functionality Group: None Status: Open Resolution: None Priority: 5 Submitted By: Petr Kuzel (pkuzel) Assigned to: fabrizio giustina (fgiust) Summary: goes wrong with <option> tag Initial Comment: if the page/pagelet contains an <option> tag (as in when using the <select> tag, the following error is displayed: Annotation: Exception occurred in Request Processor java.lang.NullPointerException at org.w3c.tidy.ParserImpl.XMLPreserveWhiteSpace (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLDocument(Unknown Source) at org.w3c.tidy.Tidy.parse(Unknown Source) at org.w3c.tidy.Tidy.parse(Unknown Source) last release (in 2001) was release 7 See also <http://tasklist.netbeans.org/issues/show_bug.cgi?id=38798> ---------------------------------------------------------------------- >Comment By: Petr Kuzel (pkuzel) Date: 2004-07-19 10:24 Message: Logged In: YES user_id=386690 Called programatically: if (tidy == null) { tidy = new Tidy(); } tidy.setOnlyErrors(true); tidy.setShowWarnings(true); tidy.setQuiet(true); // XXX Apparently JSP pages (at least those involving // JSF) need XML handling in order for JTidy not to choke on them tidy.setXmlTags(isXML || isJSP); PrintWriter output = new ReportWriter(this); tidy.setErrout(output); // Where do I direct its output? If it really obeys // setQuiet(true) it shouldn't matter... tidy.parse(input, System.err); I asked original reporter to provide his document. ---------------------------------------------------------------------- Comment By: fabrizio giustina (fgiust) Date: 2004-07-18 18:43 Message: Logged In: YES user_id=798060 can you please upload a full document and tidy options which causes this NPE? thanks ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=991469&group_id=13153 |
|
From: SourceForge.net <no...@so...> - 2004-07-19 08:22:14
|
Bugs item #991471, was opened at 2004-07-15 11:59 Message generated for change (Comment added) made by pkuzel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=991471&group_id=13153 Category: Tidy functionality Group: None Status: Open Resolution: None Priority: 5 Submitted By: Petr Kuzel (pkuzel) Assigned to: fabrizio giustina (fgiust) Summary: NPE on file with CDATA Initial Comment: java.lang.NullPointerException at org.w3c.tidy.PPrint.printXMLTree(Unknown Source) at org.w3c.tidy.PPrint.printXMLTree(Unknown Source) at org.w3c.tidy.PPrint.printXMLTree(Unknown Source) at org.w3c.tidy.PPrint.printXMLTree(Unknown Source) at org.w3c.tidy.PPrint.printXMLTree(Unknown Source) at org.w3c.tidy.Tidy.parse(Unknown Source) at org.w3c.tidy.Tidy.parse(Unknown Source) steps to reproduce: The Ant target that causes the issue is: ==== <target name="help"> <echo> <![CDATA[ *** Help message *** *** End of help message *** ]]> </echo> </target> ==== Note that the same target withOUT the CDATA element: ==== <target name="help"> <echo> *** Help message *** *** End of help message *** </echo> </target> ==== gives no problem. So the culprit seems to the CDATA elelment. Thanks! See alse <http://tasklist.netbeans.org/issues/show_bug.cgi?id=44679> ---------------------------------------------------------------------- >Comment By: Petr Kuzel (pkuzel) Date: 2004-07-19 10:22 Message: Logged In: YES user_id=386690 Called programatically: if (tidy == null) { tidy = new Tidy(); } tidy.setOnlyErrors(true); tidy.setShowWarnings(true); tidy.setQuiet(true); // XXX Apparently JSP pages (at least those involving // JSF) need XML handling in order for JTidy not to choke on them tidy.setXmlTags(isXML || isJSP); PrintWriter output = new ReportWriter(this); tidy.setErrout(output); // Where do I direct its output? If it really obeys // setQuiet(true) it shouldn't matter... tidy.parse(input, System.err); I asked original reporter to provide his document. ---------------------------------------------------------------------- Comment By: fabrizio giustina (fgiust) Date: 2004-07-18 18:39 Message: Logged In: YES user_id=798060 added a testcase in CVS. I'm however unable to reproduce the problem using both r7 and the latest cvs version. Which options are you using in formatting? (actually test simply sets input-xml= yes, output-xml= yes) Is the snippet enough to cause the problem or it's only a part of a bigger document? Can ou please uplad the original document and the option uset in tidy setup? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=991471&group_id=13153 |
|
From: SourceForge.net <no...@so...> - 2004-07-19 05:49:41
|
Bugs item #950402, was opened at 2004-05-08 18:13 Message generated for change (Comment added) made by navneetkarnani You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=950402&group_id=13153 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Navneet Karnani (navneetkarnani) Assigned to: fabrizio giustina (fgiust) Summary: HTML tags that don't have closing tags are not treated corre Initial Comment: HTML tags like BR and IMG are treated as error. Here is a sample of the output i see: line 112 column 69 - Error: unexpected </span> in <img> line 113 column 1 - Error: unexpected </td> in <img> line 115 column 1 - Error: unexpected </tr> in <img> line 165 column 17 - Error: <td> missing '>' for end of tag line 167 column 33 - Error: unexpected </a> in <br> line 167 column 39 - Error: unexpected </td> in <br> line 173 column 28 - Error: unexpected </A> in <BR> This document has errors that must be fixed before using HTML Tidy to generate a tidied up version. ---------------------------------------------------------------------- >Comment By: Navneet Karnani (navneetkarnani) Date: 2004-07-19 11:19 Message: Logged In: YES user_id=569363 I was using the default setup. Out of the zip. No customizations done. ---------------------------------------------------------------------- Comment By: fabrizio giustina (fgiust) Date: 2004-07-18 22:21 Message: Logged In: YES user_id=798060 this only should happen if you set input-xml= yes (using input- xml tidy expects a well formed xml document). Are you using this option? Can you please post the detail of your tidy setup? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=950402&group_id=13153 |
|
From: SourceForge.net <no...@so...> - 2004-07-18 16:51:17
|
Bugs item #950402, was opened at 2004-05-08 14:43 Message generated for change (Comment added) made by fgiust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=950402&group_id=13153 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Navneet Karnani (navneetkarnani) >Assigned to: fabrizio giustina (fgiust) Summary: HTML tags that don't have closing tags are not treated corre Initial Comment: HTML tags like BR and IMG are treated as error. Here is a sample of the output i see: line 112 column 69 - Error: unexpected </span> in <img> line 113 column 1 - Error: unexpected </td> in <img> line 115 column 1 - Error: unexpected </tr> in <img> line 165 column 17 - Error: <td> missing '>' for end of tag line 167 column 33 - Error: unexpected </a> in <br> line 167 column 39 - Error: unexpected </td> in <br> line 173 column 28 - Error: unexpected </A> in <BR> This document has errors that must be fixed before using HTML Tidy to generate a tidied up version. ---------------------------------------------------------------------- >Comment By: fabrizio giustina (fgiust) Date: 2004-07-18 18:51 Message: Logged In: YES user_id=798060 this only should happen if you set input-xml= yes (using input- xml tidy expects a well formed xml document). Are you using this option? Can you please post the detail of your tidy setup? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=950402&group_id=13153 |
|
From: SourceForge.net <no...@so...> - 2004-07-18 16:43:56
|
Bugs item #991469, was opened at 2004-07-15 11:56 Message generated for change (Comment added) made by fgiust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=991469&group_id=13153 Category: Tidy functionality Group: None Status: Open Resolution: None Priority: 5 Submitted By: Petr Kuzel (pkuzel) >Assigned to: fabrizio giustina (fgiust) Summary: goes wrong with <option> tag Initial Comment: if the page/pagelet contains an <option> tag (as in when using the <select> tag, the following error is displayed: Annotation: Exception occurred in Request Processor java.lang.NullPointerException at org.w3c.tidy.ParserImpl.XMLPreserveWhiteSpace (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLDocument(Unknown Source) at org.w3c.tidy.Tidy.parse(Unknown Source) at org.w3c.tidy.Tidy.parse(Unknown Source) last release (in 2001) was release 7 See also <http://tasklist.netbeans.org/issues/show_bug.cgi?id=38798> ---------------------------------------------------------------------- >Comment By: fabrizio giustina (fgiust) Date: 2004-07-18 18:43 Message: Logged In: YES user_id=798060 can you please upload a full document and tidy options which causes this NPE? thanks ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=991469&group_id=13153 |
|
From: SourceForge.net <no...@so...> - 2004-07-18 16:39:23
|
Bugs item #991471, was opened at 2004-07-15 11:59 Message generated for change (Comment added) made by fgiust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=991471&group_id=13153 Category: Tidy functionality Group: None Status: Open Resolution: None Priority: 5 Submitted By: Petr Kuzel (pkuzel) >Assigned to: fabrizio giustina (fgiust) Summary: NPE on file with CDATA Initial Comment: java.lang.NullPointerException at org.w3c.tidy.PPrint.printXMLTree(Unknown Source) at org.w3c.tidy.PPrint.printXMLTree(Unknown Source) at org.w3c.tidy.PPrint.printXMLTree(Unknown Source) at org.w3c.tidy.PPrint.printXMLTree(Unknown Source) at org.w3c.tidy.PPrint.printXMLTree(Unknown Source) at org.w3c.tidy.Tidy.parse(Unknown Source) at org.w3c.tidy.Tidy.parse(Unknown Source) steps to reproduce: The Ant target that causes the issue is: ==== <target name="help"> <echo> <![CDATA[ *** Help message *** *** End of help message *** ]]> </echo> </target> ==== Note that the same target withOUT the CDATA element: ==== <target name="help"> <echo> *** Help message *** *** End of help message *** </echo> </target> ==== gives no problem. So the culprit seems to the CDATA elelment. Thanks! See alse <http://tasklist.netbeans.org/issues/show_bug.cgi?id=44679> ---------------------------------------------------------------------- >Comment By: fabrizio giustina (fgiust) Date: 2004-07-18 18:39 Message: Logged In: YES user_id=798060 added a testcase in CVS. I'm however unable to reproduce the problem using both r7 and the latest cvs version. Which options are you using in formatting? (actually test simply sets input-xml= yes, output-xml= yes) Is the snippet enough to cause the problem or it's only a part of a bigger document? Can ou please uplad the original document and the option uset in tidy setup? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=991471&group_id=13153 |
|
From: SourceForge.net <no...@so...> - 2004-07-15 10:00:04
|
Bugs item #991471, was opened at 2004-07-15 11:59 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=991471&group_id=13153 Category: Tidy functionality Group: None Status: Open Resolution: None Priority: 5 Submitted By: Petr Kuzel (pkuzel) Assigned to: Nobody/Anonymous (nobody) Summary: NPE on file with CDATA Initial Comment: java.lang.NullPointerException at org.w3c.tidy.PPrint.printXMLTree(Unknown Source) at org.w3c.tidy.PPrint.printXMLTree(Unknown Source) at org.w3c.tidy.PPrint.printXMLTree(Unknown Source) at org.w3c.tidy.PPrint.printXMLTree(Unknown Source) at org.w3c.tidy.PPrint.printXMLTree(Unknown Source) at org.w3c.tidy.Tidy.parse(Unknown Source) at org.w3c.tidy.Tidy.parse(Unknown Source) steps to reproduce: The Ant target that causes the issue is: ==== <target name="help"> <echo> <![CDATA[ *** Help message *** *** End of help message *** ]]> </echo> </target> ==== Note that the same target withOUT the CDATA element: ==== <target name="help"> <echo> *** Help message *** *** End of help message *** </echo> </target> ==== gives no problem. So the culprit seems to the CDATA elelment. Thanks! See alse <http://tasklist.netbeans.org/issues/show_bug.cgi?id=44679> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=991471&group_id=13153 |
|
From: SourceForge.net <no...@so...> - 2004-07-15 09:56:16
|
Bugs item #991469, was opened at 2004-07-15 11:56 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=991469&group_id=13153 Category: Tidy functionality Group: None Status: Open Resolution: None Priority: 5 Submitted By: Petr Kuzel (pkuzel) Assigned to: Nobody/Anonymous (nobody) Summary: goes wrong with <option> tag Initial Comment: if the page/pagelet contains an <option> tag (as in when using the <select> tag, the following error is displayed: Annotation: Exception occurred in Request Processor java.lang.NullPointerException at org.w3c.tidy.ParserImpl.XMLPreserveWhiteSpace (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLElement (Unknown Source) at org.w3c.tidy.ParserImpl.parseXMLDocument(Unknown Source) at org.w3c.tidy.Tidy.parse(Unknown Source) at org.w3c.tidy.Tidy.parse(Unknown Source) last release (in 2001) was release 7 See also <http://tasklist.netbeans.org/issues/show_bug.cgi?id=38798> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=991469&group_id=13153 |
|
From: SourceForge.net <no...@so...> - 2004-07-14 01:02:00
|
Bugs item #990604, was opened at 2004-07-14 03:01 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=990604&group_id=13153 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Langly (langly) Assigned to: Nobody/Anonymous (nobody) Summary: Case of content of "method" attribute for forms in XHTML Initial Comment: When outputting XHTML, JTidy must convert the content of the "method" attribute of "form" elements (either "get" or "post") to lower case. According to the XHTML 1.0 DTDs, only lower case is allowed in XHTML. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=990604&group_id=13153 |
|
From: SourceForge.net <no...@so...> - 2004-07-09 18:06:01
|
Feature Requests item #988135, was opened at 2004-07-09 18:05 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=363153&aid=988135&group_id=13153 Category: None Group: None Status: Open Priority: 5 Submitted By: Chris Wilson (gcc) Assigned to: Nobody/Anonymous (nobody) Summary: Enable filtering of Word 2000 <![if...]> from any document Initial Comment: If a page contains <![if...]> tags but is not recognised by JTidy as a Word 2000 document (e.g. yahoo.com home page at time of writing), JTidy cannot be configured to remove them. This patch allows removal of such tags from any document when Word 2000 filtering is enabled, even if JTidy does not detect the document as a Word 2000 document. The attached patch also adds a --word2000 command-line option to enable Word2000 filtering mode, useful for testing and debugging JTidy. Thanks for some great software! Please keep up the good work! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=363153&aid=988135&group_id=13153 |
|
From: SourceForge.net <no...@so...> - 2004-07-08 00:23:28
|
Bugs item #986966, was opened at 2004-07-07 17:23 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=986966&group_id=13153 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: jtidy is not setting attribute type for <input type=text> Initial Comment: 1) Parse in an html file that contains <input type="text">. 2) call document.getElementsByTagName("input") 3) iterate through and call node.getAttribute("type") 4) it incorrectly returns "", it should return "text" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=986966&group_id=13153 |
|
From: Mireia R. <ri...@fb...> - 2004-06-11 10:59:07
|
Dear colleagues, I developed an application in Java that integrates Tidy (the final java = version from Dave Ragett) and processes an entire web with Tidy (copies = all subdirectories and processes all HTML pages with Tidy). The = application also converts a web composed with frames to a web equivalent = in contents but composed with CSS. All is distributed with GNU license. By the moment the application is not in Internet nor has a graphical = interface. All the documentation is written in catalan. Currently we are = constructing an interface and I plan to translate the contents to = English. I also plan to upgrade to last JTidy release. I could send a = copy of current version to any ftp site that you indicate me. If anybody is interested in getting the source or documentation please = contact me. The application is the result of my software engineer career final = project work. It has been directed by Ph.D. Jos=E9 Luis Balc=E1zar, from = Universitat Polit=E8cnica de Catalunya, in Barcelona. Mireia Ribera ri...@ub... |
|
From: SourceForge.net <no...@so...> - 2004-06-01 21:12:07
|
Bugs item #945177, was opened at 2004-04-30 02:56 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=945177&group_id=13153 Category: Tidy functionality Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: JTidy allows duplicate ID attributes Initial Comment: If you give the same ID value to two elements, this should cause an error (or warning). For example, the fragment: <p id="test">Paragraph text</p> <p id="test">New paragraph</p> would flag as an error using the on-line validator at the W3C website. JTidy does not notice this at all. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-06-01 14:12 Message: Logged In: NO It would be nice if this feature is implemented. If there is information about a standard implementation then i will gladly help with this one. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=945177&group_id=13153 |
|
From: SourceForge.net <no...@so...> - 2004-05-12 18:00:29
|
Bugs item #952734, was opened at 2004-05-12 11:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=952734&group_id=13153 Category: DOM Support Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: jtidy allows duplicate attributes Initial Comment: If the html contains duplicate attributes (such as valign, in a web page I found), jtidy will produce invalid XML containing duplicate attributes as well. It would be better to check for duplicate attributes and discard all except the first. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=952734&group_id=13153 |
|
From: SourceForge.net <no...@so...> - 2004-05-08 12:44:00
|
Bugs item #950402, was opened at 2004-05-08 18:13 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=950402&group_id=13153 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Navneet Karnani (navneetkarnani) Assigned to: Nobody/Anonymous (nobody) Summary: HTML tags that don't have closing tags are not treated corre Initial Comment: HTML tags like BR and IMG are treated as error. Here is a sample of the output i see: line 112 column 69 - Error: unexpected </span> in <img> line 113 column 1 - Error: unexpected </td> in <img> line 115 column 1 - Error: unexpected </tr> in <img> line 165 column 17 - Error: <td> missing '>' for end of tag line 167 column 33 - Error: unexpected </a> in <br> line 167 column 39 - Error: unexpected </td> in <br> line 173 column 28 - Error: unexpected </A> in <BR> This document has errors that must be fixed before using HTML Tidy to generate a tidied up version. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=950402&group_id=13153 |
|
From: SourceForge.net <no...@so...> - 2004-04-30 10:52:24
|
Bugs item #775517, was opened at 2003-07-22 10:27 Message generated for change (Comment added) made by fgiust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=775517&group_id=13153 Category: Tidy functionality Group: None >Status: Closed >Resolution: Works For Me Priority: 1 Submitted By: soujanya (tooltesting) >Assigned to: fabrizio giustina (fgiust) Summary: Regarding html pages containing nonstandard html tags Initial Comment: For some html pages containing tags of their own (nonstandard html tags), Tidy is not parsing and giving an error while parsing that tag like the following: Error: <Tag> is not recognized! After that it is displaying a message like: This document has errors that must be fixed before using HTML Tidy to generate a tidied up version. What to do if a tidied version of a html is needed for those html pages which include nonstandard html tags? ---------------------------------------------------------------------- >Comment By: fabrizio giustina (fgiust) Date: 2004-04-30 12:52 Message: Logged In: YES user_id=798060 you will need to add new (non standard tags) using the following config options: new-blocklevel-tags new-empty-tags new-inline-tags new-pre-tags see tidy quickreference at http://tidy.sourceforge.net/docs/quickref.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113153&aid=775517&group_id=13153 |
31 messages has been excluded from this view by a project administrator.
