From: Nicolas Goaziou <n.goaziou@gmail.com>
To: William Crandall <bc3141592@gmail.com>
Cc: emacs-orgmode@gnu.org, Jambunathan K <kjambunathan@gmail.com>
Subject: Re: Testing: org-export-e-html
Date: Fri, 01 Jun 2012 18:38:36 +0200 [thread overview]
Message-ID: <87d35j2dir.fsf@gmail.com> (raw)
In-Reply-To: <CAENLK5VXCuOxm7EBoZu5pZ6pVcamDp=3K-sk063Ty84ikjRKsQ@mail.gmail.com> (William Crandall's message of "Thu, 31 May 2012 20:56:34 -0700")
Hello,
William Crandall <bc3141592@gmail.com> writes:
> 1. [[directors]]
> 2. [[#directors]]
> 3. [[directors][Directors]]
> 4. [[#directors][Directors]]
>
>
> As I see it (do let me know what I'm getting wrong!),
> the old version gets all links right.
>
> (But "old" makes one error(?) see next section.)
>
> 1. [[directors]]
> old: <a href="#sec-1">directors</a>
> new: <i>directors</i>
>
> 2. [[#directors]]
> old: <a href="#directors">#directors</a>
> new: <a href="#sec-1">Directors</a>
>
> 3. [[directors][Directors]]
> old: <a href="#sec-1">Directors</a>
> new: <i>Directors</i>
>
> 4. [[#directors][Directors]]
> old: <a href="#directors">Directors</a>
> new: <a href="#sec-1">Directors</a>
>
>
> In no case is the output the same!
<i>directors</i> is a fallback output meaning that export engine wasn't
able to find which object you were linking to. Provide targets for these
links and the output will be different.
> #4 would be most useful for my purposes, as it allows
> identifying target links precisely.
Org has syntax to identify target links precisely. I gave you a few
examples in a previous mail.
> Turning to the output for targets, the new version
> does not close the <a> tag (as the old version does).
> Other than that, "new" seems fine.
>
> ("Old" generates a <pre> section from the PROPERTIES drawer,
> whether it is open or closed, with your encoding. Not my focus,
> but is this an "old" bug?)
Properties drawers are ignored in every back-end by default. There is no
old or new bug, the behaviour has evolved.
> Output ("new" engine) (Also: two extra blank-lines before each <p>):
That was a mistake in `org-e-html.el'. There should be as much blank
lines in the Org buffer as in HTML output. I fixed the problem in
a recent commit.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-06-01 16:41 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 [this message]
2012-06-02 2:56 ` William Crandall
2012-06-02 5:04 ` Jambunathan K
2012-06-02 7:40 ` William Crandall
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=87d35j2dir.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=bc3141592@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@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).