From: Robert J. <spa...@gm...> - 2013-02-20 20:56:54
|
Hi guys, I'm trying to add some stuff to the latex docs but got a new installation and can no longer get it to compile. It fails to load any graphics, see terminal output below. I suppose I'm missing some package, anyone got any clues? Regards, Robert ---- This is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012/Debian) restricted \write18 enabled. entering extended mode (./documentation.tex LaTeX2e <2011/06/27> Babel <v3.8m> and hyphenation patterns for english, dumylang, nohyphenation, lo aded. (/usr/share/texlive/texmf-dist/tex/latex/base/report.cls Document Class: report 2007/10/19 v1.4h Standard LaTeX document class (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)) (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty) (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty) (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty) (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)) (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def)) (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty (/usr/share/texlive/texmf-dist/tex/latex/base/utf8.def (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.dfu) (/usr/share/texlive/texmf-dist/tex/latex/base/ot1enc.dfu) (/usr/share/texlive/texmf-dist/tex/latex/base/omsenc.dfu))) (/usr/share/texmf/tex/latex/lm/lmodern.sty) (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty (/usr/share/texlive/texmf-dist/tex/generic/babel/english.ldf (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def))) (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg) (/usr/share/texlive/texmf-dist/tex/latex/graphics/dvips.def))) (/usr/share/texlive/texmf-dist/tex/latex/hyphenat/hyphenat.sty) (/usr/share/texlive/texmf-dist/tex/latex/wrapfig/wrapfig.sty) (/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty) (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty) (./documentation.aux LaTeX Warning: Label `Main/Arranger' multiply defined. LaTeX Warning: Label `Main/Arranger' multiply defined. ) (/usr/share/texmf/tex/latex/lm/t1lmr.fd) *geometry* driver: auto-detecting *geometry* detected driver: dvips ! LaTeX Error: File `pics/muse2' not found. See the LaTeX manual or LaTeX Companion for explanation. Type H <return> for immediate help. ... l.156 ...graphics[width=1.0\textwidth]{pics/muse2} ? ---------- |
From: Tim E. R. <ter...@ro...> - 2013-02-21 01:21:37
|
On February 20, 2013 09:56:47 PM Robert Jonsson wrote: > Hi guys, > > I'm trying to add some stuff to the latex docs but got a new > installation and can no longer get it to compile. > > It fails to load any graphics, see terminal output below. > I suppose I'm missing some package, anyone got any clues? > > Regards, > Robert Funny, I was looking at the tex file yesterday too. It's about time we started building the pdf for the users. My only question was what command should we use to build it? I built the docs last night several times, using ConText then pdflatex then texi2pdf each with no problem. Flo says in the tex file to use ConText. But it built fine without ConText, using pdflatex or texi2pdf , and ConText required me to install it, which brought in a whole bunch of other packages. So can we do OK with just pdflatex or texi2pdf ? What command did you use to build it? About the error, my guess is since that pic is the first one listed in the tex file, it may be looking in the wrong folder for the pics. I don't know how to tell it to look elsewhere, but can you try a simple test putting ./ in front of it, like "./pics/muse2" ? At least that should tell you if it's a folder problem, right? Tim. > > ---- > This is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012/Debian) > restricted \write18 enabled. > entering extended mode > (./documentation.tex > LaTeX2e <2011/06/27> > Babel <v3.8m> and hyphenation patterns for english, dumylang, nohyphenation, > lo aded. > (/usr/share/texlive/texmf-dist/tex/latex/base/report.cls > Document Class: report 2007/10/19 v1.4h Standard LaTeX document class > (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)) > (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty) > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty) > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty) > (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty > (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def)) > (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty > (/usr/share/texlive/texmf-dist/tex/latex/base/utf8.def > (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.dfu) > (/usr/share/texlive/texmf-dist/tex/latex/base/ot1enc.dfu) > (/usr/share/texlive/texmf-dist/tex/latex/base/omsenc.dfu))) > (/usr/share/texmf/tex/latex/lm/lmodern.sty) > (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty > (/usr/share/texlive/texmf-dist/tex/generic/babel/english.ldf > (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def))) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) > (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/dvips.def))) > (/usr/share/texlive/texmf-dist/tex/latex/hyphenat/hyphenat.sty) > (/usr/share/texlive/texmf-dist/tex/latex/wrapfig/wrapfig.sty) > (/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty) > (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty) > (./documentation.aux > > LaTeX Warning: Label `Main/Arranger' multiply defined. > > > LaTeX Warning: Label `Main/Arranger' multiply defined. > > ) (/usr/share/texmf/tex/latex/lm/t1lmr.fd) > *geometry* driver: auto-detecting > *geometry* detected driver: dvips > > ! LaTeX Error: File `pics/muse2' not found. > > See the LaTeX manual or LaTeX Companion for explanation. > Type H <return> for immediate help. > ... > > l.156 ...graphics[width=1.0\textwidth]{pics/muse2} > > ? > ---------- > > ---------------------------------------------------------------------------- > -- 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 > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer |
From: Tim E. R. <ter...@ro...> - 2013-02-21 01:33:39
|
On February 20, 2013 08:21:14 PM Tim E. Real wrote: > On February 20, 2013 09:56:47 PM Robert Jonsson wrote: > > Hi guys, > > > > I'm trying to add some stuff to the latex docs but got a new > > installation and can no longer get it to compile. > > > > It fails to load any graphics, see terminal output below. > > I suppose I'm missing some package, anyone got any clues? > > > > Regards, > > Robert > > Funny, I was looking at the tex file yesterday too. > > It's about time we started building the pdf for the users. Wanted to mention also we should give a choice of PDF or HTML, or to avoid the hassle of choosing, let's just go ahead and build both? And we must link them to the Help menu of MusE so that they open. It'd be really cool if we could do context sensitive help, somehow ? ... Tonight I will try to eliminate the dependency on Doxygen, since the HTML docs that MusE currently builds from the old/muse.sgm file are waaaay out of date, so I think we can trash them now. Tim. > My only question was what command should we use to build it? > > I built the docs last night several times, using ConText then pdflatex > then texi2pdf each with no problem. > > Flo says in the tex file to use ConText. > But it built fine without ConText, using pdflatex or texi2pdf , > and ConText required me to install it, which brought in a whole > bunch of other packages. > So can we do OK with just pdflatex or texi2pdf ? > > What command did you use to build it? > > About the error, my guess is since that pic is the first one listed in > the tex file, it may be looking in the wrong folder for the pics. > I don't know how to tell it to look elsewhere, but can you try > a simple test putting ./ in front of it, like "./pics/muse2" ? > At least that should tell you if it's a folder problem, right? > > Tim. > > > ---- > > This is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012/Debian) > > > > restricted \write18 enabled. > > > > entering extended mode > > (./documentation.tex > > LaTeX2e <2011/06/27> > > Babel <v3.8m> and hyphenation patterns for english, dumylang, > > nohyphenation, lo aded. > > (/usr/share/texlive/texmf-dist/tex/latex/base/report.cls > > Document Class: report 2007/10/19 v1.4h Standard LaTeX document class > > (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)) > > (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty > > (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty) > > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty) > > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty) > > (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)) > > (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty > > (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def)) > > (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty > > (/usr/share/texlive/texmf-dist/tex/latex/base/utf8.def > > (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.dfu) > > (/usr/share/texlive/texmf-dist/tex/latex/base/ot1enc.dfu) > > (/usr/share/texlive/texmf-dist/tex/latex/base/omsenc.dfu))) > > (/usr/share/texmf/tex/latex/lm/lmodern.sty) > > (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty > > (/usr/share/texlive/texmf-dist/tex/generic/babel/english.ldf > > (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def))) > > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty > > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty > > (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) > > (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg) > > (/usr/share/texlive/texmf-dist/tex/latex/graphics/dvips.def))) > > (/usr/share/texlive/texmf-dist/tex/latex/hyphenat/hyphenat.sty) > > (/usr/share/texlive/texmf-dist/tex/latex/wrapfig/wrapfig.sty) > > (/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty) > > (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty) > > (./documentation.aux > > > > LaTeX Warning: Label `Main/Arranger' multiply defined. > > > > > > LaTeX Warning: Label `Main/Arranger' multiply defined. > > > > ) (/usr/share/texmf/tex/latex/lm/t1lmr.fd) > > *geometry* driver: auto-detecting > > *geometry* detected driver: dvips > > > > ! LaTeX Error: File `pics/muse2' not found. > > > > See the LaTeX manual or LaTeX Companion for explanation. > > Type H <return> for immediate help. > > > > ... > > > > l.156 ...graphics[width=1.0\textwidth]{pics/muse2} > > > > ? > > ---------- > > > > -------------------------------------------------------------------------- > > -- -- 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 > > Lmu...@li... > > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > ---------------------------------------------------------------------------- > -- 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 > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer |
From: Orcan O. <oge...@gm...> - 2013-02-21 04:16:44
|
On Wed, Feb 20, 2013 at 8:21 PM, Tim E. Real wrote: > On February 20, 2013 09:56:47 PM Robert Jonsson wrote: >> Hi guys, >> >> I'm trying to add some stuff to the latex docs but got a new >> installation and can no longer get it to compile. >> >> It fails to load any graphics, see terminal output below. >> I suppose I'm missing some package, anyone got any clues? >> >> Regards, >> Robert > > Funny, I was looking at the tex file yesterday too. > > It's about time we started building the pdf for the users. > My only question was what command should we use to build it? > > I built the docs last night several times, using ConText then pdflatex > then texi2pdf each with no problem. > > Flo says in the tex file to use ConText. > But it built fine without ConText, using pdflatex or texi2pdf , > and ConText required me to install it, which brought in a whole > bunch of other packages. > So can we do OK with just pdflatex or texi2pdf ? > > What command did you use to build it? > pdflatex is pretty much the standard. I used for my thesis; still use it for letters, papers etc. I am pretty sure there is an easy way to do it in cmake. Don't know how (yet) though. I'll take a look. Best, Orcan |
From: Dennis S. <mus...@wi...> - 2013-02-21 16:15:59
Attachments:
Makefile
|
Hi all, Not tested with the muse docs. But I usually use a makefile like the attached one in order to trigger pdflatex. Allows to build single pdfs or all files: make clean make all make singlefile.pde Best, Dennis On Wed, 20 Feb 2013 23:16:17 -0500 Orcan Ogetbil <oge...@gm...> wrote: > On Wed, Feb 20, 2013 at 8:21 PM, Tim E. Real wrote: > > On February 20, 2013 09:56:47 PM Robert Jonsson wrote: > >> Hi guys, > >> > >> I'm trying to add some stuff to the latex docs but got a new > >> installation and can no longer get it to compile. > >> > >> It fails to load any graphics, see terminal output below. > >> I suppose I'm missing some package, anyone got any clues? > >> > >> Regards, > >> Robert > > > > Funny, I was looking at the tex file yesterday too. > > > > It's about time we started building the pdf for the users. > > My only question was what command should we use to build it? > > > > I built the docs last night several times, using ConText then pdflatex > > then texi2pdf each with no problem. > > > > Flo says in the tex file to use ConText. > > But it built fine without ConText, using pdflatex or texi2pdf , > > and ConText required me to install it, which brought in a whole > > bunch of other packages. > > So can we do OK with just pdflatex or texi2pdf ? > > > > What command did you use to build it? > > > > pdflatex is pretty much the standard. I used for my thesis; still use > it for letters, papers etc. I am pretty sure there is an easy way to > do it in cmake. Don't know how (yet) though. I'll take a look. > > Best, > 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 > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer |
From: Orcan O. <oge...@gm...> - 2013-02-21 05:24:42
|
On Wed, Feb 20, 2013 at 11:16 PM, Orcan Ogetbil wrote: > On Wed, Feb 20, 2013 at 8:21 PM, Tim E. Real wrote: >> On February 20, 2013 09:56:47 PM Robert Jonsson wrote: >>> Hi guys, >>> >>> I'm trying to add some stuff to the latex docs but got a new >>> installation and can no longer get it to compile. >>> >>> It fails to load any graphics, see terminal output below. >>> I suppose I'm missing some package, anyone got any clues? >>> >>> Regards, >>> Robert >> >> Funny, I was looking at the tex file yesterday too. >> >> It's about time we started building the pdf for the users. >> My only question was what command should we use to build it? >> >> I built the docs last night several times, using ConText then pdflatex >> then texi2pdf each with no problem. >> >> Flo says in the tex file to use ConText. >> But it built fine without ConText, using pdflatex or texi2pdf , >> and ConText required me to install it, which brought in a whole >> bunch of other packages. >> So can we do OK with just pdflatex or texi2pdf ? >> >> What command did you use to build it? >> > > pdflatex is pretty much the standard. I used for my thesis; still use > it for letters, papers etc. I am pretty sure there is an easy way to > do it in cmake. Don't know how (yet) though. I'll take a look. > 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. 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. I hope you like it. If not, feel free to revert. Please let me know if you have any questions. I have done my fair share of work in LaTeX back in the day :) Best, Orcan |
From: Robert J. <spa...@gm...> - 2013-02-21 07:53:35
|
Hi guys, 2013/2/21 Orcan Ogetbil <oge...@gm...>: >>> I built the docs last night several times, using ConText then pdflatex >>> then texi2pdf each with no problem. >>> >>> What command did you use to build it? Ah, yes, I'm a fool. I tried with latex. Actually thought I had tried with pdflatex but probably not, trying not it worked fine. >> >> pdflatex is pretty much the standard. I used for my thesis; still use >> it for letters, papers etc. I am pretty sure there is an easy way to >> do it in cmake. Don't know how (yet) though. I'll take a look. >> > > 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. > > 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? ;) 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 ;) Thanks! Robert |
From: Tim E. R. <ter...@ro...> - 2013-02-21 08:57:57
|
On February 21, 2013 08:53:28 AM Robert Jonsson wrote: > Hi guys, > > 2013/2/21 Orcan Ogetbil <oge...@gm...>: > >>> I built the docs last night several times, using ConText then pdflatex > >>> > >>> then texi2pdf each with no problem. > >>> > >>> What command did you use to build it? > > Ah, yes, I'm a fool. I tried with latex. Actually thought I had tried > with pdflatex but probably not, trying not it worked fine. Er, actually you probably weren't running from the doc directory? So it couldn't find the pics. I wrote: >Tonight I will try to eliminate the dependency on Doxygen, since > the HTML docs that MusE currently builds from the old/muse.sgm file > are waaaay out of date, so I think we can trash them now. Yikes! All these years MusE has required Doxygen - and it wasn't even used for anything! The old .sgm file isn't even compiled! The old HTML docs are pre-fab in /share/html and just simply installed! So Doxygen was totally useless! I removed it completely here. Instead I used find_package(LATEX) and created a CMakeLists.txt file in the doc folder. The file looks like this: ================================= # # Run the pdf converter at least three times to resolve cross-refs # if (ENABLE_PDF_DOCUMENTATION AND PDFLATEX_COMPILER) add_custom_target(build_docs ALL ${PDFLATEX_COMPILER} -output-directory=${PROJECT_BINARY_DIR}/doc ${PROJECT_SOURCE_DIR}/doc/documentation.tex COMMAND ${PDFLATEX_COMPILER} -output-directory=${PROJECT_BINARY_DIR}/doc ${PROJECT_SOURCE_DIR}/doc/documentation.tex COMMAND ${PDFLATEX_COMPILER} -output-directory=${PROJECT_BINARY_DIR}/doc ${PROJECT_SOURCE_DIR}/doc/documentation.tex COMMAND ${PDFLATEX_COMPILER} -output-directory=${PROJECT_BINARY_DIR}/doc ${PROJECT_SOURCE_DIR}/doc/documentation.tex WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}/doc ) endif (ENABLE_PDF_DOCUMENTATION AND PDFLATEX_COMPILER) ================================= I'm just not entirely sure if I should use add_custom_target() or add_custom_command(). Similar lines (not shown) for the HTML docs, except just single-run. Latex2html tells me there is no documentation.aux file, so links are just little 'squares'. Weird, pdflatex is the one that generates that .aux file. I allow both PDF and HTML but this might (must?) change (see why below). Having success building new docs from our cmake scripts. Will commit tomorrow or so, depending on responses here. > > >> pdflatex is pretty much the standard. I used for my thesis; still use > >> it for letters, papers etc. I am pretty sure there is an easy way to > >> do it in cmake. Don't know how (yet) though. I'll take a look. > > > > 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. > > > > 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? ;) > > 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? 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. Till tomorrow. G'night. Tim. > > Thanks! > Robert > |
From: Robert J. <spa...@gm...> - 2013-02-21 09:53:09
|
>> 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 ;) I realize this could be interpreted as somewhat arrogant and ungrateful which definitely isn't the case. I'm very happy to have it working and also learning a bit more about how latex works. It was more a nod at academic solutions and their tendency to be somewhat convoluted but still very good, once you learn :) Regards, Robert |
From: Orcan O. <oge...@gm...> - 2013-02-21 13:12:27
|
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 <oge...@gm...>: >> > 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 |
From: Robert J. <spa...@gm...> - 2013-02-21 13:38:50
|
2013/2/21 Orcan Ogetbil <oge...@gm...>: >> >> 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 Nice, thanks! <...> >> >> 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. Indeed, I guess it's more a question off where to spend the time making it look nice. It seems likely each output type may need some tweaks in the source to get it look as we want. A quick test suggests html looks ok, so maybe it's no big deal. Regards, Robert |
From: Dennis S. <mus...@wi...> - 2013-02-21 16:20:00
|
On Thu, 21 Feb 2013 03:57:40 -0500 "Tim E. Real" <ter...@ro...> wrote: > > 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? Ah you gotta understand how Tex and its packages work. Tex is a 1-pass compiler. So during the first run many packages create auxilary files which are read on successive runs. e.g. first pass collects the amount of pages, second pass inserts the page count into the document. The same with references, ToC, cites, ... Usually if the document didn't change much it's ok to run Tex only once as most auxilary files are still valid. They are recreated every time so if things don't look right it can often be fixed by another run. Best, Dennis |
From: Dennis S. <mus...@wi...> - 2013-02-21 16:22:36
|
On Thu, 21 Feb 2013 03:57:40 -0500 "Tim E. Real" <ter...@ro...> wrote: > 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. Like I said back then. Tex really is no html factory. html may work okay but many things will only work for pdf. Tex is a markup macro language for printed documents. It's not meant to be transformed to another markup language with totaly different features and design ... Dennis |
From: Robert J. <spa...@gm...> - 2013-02-21 10:25:37
|
Hi Tim, 2013/2/21 Tim E. Real <ter...@ro...>: > On February 21, 2013 08:53:28 AM Robert Jonsson wrote: >> Hi guys, >> >> 2013/2/21 Orcan Ogetbil <oge...@gm...>: >> >>> I built the docs last night several times, using ConText then pdflatex >> >>> >> >>> then texi2pdf each with no problem. >> >>> >> >>> What command did you use to build it? >> >> Ah, yes, I'm a fool. I tried with latex. Actually thought I had tried >> with pdflatex but probably not, trying not it worked fine. > > Er, actually you probably weren't running from the doc directory? > So it couldn't find the pics. It was definitely from the right dir, still I think I got it now. Will try more when I get home. <...> > Having success building new docs from our cmake scripts. > Will commit tomorrow or so, depending on responses here. > Sounds good! But please don't make doc building mandatory, installing latex takes a lot of space on my machine atleast so better not impose it on all. I think we should check in a prebuilt pdf version from time to time to make it easier for people to access. >> >> >> pdflatex is pretty much the standard. I used for my thesis; still use >> >> it for letters, papers etc. I am pretty sure there is an easy way to >> >> do it in cmake. Don't know how (yet) though. I'll take a look. >> > >> > 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. Yes I hope that can be improved, underlines would be ideal, feels kind of standard. > >> > >> > 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? ;) >> >> 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? > > Anyway I leave you with some thoughts... > > Should we pick PDF or HTML only and stick with it? If we need to chose I'd prefer PDF, everybody has a reader for pdf nowdays and it's very readable. > 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? > Good point. It's an Interesting improvement which I suppose needs a way to seek into the material. Suggests separate html files but maybe it's doable with indexing even for pdf files? Might be viewer dependent.. > 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. I agree. Having the material split up in small bits is very annoying. Haven't tried export to html though so I don't know what we are up against. Regards, Robert |
From: Tim E. R. <ter...@ro...> - 2013-02-21 21:27:29
|
On February 21, 2013 11:25:31 AM Robert Jonsson wrote: > Sounds good! But please don't make doc building mandatory, installing > latex takes a lot of space on my machine atleast so better not impose > it on all. No problem, implemented that from the start :) > > I think we should check in a prebuilt pdf version from time to time to > make it easier for people to access. Exactly. I was going to mention this. Good idea. Tim. |
From: Florian J. <flo...@we...> - 2013-02-21 14:36:02
Attachments:
signature.asc
|
Hi :) >> How about building all 3 combinations: >> -PDF >> -html one page >> -html multiple pages >> >> It's not like the HTML files take too much space. I'd like to have all three. Html multiple pages should have one HTML document per section, i'd say, so each single page is some screenful of text. And I said something about using context? Can't remember ;) i have committed like i prefer the links. One could make the in-document-links black, however... Dunno :) > > Indeed, I guess it's more a question off where to spend the time > making it look nice. i'd suggest we tune it for the printed PDF output, and let tex2html do its stuff automagically :) greetings flo |
From: Tim E. R. <ter...@ro...> - 2013-02-21 21:08:09
|
On February 21, 2013 03:35:45 PM Florian Jung wrote: > Hi :) > > >> How about building all 3 combinations: > >> -PDF > >> -html one page > >> -html multiple pages > >> > >> It's not like the HTML files take too much space. > > I'd like to have all three. > Html multiple pages should have one HTML document per section, i'd say, > so each single page is some screenful of text. Ah yes, we can do that. I mentioned the latex2html -split option where I simply used zero. I hope there's a way to automatically do it the way Flo says else we do it manually for each section? Help says: "-split num Stop making separate files at this depth (say "-split 0" for one huge HTML file)." Depth? > > And I said something about using context? Can't remember ;) Sorry my mistake you said pdflatex in the tex file. The Context thing was a snippet of text I borrowed from muse_evolution README and put in ours. I've updated the README here and will further depending on the outcomes here. Seems Context is a product. Tim. > > i have committed like i prefer the links. One could make the > in-document-links black, however... Dunno :) > > > Indeed, I guess it's more a question off where to spend the time > > making it look nice. > > i'd suggest we tune it for the printed PDF output, and let tex2html do > its stuff automagically :) > > greetings > flo |
From: Tim E. R. <ter...@ro...> - 2013-02-21 21:54:27
|
On February 21, 2013 03:35:45 PM Florian Jung wrote: > Hi :) > > >> How about building all 3 combinations: > >> -PDF > >> -html one page > >> -html multiple pages > >> > >> It's not like the HTML files take too much space. > > I'd like to have all three. > Html multiple pages should have one HTML document per section, i'd say, > so each single page is some screenful of text. > > And I said something about using context? Can't remember ;) > > i have committed like i prefer the links. One could make the > in-document-links black, however... Dunno :) Yay! Thanks. Blue works for me. Thanks for the pre-built too, which we agreed was a good idea. Now to install it via cmake. Hmm... new cmake option?: "Install pre-built PDF or re-build the PDF" Naaah, why bother offering to rebuild at all? They can do that on their own if they wish. But my concern was binaries in a source tree are... undesirable. Viruses? But I suppose that's being too cautious here. It's only docs :) So lets just ship and install the pre-built docs. Agreed? Including the HTML and whatever formats they /choose/ to install. Bonus: That eliminates the need for all this cmake building stuff and makes my task easier. Ah yes, this is looking much smoother now. Thanks! Tim. > > > Indeed, I guess it's more a question off where to spend the time > > making it look nice. > > i'd suggest we tune it for the printed PDF output, and let tex2html do > its stuff automagically :) > > greetings > flo |
From: Florian J. <flo...@we...> - 2013-02-21 20:25:47
Attachments:
signature.asc
|
Am 21.02.2013 17:22, schrieb Dennis Schulmeister: > On Thu, 21 Feb 2013 03:57:40 -0500 > "Tim E. Real" <ter...@ro...> wrote: > >> 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. > > Like I said back then. Tex really is no html factory. html may work > okay but many things will only work for pdf. Tex is a markup macro > language for printed documents. It's not meant to be transformed to > another markup language with totaly different features and design ... yes. Just to repeat myself: primary goal should be to create a good pdf handbook, which is printable and looks nice on-screen. generating HTML from it would be nice, but definitely not the goal, and it will definitely not work optimally. greetings flo > > Dennis > > ------------------------------------------------------------------------------ > 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 > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > |
From: Tim E. R. <ter...@ro...> - 2013-02-21 21:16:25
|
On February 21, 2013 09:25:34 PM Florian Jung wrote: > Am 21.02.2013 17:22, schrieb Dennis Schulmeister: > > On Thu, 21 Feb 2013 03:57:40 -0500 > > > > "Tim E. Real" <ter...@ro...> wrote: > >> 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. > > > > Like I said back then. Tex really is no html factory. html may work > > okay but many things will only work for pdf. Tex is a markup macro > > language for printed documents. It's not meant to be transformed to > > another markup language with totaly different features and design ... > > yes. Just to repeat myself: primary goal should be to create a good pdf > handbook, which is printable and looks nice on-screen. > > generating HTML from it would be nice, but definitely not the goal, and > it will definitely not work optimally. Agreed. PDF foremost for looks but.... Question though, if we create some context-sensitive help system, can a PDF viewer be told to open at an exact spot or reference in the file? okular --help -p, --page <number> Page of the document to be shown Hmm... Not optimal but workable I suppose. Tim. > > greetings > flo > > > Dennis > > |
From: Tim E. R. <ter...@ro...> - 2013-02-21 21:23:41
|
On February 21, 2013 04:16:06 PM Tim E. Real wrote: > On February 21, 2013 09:25:34 PM Florian Jung wrote: > > Am 21.02.2013 17:22, schrieb Dennis Schulmeister: > > > On Thu, 21 Feb 2013 03:57:40 -0500 > > > > > > "Tim E. Real" <ter...@ro...> wrote: > > >> 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. > > > > > > Like I said back then. Tex really is no html factory. html may work > > > okay but many things will only work for pdf. Tex is a markup macro > > > language for printed documents. It's not meant to be transformed to > > > another markup language with totaly different features and design ... > > > > yes. Just to repeat myself: primary goal should be to create a good pdf > > handbook, which is printable and looks nice on-screen. > > > > generating HTML from it would be nice, but definitely not the goal, and > > it will definitely not work optimally. > > Agreed. PDF foremost for looks but.... > > Question though, if we create some context-sensitive help system, > can a PDF viewer be told to open at an exact spot or reference in the file? > > okular --help > -p, --page <number> Page of the document to be shown > > Hmm... Not optimal but workable I suppose. Hey wait, if we instead use a library to open the PDF we could hopefully do anything we want in our context-sensitive system, right? Tim. > > Tim. > > > greetings > > flo > > > > > Dennis > |
From: Dennis S. <mus...@wi...> - 2013-02-21 23:12:58
|
On Thu, 21 Feb 2013 16:23:24 -0500 "Tim E. Real" <ter...@ro...> wrote: > Hey wait, if we instead use a library to open the PDF we could hopefully > do anything we want in our context-sensitive system, right? Great idea. :-) Dunno though if pdflatex creates anchors for each heading by default. Dennis |
From: Orcan O. <oge...@gm...> - 2013-02-22 00:18:04
|
On Thu, Feb 21, 2013 at 6:12 PM, Dennis Schulmeister wrote: > On Thu, 21 Feb 2013 16:23:24 -0500 > "Tim E. Real" <ter...@ro...> wrote: > >> Hey wait, if we instead use a library to open the PDF we could hopefully >> do anything we want in our context-sensitive system, right? > > Great idea. :-) Dunno though if pdflatex creates anchors for each > heading by default. > I am not sure either. HTML might work easier with this case. Note that we need to specify the docdir as a cmake argument as each distro puts their documentation files at different places. Cheers, Orcan |
From: Tim E. R. <ter...@ro...> - 2013-02-22 04:54:21
|
On February 21, 2013 07:17:35 PM Orcan Ogetbil wrote: > On Thu, Feb 21, 2013 at 6:12 PM, Dennis Schulmeister wrote: > > On Thu, 21 Feb 2013 16:23:24 -0500 > > > > "Tim E. Real" <ter...@ro...> wrote: > >> Hey wait, if we instead use a library to open the PDF we could hopefully > >> > >> do anything we want in our context-sensitive system, right? > > > > Great idea. :-) Dunno though if pdflatex creates anchors for each > > heading by default. > > I am not sure either. HTML might work easier with this case. Note that > we need to specify the docdir as a cmake argument as each distro puts > their documentation files at different places. > > Cheers, > Orcan > Hm, actually, PDF or HTML we would have to use a library for context-sensitive stuff, no?: How else to avoid opening multiple copies each time (context key +) F1 is hit? Else what is likelihood we could 'talk' to a running viewer process and tell it "go here"? Tim. |