On Sunday, June 28, 2015 at 9:22:48 AM UTC+2, Lex Trotman wrote: > > On 28 June 2015 at 16:26, Jacques Nilo <[email protected] <javascript:>> > wrote: > > This seems to be normal browser behaviour since you told it to load a > new page by the link. > > So either you need section2.html to have a toc too, or you need to > compile everything into the one page and have the links internal. >
I understand your point but I was trying to find a away to edit the 300+ files (converted from an initial chm doc) to replace the link:sectionx.html by xref:XXsectionx and tag sectionx with XXsectionx. Perhaps I'll find some sed trick to soften the pain :-) Still I have a "small" issue with the way <<>> or xref are translated into a pdf document If I modify the example with the following: [[xxxsect1]] === Section 1 Lorem ipsum dolor sit amet, consetetur sadipscing elitr, labore et dolore magna aliquyam erat, sed diam voluptua. See also <<xxxsect2,Section 2>> and then generate the pdf with a2x -v -f pdf master.adoc then when clicking on the link within the pdf it will put the first line at the begining of the paragraph (ie "Lorem ipsum ...") and not at "Section 1" and if I use xref instead, ie See also xref:xxxsect2[Section 2] then when I generate the pdf with the same command as above my pdf doc will have two links, the first one leading to the first line and the second one (automatically generated) leading (as expected) to the section name. See: <https://lh3.googleusercontent.com/-mVbi7eRU3D0/VY-1CNyD9kI/AAAAAAAAABs/bil35eOuonE/s1600/Capture.PNG> Is it possible to fix that ? -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
