From: Tim Cross <firstname.lastname@example.org>
Subject: Re: Feature request: in org html export, option to disable id & class properties.
Date: Mon, 04 Oct 2021 16:01:24 +1100 [thread overview]
Message-ID: <email@example.com> (raw)
Zachary Kanfer <firstname.lastname@example.org> writes:
> Sure, I'm generally interested in making this useful. Weird that it claims to be part of org, but isn't.
> I do think it would be useful to have a minimalist html exporter in org, whether slimhtml or some other one. The built-in html
> exporter is rather opinionated.
I tend to agree. Although this would be difficult to achieve now because
of the impact it would have on end users, I think the best architecture
for org would be for ALL exporters to be basic 'no thrills' exporters
and more advanced, opinionated or specialised exporters provided as
external ELPA or NONGNUE ELPA add ons which are not part of the core
architecture. Org maintenance could then just focus on core
functionality and an API which make implementing extensions/add-ons
I also agree with Bastien that adding a second HTML exporter as part of
the core is likely to lead to confusion and additional maintenance.
Probably what is needed is a new HTML exporter which is capable of doing
what slimhtml does as the default, but includes the additional
functionality already in the exporter which many people are using.
Getting this right is definitely a non-trivial problem.
next prev parent reply other threads:[~2021-10-04 5:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 7:07 Feature request: in org html export, option to disable id & class properties Zachary Kanfer
2021-07-10 7:41 ` András Simonyi
2021-07-11 5:45 ` Zachary Kanfer
2021-10-03 15:57 ` Amin Bandali
2021-10-04 4:12 ` Zachary Kanfer
2021-10-04 5:01 ` Tim Cross [this message]
2021-10-04 6:17 ` New HTML exporter (was a feature request) Timothy
2021-10-04 14:19 ` Matt Price
2022-06-11 8:06 ` Ihor Radchenko
2022-06-11 8:25 ` Timothy
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).