From: Brett g P. <bgp...@ac...> - 2002-11-18 16:07:22
|
----- Original Message ----- From: "Brett g Porter" <bgp...@ac...> To: <doc...@li...> Sent: Monday, November 18, 2002 11:00 AM Subject: More include woes > 2) Problems including a file. > > I have a file that works fine when rendered on its own. If I copy its body > into my master document at the point where I would like to .. include:: it, > the resulting master doc renders fine. However, any attempt to include this > file in another (even an otherwise empty file that just includes it) gives > me this error: 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. |
From: David G. <go...@py...> - 2002-11-19 02:47:31
|
Brett g Porter wrote: > I've stumbled on one thing that looks like a real problem, and one > that's just making me scratch my head. > > 1) Directory problems: > > I am assembling a master document that pulls in some source from a > subdirectory, ... > Then I got the bright idea that the ref_intro doc should live down > in the reference_dir directory, so I moved it, and tried patching > the paths so it was including refch*.txt as if they were in the > current directory. > > That didn't work This was a path manipulation bug. The wrong base path was being used. Should be corrected now. > 2) Problems including a file. > > I have a file that works fine when rendered on its own. If I copy > its body into my master document at the point where I would like to > .. include:: it, the resulting master doc renders fine. However, any > attempt to include this file in another (even an otherwise empty > file that just includes it) gives me this error: ... > I've tried narrowing down the problem by whittling the problematic > file down, but can't reproduce the problem or locate the source. I'm > hoping that the traceback will give you a clue as to what the > problem is. 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. > 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? 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! -- David Goodger <go...@py...> Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ |
From: Brett g P. <bgp...@ac...> - 2002-11-19 14:05:34
|
----- 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. |