> > 1) I was going to try running the pdf, but the Makefile includes a Makefile.def > > ... > ...nice explanation snipped... > At this point, it might be worth just verifying the output with HTML, > checking it into the sandbox, and watching what the PDF looks like on the > web site :)
Ok, thanks for the explanation. I'll take your advice and leave the PDF alone for the time being. > > 4) It appears that you use the <code> element within paragraphs > > to format text as opposed to <programlisting>. Not clear on the > > difference... > > Like <pre> in HTML, <programlisting> contains a block of preformatted text > (presumably for a program of some sort). <code>, on the other hand, just > changes the font to a monospaced font but does not consider its text to be > preformatted (e.g., line breaks in <code> are not significant; line breaks > in <programlisting> are significant). To be picky, <code> in HTML is > actually spelled <computeroutput> in DocBook, but BoostBook supports > <code> also because <computeroutput> is _waaaay_ too much to type. <response_tag>Got it :-)</response_tag> > > 5) I'm a little unsure about how the example extraction stuff works, > > but I'm sure you will explain the magic once you get around to > > documenting that part :-) > > Short version: anything in a <source> element is written to the file named > by the testcase. <snippet> pulls in code from a <programlisting> with the > same name attribute. Thx. > > 6) One worry is that I'm sure some users will be a bit overwhelmed > > when writing reference docs with all the various tags. > > I'm wondering if there will be a minimum subset that is less > > feature rich with links, but still works fine that can be more > > easily transitioned to? > > There might be. Actually, it may make sense to move the discussion of > linking much later, after the discussion of documenting C++ constructs. > That would limit the amount of nitpicky details in the initial sections, > and it would be easier to understand the behavior of, e.g., <functionname> > or <methodname> once we have the C++ constructs around. Ok, sounds good. Jeff ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Boost-docs mailing list [EMAIL PROTECTED] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
