Adam writes:
> Thanks for reply, guidance and suggestions.
> I agree my cgi has nothing to do with INFOJS_OPT, nor vice versa.
>
> Regarding CSS, I have gone back to the default position, of including
> these inside "org-notes" of org-publish-project-alist, and not referring
> to an external CS
Adam writes:
> Thanks for reply, guidance and suggestions.
> I agree my cgi has nothing to do with INFOJS_OPT, nor vice versa.
>
> Regarding CSS, I have gone back to the default position, of including
> these inside "org-notes" of org-publish-project-alist, and not referring
> to an external CS
Thanks for reply, guidance and suggestions.
I agree my cgi has nothing to do with INFOJS_OPT, nor vice versa.
Regarding CSS, I have gone back to the default position, of including
these inside "org-notes" of org-publish-project-alist, and not referring
to an external CSS,
:style-include-def
Hi Adam,
On Thu, 08 Jul 2010 09:48:11 +0200, Adam wrote:
#+STYLE:
or even
# STYLE:
doing a view source of the HTML published page, shows that it includes
the java stuff of org-export-html-style-export, shown below. I feel my
defined CSS is being somehow compromised.
I also use a style
Hi Adam!
Adam writes:
> The Worg tutorial "Publishing Org-mode files to HTML" ran for me first
> time, so it seems excellent and well written.
>
> However I am trying to use a vanilla CSS, say ssheet1.css, located in
> ~/org/css" as per the tutorial.
>
> With only the following line at the end o
The Worg tutorial "Publishing Org-mode files to HTML" ran for me first
time, so it seems excellent and well written.
However I am trying to use a vanilla CSS, say ssheet1.css, located in
~/org/css" as per the tutorial.
With only the following line at the end of my org file,
#+STYLE:
or
