Pushed in a780080fcf38ca6412658323eae9367a17a12bdf.
—Rasmus
--
Send from my Emacs
Hi,
For the record, if the situation ever rises again, I think that
a keyword can be added to ox.el only if
- it is supported at least in every major back-end (ASCII, HTML,
LaTeX, ODT and Texinfo)
- it comes with a toggle in the OPTIONS line e.g. keyword:nil
For subtitle I'm
Rasmus ras...@gmx.us writes:
For the record, if the situation ever rises again, I think that
a keyword can be added to ox.el only if
- it is supported at least in every major back-end (ASCII, HTML,
LaTeX, ODT and Texinfo)
- it comes with a toggle in the OPTIONS line e.g. keyword:nil
Rasmus ras...@gmx.us writes:
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Also, assuming you keep :subtitle instead of :BACKEND-subtitle, these
should also be documented in Publishing options.
So I *still* don't see this. I assume you want me to add something do you
want me to add lines
Rasmus ras...@gmx.us writes:
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
So I would keep them. The documentation explicitly states which backend
these keywords are supported by.
OK. Then DESCRIPTION and KEYWORD stay in ox.el, and documented in
Export settings. You need to revert your
Hi,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
As I explained, both are linked:
- Anything defined in ox.el is documented in Export settings ;
- Anything defined in ox-backend.el is documented in Backend
export.
This is a hard rule.
OK.
Even if it means repeating
Rasmus ras...@gmx.us writes:
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Do you mean KEYWORD and DESCRIPTION should also belong to category 1?
I'm not against it, but then, back-ends are required to support them
whenever possible.
At the moment they are. They lack ascii support, but at
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
So I would keep them. The documentation explicitly states which backend
these keywords are supported by.
OK. Then DESCRIPTION and KEYWORD stay in ox.el, and documented in
Export settings. You need to revert your patch about it.
I thought we
Hi,
I've added a patch that address the code problems, but not the
documentation issues, as the solution is still unclear.
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
But de facto KEYWORDS and DESCRIPTION were also only supported in some
backends. I think it's more convenient to have
Rasmus ras...@gmx.us writes:
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
I would like to keep a clear and somewhat future-proof rule about this:
1. A keyword a user can expect to find in all back-ends where it makes
sense should be defined in ox.el. To put it differently, it can be
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
I would like to keep a clear and somewhat future-proof rule about this:
1. A keyword a user can expect to find in all back-ends where it makes
sense should be defined in ox.el. To put it differently, it can be
considered as a bug if a
Rasmus ras...@gmx.us writes:
Could you elaborate a bit in the comment?
Consider if title is nil. With format-spec I'll get an empty h1/h1.
As I remember, the W3 checker dislike these. I have never used these
html5 slides, so I don't really know how to fix it.
You probably should add this
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Also, assuming you keep :subtitle instead of :BACKEND-subtitle, these
should also be documented in Publishing options.
So I *still* don't see this. I assume you want me to add something do you
want me to add lines like this:
@item
Rasmus ras...@gmx.us writes:
+(when formatted-subtitle
+ (concat \n formatted-subtitle))
Nitpick:
(and formatted-subtitle ...)
Can you explain why (and ⋯) should be used here?
Possibly because you don't need the implicit progn?
Hello,
Rasmus ras...@gmx.us writes:
Note: *the patch does not touch ox.el*. SUBTITLE is *only* supported in a
tiny fraction of the backends, namely ox-latex, ox-ascii, ox-html, and
ox-odt.
For some definition of tiny.
+ ;; TODO: format-spec isn't great for missing details.
Could you
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Could you elaborate a bit in the comment?
Consider if title is nil. With format-spec I'll get an empty h1/h1.
As I remember, the W3 checker dislike these. I have never used these
html5 slides, so I don't really know how to fix it.
+can use
Hi,
I'm starting a new thread as the previous discussion attracted much
dissuasion not directly related to the patch in question. Changes:
- Html subtitles now follow the W3 recommendations, I think/hope. It
would be great if somebody who knows css would check the styling.
Hi Rasmus,
Rasmus ras...@gmx.us writes:
Hi,
I'm starting a new thread as the previous discussion attracted much
dissuasion not directly related to the patch in question. Changes:
- Html subtitles now follow the W3 recommendations, I think/hope. It
would be great if somebody who
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
I have not followed the discussion. But I like a uniform subtitle
support across relevant backends. So, my only question is: this patch
does not include ox-beamer, right? This is where I include my own latex
subtitle most times
Rasmus ras...@gmx.us writes:
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
I have not followed the discussion. But I like a uniform subtitle
support across relevant backends. So, my only question is: this patch
does not include ox-beamer, right? This is where I include my own
20 matches
Mail list logo
