From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: 3 bugs and 2 proposals on ascii/html export [7.8.03]
Date: Fri, 09 Mar 2012 03:09:46 +0100 [thread overview]
Message-ID: <87r4x2jzit.fsf@gnu.org> (raw)
In-Reply-To: <20120309005334.GA19970@gmx.org> (Mathias Bauer's message of "Fri, 9 Mar 2012 01:53:34 +0100")
Hi Mathias,
Mathias Bauer <mbauer@gmx.org> writes:
> I just played with org's export functionality and following
> minimal org file. This results in three minor bugs and two
> proposals/questions on org's behavior.
Thanks for this report -- next time, please consider sending
one mail per bug/request, it makes issues easier to track.
> ** Bug 1: Underlining the headlines
>
> Headlines without tags are underlined in a wrong manner. It's
> one character too long.
It's a matter of taste. I like this additionnal character
and I think Carsten added it intentionally.
> ** Question/Proposal
>
> As default, all level 1 headlines are underlined by - characters
> and level 2 headlines with =. Wouldn't it be more logical the
> other way round: the lower the level, the more important the
> headline and hence the "bigger" its underlining? (Of course the
> user can change the variable org-export-ascii-underline.)
Unless many users think this is illogical, I won't change the
default.
> * HTML export
>
> ** Question/Proposal
>
> ----------snip----------
> <h2>...Some section with TAG at the end <span class="tag"><span class="some_tag">some_tag...
> ----------snip----------
>
> Isn't a single space enough for separating the heading's text and
> the tag? Beside their number, the additional three (why not five
> or n?) " " seem a little bit freaky to me...
They _are_ freaky :) But they are also needed.
Even if the tags display is taken care of by the CSS,
we must prevent collapsing the tags with the previous
strings in case the CSS is not available -- just think
of what the HTML page should look like with w3m/lynx.
> ** Bug 2: Exporting the tag into the toc
>
> Adding "#+OPTIONS: tags:t" results in the following exported toc:
>
> ----------snip----------
> <li>...Some section with TAG at the end <span class="tag"> some_tag</span></a></li>
> ----------snip----------
>
> There is a space inside the <span>...</span> just before the tag
> name which should not be there.
Fixed, thanks.
> ** Bug 3: Exporting the TODO keywords
>
> ----------snip----------
> <h2>...<span class="todo TODO"> TODO</span> Some section with a TODO keyword</h2>
> ----------snip----------
>
> There is a space inside the <span>...</span> just before the TODO
> keyword which should not be there.
Fixed, thanks.
--
Bastien
next prev parent reply other threads:[~2012-03-09 2:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 0:53 Bug: 3 bugs and 2 proposals on ascii/html export [7.8.03] Mathias Bauer
2012-03-09 2:09 ` Bastien [this message]
2012-03-09 3:24 ` Mathias Bauer
2012-03-09 10:12 ` Sebastien Vauban
2012-03-09 12:55 ` Gustav Wikström
2012-03-09 16:02 ` Gregor Zattler
2012-03-10 4:57 ` Carsten Dominik
2012-03-10 9:05 ` Nicolas Goaziou
2012-03-09 21:29 ` Ivy Foster
2012-04-11 6:50 ` Bastien
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=87r4x2jzit.fsf@gnu.org \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
/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).