Re: So close yet so far: DOCTYPE

2002-01-28 Thread Rob S.
>attribute but at the moment how to do it is a bit obscure (to me). if this >is important to you, i'll take a look into it. Not really, but thanks for the offer ;) - r -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: So close yet so far: DOCTYPE

2002-01-28 Thread robert burrell donkin
On Saturday, January 26, 2002, at 07:33 PM, Rob S. wrote: > Here's the first few lines of the file... note how there's no "encoding" > attribute in the processing instruction, even though I've used a > constructor specifying it. hi rob this explanation is going to sound a little obscure... t

Re: So close yet so far: DOCTYPE

2002-01-28 Thread Rob S.
>i've committed a fix for the doctype pretty print bug into cvs. Awesome, thanks very much! =) - r -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: So close yet so far: DOCTYPE

2002-01-28 Thread robert burrell donkin
hi rob i've committed a fix for the doctype pretty print bug into cvs. - robert On Saturday, January 26, 2002, at 07:33 PM, Rob S. wrote: > Oops, sent the message too quickly =) > > Here's the first few lines of the file... note how there's no "encoding" > attribute in the processing instruct

Re: So close yet so far: DOCTYPE

2002-01-26 Thread snagy
ent: Saturday, January 26, 2002 1:48 PM Subject: Re: So close yet so far: DOCTYPE > > I have to setPrettyPrint() for every element I want pretty printed. I > > assumed setting a parent element to pretty print would affect all children > > as well, but it doesn't. I figured I

Re: So close yet so far: DOCTYPE

2002-01-26 Thread Chris Reeves
> I have to setPrettyPrint() for every element I want pretty printed. I > assumed setting a parent element to pretty print would affect all children > as well, but it doesn't. I figured I'll just attach the file since it's > pretty short. The part you're interested in is right at the top (re: >

Re: So close yet so far: DOCTYPE

2002-01-26 Thread Rob S.
Oops, sent the message too quickly =) Here's the first few lines of the file... note how there's no "encoding" attribute in the processing instruction, even though I've used a constructor specifying it. As well, there is no line break after the . - r At 06:29

Re: So close yet so far: DOCTYPE

2002-01-26 Thread Rob S.
>i've taken a quick look but i can't find an obvious easy fix. pretty print >formatting is controlled by the parent not the child so it'd be useful if >you could tell me what your particular parent element is or even better >supply a small snippet of code giving me an example of your use of Do

Re: So close yet so far: DOCTYPE

2002-01-26 Thread robert burrell donkin
On Thursday, January 24, 2002, at 11:08 PM, Rob S. wrote: > Bingo! Thanks a lot Robert! =) > > Icing on the cake would be if I could get a carriage return before the > root element (after the DTD), having already set everything to > prettyPrint. I can live with that because it's just an aest

Re: So close yet so far: DOCTYPE

2002-01-24 Thread Rob S.
Bingo! Thanks a lot Robert! =) Icing on the cake would be if I could get a carriage return before the root element (after the DTD), having already set everything to prettyPrint. I can live with that because it's just an aesthetic issue, thankfully ;) - r At 02:50 PM 1/24/2002, robert burrel

Re: So close yet so far: DOCTYPE

2002-01-24 Thread robert burrell donkin
hi rob i think that you can do what you need by using the other constructor eg. Doctype dtdRef = new Doctype("horizons", "SYSTEM", "etc/horizons.dtd", "") ; i do agree that this is a bit confusing and pretty badly documented. it might be a good idea to add a factory method. BTW this is from t

Re: So close yet so far: DOCTYPE

2002-01-24 Thread Rob S.
Err, I should have explained the subject. I wrote a pretty big SAX2 parser a few days ago, and this is the only thing left before the writer will be finished =) - r At 02:12 PM 1/24/2002, Rob S. wrote: >Hiya everyone, > >Upon using the following code: > >Doctype dtdRef = new Doctype("horizons