From: Thomas Redelberger <redetho@t-online.de>
To: emacs-orgmode@gnu.org
Subject: Re: How to export to the simplest possible HTML?
Date: Thu, 8 Jun 2023 17:18:01 +0200 [thread overview]
Message-ID: <280758ee-ab9f-e0c1-b45b-ab9be26b113c@t-online.de> (raw)
In-Reply-To: <871qixr6yl.fsf@mbork.pl>
Dear Marcin and everybody,
I had a similar requirement for "simplest HTML" and have documented how I tackled this under
http://web222.webclient5.de/doc/swdev/emacs/orgmode/html
In summary, it is
- a few settings in init.el:
+ org-html-text-markup-alist similar to below
+ setting org-export-allow-bind-keywords to t
- seeting quite some org variables via in-buffer settings
- elisp to steer a final XSLT transformation of the generated HTML
I had coded a derived export back-end (for Emacs 25.1) and used it quite for some time. When I moved to Emacs 27.2, the derived back-end did not work any more, hence I changed to above aproach.
Best regards
Thomas
Am 2023-05-30 um 20:48 schrieb Marcin Borkowski:
>
> On 2023-05-30, at 17:32, Max Nikulin <manikulin@gmail.com> wrote:
>
>> On 30/05/2023 10:47, Marcin Borkowski wrote:
>>> since I'm going to
>>> call my exporting function in a loop over many elements. I tried
>>> (org-export-with-backend 'html (org-element-at-point (point)))
>>
>> There is `org-export-string-as', but likely it is not suitable for
>> you. My guess is that you are going to export headings (blog posts) to
>> separate html files.
>
> Correct, dear Holmes. ;-)
>
>>> This is /italic/.
>>> can become e.g.
>>> This is <span class="emphasize">italic</span>.
>>
>> I am curious whether <em> is more friendly to screen readers
>> https://developer.mozilla.org/en-US/docs/Web/HTML/Element/em
>
> Good point. You're right, I'll probably go with `<em>' then. (The
> reason I wanted `<span>' was that I wan't somewhat atypical styling,
> namely letterspace. But of course css magic can make `<em>' do this,
> too.)
>
>>> I'm considering writing a custom (derived) export backend, but maybe
>>> that is an overkill? Any ideas?
>>
>> I just have noticed
>>
>> (defcustom org-html-text-markup-alist
>> '((bold . "<b>%s</b>")
>> (code . "<code>%s</code>")
>> (italic . "<i>%s</i>")
>> (strike-through . "<del>%s</del>")
>> (underline . "<span class=\"underline\">%s</span>")
>> (verbatim . "<code>%s</code>"))
>> "Alist of HTML expressions to convert text markup.
>>
>> You may look into ox-html customizations such as
>> (:html-doctype "HTML_DOCTYPE" nil org-html-doctype)
>> (:html-html5-fancy nil "html5-fancy" org-html-html5-fancy)
>>
>> I have never tried ox-slimhtml:
>> Laszlo Elo. ox-slimhtml. Mon, 14 Dec 2020 00:48:27
>> -0500. https://list.orgmode.org/41D2E10D-BCFF-4604-8417-B499514AF904@bald.cat
>
> Ah, that looks interesting, too.
>
> Thanks!
>
next prev parent reply other threads:[~2023-06-14 8:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 3:47 How to export to the simplest possible HTML? Marcin Borkowski
2023-05-30 6:21 ` Ihor Radchenko
2023-05-30 18:45 ` Marcin Borkowski
2023-06-03 3:36 ` Marcin Borkowski
2023-06-03 5:08 ` Ihor Radchenko
2023-06-03 6:24 ` Marcin Borkowski
2023-06-03 8:37 ` Ihor Radchenko
2023-06-24 13:25 ` Marcin Borkowski
2023-06-24 13:34 ` Ihor Radchenko
2023-06-24 13:48 ` Marcin Borkowski
2023-05-30 15:32 ` Max Nikulin
2023-05-30 18:48 ` Marcin Borkowski
2023-06-08 15:18 ` Thomas Redelberger [this message]
2023-06-24 15:04 ` Max Nikulin
2023-06-25 19:56 ` Marcin Borkowski
2023-06-27 11:00 ` Max Nikulin
2023-06-28 9:03 ` Marcin Borkowski
-- strict thread matches above, loose matches on Subject: below --
2023-06-10 8:25 Thomas Redelberger
2023-06-24 13:16 ` Marcin Borkowski
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=280758ee-ab9f-e0c1-b45b-ab9be26b113c@t-online.de \
--to=redetho@t-online.de \
--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).