On Jan 14, 2008 12:41 AM, Harald Schilly <[EMAIL PROTECTED]> wrote: > > Inside SAGE_BASE/examples/latex_embed is a small script for including > SAGE code in latex files. This is in my opinion very useful for > creating documents: reduces errors, no copy/paste and therefore takes > less time to write tex files! Parsing and computing is separated and > therefore no computational overhead when editing the file without > changing the sage code. > > I've enhanced the included README to document the functionality, > added support for plots: takes sage-plot objects and "show"s them, it > sets the dpi value to 150 (default is 100) and you can choose the > width of the output graphic. > > Ticket: http://sagetrac.org/sage_trac/ticket/1766 > > Since I didn't found this functionality on the website, this should be > included in the official documentation. > It could also be possible to include this in sage itself (sage -tex > parses the .sout file and sage -texstyle writes the .sty file into the > current directory)
I wanted to check the code out, but is there some easy way to see what's inside .hg files? I don't have the latest release of Sage, and with the one I have: $ hg in ~/Desktop/Downloads/latex_embedding.hg comparing with /home/ondra/Desktop/Downloads/latex_embedding.hg abort: unknown parent 7a0d0b988999! Is there some advantage of using the .hg binary format? If not, one can use "hg export", so that you can actually see the patch. I think only when having some binary files, it is necessary to use .hg, because they cannot be stored in a patch. Ondrej --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
