Fixing the various minor problems with exporting "ps" image
might take a while.
In the mean time, I'd like to discuss another aspect of
book.pdf generation.
I guess no one uses book.dvi or book.ps? Using pdflatex
to generate pdf directly is faster and produces better result
according to some sources.
(Luatex supports unicode, but we don't require it, yet.)
The problem is that pdflatex can't use ps image directly,
but we already have awk script to do the xpm->ps conversion.
We can do xpm->pdf (or ps->pdf when we generate ps image directly.)
Then we use the \includegraphics command from "graphicsx"
package to replace the out-dated "epsf" package.
With minimal effort we can support pdflatex, while maintaining
compatibility with current latex->dvips->ps2pdf process.
Not a TeX expert my self, so how to define the equivalent thing
with includegraphics?
\def\epsfsize#1#2{.24\textheight}
\let\spadepsffilesave\epsffile
\def\epsffile[#1]#2{\begin{center}\spadepsffilesave[#1]{#2}\end{center}}
- Qian
--
You received this message because you are subscribed to the Google Groups "FriCAS -
computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/fricas-devel/3617c000-57a2-4aa4-9968-adeb678a593f%40gmail.com.
