Hello,
Timothy writes:
> Going off this, I've taken this as assent and just pushed my patch in
> its current form as 981f25031.
Thank you.
Regards,
--
Nicolas Goaziou
Hi,
Nicolas Goaziou writes:
>> I just thought there may be people who like me are interested in
>> s for LaTeX in HTML, but not in Markdown.
>
> Fair enough. Let's push your last patch, then.
Going off this, I've taken this as assent and just pushed my patch in
its current form as 981f25031.
Hello,
Timothy writes:
> I just thought there may be people who like me are interested in
> s for LaTeX in HTML, but not in Markdown.
Fair enough. Let's push your last patch, then.
Thank you.
Regards,
--
Nicolas Goaziou
Hello,
Nicolas Goaziou 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
Hello,
Timothy 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.
>
Hi Nicolas,
So, I've now fixed the handling of already-$-delaminated fragments, and
removed the $$ from around environments.
Sorry to complicate things, but, looking at what the HTML fallback
actually is, I've had some further thoughts. The HTML backend will
either leave the content as-is, run
Timothy writes:
> Actually, since writing this patch I'm not sure that $$-surrounding
> \begin{}...\end{} environments is also a good idea. I'm inclined to
> leave this out of the patch.
Sounds good.
> I do rather like the `rx' macro, however I'm not sure that
> (rx bol "\\(") is really an
Nicolas Goaziou writes:
> This sounds reasonable.
I'm glad to hear that!
>> +(defun org-md-latex-environment [...]
> Nitpick: I would use `format', also the final newline character is
> useless, since it will be removed later during the export process.
Actually, since writing this patch I'm
Hello,
Timothy writes:
> I anticipate that this change may be somewhat contentions because ox-md
> explicitly follows only the original Markdown spec from 2003, however
> I've thought this over and come to the conclusion that this change is
> still in keeping with that, and beneficial.
>
>
Hello Nicolas,
In my plea for patch feedback email, Bastien said he'd like to leave
this patch to your discretion.
As such, it would be fantastic if you might be able to provide your
thoughts on this.
All the best,
Timothy.
> Will this handle LaTeX macros[1] gracefully and other things intended as raw
> LaTeX?
> [1] https://pandoc.org/MANUAL.html#latex-macros
This only affects LaTeX fragments, and then it's just changing \(\) /
\[\] for $ / $$. I don't think this has any effect on your concerns.
--
Timothy
> On Mar 31, 2021, at 9:41 AM, Timothy wrote:
>
> I anticipate that this change may be somewhat contentions because ox-md
> explicitly follows only the original Markdown spec from 2003, however
> I've thought this over and come to the conclusion that this change is
> still in keeping with
Hi All,
I anticipate that this change may be somewhat contentions because ox-md
explicitly follows only the original Markdown spec from 2003, however
I've thought this over and come to the conclusion that this change is
still in keeping with that, and beneficial.
Currently ox-md simply inherits
13 matches
Mail list logo
