[1.32 Release] Fixing tabs/links/filenames -- the last round
Dear All, I'd appreciate if you bear with me one more time and find a moment to fix the following issues ASAP (see http://www.meta-comm.com/engineering/boost/issues.html): algorithm --------- libs/algorithm/minmax/index.html: broken link: ../../../../boost/minmax.hpp, broken link: minmax_benchs.html assign ------ libs/assign/test/list_inserter.cpp: tabs in file libs/assign/test/list_of.cpp: tabs in file build ----- tools/build/v2/index.html: broken link: ../../../doc/html/bbv2.installation.html, broken link: doc/html/index.html tools/build/v2/test/railsys/program/Jamfile: tabs in file tools/build/v2/test/test_system.html: unlinked file BoostBook-generated, need to be fixed in sources: doc/html/bbv2/advanced/jamfiles.html: broken link: ../../doc/extending.html#main_target_rules doc/html/bbv2/extender.html: broken link: ../../../example/customization doc/html/bbv2/howto.html: broken link: ../../../../../more/mailing_lists.htm#jamboost doc/html/bbv2/installation.html: broken link: ../../../jam_src/index.html#building_bjam, broken link: ../../jam_src/index.html doc/html/bbv2/tutorial/prebuilt.html: broken link: ../../doc/recipes.html#site_config_targets date_time --------- boost/date_time/local_time/posix_time_zone.hpp: tabs in file boost/index.htm: broken link: libs/date_time/doc/Changes.html BoostBook-generated, need to be fixed in sources: doc/html/date_time/details.html: broken link: ../../../libs/tokenizer/index.htm doc/html/date_time/doxy.html: broken link: ../../../boost/date_time/dst_transition_day_generators.hpp, broken link: ../../../boost/date_time/local_time_base.hpp doc/html/date_time/posix_time.html: broken link: ../../../libs/date_time/doc/time_duration_inherit.png graph ----- boost/graph/adjacency_list.hpp: tabs in file boost/graph/detail/adjacency_list.hpp: tabs in file libs/graph/src/graphviz_digraph_parser.cpp: tabs in file libs/graph/src/graphviz_graph_parser.cpp: tabs in file boost/index.htm: broken link: libs/graph/doc/astar_search.html, broken link: libs/graph/doc/floyd_warshall_shortest.html, broken link: libs/graph/doc/fruchterman_reingold.html iterator -------- libs/iterator/doc/filter_iterator_ref.html: unlinked file libs/iterator/doc/indirect_iterator_ref.html: unlinked file libs/iterator/doc/issues.html: unlinked file libs/iterator/doc/iter-issue-list.html: unlinked file libs/iterator/doc/iterator_adaptor_ref.html: unlinked file libs/iterator/doc/make_filter_iterator.html: unlinked file libs/iterator/doc/ref_problem.html: unlinked file libs/iterator/doc/zip_iterator.html: broken link: ../example/zip_iterator_examples.cpp numeric ------- libs/numeric/conversion/doc/converter.html: broken link: udt_support.html libs/numeric/conversion/doc/converter_policies.html: broken link: udt_support.html python ------ libs/python/doc/new-conversions.html: unlinked file libs/python/doc/tutorial/doc/html/index.html: broken link: ../../index.htm, broken link: ../../more/faq.htm, broken link: ../../more/index.htm, broken link: ../../people/people.htm, broken link: libraries.html libs/python/doc/tutorial/doc/html/python/embedding.html: broken link: ../../../../building.html%20Building, broken link: ../../../index.htm, broken link: ../../../more/faq.htm, broken link: ../../../more/index.htm, broken link: ../../../people/people.htm, broken link: ../../v2/handle.html, broken link: ../../v2/handle.html#allow_null-spec, broken link: ../libraries.html libs/python/doc/tutorial/doc/html/python/exception.html: broken link: ../../../index.htm, broken link: ../../../more/faq.htm, broken link: ../../../more/index.htm, broken link: ../../../people/people.htm, broken link: ../libraries.html libs/python/doc/tutorial/doc/html/python/exposing.html: broken link: ../../../index.htm, broken link: ../../../more/faq.htm, broken link: ../../../more/index.htm, broken link: ../../../people/people.htm, broken link: ../libraries.html libs/python/doc/tutorial/doc/html/python/functions.html: broken link: ../../../index.htm, broken link: ../../../more/faq.htm, broken link: ../../../more/index.htm, broken link: ../../../people/people.htm, broken link: ../libraries.html libs/python/doc/tutorial/doc/html/python/hello.html: broken link: ../../../index.htm, broken link: ../../../more/faq.htm, broken link: ../../../more/index.htm, broken link: ../../../people/people.htm, broken link: ../libraries.html libs/python/doc/tutorial/doc/html/python/iterators.html: broken link: ../../../index.htm, broken link: ../../../more/faq.htm, broken link: ../../../more/index.htm, broken link: ../../../people/people.htm, broken link: ../libraries.html libs/python/doc/tutorial/doc/html/python/object.html: broken link: ../../../index.htm, broken link: ../../../more/faq.htm, broken link: ../../../more/index.htm, broken link: ../../../people/people.htm, broken link: ../libraries.html libs/python/doc/tutorial/doc/html/python/techniques.html: broken link: ../../../index.htm, broken link: ../../../more/faq.htm, broken link: ../../../more/index.htm, broken link: ../../../people/people.htm, broken link: ../libraries.html libs/python/doc/v2/bibliography.html: unlinked file libs/python/doc/v2/errors.html: broken link: ../../../function/doc/reference.html#functionN libs/python/doc/v2/faq.html: broken link: ../tutorial/doc/creating_packages.html, broken link: ../tutorial/doc/reducing_compiling_time.html libs/python/doc/v2/from_python.html: unlinked file libs/python/doc/v2/header.html: unlinked file libs/python/doc/v2/overview.html: unlinked file libs/python/doc/v2/pickle.html: broken link: ../tutorial/doc/extending_wrapped_objects_in_python.html libs/python/doc/v2/rationale.html: broken link: ../../../../../people/dave_abrahams.htm, unlinked file libs/python/pyste/doc/introduction.html: broken link: ../../doc/tutorial/doc/exposing_classes.html libs/python/pyste/doc/policies.html: broken link: ../../doc/tutorial/doc/call_policies.html libs/python/pyste/doc/running_pyste.html: broken link: ../../doc/tutorial/doc/building_hello_world.html libs/python/pyste/index.html: broken link: introduction.html range ----- libs/range/doc/intro.html: unlinked file regex ----- libs/regex/performance/input.html: unlinked file serialization ------------- libs/serialization/doc/contents.html: broken link: definitions.html, broken link: doc/configuration.html, broken link: faq.html, invalid character in URL: overview.html#Other implementations libs/serialization/doc/serialization.html: broken link: ../../../boost/serialization/shared_count.hpp, broken link: bibliograph.html#14 libs/serialization/src/basic_iarchive.cpp: tabs in file libs/serialization/test/Jamfile: tabs in file libs/serialization/test/test_non_default_ctor2.cpp: tabs in file libs/serialization/vc7ide/Boost Serialization Library.sln: nonportable path libs/serialization/vc7ide/Boost Serialization Library.suo: nonportable path signals ------- boost/signals/signal_template.hpp: tabs in file boost/signals/slot.hpp: tabs in file libs/signals/src/signal_base.cpp: tabs in file libs/signals/src/slot.cpp: tabs in file thread ------ libs/thread/src/xtime.cpp: invalid (cr only) line-ending utility ------- boost/utility/base_from_member.hpp: tabs in file libs/utility/generator_iterator.htm: unlinked file libs/utility/operators.htm: broken link: function_output_iterator.htm TIA, -- Aleksey Gurtovoy MetaCommunications Engineering
On Oct 29, 2004, at 4:18 AM, Aleksey Gurtovoy wrote:
graph -----
boost/graph/adjacency_list.hpp: tabs in file boost/graph/detail/adjacency_list.hpp: tabs in file libs/graph/src/graphviz_digraph_parser.cpp: tabs in file libs/graph/src/graphviz_graph_parser.cpp: tabs in file
All fixed.
boost/index.htm: broken link: libs/graph/doc/astar_search.html, broken link: libs/graph/doc/floyd_warshall_shortest.html, broken link: libs/graph/doc/fruchterman_reingold.html
This was due to the accidental merge of index.html to the release branch: none of these links will appear in the release once that's fixed.
signals -------
boost/signals/signal_template.hpp: tabs in file boost/signals/slot.hpp: tabs in file libs/signals/src/signal_base.cpp: tabs in file libs/signals/src/slot.cpp: tabs in file
All fixed. Doug
Doug Gregor writes:
On Oct 29, 2004, at 4:18 AM, Aleksey Gurtovoy wrote:
graph -----
boost/graph/adjacency_list.hpp: tabs in file boost/graph/detail/adjacency_list.hpp: tabs in file libs/graph/src/graphviz_digraph_parser.cpp: tabs in file libs/graph/src/graphviz_graph_parser.cpp: tabs in file
All fixed.
boost/index.htm: broken link: libs/graph/doc/astar_search.html, broken link: libs/graph/doc/floyd_warshall_shortest.html, broken link: libs/graph/doc/fruchterman_reingold.html
This was due to the accidental merge of index.html to the release branch: none of these links will appear in the release once that's fixed.
Already.
signals -------
boost/signals/signal_template.hpp: tabs in file boost/signals/slot.hpp: tabs in file libs/signals/src/signal_base.cpp: tabs in file libs/signals/src/slot.cpp: tabs in file
All fixed.
Thank you! -- Aleksey Gurtovoy MetaCommunications Engineering
Aleksey Gurtovoy wrote:
Dear All,
I'd appreciate if you bear with me one more time and find a moment to fix the following issues ASAP (see http://www.meta-comm.com/engineering/boost/issues.html):
python ------
Hi, Most of the broken links (in the Python tutorial) is in the boostbook auto-generated header (at the top) broken link: ../../index.htm, broken link: ../../more/faq.htm, broken link: ../../more/index.htm, broken link: ../../people/people.htm, broken link: libraries.html I'm not sure of the proper way to fix this. Shouldn't boostbook automatically generate the proper links? Is this a boostbook bug? Or, am I not using boostbook properly? I'll correct the other broken links, those which I have a control over. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net
Joel writes:
Aleksey Gurtovoy wrote:
Dear All,
I'd appreciate if you bear with me one more time and find a moment to fix the following issues ASAP (see http://www.meta-comm.com/engineering/boost/issues.html):
python ------
Hi,
Hi Joel,
Most of the broken links (in the Python tutorial) is in the boostbook auto-generated header (at the top)
broken link: ../../index.htm, broken link: ../../more/faq.htm, broken link: ../../more/index.htm, broken link: ../../people/people.htm, broken link: libraries.html
I'm not sure of the proper way to fix this. Shouldn't boostbook automatically generate the proper links?
It does.
Is this a boostbook bug? Or, am I not using boostbook properly?
The latter. The BoostBook stylesheets employ the aptly named "boost.root" parameter to determine the relative location of the Boost root directory. If your docs are not located in the "$BOOST_ROOT/doc/html" directory, you need to override the default "../.." with more appropriate value in your jamfile. In your case, something like this should do the job: boostbook tutorial : tutorial.xml : <xsl:param>boost.root=../../../../../.. ;
I'll correct the other broken links, those which I have a control over.
Thank you! -- Aleksey Gurtovoy MetaCommunications Engineering
Aleksey Gurtovoy wrote:
Is this a boostbook bug? Or, am I not using boostbook properly?
The latter. The BoostBook stylesheets employ the aptly named "boost.root" parameter to determine the relative location of the Boost root directory. If your docs are not located in the "$BOOST_ROOT/doc/html" directory, you need to override the default "../.." with more appropriate value in your jamfile.
In your case, something like this should do the job:
boostbook tutorial : tutorial.xml : <xsl:param>boost.root=../../../../../.. ;
Thanks. I should have RTFM first, pardon the noise. -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net
Joel wrote:
Aleksey Gurtovoy wrote:
Is this a boostbook bug? Or, am I not using boostbook properly?
The latter. The BoostBook stylesheets employ the aptly named "boost.root" parameter to determine the relative location of the Boost root directory. If your docs are not located in the "$BOOST_ROOT/doc/html" directory, you need to override the default "../.." with more appropriate value in your jamfile. In your case, something like this should do the job:
boostbook tutorial : tutorial.xml : <xsl:param>boost.root=../../../../../.. ;
Thanks. I should have RTFM first, pardon the noise.
Ok. Fixed. -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net
Joel writes:
Joel wrote:
Aleksey Gurtovoy wrote:
Is this a boostbook bug? Or, am I not using boostbook properly?
The latter. The BoostBook stylesheets employ the aptly named "boost.root" parameter to determine the relative location of the Boost root directory. If your docs are not located in the "$BOOST_ROOT/doc/html" directory, you need to override the default "../.." with more appropriate value in your jamfile. In your case, something like this should do the job:
boostbook tutorial : tutorial.xml : <xsl:param>boost.root=../../../../../.. ;
Thanks. I should have RTFM first, pardon the noise.
Ok. Fixed.
Thank you! Hmm, running the report again, it seems a number of issues is still there: libs/python/doc/new-conversions.html: unlinked file libs/python/doc/tutorial/doc/html/index.html: broken link: libraries.html libs/python/doc/tutorial/doc/html/python/embedding.html: broken link: ../libraries.html, broken link: ../object.html libs/python/doc/tutorial/doc/html/python/exception.html: broken link: ../libraries.html libs/python/doc/tutorial/doc/html/python/exposing.html: broken link: ../libraries.html libs/python/doc/tutorial/doc/html/python/functions.html: broken link: ../libraries.html libs/python/doc/tutorial/doc/html/python/hello.html: broken link: ../libraries.html libs/python/doc/tutorial/doc/html/python/iterators.html: broken link: ../libraries.html libs/python/doc/tutorial/doc/html/python/object.html: broken link: ../libraries.html libs/python/doc/tutorial/doc/html/python/techniques.html: broken link: ../libraries.html libs/python/doc/v2/bibliography.html: unlinked file libs/python/doc/v2/errors.html: broken link: ../../../function/doc/reference.html#functionN libs/python/doc/v2/faq.html: broken link: ../tutorial/doc/creating_packages.html, broken link: ../tutorial/doc/reducing_compiling_time.html libs/python/doc/v2/from_python.html: unlinked file libs/python/doc/v2/header.html: unlinked file libs/python/doc/v2/overview.html: unlinked file libs/python/doc/v2/pickle.html: broken link: ../tutorial/doc/extending_wrapped_objects_in_python.html libs/python/doc/v2/rationale.html: broken link: ../../../../../people/dave_abrahams.htm, unlinked file libs/python/pyste/doc/introduction.html: broken link: ../../doc/tutorial/doc/exposing_classes.html libs/python/pyste/doc/policies.html: broken link: ../../doc/tutorial/doc/call_policies.html libs/python/pyste/doc/running_pyste.html: broken link: ../../doc/tutorial/doc/building_hello_world.html libs/python/pyste/index.html: broken link: introduction.html "libraries.html" is a particularly puzzling since setting "boost.root" supposedly should have taken care of it. Oh, it's managed by another parameter, "boost.libraries" :(. OK, adding this to the jamfile and re-generating everything one more time; here's what's left: libs/python/doc/new-conversions.html: unlinked file libs/python/doc/v2/bibliography.html: unlinked file libs/python/doc/v2/errors.html: broken link: ../../../function/doc/reference.html#functionN libs/python/doc/v2/faq.html: broken link: ../tutorial/doc/creating_packages.html, broken link: ../tutorial/doc/reducing_compiling_time.html libs/python/doc/v2/from_python.html: unlinked file libs/python/doc/v2/header.html: unlinked file libs/python/doc/v2/overview.html: unlinked file libs/python/doc/v2/pickle.html: broken link: ../tutorial/doc/extending_wrapped_objects_in_python.html libs/python/doc/v2/rationale.html: broken link: ../../../../../people/dave_abrahams.htm, unlinked file libs/python/pyste/doc/introduction.html: broken link: ../../doc/tutorial/doc/exposing_classes.html libs/python/pyste/doc/policies.html: broken link: ../../doc/tutorial/doc/call_policies.html libs/python/pyste/doc/running_pyste.html: broken link: ../../doc/tutorial/doc/building_hello_world.html libs/python/pyste/index.html: broken link: introduction.html Could you please look over these one more time? -- Aleksey Gurtovoy MetaCommunications Engineering
Aleksey Gurtovoy wrote:
"libraries.html" is a particularly puzzling since setting "boost.root" supposedly should have taken care of it. Oh, it's managed by another parameter, "boost.libraries" :(. OK, adding this to the jamfile and re-generating everything one more time; here's what's left:
libs/python/doc/new-conversions.html: unlinked file libs/python/doc/v2/bibliography.html: unlinked file libs/python/doc/v2/errors.html: broken link: ../../../function/doc/reference.html#functionN libs/python/doc/v2/faq.html: broken link: ../tutorial/doc/creating_packages.html, broken link: ../tutorial/doc/reducing_compiling_time.html libs/python/doc/v2/from_python.html: unlinked file libs/python/doc/v2/header.html: unlinked file libs/python/doc/v2/overview.html: unlinked file libs/python/doc/v2/pickle.html: broken link: ../tutorial/doc/extending_wrapped_objects_in_python.html libs/python/doc/v2/rationale.html: broken link: ../../../../../people/dave_abrahams.htm, unlinked file libs/python/pyste/doc/introduction.html: broken link: ../../doc/tutorial/doc/exposing_classes.html libs/python/pyste/doc/policies.html: broken link: ../../doc/tutorial/doc/call_policies.html libs/python/pyste/doc/running_pyste.html: broken link: ../../doc/tutorial/doc/building_hello_world.html libs/python/pyste/index.html: broken link: introduction.html
Could you please look over these one more time?
Will do. Thanks! Cheers, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net
Joel wrote: [...]
Could you please look over these one more time?
Will do. Thanks!
Ok. Except the links to boost.function html files, which I can't find (where are the boost.function html files?), all broken links are fixed. I didn't fix the unlinked files. -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net
Joel writes:
Joel wrote:
[...]
Could you please look over these one more time?
Will do. Thanks!
Ok. Except the links to boost.function html files, which I can't find (where are the boost.function html files?),
They are BoostBook generated as well, and therefore lay in "doc/html/function" now.
all broken links are fixed.
Thank you! Everything in Boost.Python looks clean now.
I didn't fix the unlinked files.
They seem to be stale anyway. Something to cleanup for the next release. -- Aleksey Gurtovoy MetaCommunications Engineering
Aleksey Gurtovoy wrote:
build -----
tools/build/v2/index.html: broken link: ../../../doc/html/bbv2.installation.html, broken link: doc/html/index.html
Fixed.
tools/build/v2/test/railsys/program/Jamfile: tabs in file
Fixed.
tools/build/v2/test/test_system.html: unlinked file
I can hardly do it for this release, sorry.
BoostBook-generated, need to be fixed in sources:
doc/html/bbv2/advanced/jamfiles.html: broken link: ../../doc/extending.html#main_target_rules
Fixed.
doc/html/bbv2/extender.html: broken link: ../../../example/customization
I've fixed this for release. I wonder if it's possible to somehow make the links relative to the *Boostbook sources*, not the the final doc location. That would be a great help for V2.
doc/html/bbv2/howto.html: broken link: ../../../../../more/mailing_lists.htm#jamboost
Fixed.
doc/html/bbv2/installation.html: broken link: ../../../jam_src/index.html#building_bjam, broken link: ../../jam_src/index.html
Fixed.
doc/html/bbv2/tutorial/prebuilt.html: broken link: ../../doc/recipes.html#site_config_targets
Fixed. - Volodya
Vladimir Prus writes:
Aleksey Gurtovoy wrote:
build -----
tools/build/v2/index.html: broken link: ../../../doc/html/bbv2.installation.html, broken link: doc/html/index.html
Fixed.
tools/build/v2/test/railsys/program/Jamfile: tabs in file
Fixed.
tools/build/v2/test/test_system.html: unlinked file
I can hardly do it for this release, sorry.
No problem. In general, "unlinked file" issues are more of "FYI" kind.
BoostBook-generated, need to be fixed in sources:
doc/html/bbv2/advanced/jamfiles.html: broken link: ../../doc/extending.html#main_target_rules
Fixed.
doc/html/bbv2/extender.html: broken link: ../../../example/customization
I've fixed this for release. I wonder if it's possible to somehow make the links relative to the *Boostbook sources*, not the the final doc location. That would be a great help for V2.
It'd be possible to make links relative to _the master XML file that is being built_. But given that it's not uncommon for this master document to be composed from smaller subdocuments, which, in their turn, often lay in subdirectories, I'm not sure that it's not going to make things even more confusing/error-prone.
doc/html/bbv2/howto.html: broken link: ../../../../../more/mailing_lists.htm#jamboost
Fixed.
doc/html/bbv2/installation.html: broken link: ../../../jam_src/index.html#building_bjam, broken link: ../../jam_src/index.html
Fixed.
doc/html/bbv2/tutorial/prebuilt.html: broken link: ../../doc/recipes.html#site_config_targets
Fixed.
Thank you! -- Aleksey Gurtovoy MetaCommunications Engineering
Aleksey Gurtovoy wrote:
doc/html/bbv2/extender.html: broken link: ../../../example/customization
I've fixed this for release. I wonder if it's possible to somehow make the links relative to the *Boostbook sources*, not the the final doc location. That would be a great help for V2.
It'd be possible to make links relative to _the master XML file that is being built_. But given that it's not uncommon for this master document to be composed from smaller subdocuments, which, in their turn, often lay in subdirectories, I'm not sure that it's not going to make things even more confusing/error-prone.
It surely would not help, because for boost build docs the master file could be either tools/build/v2/doc/src/userman.xml or doc/src/boost.xml. OTOH, the relative path from v2/doc/src/extending.xml to v2/example/customization is always the same, that's why it would be very handy to have source-relative links. - Volodya
participants (5)
-
Aleksey Gurtovoy -
Daniel Frey -
Doug Gregor -
Joel -
Vladimir Prus