Sorry for reviving the old thread but I've searched quite extensively and
didn't find a better answer.
On Tuesday, July 24, 2012 6:40:59 PM UTC-4, Tomek Kaczanowski wrote:
>
> Hi,
>
> I did it like this:
> /home/tomek/bin/asciidoc-8.6.7/asciidoc.py --attribute
> stylesheet=`pwd`/my_styles.css --backend slidy -a icons -o output.html
> source.txt
>
I tried several things that didn't work but in the end I expected something
like this:
:stylesheet: {docdir}/my_styles.css
to work. Working on distributed documents, it would be best if all the
configuration/meta could be relative or inlined, including CSS, something
that asciidoc is really generally very good at.
I dislike having a README that needs to tell my users how to render
documents properly with long CLI when I could have it in the file itself.
My question: is there something I overlooked? It is possible to inline CSS
w/o custom command line options or asking users to modify stuff in
/etc/asciidoc/? I've tried stylesheet attributes w/o path component,
relative themes, etc. Nothing worked.
Thanks! (btw asciidoc is awesome!)
Context (unfortunately reply was top-posted):
> On 16 Lip, 17:34, carloratm <[email protected]> wrote:
> > Hi all,
> > I am trying to produce a presentation with Slidy backend and a custom
> css.
> >
> > I have placed my css in /et/asciidoc/ and (using --attribute stylesheet)
> it
> > works.
> > Is there a way to specifiy a relative path for the css file?
> > I mean relative to the input file
> >
> > Thank you
>
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/asciidoc?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
