Randy McMurchy wrote: > I'm not sure I understand what is wrong with the PDF output. > How does this differ from HTML output? They both are simply > a link that you click on with your mouse. If you're reading > *either* from hard-copy, you can't determine what the link > is (using your method proposed above). Why does PDF need to > be different? > > I suppose I don't understand what you are trying to propose > for the PDF links (or why they must be different than the HTML).
I just downloaded the 6.1 version of the pdf. In page 52 (54th physical page): "Refer to ../../../../lfs/view/stable/chapter07/bootscripts.html for more information on the LFS-Bootscripts package." IMO, pdfs are designed for printing on paper for reading offline with optional annotating by the reader. That sort of link is not appropriate for a printed document. I guess I had a misunderstanding how links were rendered in pdf documents. I thought they were something like: text of link (url of link) I think they should be that way and I'm pretty sure I saw them that way in some pdf documents. That said, this shouldn't take our time right now. pdf is not our primary medium. I think we might be able to handle this at the appropriate time with some clever xslt processing though. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
