Here is a quick patch. Not meant to be applied but meant for testing
purpose only.
So there is a html backend which doesn't add divs and there is a HTML
backend that adds divs. (The difference is between html and HTML, in
capslock).
The `org-export-dispatch' uses HTML backend, while you can c
The aren't really content elements but merely structuring
or styling elements.
I think there should be a clear separation between contents and how it
is wrapped. The base HTML exporter should just generate content with no
divs at all. There could be a fancy HTML exporter which does generate
On Tue, Mar 05, 2013 at 09:16:16AM +0100, Nicolas Goaziou wrote:
> Rick Frankel writes:
> > On the other hand, it would be easier if ox-html were modified so that
> > org-html-headline uses a variable (or callback) for the format of the
> > wrapper (currently " > generation. This would add flexib
Hello,
Rick Frankel writes:
> I seem to have reached the limit of my emacs-fu. I am looking at
> adding XOXO output to the S5 exporter (S5 has built-in support for
> XOXO structured documents) and was trying to use an element (headline)
> filter to modify the document structure. I am also trying
This may be a question for Nicolas ---
I seem to have reached the limit of my emacs-fu. I am looking at
adding XOXO output to the S5 exporter (S5 has built-in support for
XOXO structured documents) and was trying to use an element (headline)
filter to modify the document structure. I am also tryin
Dear Nicolas,
On 26.02.2013, at 00:14, Nicolas Goaziou wrote:
>> [...] This code used to be suppressed by
>>
>> :style-include-default nil
>> :style-include-scripts nil
>>
>> in the org-publish-project-alist - either this functionality is
>> currently not available or the keyword has changed. T
Hello,
Stefan Vollmar writes:
> if you look at the HTML code generated by Org-mode you will find this line in
> the embedded CSS code (line 45):
>
> div.figure p { text-align: center; }
>
> which causes the effect you have described.
> This code used to be suppressed by
>
> :style-include-def
Dear Richard,
On 25.02.2013, at 18:55, Richard Stanton wrote:
> It seems that figure placement has changed in HTML files generated by the
> new (compared with the old) exporter.
>
> For example, here's a simple org file:
>
> -
>
> This is an org file
>
> [[file:figure.png]]
>
> * Abs
It seems that figure placement has changed in HTML files generated by the
new (compared with the old) exporter.
For example, here's a simple org file:
-
This is an org file
[[file:figure.png]]
* Abstract
This is an abstract
-
When I export, all looks fine, except that the fig
Nicolas Goaziou writes:
> Hello,
>
> henry atting writes:
>
>> Only a single file. I understand that something like this will no work
>> anymore with the new exporter.
>>
>> #+SETUPFILE: /home/me/.setup.org
>
> It's #+SETUP_FILE: in the new exporter.
Okay, then it applies the `#+STYLE:' option
Hello,
henry atting writes:
> Okay, then it applies the `#+STYLE:' option from the setup file but not
> the path to org-info.js set in `#+INFOJS_OPT: path:~/.org-info.js'.
This is to be expected: org-jsinfo.el doesn't recognize the new exporter
yet.
> As to me I am content with e.g. org-export
Hello,
henry atting writes:
> Only a single file. I understand that something like this will no work
> anymore with the new exporter.
>
> #+SETUPFILE: /home/me/.setup.org
It's #+SETUP_FILE: in the new exporter.
> Besides I'm pretty happy with the old exporter and was only curious
> because I r
Robert Klein writes:
> On 09/29/2012 01:36 PM, henry atting wrote:
>> Hi,
>>
>> I gave the new html exporter a try (org-e-html-to-file). The export
>> obviously ignores my setup file, and so the path to my css and js files.
>>
>> Maybe with the new exporter everything has changed and I only miss
On 09/29/2012 01:36 PM, henry atting wrote:
Hi,
I gave the new html exporter a try (org-e-html-to-file). The export
obviously ignores my setup file, and so the path to my css and js files.
Maybe with the new exporter everything has changed and I only miss a
good tutorial?
henry
Do you want
Hi,
I gave the new html exporter a try (org-e-html-to-file). The export
obviously ignores my setup file, and so the path to my css and js files.
Maybe with the new exporter everything has changed and I only miss a
good tutorial?
henry
--
http://literaturlatenight.de
15 matches
Mail list logo
