Re: [Docutils-users] Re: More include woes

[Brett g P. <bgp...@ac...>]

----- Original Message -----
From: "David Goodger" <go...@py...>
To: "Brett g Porter" <bgp...@ac...>;
<doc...@li...>
Sent: Monday, November 18, 2002 9:47 PM
Subject: Re: [Docutils-users] Re: More include woes


> This was a path manipulation bug.  The wrong base path was being used.
> Should be corrected now.
Excellent -- thanks!


> Looks like a data encoding error.  Are there any non-US-ASCII
> characters in your included document?  The "include" directive wasn't
> decoding new files properly, but that's corrected now.
That's exactly what it was -- should have been corrected before now, but a
few instances slipped through.


> > Never mind on this one -- once I actually bothered to think about the
> > traceback, I found the error in my source and fixed it. Still curious
> > that this problem only happens when this file was being included.
>
> I'm curious too.  When you say "error in my source", are you talking
> about source code or source text?
Sorry -- my text. Guess that I shouldn't use the word 'source' to refer to
everything in the whole world, hm?


> This "include" directive seemed like such a simple beast at the
> beginning, but it has displayed unexpected complexity.  Hopefully it's
> been tamed now; time will tell.
>
> You'll have to update Docutils directly from CVS.  SourceForge has been
> doing some maintenance since yesterday, and the group directories are
> read-only.  The cron job that updates the snapshot files can't run
> until they're done.
>
> Thanks for the report, and for exercising Docutils in interesting ways!
You bet -- thanks for your speedy response. Today, I'm going to make a stab
at bringing the rlpdf writer in the sandbox up to snuff (it's missing a ton
of {visit|depart}_XXXX() handlers) or perhaps a rewrite. Wish me luck.