Protect LaTeX commands-turn off LaTeX escaping

[daggerquill1]

I’ve seen instructions on resolving specific issues, but how can I just turn off escaping entirely?

Seriously, if I’m using Latex regularly and planning to export to LaTeX, isn’t it far more likely that any backslash I type will be part of a LaTeX command than that it won’t? Ditto curly braces, ampersands, dollar signs, etc.

I know nothing about XSLT; what lines do I comment out in which style file to make MMD just parse Markdown syntax? Given that LaTeX and Markdown syntaxes don’t realy overlap, it shouldn’t be too hard, I wouldn’t think, to convince article.xslt to just convert Markdown to LaTeX, and leave anything that’s not Markdown syntax alone.

I actually expected this to be the default behavior, and was pretty surprised to discover it isn’t.

Thanks!

[signinstranger]

@"[url=https://forum.literatureandlatte.com/t/lists-and-mmd-latex/2832/1

fletcher[/url]"]You need to change the clean-text.xslt file. But in fact, I have already done this. The clean-text-allow-latex.xslt should allow LaTeX commands to pass through unharmed (though I have not tested this overly extensively).

Change any reference to clean-text.xslt in the XSLT stylesheets you use to reference the allow-latex version instead, and see if that works for you.

[daggerquill1]

@signinstranger

@"[url=https://forum.literatureandlatte.com/t/lists-and-mmd-latex/2832/1

fletcher[/url]"]Change any reference to clean-text.xslt in the XSLT stylesheets you use to reference the allow-latex version instead, and see if that works for you.

Thanks! That was a great help, although it took me a while to figure out where clean-text.xslt was being loaded. Gotta love inheritance.

It doesn’t seem to really allow pass-through, though.

~

for instance, is still being converted to

\ensuremath{\sim}

Since I am writing about a number of people with names like “W. W. Greg,” “R. B. McKerrow,” and “J. C. C. Mays,” that is a problem, since the line break rules require

J.~C.~C.~Mays

Right now I’m handling it by doing straight search and replace all, which is fine for ‘~’, but it has the potential to get tedious in a hurry; the list of escapes that still don’t pass through clean-text-allow-latex.xslt is long.

Is it save to just cut chunks like this from the file?

</xsl:with-param> </xsl:call-template> </xsl:with-param> <xsl:with-param name="substring"> <xsl:text>~</xsl:text> </xsl:with-param> <xsl:with-param name="replacement"> <xsl:text>\ensuremath{\sim}</xsl:text> </xsl:with-param> </xsl:call-template>

Thanks again!

[signinstranger]

Is it save to just cut chunks like this from the file?

It’s much easier to nullify the replacement by changing <xsl:text>\ensuremath{\sim}</xsl:text> to <xsl:text>~</xsl:text>

[daggerquill1]

That makes sense. Thanks!