Remove green brackets by text edit XMCD (XML)

Quinn M wrote: I need removal, not hiding.

I don't know of a way to do it through the Mathcad interface, but there are several methods you could try.

In Mathcad, click immediately after a region's opening tag and press backspace; this deletes the region's provenance metadata.  Editing a region also deletes the provenance metadata.

You might also be able to do it via the automation interface by writing a script that deletes all regional provenance metadata. 

In a text editor, look for the <ml:provenance and </ml:provenance xml tags and delete them and everything between them, except for the <ml:define ... </ml:define region ... this is actual maths part.  The xml file format is not well documented from a user perspective (as far as I know and unless Maintenance customers have access to resources I don't), so all I can go on is inspection of a region with metadata, which looks something like the following:

  <math optimize="false" disable-calc="false">

[[[ Delete the <ml:provenance bit ... ]]]

    <ml:provenance expr-id="1" xmlns:ml="http://schemas.mathsoft.com/math30">

    <originRef doc-id="...  </originRef>

    <parentRef doc-id="...  </parentRef>

    <comment xmlns="http://schemas.mathsoft.com/provenance10"/>

    <originComment xmlns="http://schemas.mathsoft.com/provenance10"/>

    <contentHash xmlns="http://schemas.mathsoft.com/provenance10">0a73aa6fb0c58b88ada5b8d849c4dbb4</contentHash>

[[[ up to here ]]]

[[[ Keep the bit ... ]]]

    <ml:define>

      <ml:id xml:space="preserve">k</ml:id>

      <ml:range>

      <ml:real>0</ml:real>

      <ml:apply>

        <ml:id xml:space="preserve">last</ml:id>

        <ml:id xml:space="preserve">x</ml:id>

      </ml:apply>

      </ml:range>

    </ml:define>

[[[ up to here ... this is the actual region math definition]]]

[[[ Delete the <ml:provenance bit ... ]]]

    </ml:provenance>

[[[ up to here ]]]

  </math>

It would be wise to keep a backup copy with provenance if you adopted this route, just in case any regions differed from the above xml format and give rise to errors in the converted worksheet.

Hopefully, somebody will have some better options.

Stuart