Activity for Juan
-
Juan created ticket #153
Inconsistent attribute "Fill intensity %"
-
Works! -C is no longer needed. There is no ./configure when downloading a snapshot. I've generated it with autoreconf, without any options.
-
Thanks for your response. Using fig2dev with some options enables the generation of the desired tikz file. Especifically, -F unsets font family and the .tex default is used. Also, -C 1 unsets color one, so the default .tex color is used. I am still puzzled about the -C parameter, since the color list of help description with -h "(0=black, 1=red, etc.)" differs from that of the description in the fig2dev man page. Moreover, the color set to LaTeX default with "-C 1" seems to correspond with the xfig...
-
Thanks for your response. Effectively, fig2dev uses relative paths, and the -i option allows tuning the desired paths. The incorrect tikz in the attached files can be correctly generated by fig2dev -L tikz -i crono/ -F -C 1 crono.fig crono.tikz.
-
Actually, I have never used transfig nor fig2dev. I always exported directly from xfig, sharing the exported versions if needed. However, recently I've been working on shared documents through gitlab, and using its continuous integration capabilities to build the documents on each push to ensure that they build correctly. Thus, ideally, exporting fig files should be part of this building process. So, transfig was my first option to try. I really don't know if transfig is what I need. Writing my own...
-
tikz: exports fail to obey the default values of LaTeX documents
-
tikz: absolute paths to images prevent sharing it
-
xfig/fig2dev: some items not exported to pdftex
-
transfig: "No rule to make..."
1
