emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Avdi Grimm <groups@inbox.avdi.org>
To: William Crandall <bc3141592@gmail.com>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <n.goaziou@gmail.com>,
	Jambunathan K <kjambunathan@gmail.com>
Subject: Re: New Link Syntax: Adding ATTRIBUTES (Was: org-e-html: Including ATTR_HTML)
Date: Fri, 15 Jun 2012 11:15:25 -0400	[thread overview]
Message-ID: <CA+XG7-ikPL5mjkexgzJJ2pMFaReevbs5hf=W5dmg0JWZ-OFM_Q@mail.gmail.com> (raw)
In-Reply-To: <CAENLK5VQ78GVEe8cy6SpD48qgu=1JFa9FuXUcEkX4d1nhuaAaw@mail.gmail.com>

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

On Thu, Jun 14, 2012 at 8:53 PM, William Crandall <bc3141592@gmail.com>wrote:

> ATTRIBUTES would consisting of name:value pairs, perhaps
> giving names export-type prefixes, such as HTML_STYLE and
> HTML_TITLE, or LATEX_PDFBORDER and LATEX_URLCOLOR.
>
> HTML ATTRIBUTES would map to HTML 'attributes':
>
> http://www.w3.org/TR/html5/section-index.html#attributes-1
>
> LATEX ATTRIBUTES would map to Latex \hypersetup 'options':
>
> http://en.wikibooks.org/wiki/LaTeX/Hyperlinks#.5Chyperref
> (Subsection: Customization)
>
>
> --------------------------------------------------
>
> This would be a significant change, but it would make LINKS
> "first class objects," and allow Org mode users to directly
> apply rich families of link attributes/options.
>
>
I really like this idea!

--
Avdi

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

  parent reply	other threads:[~2012-06-15 15:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15  0:53 New Link Syntax: Adding ATTRIBUTES (Was: org-e-html: Including ATTR_HTML) William Crandall
2012-06-15  4:14 ` New Link Syntax: Adding ATTRIBUTES Thomas S. Dye
2012-06-19  2:29   ` Samuel Wales
2012-06-19 20:11     ` Thomas S. Dye
2012-06-15 15:15 ` Avdi Grimm [this message]
2012-06-19  1:47   ` New Link Syntax: Adding ATTRIBUTES (Was: org-e-html: Including ATTR_HTML) William Crandall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+XG7-ikPL5mjkexgzJJ2pMFaReevbs5hf=W5dmg0JWZ-OFM_Q@mail.gmail.com' \
    --to=groups@inbox.avdi.org \
    --cc=bc3141592@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@gmail.com \
    --cc=n.goaziou@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).