From: William Crandall <bc3141592@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Testing: org-export-e-html
Date: Sat, 2 Jun 2012 00:40:07 -0700 [thread overview]
Message-ID: <CAENLK5VgjsjoJmPXOL+T9kvoJNhBu=414orH3TQ0o9Gu_EX1Dw@mail.gmail.com> (raw)
In-Reply-To: <81ipfanw34.fsf@gmail.com>
Jambunathan,
Thanks to you, and Nicolas, for your patience.
I now see (blindingly, now that I do see) that the export engine
adds the # to internal links, not me.
The only trailing issue I see is the "soft error" of no </a> tag
on <<targets>> (see W3C notes below).
This (org):
------------------------------------------------------------
Link and description, to anchor in paragraph: [[bc][BC]]
Paragraph with a /dedicated target/: <<bc>>BC
------------------------------------------------------------
Exports to (new):
------------------------------------------------------------
<p>
Link and description, to anchor in paragraph: <a href="#bc">BC</a>
</p>
<p>
Paragraph with a <i>dedicated target</i>: <a id="bc" name="bc"/>BC
</p>
------------------------------------------------------------
Success!
------------------------------------------------------------
And headlines with a <<target>> are also fine:
This (org):
------------------------------------------------------------
Link and description, to anchor in headline: [[directors][Directors]]
* <<directors>>Directors
------------------------------------------------------------
Exports to (new):
------------------------------------------------------------
<p>
Link and description, to anchor in headline: <a href="#directors">Directors</a>
</p>
<div id="outline-container-1" class="outline-2">
<h2 id="sec-1"><a id="directors" name="directors"/>Directors</h2>
<div class="outline-text-2" id="text-1">
------------------------------------------------------------
Success!
------------------------------------------------------------
And I /understand/ how ":PROPERTIES: :CUSTOM_ID: directors" in
a headline, can be linked to with: [[#directors][Directors]],
WITH a # that I, not the engine, insert.
So I'm good to go! Many thanks.
------------------------------------------------------------
------------------------------------------------------------
One trailing point:
You may want to consider adding a formal closing </a> tag for
<<target>> elements (as the "old" engine does) rather than just
"self-closing" the <a> tag with a "/>".
A Firefox comment (viewing source) caught my attention:
"Self-closing syntax ("/>") used on a non-void HTML element.
Ignoring the slash and treating as a start tag."
Then I found this:
http://www.w3.org/TR/html-markup/syntax.html#syntax-elements
"A non-void element must have an end tag, unless the subsection
for that element in the HTML elements section of this reference
indicates that its end tag can be omitted."
And this:
http://www.w3.org/TR/html-markup/a.html#a-tags
"An a element must have both a start tag and an end tag."
------------------------------
I take all of this to mean that "it would be best" to use "</a>"
closing tags, rather than "self-closing" an "<a ..." with a "/>".
But again, the way it is works for me. Many thanks.
Best of luck on the rest of it!
-BC
On Fri, Jun 1, 2012 at 10:04 PM, Jambunathan K <kjambunathan@gmail.com> wrote:
>
> Crandall
>
> There is some confusion on your end :-).
next prev parent reply other threads:[~2012-06-02 7:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 6:27 Testing: org-export-e-html (was: Drupal syntax on html-export) William Crandall
2012-05-30 7:08 ` Testing: org-export-e-html Sebastien Vauban
2012-05-30 11:07 ` Nicolas Goaziou
2012-05-30 23:50 ` William Crandall
2012-05-30 23:53 ` William Crandall
2012-05-31 4:28 ` Jambunathan K
2012-05-31 12:08 ` Nicolas Goaziou
2012-06-01 3:56 ` William Crandall
2012-06-01 6:42 ` William Crandall
2012-06-01 16:38 ` Nicolas Goaziou
2012-06-02 2:56 ` William Crandall
2012-06-02 5:04 ` Jambunathan K
2012-06-02 7:40 ` William Crandall [this message]
2012-06-02 10:26 ` Jambunathan K
2012-05-31 6:42 ` Jambunathan K
2012-06-01 3:44 ` 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='CAENLK5VgjsjoJmPXOL+T9kvoJNhBu=414orH3TQ0o9Gu_EX1Dw@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).