Description of problem: Publican's internal navigation assumes that a multi-page HTML version of a doc will be available. This makes it difficult to incorporate legacy or upstream documentation in a different format (for example, PDF or ODT) into a Publican-generated website if we do not also have a HTML version available. Actual results: We need either to perform an expensive conversion of the docs to HTML, or to publish the doc in the "files" directory of a Publican document. Expected results: Site navigation links directly to formats other than HTML if that's all that's available.
HSS-QE has reviewed and declined this request. QE for this bug will be handled by IED.
This is actually a much bigger change than I initially thought. It required updating WebSite.pm and most of the web site templates. Lots of QE will then be required for web sites.
Initial code checked in, need to discuss phrasing and layout for marker.
Note: this only works for existing supported formats. To support other fomrats you need to open a separate bug.
(In reply to Jeff Fearn from comment #5) > Note: this only works for existing supported formats. To support other > fomrats you need to open a separate bug. WFM; if we have docs in other formats, we should be able to convert at least to PDF.
Verified with publican-3.9.9-0.fc19.t7.noarch