Stuart, do you have any other suggestions to make it compliant with your new installation scheme/proposal?
If not I would re-zip it using mode 755 fore the Python script and publish the new releases. Cheers Henrik On Feb 7, 7:18 pm, Stuart Rackham <[email protected]> wrote: > On 07/02/11 22:04, Henrik wrote: > > > > > Good to have it checked on a non-windows system as well. It appears > > the fill options requires quotes on Linux as the # character may be > > special to the shell. > > > Could you please replace the filter style in aafigure-filter.conf > > with: > > > [aafigure-filter-style] > > aafigure-style=template="aafigure- > > block",subs=(),posattrs=("style","target"),filter='aafig2img.py > > {verbose?-v} -o "{outdir={indir}}/{imagesdir=}{imagesdir?/}{target}" - > > F{format={basebackend-docbook!png}{basebackend-docbook?svg}}{fill? -- > > fill "{fill}"}{foreground? --foreground "{foreground}"}{background? -- > > background "{background}"}{scaling? --scale {scaling}}{aspect? -- > > aspect {aspect}}{linewidth? --linewidth {linewidth}}{textual-option? -- > > textual}{proportional-option? --proportional}{fixed-option? --fixed} > > -' > > > ad run it again? > > Ran without errors or warnings and the output looks good. > > > > > Once this has been checked I can re-zip it with the execute flag set. > > > Cheers > > > Henrik > > > On Feb 7, 2:35 pm, Stuart Rackham<[email protected]> wrote: > >> Hi Henrik > > >> - Installed python-aafigure package on my Xubuntu 10.04. > >> - Installed filter: > > >> asciidoc --filter -v install ~/tmp/aafigure-filter-1.0.zip > > >> There's a bug in my unzip routine: it does not restore the the aafig2img.py > >> execute permission (it would have failed anyway though as aafig2img.py > >> does not > >> have execute set in the archive, presumably it was created on Windows?). > > >> I fixed it with: chmod +x aafig2img.py > > >> I can now generate the asciidoc-aafigure-readme.html, but I still get a > >> couple > >> of filter errors: > > >> $ asciidoc asciidoc-aafigure-readme.txt > >> Usage: aafig2img.py [options] inputfile > > >> aafig2img.py: error: --fill option requires an argument > >> asciidoc: WARNING: asciidoc-aafigure-readme.txt: line 232: filter non-zero > >> exit > >> code: "/home/srackham/.asciidoc/filters/aafigure/aafig2img.py" -o > >> "/home/srackham/.asciidoc/filters/aafigure/asciidoc-aafigure-readme__8.png" > >> -Fpng --fill #fff -: returned 2 > >> asciidoc: WARNING: asciidoc-aafigure-readme.txt: line 232: no output from > >> filter: "/home/srackham/.asciidoc/filters/aafigure/aafig2img.py" -o > >> "/home/srackham/.asciidoc/filters/aafigure/asciidoc-aafigure-readme__8.png" > >> -Fpng --fill #fff - > >> Usage: aafig2img.py [options] inputfile > > >> aafig2img.py: error: --fill option requires an argument > >> asciidoc: WARNING: asciidoc-aafigure-readme.txt: line 271: filter non-zero > >> exit > >> code: "/home/srackham/.asciidoc/filters/aafigure/aafig2img.py" -o > >> "/home/srackham/.asciidoc/filters/aafigure/asciidoc-aafigure-readme__9.png" > >> -Fpng --fill #fff --scale 0.8 --textual -: returned 2 > >> asciidoc: WARNING: asciidoc-aafigure-readme.txt: line 271: no output from > >> filter: "/home/srackham/.asciidoc/filters/aafigure/aafig2img.py" -o > >> "/home/srackham/.asciidoc/filters/aafigure/asciidoc-aafigure-readme__9.png" > >> -Fpng --fill #fff --scale 0.8 --textual - > >> Usage: aafig2img.py [options] inputfile > > >> aafig2img.py: error: --foreground option requires an argument > >> asciidoc: WARNING: asciidoc-aafigure-readme.txt: line 328: filter non-zero > >> exit > >> code: "/home/srackham/.asciidoc/filters/aafigure/aafig2img.py" -o > >> "/home/srackham/.asciidoc/filters/aafigure/asciidoc-aafigure-readme__12.png" > >> -Fpng --foreground #ff1050 --aspect 0.7 -: returned 2 > >> asciidoc: WARNING: asciidoc-aafigure-readme.txt: line 328: no output from > >> filter: "/home/srackham/.asciidoc/filters/aafigure/aafig2img.py" -o > >> "/home/srackham/.asciidoc/filters/aafigure/asciidoc-aafigure-readme__12.png" > >> -Fpng --foreground #ff1050 --aspect 0.7 - > > >> Cheers, Stuart > > >> On 07/02/11 16:40, Henrik wrote: > > >>> I published it now on Google Code. Here are the links: > > >>>http://code.google.com/p/asciidoc-aafigure-filter/ > > >>> and > > >>>http://code.google.com/p/asciidoc-ditaa-filter/ > > >>> Cheers > > >>> Henrik > > >>> On Feb 7, 11:54 am, Stuart Rackham<[email protected]> wrote: > >>>> On 07/02/11 14:36, Henrik wrote: > > >>>>> Hi all, > > >>>>> I finalized the implementation of a ditaa and aafigure filter and they > >>>>> are ready to be published. > > >>>>> The challenging question is where to upload and host them so they can > >>>>> be easily found and maintained. Unfortunately Google discontinued the > >>>>> feature of uploading files to Google Groups. > > >>>>> Ideas and suggestions are welcome. > > >>>> You could host it as as a project on Google Code/Github/Sourceforge etc. > >>>> That > >>>> way you also get the source hosted in a public repository. > > >>>> Cheers, Stuart > > >>>>> Henrik > > >>>>> On Feb 2, 4:15 pm, Wilhelm<[email protected]> wrote: > >>>>>> Am 02.02.2011 04:25, schrieb Henrik: > > >>>>>>> Hi all, > > >>>>>>> Inspired by discussions in this thread I trialled both ditaa and > >>>>>>> aafigure. > > >>>>>>> Graphics with ditaa look nice and modern, it supports colour and drop- > >>>>>>> shadows as well as different shapes. Biggest drawback is the missing > >>>>>>> vector graphic output like SVGs. There is an EPS add-on but FOP > >>>>>>> unfortunately does not support EPS for PDF output. So we are stuck > >>>>>>> with PNG only which is less ideal for PDF output. > > >>>>>>> Aafigurehowever supports SVG output so I wrote a filter for AsciiDoc > >>>>>>> but got stuck withaafigure'sinability to load fonts in a robust an > >>>>>>> OS independent way and also the type of SVG it creates. There is a > >>>>>>> work around for the font issue but the SVGs it generates are kind of > >>>>>>> unusable by FOP as they do not contain width and height information. > > >>>>>>> Without such information the viewport cannot be calculated > >>>>>>> automatically and the user has to provide viewport height and width as > >>>>>>> well as content height and width, and this is kind of guesswork and > >>>>>>> images will appear clipped or distorted. > > >>>>>>> If one is happy with PNG output both solutions can be used and I > >>>>>>> should publish these filters shortly. > > >>>>>> This would be very nice, if you do so! > > >>>>>>> Henrik > > >>>>>>> On Dec 28 2010, 3:51 pm, Wilhelm<[email protected]> wrote: > >>>>>>>> Am 27.12.2010 18:52, schrieb Gary F.: > > >>>>>>>>> Re: ditaa and ascii art -> graphics. I installed and tried > >>>>>>>>> ditaa. > >>>>>>>>> Ditaa is > >>>>>>>>> written in java, and has almost no documentation. Its help line is > >>>>>>>>> pretty > >>>>>>>>> much all you get. A quick search for something in Python that might > >>>>>>>>> be more > >>>>>>>>> asciidoc friendly turned this up: > >>>>>>>>>http://packages.python.org/aafigure/manual.html > > >>>>>>>>> The author has provided several plug-ins. Perhaps he can be coaxed > >>>>>>>>> into > >>>>>>>>> providing asciidoc support? > > >>>>>>>> aafigurelooks also very promising to create usefull diagrams. > > >>>>>>>> Since I'm very new to asciidoc, I don't know exactly how to integrate > >>>>>>>> that into asciidoc. But I think aafilter or ditaa can be integrated > >>>>>>>> using the same approch as the graphiz-filter. > > >>>>>>>> -- > >>>>>>>> Wilhelm > > >>>>>> -- > >>>>>> Wilhelm > > -- You received this message because you are subscribed to the Google Groups "asciidoc" group. 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/asciidoc?hl=en.
