A few months ago I experimented with SageTex using Sage 4.7.1 on a virtual machine running on my windows PC and got everything working with little difficulty. I now have had a real Iinux server set up for me running Sage 4.7.2. I have been very careful to replace my old sagetex.sty and remote-sagetex.py with the latest ones, but now run into (at least) two problems.
The first, that I can work around although it is redious, is that sagetex when processing "test.tex" now produces "test.sagetex.sage" rather than "test.sage". When processed using remote-sagetex.py this puts plots into a directory "sage-plots-for-test.sagetex.tex". Unfortunately when running LaTeX on test.tex again LaTeX looks in "sage-plots-for-test.tex" for the plots. A rename can get around this but it is a bit of a pain. The second is probably a problem with our server set up, but my IT support can't track it down. Any plots produced by Sage in PDF or PNG formats are corrupted and unreadable by the appropriate viewer. LaTeX claims that they have been corrupted by ASCII conversion. There is not the same probem with EPS format, but that limits my possible actions.My guess was that the corruption takes place in the transfer from linux server to local (windows) PC. My IT support doesn't know how this might have happened. Are there cached copies on the server of the plots produced to compare with the versions donwloaded by remote- sagetex.py? Or has anyone else come across this problem? Any help at all would be appreciated. Tony -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
