From: Timothy <firstname.lastname@example.org> To: Nicolas Goaziou <email@example.com> Cc: org-mode-email <firstname.lastname@example.org> Subject: Re: [PATCH] Wrap LaTeX snippets in $$ with markdown export Date: Tue, 04 May 2021 21:31:21 +0800 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Hello, Nicolas Goaziou <email@example.com> writes: >> Should one want to convert LaTeX images say to an SVG for HTML export, I >> do not think one would want this behaviour to also apply to LaTeX being >> exported to markdown. > > Why do you think so? This is consistent with everything else not > supported by vanilla Markdown. To speak personally, at the moment I use mathjax for HTML. I'm quite content with the markdown output from this patch without what's discussed below. However, if/when I can get the SVG baseline to work with dvisvgm I plan on switching to that for HTML files. However, I'd consider this behaviour undesirable for markdown. The main reason why I'm hesitant about including <img>s in Markdown, is because unlike <table> etc. the output now relies on external files. >> As such I see two 'sensible' paths forward: (1) just include LaTeX >> verbatim when :with-latex is non-nil, or (2) introduce >> `org-markdown-with-latex' which can be set to t/'verbatim or 'html. >> > Obeying to :with-latex property means "ox-md" is somehow actively > handling LaTeX fragments, which was not the initial intent, IIUC. The > first idea was to provide a sensible default for such objects, because > we're outside the specification anyway. I'd rather not overdo it. I'm happy to strip this out of the patch (there's always advice for my own config...), I just thought there may be people who like me are interested in <img>s for LaTeX in HTML, but not in Markdown. -- Timothy
next prev parent reply other threads:[~2021-05-04 13:37 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-31 16:41 Timothy 2021-03-31 20:59 ` Berry, Charles via General discussions about Org-mode. 2021-05-02 20:20 ` Timothy 2021-05-02 20:23 ` Timothy 2021-05-03 16:13 ` Nicolas Goaziou 2021-05-03 18:03 ` Timothy 2021-05-03 22:54 ` Nicolas Goaziou 2021-05-04 3:35 ` Timothy 2021-05-04 13:03 ` Nicolas Goaziou 2021-05-04 13:31 ` Timothy [this message] 2021-05-06 21:56 ` Nicolas Goaziou 2021-05-09 20:12 ` Timothy 2021-05-10 20:54 ` Nicolas Goaziou
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH] Wrap LaTeX snippets in $$ with markdown export' \ /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
Code repositories for project(s) associated with this 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).