From: Ihor Radchenko <yantar92@posteo.net>
To: Daniel Radetsky <dradetsky@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: [POLL] Mark all the tags in HTML export with unique class (was: Adding a class to the auto-inserted <br> elements)
Date: Mon, 09 Sep 2024 17:13:54 +0000 [thread overview]
Message-ID: <87zfogpx65.fsf@localhost> (raw)
In-Reply-To: <CABLa6CR2kbN0E2KD97dpr45fyTktLvV6GdWMWQL+bWxi4V9j+A@mail.gmail.com>
We are discussing the way Org formats HTML tags in HTML export.
Some of the tags added by Org are simply bare tags, like <br /> below.
<li><a id=".."></a>Low-level heading<br />
The suggestion is to add a unique class to each tag produced by Org HTML
export, so that CSS rules can precisely target various tags.
For example, Org can produce <br> tag in multiple contexts:
1. when exporting explicit line break \\
2. when exporting a heading as list item, to avoid merging the heading
and its text
3. to separate title/subtitle
4. to separate inlinetask headline from its contents
etc...
We may export each <br> (or any other tag) as <br class="tag context">
Pros: Easier to write CSS selectors and possibly to post-process the
generated HTML
Cons: HTML will become less readable
WDYT?
Daniel Radetsky <dradetsky@gmail.com> writes:
>> The fact that some specific suggestion...
>
> This is an example of "motivation"; a specific concrete use-case that
> actually came for the user to demonstrate that the issue is not merely
> theoretical.
> ... <multiple other arguments>
Ok. I see your motivation.
However, it does not make any sense to change _only_ one single specific
case where we insert <br> tag.
If we follow your argument, we should do it for every single tag that
ox-html inserts.
I am personally neutral to having such a change.
However, we discussed a somewhat similar proposal in the past wrt LaTeX
export and some users were concerned about reduced readability of the
produced .tex documents. See
https://list.orgmode.org/orgmode/87a65vitbz.fsf_-_@posteo.net/
So, I'd like to hear from other Org users first, because deciding
whether we want to add the feature you are asking for.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-09-09 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 23:23 Adding a class to the auto-inserted <br> elements Daniel Radetsky
2024-09-01 16:31 ` Ihor Radchenko
2024-09-01 22:23 ` Daniel Radetsky
2024-09-02 2:20 ` Suhail Singh
2024-09-09 17:13 ` Ihor Radchenko [this message]
2024-09-09 17:16 ` Ihor Radchenko
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=87zfogpx65.fsf@localhost \
--to=yantar92@posteo.net \
--cc=dradetsky@gmail.com \
--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).