OK, so this bug report belongs in MultiMarkdown... I suspected as much, although had no idea which library Textastic uses... this is the first time since VSCode exists that I have a tablet that's not Windows, and this all works in VSCode (as well as in Markdown previews inside GitHub & Azure DevOps git repos)... I did open a bug over there
as far as the & escaping... if a browser sees & inside a URL when it's parsing HTML, it renders an & ... and the only way to get & in the HTML from a Markdown file is to put & in the Markdown (technically \& should probably also do it, but most MD to HTML converters usually just output &)
but again, that's an MD converter issue, not Textastic... I doubt I'll do much, if any, coding on my iPad... but I definitely like Textastic... I was looking for an excuse to not subscribe to IAWriter & I found it! (even if it does mean I need to tone down my MD escaping a bit)
OK, so this bug report belongs in MultiMarkdown... I suspected as much, although had no idea which library Textastic uses... this is the first time since VSCode exists that I have a tablet that's not Windows, and this all works in VSCode (as well as in Markdown previews inside GitHub & Azure DevOps git repos)... I did open a bug over there
as far as the & escaping... if a browser sees & inside a URL when it's parsing HTML, it renders an & ... and the only way to get & in the HTML from a Markdown file is to put & in the Markdown (technically \& should probably also do it, but most MD to HTML converters usually just output &)
but again, that's an MD converter issue, not Textastic... I doubt I'll do much, if any, coding on my iPad... but I definitely like Textastic... I was looking for an excuse to not subscribe to IAWriter & I found it! (even if it does mean I need to tone down my MD escaping a bit)