Hi Suvayu,
Suvayu Ali 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 #+HTML_STYLE
> doc/org
On Monday, March 4, 2013, Nicolas Goaziou wrote:
> Mike McLean > writes:
>
> > On Mon, Mar 4, 2013 at 10:24 AM, Nicolas Goaziou
> >
> >wrote:
> >
> >> Hello,
> >>
> >> Mike McLean > writes:
> >>
> >> > I noticed that it no longer concatenates multiple lines from the file
> >> > header. I used to
Mike McLean writes:
> On Mon, Mar 4, 2013 at 10:24 AM, Nicolas Goaziou wrote:
>
>> Hello,
>>
>> Mike McLean 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 differen
On Mon, Mar 4, 2013 at 10:24 AM, Nicolas Goaziou wrote:
> Hello,
>
> Mike McLean 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 desi
Hi Bastien,
On Sat, Mar 02, 2013 at 07:14:07PM +0100, Bastien wrote:
> Hi Sean,
>
> "Sean O'Halpin" 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,
Hello,
Mike McLean 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 and could change
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 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
On Saturday, March 2, 2013, Bastien wrote:
> Hi Sean,
>
> "Sean O'Halpin" > 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 i
Hello,
Rick Frankel 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..." to "html-head
Hi Rick,
please check against the latest ox-html.el, I updated it yesterday
with some modifications in this area, fixing typos and reintroducing
`org-html-head-extra'.
(I'm in a rush right now and need to leave.)
Thanks in advance,
--
Bastien
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 e
Hi Sean,
"Sean O'Halpin" 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 setting or an
envir
On Sat, Mar 2, 2013 at 6:14 PM, Bastien wrote:
> Hi Sean,
>
> "Sean O'Halpin" 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 i
Hi Sébastien,
"Sebastien Vauban"
writes:
> - html-STYLE-include-default -> html-STYLE-include-default
> (unchanged)
Fixed, thanks.
--
Bastien
Hi Bastien,
Bastien wrote:
> "Sean O'Halpin" 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
>> element? I suggest we
Hi Sean,
"Sean O'Halpin" 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
> element? I suggest we rename it to "#+HTML_HEA
Nicolas Goaziou writes:
> "Sean O'Halpin" 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
>> suggestion is really not so differen
"Sean O'Halpin" 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 adds its own keyw
On Sat, Feb 9, 2013 at 1:56 PM, Nicolas Goaziou wrote:
> Hello,
>
> "Sean O'Halpin" 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
Achim Gratz 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,
> Achim.
Hello,
"Sean O'Halpin" 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. (We also have =ht
On Fri, Feb 8, 2013 at 4:45 PM, Sebastien Vauban
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 (not
> enough
Nicolas Goaziou writes:
> Achim Gratz 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
Achim Gratz 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
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 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
Hello,
Achim Gratz 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) might have anoth
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 fo
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
> element?
Why not...
> I suggest we rename it to
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
element? I suggest we rename it to "#+HTML_HEAD".
Regard
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 Congratulat
Hi Eric,
On Tue, Feb 05, 2013 at 11:20:18PM +1030, Eric S Fraga wrote:
> Suvayu Ali 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 point then I will push i
Suvayu Ali writes:
> Hi Eric,
>
> On Tue, Feb 05, 2013 at 07:55:46PM +1030, Eric S Fraga wrote:
>> Suvayu Ali 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.
Hi Eric,
On Tue, Feb 05, 2013 at 07:55:46PM +1030, Eric S Fraga wrote:
> Suvayu Ali 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 happy to work on any
Suvayu Ali 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 special blocks, columns,
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 f
Suvayu Ali 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 for my day to day use becau
Hi Detlef and all,
Detlef Steuer 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 migration path has
On Mon, Feb 04, 2013 at 08:49:28AM -0500, David Bjergaard wrote:
>
> Detlef Steuer 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,
Detlef Steuer 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 still be t
Nicolas Goaziou writes:
> ━
> ANNOUNCING THE NEW EXPORT FRAMEWORK
> ━
Thanks Nicolas, this is much appreciated. I have been looking forward
to this for a long time.
Perh
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
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
━
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 Handling
44 matches
Mail list logo
