The inspection report shows that we have a bunch of little fixes to make before we release. Please check it out and fix whatever you can: http://www.boost.org/regression-logs/inspection_report.html Doug
On Jul 11, 2005, at 6:52 PM, Douglas Gregor wrote:
The inspection report shows that we have a bunch of little fixes to make before we release. Please check it out and fix whatever you can:
graph, signals should now be clear Doug
Douglas Gregor wrote:
The inspection report shows that we have a bunch of little fixes to make before we release. Please check it out and fix whatever you can:
Ooops! I'm responsible for almost half the violations. I'll fix this soon. A number of the broken links in the iostreams docs are supposed to point to the document at http://www.boost.org/doc/html/CopyConstructible.html. I used a relative path so that users without full time web access would be directed to their own hard drives. I've verified that (at least some of) these relative links are correct, under the assumption that the document $(BOOST_ROOT)/doc/html/CopyConstructible.html will be present in the distribution. What's the policy for linking to documents in the directory doc/html? Jonathan
On Jul 11, 2005, at 11:25 PM, Jonathan Turkanis wrote:
Douglas Gregor wrote:
The inspection report shows that we have a bunch of little fixes to make before we release. Please check it out and fix whatever you can:
Ooops! I'm responsible for almost half the violations. I'll fix this soon.
Thanks!
A number of the broken links in the iostreams docs are supposed to point to the document at http://www.boost.org/doc/html/CopyConstructible.html. I used a relative path so that users without full time web access would be directed to their own hard drives. I've verified that (at least some of) these relative links are correct, under the assumption that the document $(BOOST_ROOT)/doc/html/CopyConstructible.html will be present in the distribution.
What's the policy for linking to documents in the directory doc/html?
The best way to deal with this is to create a file $(BOOST_ROOT)/doc/html/CopyConstructible.html that forwards to the MetaComm-generated documentation. See, e.g., doc/html/function.html. Go ahead and check that into CVS, so that users browsing CVS documentation always get up-to-date docs. Doug
Douglas Gregor wrote:
Jonathan Turkanis wrote:
Ooops! I'm responsible for almost half the violations. I'll fix this soon.
This is about half done now.
What's the policy for linking to documents in the directory doc/html?
The best way to deal with this is to create a file $(BOOST_ROOT)/doc/html/CopyConstructible.html that forwards to the MetaComm-generated documentation. See, e.g., doc/html/function.html. Go ahead and check that into CVS, so that users browsing CVS documentation always get up-to-date docs.
Done.
Doug
Jonathan
A number of the broken links in the iostreams docs are supposed to point to the document at http://www.boost.org/doc/html/CopyConstructible.html. I used a relative path so that users without full time web access would be directed to their own hard drives. I've verified that (at least some of) these relative links are correct, under the assumption that the document $(BOOST_ROOT)/doc/html/CopyConstructible.html will be present in the distribution.
The broken links for date_time also point to a file in the $(BOOST_ROOT)/doc/html directory. I've verified these links will work as long as $(BOOST_ROOT)/doc/html/date_time.html will be present in the distribution. The min/max violations for date_time are not violations. They appear in comments. We are addressing the remaining date_time issues. Bart
Douglas Gregor wrote:
The inspection report shows that we have a bunch of little fixes to make before we release. Please check it out and fix whatever you can:
The page appears to have broken HTML. Everything starting from "iterator" header looks like one big link to http://www.boost.org/regression-logs/libs/iostreams/doc/tutorial/writing_fil... in my browser. - Volodya
Vladimir Prus wrote:
Douglas Gregor wrote:
The inspection report shows that we have a bunch of little fixes to make before we release. Please check it out and fix whatever you can:
The page appears to have broken HTML. Everything starting from "iterator" header looks like one big link to http://www.boost.org/regression-logs/libs/iostreams/doc/tutorial/writing_fil...
in my browser.
Firefox displays it OK. The problem comes from the reporting of the invalid char in a link above that section. I guess the reporting program could URLencode those things but it's probably not worth it right now. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org
On Jul 12, 2005, at 12:31 AM, Vladimir Prus wrote:
Douglas Gregor wrote:
The inspection report shows that we have a bunch of little fixes to make before we release. Please check it out and fix whatever you can:
The page appears to have broken HTML. Everything starting from "iterator" header looks like one big link to http://www.boost.org/regression-logs/libs/iostreams/doc/tutorial/ writing_filters.html
in my browser.
Looks like the "filename > 31 chars" didn't have the > escaped. Fixed in CVS, but I don't know how that propagates to the online inspection report. Let's see if it happens automagically. Doug
Douglas Gregor wrote:
On Jul 12, 2005, at 12:31 AM, Vladimir Prus wrote:
Douglas Gregor wrote:
The inspection report shows that we have a bunch of little fixes to make before we release. Please check it out and fix whatever you can:
The page appears to have broken HTML. Everything starting from "iterator" header looks like one big link to http://www.boost.org/regression-logs/libs/iostreams/doc/tutorial/ writing_filters.html
in my browser.
Looks like the "filename > 31 chars" didn't have the > escaped. Fixed in CVS, but I don't know how that propagates to the online inspection report. Let's see if it happens automagically.
Well almost automagically... I run it manually but periodically. Usually at least once a day. But always each time I update my Boost checkout. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org
Douglas Gregor <doug.gregor <at> gmail.com> writes:
The inspection report shows that we have a bunch of little fixes to make before we release. Please check it out and fix whatever you can:
range ----- libs/range/doc/intro.html: unlinked file This is completely wrong. The file is linked from libs/range/index.html what am I missing? ptr_container ------------- libs/ptr_container/doc/comp_associative_ptr_container.sh: filename > 31 chars libs/ptr_container/doc/comp_reversible_ptr_container.sh: filename > 31 chars libs/ptr_container/doc/tut1.html: unlinked file libs/ptr_container/doc/tut2.html: unlinked file fixed. br Thorsten
Thorsten Ottosen wrote:
Douglas Gregor <doug.gregor <at> gmail.com> writes:
The inspection report shows that we have a bunch of little fixes to make before we release. Please check it out and fix whatever you can:
range ----- libs/range/doc/intro.html: unlinked file
This is completely wrong. The file is linked from
libs/range/index.html
what am I missing?
Double quotes around the value of the href attribute, I think. Jonathan
On Jul 14, 2005, at 10:47 AM, Thorsten Ottosen wrote:
range ----- libs/range/doc/intro.html: unlinked file
This is completely wrong. The file is linked from
libs/range/index.html
what am I missing?
Valid HTML :) It's improperly linked like this: <a href=doc/intro.html>Introduction </a> I've changed everything in libs/range/index.html to use ""'s properly and checked it in. The range library is now clear of any issues.
ptr_container ------------- libs/ptr_container/doc/comp_associative_ptr_container.sh: filename > 31 chars libs/ptr_container/doc/comp_reversible_ptr_container.sh: filename > 31 chars libs/ptr_container/doc/tut1.html: unlinked file libs/ptr_container/doc/tut2.html: unlinked file
fixed.
Thanks! Looks good. A new report is online now. Doug
participants (6)
-
Bart -
Doug Gregor -
Douglas Gregor -
John Maddock -
Jonathan Turkanis -
Rene Rivera -
Thorsten Ottosen -
Vladimir Prus