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 <dradet...@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>
