"Jacob S. Gordon" <jacob.as.gor...@gmail.com> writes: > Please find v1 of a patch attached. All emphasis markers are stripped > except for strike-through, as that could change the meaning or create > ambiguous text. Everything else is not transcoded, including: > > 1. inline source blocks > 2. radio targets & links > 3. math > 4. sub/superscripts > > I think 1 and 2 would be reasonable to support, i.e. replacing links > with a description, falling back to the URI. The others I don’t think > can be handled in an unopinionated, backend-independent way. > > What do people think?
I think that we should not strip "everything else". That's certainly not expected. Rather we should better leave it be. Stripping is rather opinionated :) +1 for links. inline src blocks can be treated same with code markup. export-snippets should probably be stripped. timestamps - org-export-get-date > +(defun org-export-strip-markup (data info) > + "Export DATA to text without emphasis markup using > +`org-export-strip-markup-backend'." I think it may be a good idea to accept optional argument - custom backend. Then, we will be explicit that individual backends are free to replace the default `org-export-string-markup-backend' with their own, possibly derived from default. That will be most flexible. -- Ihor Radchenko // yantar92, Org mode maintainer, 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>
