JTidy

Bugs item #513999, was opened at 2002-02-06 14:23
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=113153&aid=513999&group_id=13153

Category: DOM Support
Group: None
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Gary L Peskin (garypeskin)
Summary: can not compile tidy under java 1.1.6

Initial Comment:
I have tried to deploy tidy with a 1.1.6 version of our app and it won't work.
The error that shows up is a missing interface, and when you track it down
further it seems that tidy can not compile at all under java 1.1.6. The error is in
DOMDocumentImpl, that it does not implement getEncoding(). 

I assume the intention is that tidy should work in older java runtimes
and that this bug slipped in somewhere along the line. I hope that is the
case and that this report helps. I noticed that a new build is under development.

Thanks for all the great work - our clients really appreciate the ability to
upgrade html to xhtml on the fly. Tidy has fit seemlessly into our xml browser
and editor.

Regards,

Rob Brown
InDelv, Inc.
 http://www.indelv.com

----------------------------------------------------------------------

>Comment By: Gary L Peskin (garypeskin)
Date: 2002-02-06 18:03

Message:
Logged In: YES 
user_id=91501

Document.getEncoding() is a DOM Level 3 interface and is 
not supported by JTidy under any level of the JVM.  This 
interface is not shipped with JTidy.  You must have a .jar 
file in your compile CLASSPATH with the DOM Level 3 
interfaces that you obtained from somewhere.  If you remove 
that library, JTidy should compile just fine.  If not, 
please open a new problem and include the specific error 
message that you're getting from your java compiler.
Thanks,
Gary

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=113153&aid=513999&group_id=13153

Bugs item #468706, was opened at 2001-10-06 23:02
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=113153&aid=468706&group_id=13153

Category: DOM Support
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Gary L Peskin (garypeskin)
Summary: Can't add text nodes

Initial Comment:
I've created an element and now I would like to add a 
text node to it, like <a>TEXT NODE</a>  My code that 
works in JAXP, IBM and ProjectX doesn't work in JTidy, 
example below;

Node tx = xmldoc.createTextNode
(submitnode.getAttributes().getNamedItem
("value").getNodeValue());
        subele.appendChild(tx); //bug, never works 
with a Jtidy Document
        newsub = parent.replaceChild(subele, 
submitnode); 

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=113153&aid=468706&group_id=13153

Bugs item #462423, was opened at 2001-09-17 19:09
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=113153&aid=462423&group_id=13153

Category: Tidy functionality
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Gary L Peskin (garypeskin)
Summary: stdin support doesn't work on cmd line

Initial Comment:
For example, whenever I try to process stdin I get this:

cat x.html | jtidy -asxml
Tidy: can't open file "stdin"

I don't think the processing of stdin in Tidy.java's main() is correct.

Around line 1562 we have this:

if (argc > 1)
            {
                file = argv[argIndex];
            }
            else
            {
                file = "stdin";
            }
whereas I think we want this ?

if (argc > 1)
            {
                file = argv[argIndex];
            }
            else
            {
                file = null;
            }

Because:
    private Node parse(InputStream in, String file, OutputStream out)

has this:

        if (file != null)
        {
            in = new FileInputStream(file);
            inputStreamName = file;
        }
        else if (in == null)
        {
            in = System.in;
            inputStreamName = "stdin";
        }


so passing null as 1st argument to parse() will cause it to use stdin. passing "stdin" will cause it to try and open a fie of that name.

Anyway - I have tried patching it like this and I can now get my example command to work.

Dave

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2001-09-17 19:25

Message:
Logged In: NO 

Sorry - hadn't meant to be quite so anonymous. Haven't used this system before.

Also, should maybe note that the problem occured with the 04aug200-r7dev release.

Cheers,
dave@...

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=113153&aid=462423&group_id=13153