<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 3/22/2021 10:37 AM, Marius Spix via
      Unicode wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:trinity-598d1498-ee82-4cc8-ad1e-f488765ddafc-1616434640211@3c-app-webde-bs04">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div style="font-family: Verdana;font-size: 12.0px;">
        <div>Dear Christoph,</div>
        <div> </div>
        <div>according to Mozilla [1],</div>
        <div> </div>
        <div>"The <sup> element should only be used for
          typographical reasons—that is, to change the position of the
          text to complywith typographical conventions or standards,
          rather than solely for presentation or appearance purposes."</div>
        <div> </div>
        <div>[1]
          <a class="moz-txt-link-freetext" href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/sup">https://developer.mozilla.org/en-US/docs/Web/HTML/Element/sup</a></div>
        <div> </div>
      </div>
    </blockquote>
    <p>Now, I have a hard time coming up with examples of "presentation
      or appearance" purposes that require small, raised letters or
      digits and are *not* related to some "typographical convention".</p>
    <p>The problem with <sup> seems to be more in the fact that
      there's more than one convention that might apply.</p>
    <p>A./<br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
    <blockquote type="cite"
cite="mid:trinity-598d1498-ee82-4cc8-ad1e-f488765ddafc-1616434640211@3c-app-webde-bs04">
      <div style="font-family: Verdana;font-size: 12.0px;">
        <div>Regards,</div>
        <div> </div>
        <div>Marius Spix</div>
        <div> 
          <div> 
            <div name="quote" style="margin:10px 5px 5px 10px; padding:
              10px 0 10px 10px; border-left:2px solid #C3D9E5;
              word-wrap: break-word; -webkit-nbsp-mode: space;
              -webkit-line-break: after-white-space;">
              <div style="margin:0 0 10px 0;"><b>Gesendet:</b> Montag,
                22. März 2021 um 18:17 Uhr<br>
                <b>Von:</b> "Christoph Päper via Unicode"
                <a class="moz-txt-link-rfc2396E" href="mailto:unicode@unicode.org"><unicode@unicode.org></a><br>
                <b>An:</b> <a class="moz-txt-link-abbreviated" href="mailto:unicode@unicode.org">unicode@unicode.org</a><br>
                <b>Betreff:</b> Re: HTML entities</div>
              <div name="quoted-content">Marius Spix via Unicode
                <a class="moz-txt-link-rfc2396E" href="mailto:unicode@unicode.org"><unicode@unicode.org></a>:<br>
                ><br>
                > CSS is also no solution, because <sub> and
                <sub> are semantic tags (like <del>,
                <strong>, <em> and <kbd>) and not just
                stylistic ones (like <s>, <b>, <i> or
                <tt>).<br>
                <br>
                When HTML introduced the `b`/`strong` and `i`/`em`
                distinctions, it should also have added
                presentational/semantic pairs<br>
                <br>
                - `sup`/`exp` (exponent) or `pow` (power) and<br>
                - `sub`/`idx`, `ind` (index) or `base`.<br>
                <br>
                I don’t think the WHATWG or W3C would be interested in
                adding them now.<br>
                 </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>