From: William Crandall <bc3141592@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org, Jambunathan K <kjambunathan@gmail.com>
Subject: Re: New Link Syntax: Adding ATTRIBUTES (Was: org-e-html: Including ATTR_HTML)
Date: Thu, 14 Jun 2012 17:53:27 -0700 [thread overview]
Message-ID: <CAENLK5VQ78GVEe8cy6SpD48qgu=1JFa9FuXUcEkX4d1nhuaAaw@mail.gmail.com> (raw)
Hello Nicolas,
Many thanks for expanded clarity, and a new direction.
On Thu, Jun 14, 2012 at 2:51 AM,
Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> I understand your problem, but inserting ATTR_HTML
> keywords in a paragraph isn't possible anymore. I cannot
> allow that as it would defeat a fundamental change in the
> new Org syntax.
This is good. While not familiar with the details, I clearly
see the value of maintaining the logical integrity of the new
architecture.
> ATTR_HTML could ... accept a list of properties that would
> be applied in order to each link in the paragraph. But it
> wouldn't scale well...
Agreed; this is not the way to go.
> I'm open to any other suggestion. For example, link's
> syntax could be extended to allow attributes.
I like this idea, and think it is the way to go.
--------------------------------------------------
One approach would be to expand the current link syntax
from TWO to THREE pairs of square brackets.
Current syntax:
http://orgmode.org/org.html#Link-format
New syntax:
[[link]]
[[link][description]]
[[link][description][ATTRIBUTES]]
Description and attributes would be optional.
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.
The Manual should then indicate that ATTR_HTML is a
/paragraph/-level mechanism, and is no longer intended
for use with links:
http://orgmode.org/org.html#Links-in-HTML-export
There may, of course, be different/better solutions.
Thanks for continuing to move this forward!
-BC
next reply other threads:[~2012-06-15 0:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 0:53 William Crandall [this message]
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 ` New Link Syntax: Adding ATTRIBUTES (Was: org-e-html: Including ATTR_HTML) Avdi Grimm
2012-06-19 1:47 ` 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='CAENLK5VQ78GVEe8cy6SpD48qgu=1JFa9FuXUcEkX4d1nhuaAaw@mail.gmail.com' \
--to=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).