Hi
I have upgraded to org-mode, but from release_8.0 the old
publishing-function org-publish-org-to-html have been replaced by
org-html-publish-to-html.
This gives me a few issues:
My #+STYLE: content are ignored. I have tried to replace it with
#+HTML-HEAD:, but does change anything.
I use
Benny Simonsen be...@slbs.dk writes:
Hi
I have upgraded to org-mode, but from release_8.0 the old
publishing-function org-publish-org-to-html have been replaced by
org-html-publish-to-html.
This gives me a few issues:
My #+STYLE: content are ignored. I have tried to replace it with
Thank you! That was the hints I need
#+HTML_HEAD_EXTRA and @@html:@@ was what I was looking for.
I will dig more into the manual :)
/Benny
Benny Simonsen be...@slbs.dk writes:
#+HTML-HEAD:, but does change anything.
You have to use an underscore, not a hyphen. Maybe that explains why
nothing happened?
Yours,
Christian
Samuel Wales samolog...@gmail.com writes:
For flexibility and future proofing, it might be worth considering
universal syntax (e.g. $[link ... :attr1 ... :attr2 ... ...]) for
fancy links instead of changing link syntax.
I've called it extensible syntax too.
There are already four completely
Hello Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
tftor...@tftorrey.com (T.F. Torrey) writes:
You don't assign attributes to an image in a paragraph, you assign
attributes to the paragraph itself.
It would be nice if there actually was a way to assign an attribute to a
paragraph,
tftor...@tftorrey.com (T.F. Torrey) writes:
It would be ATTR_HTML: :class XXX. I try to unify syntax for
attributes with syntax for Babel and AFAICT, `html' is the last back-end
to have key=value syntax.
I see that this does not presently work, and the author listed on
ox-html.el is not
#+ATTR_HTML: :options width=\400px\
This is heavier but will be consistent with other back-ends. Otherwise,
there is also:
#+ATTR_HTML: :width 400px
But this requires to have a list of all properties supported.
How about both? I.e. a short-list of common options (class, title, id for
Hello,
Vincent Beffara vbeff...@ens-lyon.fr writes:
#+ATTR_HTML: :options width=\400px\
This is heavier but will be consistent with other back-ends. Otherwise,
there is also:
#+ATTR_HTML: :width 400px
But this requires to have a list of all properties supported.
How about both? I.e.
Hello Nicolas,
Thanks for your prompt reply, though I think our discussion is a little
off-track here, as noted below.
Nicolas Goaziou n.goaz...@gmail.com writes:
tftor...@tftorrey.com (T.F. Torrey) writes:
It would be ATTR_HTML: :class XXX. I try to unify syntax for
attributes with syntax
For flexibility and future proofing, it might be worth considering
universal syntax (e.g. $[link ... :attr1 ... :attr2 ... ...]) for
fancy links instead of changing link syntax.
I've called it extensible syntax too.
Samuel
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
The
Hello,
First, as always, thanks for the prompt reply.
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
tftor...@tftorrey.com (T.F. Torrey) writes:
Where attributes have been assigned to an image in a paragraph, the new
exporter applies those attributes to both the image and a following
tftor...@tftorrey.com (T.F. Torrey) writes:
You don't assign attributes to an image in a paragraph, you assign
attributes to the paragraph itself.
It would be nice if there actually was a way to assign an attribute to a
paragraph, so that the ATTR_HTML: class=XXX syntax would export as p
Hello,
Where attributes have been assigned to an image in a paragraph, the new
exporter applies those attributes to both the image and a following
link.
For example, this:
#+BEGIN_SRC org
#+ATTR_HTML: width=10 alt= [Cool thing]
[[file:cool_thing.jpg]]
Cool thing found here
Hello,
tftor...@tftorrey.com (T.F. Torrey) writes:
Where attributes have been assigned to an image in a paragraph, the new
exporter applies those attributes to both the image and a following
link.
You don't assign attributes to an image in a paragraph, you assign
attributes to the paragraph
Hello everybody,
Org-mode version 7.9.2 (a99402fac
GNU Emacs 24.2.1 (i386-mingw-nt6.1.7601) of 2012-08-29 on MARVIN
When I try to HTML export the whole file the result is as expected.
When I try to HTML export a *subtree*
with the new exporter I get \\ if in the org file there is a newline
Hello,
Giovanni Ridolfi giovanni.rido...@yahoo.it writes:
When I try to HTML export a *subtree*
with the new exporter I get \\ if in the org file there is a newline
You need to update Org. I fixed this several days ago.
Regards,
--
Nicolas Goaziou
Da: Nicolas Goaziou n.goaz...@gmail.com
Inviato: Martedì 6 Novembre 2012 17:48
Giovanni Ridolfi giovanni.rido...@yahoo.it writes:
When I try to HTML export a *subtree*
with the new exporter I get \\ if in the org file there is a newline
I fixed this several days ago.
did you try to
Giovanni Ridolfi giovanni.rido...@yahoo.it writes:
did you try to replicate the bug?
Yes, sir.
I get:
--8---cut here---start-8---
body
div id=content
h1 class=titleI am interested in this/h1
div id=outline-container-1 class=outline-2
19 matches
Mail list logo
