emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Price <moptop99@gmail.com>
To: Timothy <tecosaur@gmail.com>
Cc: Tim Cross <theophilusx@gmail.com>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: New HTML exporter (was a feature request)
Date: Mon, 4 Oct 2021 10:19:17 -0400	[thread overview]
Message-ID: <CAN_Dec8wHmx2qNax1CbOcj4mK-haGo+B=UOhpuLGZkkiOTyLOQ@mail.gmail.com> (raw)
In-Reply-To: <87ilydgvlv.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 878 bytes --]

On Mon., Oct. 4, 2021, 2:21 a.m. Timothy, <tecosaur@gmail.com> wrote:

> Hi Tim,
> > 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.
> I think there may be some promise in the idea of rewriting (large parts
> of) the
> current HTML exporter. The way that the web has changed over the last
> decade I
> think we can now make some assumptions that can simplify things — for
> example
> I think we could safely go HTML5-only

> It seems to me that if the html exporter is being rewritten, we might want
to think about ways to make it easier to export some elements as custom
components. As their use becomes more and more common, I would reckon this
will be a desirable feature.


[-- Attachment #2: Type: text/html, Size: 1489 bytes --]

  reply	other threads:[~2021-10-04 14:21 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
2021-10-04  6:17           ` New HTML exporter (was a feature request) Timothy
2021-10-04 14:19             ` Matt Price [this message]
2022-06-11  8:06             ` Ihor Radchenko
2022-06-11  8:25               ` Timothy

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:

  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='CAN_Dec8wHmx2qNax1CbOcj4mK-haGo+B=UOhpuLGZkkiOTyLOQ@mail.gmail.com' \
    --to=moptop99@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tecosaur@gmail.com \
    --cc=theophilusx@gmail.com \


* 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).