On Thu, Feb 21, 2013 at 3:57 AM, Tim E. Real wrote:
> On February 21, 2013 08:53:28 AM Robert Jonsson wrote:
>> Hi guys,
>>
>> 2013/2/21 Orcan Ogetbil <[email protected]>:
>> > I added some fancy features to the documentation, such as table of
>> > contents and hyperrefs.
>> > hyperrefs allow you to click on the PDF file to launch a browser to go
>> > to a link directly. They also help jumping around the PDF file by
>> > clicking on the "\ref" references, e.g. to sections, figures.
>> > I also fixed some formatting issues.
>
> Thanks Orcan! Nice work.
>
> I'm not crazy about the red and blue surrounding boxes though.
> I hope pdflatex allows us to tweak these things to use underlines etc.
>
I think those red boxes won't appear on paper when you print the
document. If you want to change the way they look on you PDF viewer,
try adding the following right after
\usepackage{hyperref}
\usepackage{xcolor}
\hypersetup{
colorlinks=false,% hyperlinks will be black
linkbordercolor=blue,% hyperlink borders will be blue
pdfborderstyle={/S/U/W 1}% border style will be underline of width
1pt
}
You might want to play with the hypersetup settings furthermore. See
http://en.wikibooks.org/wiki/LaTeX/Hyperlinks#Customization
>> >
>> > Before building, I recommend removing all the temporary files from the
>> > doc/ directory (basically remove everything but the .tex file). Then
>> > run
>> > $ pdflatex documentation.tex
>> > at least 3 times. This will sort out all the references and labels.
>>
>> You mean knocking your heels together three times? ;)
>>
Haha :) Yeah, and you might need to say "open sesame" at some point.
>> Upon running it just once I got no toc, did it two times more and now
>> the toc is there. I refuse to be amazed ;)
>
> Good grief, is there no way to tell pdflatex to do this for us?
> As you can see above I had to tell cmake to arbitrarily build it four times
> (four for good luck). If not, hopefully some return code from pdflatex that
> we can use?
>
Not that I know of. I'd be curious to know if there is a way to build
it in one shot. I always did it this way.
I am sure I looked it up once and could not find a solution, but it is
possible someone figured a way since.
> Anyway I leave you with some thoughts...
>
> Should we pick PDF or HTML only and stick with it?
> Because if we allow the user to choose both or either, that
> complicates what should happen when the user hits F1 for help.
> And if we ever try to do context-sensitive help we'll need two
> different systems - one to cross-ref PDF and one for HTML.
> Got some ideas for context-sensitive help. How 'bout you?
>
> For HTML, should we do one big file or many small ones?
> Or give the user yet another cmake option?
> I tried both and I prefer the one big file (latex2html -split 0), but then
> this could get really big over time, but then so is the single PDF.
> Many small files is kinda silly, you end up with little pieces of text
> and the user has to click forward/backward a lot. Rather incoherent.
>
How about building all 3 combinations:
-PDF
-html one page
-html multiple pages
It's not like the HTML files take too much space.
Cheers,
Orcan
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
