From: Timothy <email@example.com>
To: Bastien <firstname.lastname@example.org>
Cc: org-mode-email <email@example.com>
Subject: Re: W3C violations in Org's HTML export
Date: Fri, 30 Apr 2021 16:57:41 +0800 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Bastien <email@example.com> writes:
>> ** Suggestion
>> Make the subtitle an independent element, is can still be a
>> p.subtitle, just not /inside/ the h2 title
> Agreed, can you provide a patch for this?
I'll add that to my todo list.
>> ** Suggestion
> Can you confirm the two issues above are already fixed?
As of d96e897579 I'm not seeing any more W3C complaints :)
>> * Error: Duplicate ID org0424ed6.
>> Clearly, this can happen. I'm not sure how.
>> I'd like to draw attention to this email I sent a while ago
>> the mangled start)
> I cannot reproduce this.
This may have been a low-chance once off / short-lived strange bug.
If nobody else has seen this happen, I'd be inclined to dismiss this.
>> * Error: Character reference expands to a control character
>> I suspect this may be htmlize, but I'm not sure, and it's
>> so I'll include it.
> I don't observe this, a reproducible recipe is welcome.
I'll come back to this if I can find out more.
>> * (not an error) Difficulty in 'wrapping' sections
>> It's quite reasonable (IMO) to want to wrap a (sub*)section in a
>> certain element, such as a link. Indeed I've wanted to do this
>> to create clickable 'cards' on the homepage of my org website
>> revamp. Unfortunately there doesn't seem to be any property like
>> :HTML_WRAP: etc. that can be applied, forcing me to try this:
> Please open a separate proposal for this.
Will do once I've thought a bit about what would be a good
interface/implementation for this.
> Once all issues listed here are handles, please close the call for
> help with "X-Woof-Help: close" as a header.
Will do 👍
Thanks for reminding me about this,
next prev parent reply other threads:[~2021-04-30 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 19:04 W3C violations in Org's HTML export TEC
2020-10-24 11:28 ` Bastien
2020-12-17 17:55 ` TEC
2020-12-20 17:11 ` Bastien
2021-04-30 8:27 ` Bastien
2021-04-30 8:57 ` Timothy [this message]
2021-04-30 11:37 ` Bruce D'Arcus
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).