#885: Latex "warnings" (errors) when building the thorn guide ------------------------------------+--------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: major | Milestone: ET_2012_05 Component: EinsteinToolkit thorn | Version: Resolution: | Keywords: ------------------------------------+---------------------------------------

Comment (by eschnett):

All but one are corrected.

This last warning occurs while building the reference manual. This includes an appendix (verbatim) from the users' guide. This appendix refers to the main users' guide (via \ref{...}), and this reference cannot be resolved while building the reference manual: {{{ LaTeX Warning: Reference `sect-ThornWriting/DataTypes' on page C22 undefined on }}}

I don't see much value in including this appendix twice; I would just remove it from the reference manual (or from the users' guide).

#885: Latex "warnings" (errors) when building the thorn guide ------------------------------------+--------------------------------------- Reporter: eschnett | Owner: knarf Type: defect | Status: accepted Priority: major | Milestone: ET_2012_05 Component: EinsteinToolkit thorn | Version: Resolution: | Keywords: ------------------------------------+--------------------------------------- Changes (by knarf):

* owner: => knarf * status: new => accepted

#885: Latex "warnings" (errors) when building the thorn guide ------------------------------------+--------------------------------------- Reporter: eschnett | Owner: knarf Type: defect | Status: reopened Priority: major | Milestone: ET_2012_05 Component: EinsteinToolkit thorn | Version: Resolution: | Keywords: ------------------------------------+--------------------------------------- Changes (by eschnett):

* status: closed => reopened * resolution: fixed =>

Comment:

I would rather have a reference that fails in the reference manual (and works fine in the users' guide) than removing information from the user's guide. Currently, the text uses the expression "the usual Cactus types" without explaining any more what they are. Another possible solution for this would have been to write "see section X.Y.Z in the User's Guide".

Also, Ian and I agreed above that it does not really make sense to have the same appendix appear in multiple documents. With the ticket closed, this will likely be forgotten.

If we want to clean up things for the release only, then we should branch.