Hello,
Rick Frankel r...@rickster.com writes:
Also, shouldn't :html-style-include-default be
:html-head-include-default?
The variable and this property should stay html-style-include-default,
or at worst become html-head-include-default-style.
The intent of changing things from html-style...
On Saturday, March 2, 2013, Bastien wrote:
Hi Sean,
Sean O'Halpin sean.ohal...@gmail.com javascript:; writes:
One small point: as we're going to have to change the meta directive
#+STYLE to #+HTML_STYLE, can we change the name to reflect what it
really does in the HTML backend, i.e.
On Tue, Feb 05, 2013 at 02:07:50PM +0100, Suvayu Ali wrote:
Hi Eric,
On Tue, Feb 05, 2013 at 11:20:18PM +1030, Eric S Fraga wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
I have attached a somewhat cleaned up version of what I had so far. You
can apply the patch on top of
Hello,
Mike McLean mike.mcl...@pobox.com writes:
I noticed that it no longer concatenates multiple lines from the file
header. I used to have multiple #+HTML_STYLE: lines in my Org files that
layered in different CSS. The nice thing about designing my CSS this way is
that I have a base style
Hi Bastien,
On Sat, Mar 02, 2013 at 07:14:07PM +0100, Bastien wrote:
Hi Sean,
Sean O'Halpin sean.ohal...@gmail.com writes:
One small point: as we're going to have to change the meta directive
#+STYLE to #+HTML_STYLE, can we change the name to reflect what it
really does in the HTML
On Mon, Mar 4, 2013 at 10:24 AM, Nicolas Goaziou n.goaz...@gmail.comwrote:
Hello,
Mike McLean mike.mcl...@pobox.com writes:
I noticed that it no longer concatenates multiple lines from the file
header. I used to have multiple #+HTML_STYLE: lines in my Org files that
layered in different
Mike McLean mike.mcl...@pobox.com writes:
On Mon, Mar 4, 2013 at 10:24 AM, Nicolas Goaziou n.goaz...@gmail.comwrote:
Hello,
Mike McLean mike.mcl...@pobox.com writes:
I noticed that it no longer concatenates multiple lines from the file
header. I used to have multiple #+HTML_STYLE: lines
On Monday, March 4, 2013, Nicolas Goaziou wrote:
Mike McLean mike.mcl...@pobox.com javascript:; writes:
On Mon, Mar 4, 2013 at 10:24 AM, Nicolas Goaziou
n.goaz...@gmail.comjavascript:;
wrote:
Hello,
Mike McLean mike.mcl...@pobox.com javascript:; writes:
I noticed that it no
Hi Suvayu,
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
$ git grep -i html_style
contrib/lisp/ox-deck.el: (:html-style-extra HTML_STYLE nil
org-html-style-extra newline)
contrib/lisp/ox-s5.el: (:html-style-extra HTML_STYLE nil
org-html-style-extra newline)
doc/org.texi:@cindex
On Sat, Mar 2, 2013 at 6:14 PM, Bastien b...@altern.org wrote:
Hi Sean,
Sean O'Halpin sean.ohal...@gmail.com writes:
One small point: as we're going to have to change the meta directive
#+STYLE to #+HTML_STYLE, can we change the name to reflect what it
really does in the HTML backend, i.e.
Hi Sean,
Sean O'Halpin sean.ohal...@gmail.com writes:
Also, it's just struck me - wouldn't it be more consistent if
ATTR_HTML were HTML_ATTR, ATTR_LATEX were LATEX_ATTR, etc.?
I don't really think so -- ATTR_HTML is more like BEGIN_HTML than
#+HTML_HEAD, which is a global option, not a local
Bastien-
On Sat, Mar 02, 2013 at 07:14:07PM +0100, Bastien wrote:
Done. You can now use HTML_HEAD instead of HTML_STYLE.
Some variables were also renamed, check the details here:
http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=2752ef
In trying to migrate these changes to the slide
Hi Sean,
Sean O'Halpin sean.ohal...@gmail.com writes:
One small point: as we're going to have to change the meta directive
#+STYLE to #+HTML_STYLE, can we change the name to reflect what it
really does in the HTML backend, i.e. insert text verbatim into the
head element? I suggest we rename
Hi Bastien,
Bastien wrote:
Sean O'Halpin sean.ohal...@gmail.com writes:
One small point: as we're going to have to change the meta directive
#+STYLE to #+HTML_STYLE, can we change the name to reflect what it
really does in the HTML backend, i.e. insert text verbatim into the
head element? I
Hi Sébastien,
Sebastien Vauban
wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes:
- html-STYLE-include-default - html-STYLE-include-default
(unchanged)
Fixed, thanks.
--
Bastien
Nicolas Goaziou writes:
[…]
Nicolas, moving the old exporter files to contrib/lisp/ will create
problems for the org-plus-contrib ELPA archive. Can I move them to
contrib/oldexp/ instead?
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD adaptations for
Hello,
Achim Gratz strom...@nexgo.de writes:
Nicolas Goaziou writes:
[…]
Nicolas, moving the old exporter files to contrib/lisp/ will create
problems for the org-plus-contrib ELPA archive. Can I move them to
contrib/oldexp/ instead?
As far as I am concerned, you can. Bastien (CC'ed)
Achim Gratz strom...@nexgo.de writes:
Nicolas, moving the old exporter files to contrib/lisp/ will create
problems for the org-plus-contrib ELPA archive. Can I move them to
contrib/oldexp/ instead?
Yes, please go ahead.
Thanks,
--
Bastien
Bastien writes:
Nicolas, moving the old exporter files to contrib/lisp/ will create
problems for the org-plus-contrib ELPA archive. Can I move them to
contrib/oldexp/ instead?
Yes, please go ahead.
Done, please check that I didn't miss any file.
Regards,
Achim.
--
+[Q+ Matrix-12
Achim Gratz strom...@nexgo.de writes:
Done, please check that I didn't miss any file.
org2rem.el and org-export-generic.el both require org-exp.el. Shouldn't
they go into oldexp, too?
Regards,
--
Nicolas Goaziou
Nicolas Goaziou n.goaz...@gmail.com writes:
Achim Gratz strom...@nexgo.de writes:
Done, please check that I didn't miss any file.
org2rem.el and org-export-generic.el both require org-exp.el. Shouldn't
they go into oldexp, too?
Indeed, done.
--
Bastien
On Fri, Feb 8, 2013 at 4:45 PM, Sebastien Vauban
wxhgmqzgw...@spammotel.com wrote:
Sean O'Halpin wrote:
I suggest we rename it to #+HTML_HEAD.
But I'd like to propose HTML_HEADER instead (?), to mirror what LaTeX_HEADER
does -- at least, if that one still exists, which I'm not sure about
Hello,
Sean O'Halpin sean.ohal...@gmail.com writes:
This raises another question which is more about Org document export
headers in general: why do we have specific document headers for LaTeX
and HTML? Because we need to able to insert raw markup at specific
points in the exported document.
Achim Gratz strom...@nexgo.de writes:
Nicolas Goaziou writes:
[…]
Nicolas, moving the old exporter files to contrib/lisp/ will create
problems for the org-plus-contrib ELPA archive. Can I move them to
contrib/oldexp/ instead?
I recommend contrib/obsolete/ or contrib/attic/.
Regards,
On Sat, Feb 9, 2013 at 1:56 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
Sean O'Halpin sean.ohal...@gmail.com writes:
This raises another question which is more about Org document export
headers in general: why do we have specific document headers for LaTeX
and HTML? Because we
Sean O'Halpin sean.ohal...@gmail.com writes:
I haven't made myself clear. I'm not suggesting a general concept of
head. What I am suggesting is that the back-ends handle these
back-end specific concepts themselves, rather than add more buffer
keywords for every new exporter.
Each back-end
Nicolas Goaziou n.goaz...@gmail.com writes:
Sean O'Halpin sean.ohal...@gmail.com writes:
You would avoid having to add document level keywords such as
HTML_STYLE and MAN_CLASS_OPTIONS for new exporters. It would be the
back-end's responsibility to validate and document these options. My
Great work on the new exporter!
One small point: as we're going to have to change the meta directive
#+STYLE to #+HTML_STYLE, can we change the name to reflect what it
really does in the HTML backend, i.e. insert text verbatim into the
head element? I suggest we rename it to #+HTML_HEAD.
Hi Sean,
Sean O'Halpin wrote:
One small point: as we're going to have to change the meta directive
#+STYLE to #+HTML_STYLE, can we change the name to reflect what it
really does in the HTML backend, i.e. insert text verbatim into the
head element?
Why not...
I suggest we rename it to
Greetings,
The new exporter just arrived in my git repository and I wanted to say
Congratulations! but even more importantly, THANK YOU. Kudos on a
job very well done, if not 100% complete yet. I have been looking
forward to this for quite some time, now.
I would like to extend my
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
Hi Eric,
I have used the beamer export quite a few times with the new exporter,
I must admit I haven't actually tried any of my big beamer talks
(hundreds of slides)... I've been too intimidated to do so! I have done
a short talk but one with no
Hi Eric,
On Tue, Feb 05, 2013 at 07:55:46PM +1030, Eric S Fraga wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
Maybe I should put whatever I have on Worg so that others can work on
it. I'll try to find some time in the coming two weeks.
I think that would be great. I would be
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
Hi Eric,
On Tue, Feb 05, 2013 at 07:55:46PM +1030, Eric S Fraga wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
Maybe I should put whatever I have on Worg so that others can work on
it. I'll try to find some time in the coming two
Hi Eric,
On Tue, Feb 05, 2013 at 11:20:18PM +1030, Eric S Fraga wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
I have attached a somewhat cleaned up version of what I had so far. You
can apply the patch on top of Worg master. If you think this is clean
enough for a starting
Hi Nicolas!
Great news and I'm really looking forward using the new exporter, but:
3. Export section from Org manual is now obsolete. It is being
rewritten, but until this task is completed, your best source of
information will still be the ML or the source files.
I rely
Nicolas Goaziou n.goaz...@gmail.com writes:
━
ANNOUNCING THE NEW EXPORT FRAMEWORK
━
Thanks Nicolas, this is much appreciated. I have been looking forward
to this for a
Detlef Steuer detlef.ste...@gmx.de writes:
Hi Nicolas!
Great news and I'm really looking forward using the new exporter, but:
3. Export section from Org manual is now obsolete. It is being
rewritten, but until this task is completed, your best source of
information will
On Mon, Feb 04, 2013 at 08:49:28AM -0500, David Bjergaard wrote:
Detlef Steuer detlef.ste...@gmx.de writes:
[...]
If there are no docs at all I, as a simple user, would suggest to
postpone the release till after some usage notes are available.
Alternatively keep the old exporter
Hi Detlef and all,
Detlef Steuer detlef.ste...@gmx.de writes:
If there are no docs at all I, as a simple user, would suggest to
postpone the release till after some usage notes are available.
Alternatively keep the old exporter alive , please, till the new one
has documentation. (or the
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
[...]
I would echo this sentiment. Org mode from master has no business in a
production environment, just like any other software project.
Although I agree, in principle, with this statement, life is not always
so straightforward. I track org
Hi Eric,
On Tue, Feb 05, 2013 at 11:37:35AM +1030, Eric S Fraga wrote:
I have been using the new exporter for many tasks but have not
completely moved over for two: generation of beamer presentations and
publishing of web pages. The latter is probably not a major issue for
me but the
━
ANNOUNCING THE NEW EXPORT FRAMEWORK
━
Table of Contents
─
1 To Whom Used the Experimental Version
2 What’s New
.. 2.1 New Back-Ends
.. 2.2 Drawer
Le dimanche 3 février 2013 à 20h00, Nicolas Goaziou a écrit:
I will install the new export framework along with a set of back-ends
Wednesday evening (UTC). Here are a few notes to help you make the
transition.
That's an exciting news! Thanks for all the job already done and to be
done. If
43 matches
Mail list logo
