-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch document building to PDF #5
Comments
A quick investigation indicates this may be easier than expected as
versus
Maybe there are two different paths and I've only patched the first one in |
The difference that the trailing slash makes is that it assigns the list of targets (including In the version of starconf.m4.in at a1993b0, I can see that I remember someone mentioning in passing that the current build doesn't build the SGML docs. That's probably wise, since they depend on DSSSL/Jade, which has very unfortunately sunk without trace, to be replaced by its stunted evil twin, XSL. Given that, it might be wise to discard
I've just noticed that the significance of the trailing slash is explained in the |
I had a local patch and a completely clean checkout other than that:
and of course some PDF files were built but only the ones that were in subdirectories. No additional cleverness in the |
@nxg it's the |
@nxg wrote:
No great loss as the XML documents haven't been maintained. OTOH there's MalcolmScanned by iCritical. |
I have moved XML documents discussion to #7. It's off-topic for this one. |
Documents all seem to build now with All the latex documents now use graphicx and they all no longer specify a file extension for the embedded image. @dsberry AST seems to be deliberately forcing postscript output in the makefile. I assume there is a reason it is not picking up the default rules but can it be switched to PDF? (once installed the AST web pages will need to link to the right place but that's a good thing because PDF is better in a web browser than postscript anyhow). |
Star2HTML also seems to hard-wire in Postscript file building. @nxg is that some sort of hack to ensure that the MUD document is installed? Can't the MUD be installed using an explicit |
@nxg Probably should be a separate ticket but SUN/152 has a funky specialist |
Re star2html: yes, star2html hard-wires in a lot of things. star2html is quite clever. Notice the prominent lack of me going anywhere near the thing in the star2html header's history list. |
Re SUN/152: the I don't think there's any deep reason why this Makefile builds |
@nxg It does install the |
Images are still encapsulated postscript in the most part but pdflatex will now be used and will automatically convert the EPS files to PDF. Components that explicitly override the default documentation macros will still build postscript files. This includes Star2HTML, AST and ECHOMOP. This work is associated with Issue #5
I've enabled PDF building in starconf so we'll see whether Jenkins breaks. @grahambell there might be issues if |
I'm making good progress with the migration to PDF but the biggest problem now is latex2html since it ignores .png and .pdf images. Needs to be hacked to copy .png files and convert PDF to PNG. The latter can be done natively in ghostscript using the |
Latex2html uses latex and dvips to generate postscript images from supplied EPS images in order to handle the options for
Option 1 might be the sanest although it feels wrong. The problem with option 2 is that you can't just do it for the externally provided images and it seems like a lot of work. I think I'll probably go with option 1 as it means only changing |
Images are still encapsulated postscript in the most part but pdflatex will now be used and will automatically convert the EPS files to PDF. Many pdflatex installations do not do the automatic conversion. Components that explicitly override the default documentation macros will still build postscript files. This includes Star2HTML, AST and ECHOMOP. This work is associated with Issue #5
Despite commenting on this in #5 I had forgotten that star2html explicitly requests a postscript output file.
Currently the document creation system generates Postscript documents by using latex and dvips. It would be much more convenient if we generated PDF documents directly with pdflatex.
I think this needs:
.ps
target and addition of.pdf
target for LaTeX files.includegraphics
command provided bygraphicx
in LaTeX2e./star/docs
.This seems like a fairly well-constrained task and shouldn't take very long. Many of the documents don't need any changes at all to work.
The text was updated successfully, but these errors were encountered: