emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Visher <tim.visher@gmail.com>
To: mail@nicolasgoaziou.fr
Cc: Jens Lechtenboerger <lechten@wi.uni-muenster.de>,
	"Dr. Arne Babenhauserheide" <arne_bab@web.de>,
	Emacs Org Mode mailing list <emacs-orgmode@gnu.org>,
	Kyle Meyer <kyle@kyleam.com>
Subject: Re: ox-html Incorrectly (?) Puts HTML Into the `<title>` Tag
Date: Thu, 22 Apr 2021 10:08:55 -0400	[thread overview]
Message-ID: <CAHa53uxERrGDk=emzqAfQG5JmMsessQfMgoOtFUQTccAi4aYxQ@mail.gmail.com> (raw)
In-Reply-To: <87h7jy4ebe.fsf@nicolasgoaziou.fr>

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

On Thu, Apr 22, 2021 at 9:52 AM Nicolas Goaziou <mail@nicolasgoaziou.fr>

> Tim Visher <tim.visher@gmail.com> writes:
> > Awesome. Do you know whether there's an official way to share this sort
> of
> > behavior between ox backends or is it just creating a function and
> calling
> > it from both places or something?
> Do you want to remove all markup from some parsed text?
> You could define temporary export back-end with
> `org-export-create-backend', and apply it with
> `org-export-data-with-backend'. See for example, how
> `org-latex-headline' formats headings (`text' binding in the function).
> If that's the case, you need to know exactly what you want. It is pretty
> obvious for bold markup, but what would happen to, e.g., a_b or \alpha
> or <<target>>?

Thanks for the tip. What I'm thinking more is somehow getting the heading
pre-output generation, stripping any characters that `org` would consider
special (I'm hoping there's already a function that can at least mark
'markup' text in a given org string), and _then_ passing it to whatever ox
function is responsible for using the title. That way it's as generic as it
can possibly be.

I confess though that I don't follow exactly what you're talking about
defining a temporary export back-end. Why would that be necessary or
beneficial to the end of teaching org how to use only the 'plain text' of a
heading for the title in N ox backends?


In Christ,

Timmy V.


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

  reply	other threads:[~2021-04-22 14:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 15:32 ox-html Incorrectly (?) Puts HTML Into the `<title>` Tag Tim Visher
2021-01-12  1:19 ` Kyle Meyer
2021-01-12 14:51   ` Tim Visher
2021-01-13  3:43     ` Kyle Meyer
2021-01-13 15:26       ` Tim Visher
2021-01-21  4:10         ` Kyle Meyer
2021-03-30 22:58           ` Tim Visher
2021-04-11 15:11             ` Tim Visher
2021-04-20  3:01             ` Kyle Meyer
2021-04-20  4:58               ` Jens Lechtenboerger
2021-04-20 21:29                 ` Tim Visher
2021-04-21  5:21                   ` Jens Lechtenboerger
2021-04-21  6:39                     ` Dr. Arne Babenhauserheide
2021-04-21 15:05                       ` Tim Visher
2021-04-22 13:52                         ` Nicolas Goaziou
2021-04-22 14:08                           ` Tim Visher [this message]
2021-04-22 15:36                             ` Nicolas Goaziou
2021-04-22 17:34                               ` Tim Visher

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='CAHa53uxERrGDk=emzqAfQG5JmMsessQfMgoOtFUQTccAi4aYxQ@mail.gmail.com' \
    --to=tim.visher@gmail.com \
    --cc=arne_bab@web.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=kyle@kyleam.com \
    --cc=lechten@wi.uni-muenster.de \
    --cc=mail@nicolasgoaziou.fr \


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