Rasmus writes:
> Isn't the point that you don't have to support those (e.g. markddown).
> The current documentation is pretty specific about not having expectations
> about KEYWORDS and DESCRIPTION working. It would be the same for
> SUBTITLE.
OK, then SUBTITLE is expected to be out of "ox.el".
See inline.
On 3/26/2015 6:42 AM, Rasmus wrote:
Rasmus writes:
This would be the title and this the subtitle
ref: http://getbootstrap.com/components/#page-header
According to html5doctor.com:
Note: Some have been advocating of the use of the small element to
signify subtitl
Rasmus writes:
>>
>> This would be the title and this the subtitle
>>
>>
>> ref: http://getbootstrap.com/components/#page-header
According to html5doctor.com:
Note: Some have been advocating of the use of the small element to
signify subtitles. This has been under discussion in the
Hi,
Melanie Bacou writes:
> I would indeed go further and suggest adding the following once and
> for all as common ox features:
I don't think so. Consider the ultra important ox-ical (it's important
'cause it keep my calendar in sync via org-caldav). How should it handle
these fields? I thi
Melanie Bacou writes:
> Here is how titles and subtitles are supported in Bootstrap ("the most
> popular HTML/CSS/JS framework"):
>
>
> This would be the title and this the subtitle
>
>
> ref: http://getbootstrap.com/components/#page-header
I don't know what bootstrap is. I have softened on
Here is how titles and subtitles are supported in Bootstrap ("the most
popular HTML/CSS/JS framework"):
This would be the title and this the subtitle
ref: http://getbootstrap.com/components/#page-header
Another commonly seen approach is this (many web CMS use this pseudo
standard):
My T
I forgot:
#+COPYRIGHT
On 3/25/2015 10:36 PM, Melanie Bacou wrote:
I would indeed go further and suggest adding the following once and for
all as common ox features:
#+TITLE
#+SUBTITLE
#+DATE
#+AUTHORS (support multiple)
#+EMAILS (1 per author)
#+AFFILIATIONS (1 per author)
#+CLASSIFICATION (e
I would indeed go further and suggest adding the following once and for
all as common ox features:
#+TITLE
#+SUBTITLE
#+DATE
#+AUTHORS (support multiple)
#+EMAILS (1 per author)
#+AFFILIATIONS (1 per author)
#+CLASSIFICATION (e.g. "ACM", "JEL", "Dublin Core", "your corporate
classification", et
Nicolas Goaziou writes:
> E.g., when creating a new export back-end, it is quite obvious that one
> will need to handle TITLE, DATE, AUTHOR and EMAIL somehow. Now, if you
> request handlers for SUBTITLE, KEYWORDS and DESCRIPTION, it becomes more
> tedious to achieve the task.
Isn't the point tha
Rasmus writes:
> Nicolas Goaziou writes:
>
>> However, I think porting this feature to back-ends that do not support
>> it out of the box is pushing too hard.
>
> In the patch there's ox-latex where e.g. KOMA-Script has as
> subtitle-macro. ox-html, ox-ascii, ox-odt all are pretty liberate for
Marcin Borkowski wrote:
> On 2015-03-22, at 16:29, Rasmus wrote:
>
>> IMO it is. The only place where there's a "hack" is in ox-latex and
>> that's cause article is the default class. If you prefer, it can just
>> output to the \subtitle{·} by default and say it's KOMA-script only. That
>> seem
On 2015-03-23, at 01:05, Rasmus wrote:
> Hi,
>
> First: Please don't take me being critical as meaning I'm necessarily
> negative about. I'm just minimizing risk over the expectation.
Of course, fine with me. It’s the criticism which can make this project
better (or help decide it’s unnecessa
Rasmus writes:
> Eric Abrahamsen writes:
>
>> Rasmus writes:
>>
>> In ox-html, You might consider wrapping the title and subtitle in an
>> if :html5-fancy is t. Or maybe that's going too far! Either
>> way, I like this.
>
> First result on my search engine says¹ :
>
> Update 16th April, 2
Hi,
First: Please don't take me being critical as meaning I'm necessarily
negative about. I'm just minimizing risk over the expectation.
Marcin Borkowski writes:
>> - What happens when you cannot maintain it any longer? Note also that the
>
> Either the project dies, or someone takes it over.
On 2015-03-22, at 23:43, Rasmus wrote:
> Marcin Borkowski writes:
>
>> [TL;DR: imho, the right way to do LaTeX export is to prepare a dedicated
>> package for Org-mode generated files (easy/medium), arrange for it to be
>> included in all major TeX distros (easy) and simplify the LaTeX exporter
Marcin Borkowski writes:
> [TL;DR: imho, the right way to do LaTeX export is to prepare a dedicated
> package for Org-mode generated files (easy/medium), arrange for it to be
> included in all major TeX distros (easy) and simplify the LaTeX exporter
> to comply with it (easy). This could greatly
I, for one, find your ideas exciting, Marcin. If you're simply looking
for votes in order to start work on this: +1.
Thanks!
> Marcin Borkowski writes:
> On 2015-03-22, at 16:29, Rasmus wrote:
>> IMO it is. The only place where there's a "hack" is in ox-latex
>> and that's c
Marcin Borkowski writes:
> On 2015-03-22, at 16:29, Rasmus wrote:
>
>> IMO it is. The only place where there's a "hack" is in ox-latex and
>> that's cause article is the default class. If you prefer, it can just
>> output to the \subtitle{·} by default and say it's KOMA-script only. That
>> s
On 2015-03-22, at 16:29, Rasmus wrote:
> IMO it is. The only place where there's a "hack" is in ox-latex and
> that's cause article is the default class. If you prefer, it can just
> output to the \subtitle{·} by default and say it's KOMA-script only. That
> seems harsh, though.
Hi there,
b
Eric Abrahamsen writes:
> Rasmus writes:
>
> In ox-html, You might consider wrapping the title and subtitle in an
> if :html5-fancy is t. Or maybe that's going too far! Either
> way, I like this.
First result on my search engine says¹ :
Update 16th April, 2013. hgroup has now been remove
Hi Nicolas,
I'm a bit confused by your message.
Nicolas Goaziou writes:
> However, I think porting this feature to back-ends that do not support
> it out of the box is pushing too hard.
In the patch there's ox-latex where e.g. KOMA-Script has as
subtitle-macro. ox-html, ox-ascii, ox-odt all
Rasmus writes:
> Hi,
>
> This patch adds #+SUBTITLE to a couple of backends. This property is
> already supported in ox-texinfo and e.g. beamer.cls has a subtitles macro,
> but ox-beamer.el has no #+SUBTITLE. I have used subtitles in
> e.g. applications for research funds.
>
> The value-added i
Hello,
Rasmus writes:
> This patch adds #+SUBTITLE to a couple of backends. This property is
> already supported in ox-texinfo and e.g. beamer.cls has a subtitles macro,
> but ox-beamer.el has no #+SUBTITLE. I have used subtitles in
> e.g. applications for research funds.
>
> The value-added i
Very nice, thanks!
On 3/20/2015 10:26 PM, Marcin Borkowski wrote:
On 2015-03-21, at 00:23, Rasmus wrote:
This patch adds #+SUBTITLE to a couple of backends. This property is
WDTY?
+1
Best,
--
Melanie BACOU
International Food Policy Research Institute
Snr. Program Manager, HarvestChoi
On 2015-03-21, at 00:23, Rasmus wrote:
> This patch adds #+SUBTITLE to a couple of backends. This property is
>
> WDTY?
+1
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
Hi,
This patch adds #+SUBTITLE to a couple of backends. This property is
already supported in ox-texinfo and e.g. beamer.cls has a subtitles macro,
but ox-beamer.el has no #+SUBTITLE. I have used subtitles in
e.g. applications for research funds.
The value-added is twofold:
- It adds a con
26 matches
Mail list logo
