* Perhaps the software can be more advanced and remember if someone has altered any of the SVG segments of code. This way we don't get large swathes of SVG code cluttering up the text area. If you click "(-)", the code collapses again. In other words, there's a little command in the text "Expand SVG code (+)" and if you click the (+), it expands all the code out. * Here's the trick: the next time someone clicks "Edit page" in the nLab, the Instiki software is intelligent and displays the SVG text as a javascript "expand box". * You copy and paste this svg text into the nLab page you are editing. * You draw a picture using your favourite method (TikZ, Inkscape, etc.) Right now I am thinking that the following procedure could work well: I got this hint originally from someone's user page on Wikipedia, but it's covered fully in the PGF manual.Īuthor: Andrew Stacey Format: Markdown Cross-posted from the n-Lab: Bruce Bartlett said:īeen a while since I thought about getting a good graphics engine here in inStiki, but these pictures have got me excited again. The trick, from the pgf manual, is to load the correct output driver _before_ loading the Ti_k_Z package. Compare the picture in the sandbox with the original SVG:įor more examples, see the page of my talk on Comparative Smootheology at the Ottawa conference which is (). However, including SVGs in Instiki doesn't seem to work exactly. There are a few limitations, mainly to do with text, but it seems to work.
Basically, running htlatex (from the TeX4ht package) on a latex document with tikz pictures in produces SVG versions of the pictures. Author: Andrew Stacey Format: Markdown Following on from the discussion on the cafe, I've discovered that tikz (a fairly sophisticated LaTeX picture package) can be converted to SVG.
0 kommentar(er)
