Re: [Python-markdown-discuss] Markdown's deprecated "save_mode" option

[Dr R. W. <rai...@gm...>]

Waylan,

sorry for the late reply.

On Wednesday, 2019-01-30 19:28:49 -0500, you wrote:

> Ah, I see your problem. The change was introduced in #670
> <https://github.com/Python-Markdown/markdown/pull/670>. The thinking
> behind that change was that we should only escape things which have
> not already been escaped. Of course, `&amp;` is already an HTML entity
> so it is escaped and should not be escaped a second time.

I slightly help  maintaining  the documentation  of a project  hosted at
Bitbucket by providing a Python script  which locally turns "*.md" files
into *.html" files exactly the same way as Bitbucket would do.   Accord-
ing to Bitbucket they are using Python Markdown with save mode to escape
any characters having a special meaning in HTML.   To quote from our own
Markdown file explaining how to write documentation:

   This is required because the _Markdown_ language implemented on
   the Bitbucket server does not pass any HTML entities like for
   instance "`&amp;`", "`&ecirc;`", or the equivalent forms for the
   latter, "`&#234;`" and "`&#x000EA;`", on to the HTML code.
   Rather it renders "`&amp;`" into "`&amp;amp;`" which will then
   again be displayed literally as "`&amp;`" by your browser.

And this is the HTML  generated from  the above Markdown source  using a
Markdown version slightly before #670:

   <p>This is required because the <em>Markdown</em> language
   implemented on the Bitbucket server does not pass any HTML entities
   like for instance "<code>&amp;amp;</code>",
   "<code>&amp;ecirc;</code>", or the equivalent forms for the latter,
   "<code>&amp;#234;</code>" and "<code>&amp;#x000EA;</code>", on to the
   HTML code.  Rather it renders "<code>&amp;amp;</code>" into
   "<code>&amp;amp;amp;</code>" which will then again be displayed
   literally as "<code>&amp;amp;</code>" by your browser.

So all we are needing  is a way to modify  our "EscapeHtml" extension so
that the above Markdown source is still turned into the above HTML text.

> ...
>                          I would suggest opening a new issue in GitHub
> to discuss any possible future changes to the code.

Yes,  please do so.   And do not hesitate  to use the above Markdown and
HTML examples as a rationale for this request.

Sincerely,
  Rainer