#+HOMEPAGE in metadata - feature request?

#+HOMEPAGE in metadata - feature request?

[Marcin Borkowski]

Hi all (and devs;)),

what about adding #+HOMEPAGE (alongside #+AUTHOR and #+EMAIL) to the
metadata?  What are the pros and cons?  (One argument against: default
LaTeX classes do not support this.  Any other?)

Regards,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University

Re: #+HOMEPAGE in metadata - feature request?

[Bastien]

Hi Marcin,

Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:

> what about adding #+HOMEPAGE (alongside #+AUTHOR and #+EMAIL) to the
> metadata?

What would it do?

> What are the pros and cons?  (One argument against: default
> LaTeX classes do not support this.  Any other?)

Not sure what "supporting" means :)

-- 
 Bastien

Re: #+HOMEPAGE in metadata - feature request?

[Waldemar Quevedo]

[-- Attachment #1: Type: text/plain, Size: 804 bytes --]

I think already 'supported' in the sense that something like #+HOMEPAGE:
would count as being an in-buffer setting as described in the
http://orgmode.org/manual/In_002dbuffer-settings.html

Org mode uses special lines in the buffer to define settings on a per-file
basis. These lines start with a '#+' followed by a keyword, a colon, and
then individual words defining a setting.




On Fri, Mar 21, 2014 at 10:07 PM, Bastien <bzg@gnu.org> wrote:

> Hi Marcin,
>
> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
>
> > what about adding #+HOMEPAGE (alongside #+AUTHOR and #+EMAIL) to the
> > metadata?
>
> What would it do?
>
> > What are the pros and cons?  (One argument against: default
> > LaTeX classes do not support this.  Any other?)
>
> Not sure what "supporting" means :)
>
> --
>  Bastien
>
>

[-- Attachment #2: Type: text/html, Size: 2247 bytes --]

Re: #+HOMEPAGE in metadata - feature request?

[Marcin Borkowski]

Dnia 2014-03-21, o godz. 14:07:58
Bastien <bzg@gnu.org> napisał(a):

> Hi Marcin,
> 
> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
> 
> > what about adding #+HOMEPAGE (alongside #+AUTHOR and #+EMAIL) to the
> > metadata?
> 
> What would it do?
> 
> > What are the pros and cons?  (One argument against: default
> > LaTeX classes do not support this.  Any other?)
> 
> Not sure what "supporting" means :)

OK, I was too vague - sorry.

What I mean is that quite often you want to include some kind of web
page in the titlepage, be it a LaTeX book/textbook/manual, Beamer or
reveal.js presentation etc.  The problem is, LaTeX does not have a
syntax for this (it is too old for that, apparently...).
Interestingly, Beamer doesn't have anything for that, either.  In
org-reveal, however, the "author" and "email" are just generic <h2>'s
(in fact, I fixed it in my config by adding them a "titlepage" class,
so that they can be different from <h2>'s on regular slides).

So the problem is: it would be (imho) useful to have a "homepage" added
to general metadata, but it is not clear how to translate this to e.g.
LaTeX's (rather ancient) concept of metadata.  (Interestingly, some
other classes, e.g. memoir, koma-script and titlepage, also do not seem
to cater for this need.  I'm going to ask on TeX.SE if there's any
class/package enabling putting a url on the titlepage...)  So while (I
assume) adding a #+HOMEPAGE field/option in Org would be easy, it is
not obvious how to render it for different exporters.

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University

Re: #+HOMEPAGE in metadata - feature request?

[Bastien]

Hi Marcin,

Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:

> So the problem is: it would be (imho) useful to have a "homepage" added
> to general metadata, but it is not clear how to translate this to e.g.
> LaTeX's (rather ancient) concept of metadata.  (Interestingly, some
> other classes, e.g. memoir, koma-script and titlepage, also do not seem
> to cater for this need.  I'm going to ask on TeX.SE if there's any
> class/package enabling putting a url on the titlepage...)  So while (I
> assume) adding a #+HOMEPAGE field/option in Org would be easy, it is
> not obvious how to render it for different exporters.

Thanks for the explanations, I get it now; but unless I'm really tired
(could be), you only mention backends that do not support a concept of
"homepage"... right?

There is #+HTML_LINK_HOME in the ox-rss.el backend to specify a link
to the homepage (different from the baseurl, since you don't want to
use a baseurl in a RSS feed.)  So maybe that's a start.

-- 
 Bastien

Re: #+HOMEPAGE in metadata - feature request?

[Marcin Borkowski]

Dnia 2014-03-22, o godz. 00:44:40
Bastien <bzg@gnu.org> napisał(a):

> Hi Marcin,
> 
> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
> 
> > So the problem is: it would be (imho) useful to have a "homepage"
> > added to general metadata, but it is not clear how to translate
> > this to e.g. LaTeX's (rather ancient) concept of metadata.
> > (Interestingly, some other classes, e.g. memoir, koma-script and
> > titlepage, also do not seem to cater for this need.  I'm going to
> > ask on TeX.SE if there's any class/package enabling putting a url
> > on the titlepage...)  So while (I assume) adding a #+HOMEPAGE
> > field/option in Org would be easy, it is not obvious how to render
> > it for different exporters.
> 
> Thanks for the explanations, I get it now; but unless I'm really tired
> (could be), you only mention backends that do not support a concept of
> "homepage"... right?

Right.  I did not really use other backends; what drives my suggestion
is a /need/ for a url in the titlepage, not an /existence/ of such
feature in other tools.  (It would be hard for me to believe that I'm
the only one needing this, btw...)

> There is #+HTML_LINK_HOME in the ox-rss.el backend to specify a link
> to the homepage (different from the baseurl, since you don't want to
> use a baseurl in a RSS feed.)  So maybe that's a start.

I see.  I'll look into this tomorrow.

Thanks,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University

Re: #+HOMEPAGE in metadata - feature request?

[Nick Dokos]

Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:

> Dnia 2014-03-22, o godz. 00:44:40
> Bastien <bzg@gnu.org> napisał(a):
>
>> Hi Marcin,
>> 
>> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
>> 
>> > So the problem is: it would be (imho) useful to have a "homepage"
>> > added to general metadata, but it is not clear how to translate
>> > this to e.g. LaTeX's (rather ancient) concept of metadata.
>> > (Interestingly, some other classes, e.g. memoir, koma-script and
>> > titlepage, also do not seem to cater for this need.  I'm going to
>> > ask on TeX.SE if there's any class/package enabling putting a url
>> > on the titlepage...)  So while (I assume) adding a #+HOMEPAGE
>> > field/option in Org would be easy, it is not obvious how to render
>> > it for different exporters.
>> 
>> Thanks for the explanations, I get it now; but unless I'm really tired
>> (could be), you only mention backends that do not support a concept of
>> "homepage"... right?
>
> Right.  I did not really use other backends; what drives my suggestion
> is a /need/ for a url in the titlepage, not an /existence/ of such
> feature in other tools.  (It would be hard for me to believe that I'm
> the only one needing this, btw...)
>

For latex, the ams classes (amsart, etc) provide a \urladdr macro.
I imagine something similar could be easily added to the standard
classes. Or you can cheat:

#+AUTHOR:
#+LATEX_HEADER: \author{A.U.Thor\thanks{http://www.foo.org}

-- 
Nick