This is the HTML I get both \text{\r A} and \text{Å}

<span class="mord text">
  <span class="mord accent">
    <span class="vlist-t">
      <span class="vlist-r">
        <span class="vlist" style="height: 0.94677em;">
          <span class="" style="top: -3em;">
            <span class="pstrut" style="height: 3em;"></span>
            <span class="mord">A</span>
          </span>
          <span class="" style="top: -3.25233em;">
            <span class="pstrut" style="height: 3em;"></span>
            <span class="accent-body" style="left: -0.375em;">˚</span>
          </span></span></span></span></span></span>

So when I use Å in the input, it doesn't just get decomposed into an A and a Unicode combining form, it gets decomposed into an A and a manually positioned ring glyph. In this case, if the -0.375em had been about -0.25em instead we might not have noticed the issue.

Ah ha! I see now that unicodeSymbols.js decomposes all latin accented forms, so that Å really does end up parsing just like \r A.

If I comment out this line:

"\u00c5": "\u0041\u030a", // Å = \r{A}

Then I get a parse error for \text{Å} because it is not a recognized codepoint.

But since I've just added Latin Extended A and B, I bet that this trick will work for characters in those blocks:

\text{ů} displays with the ring too far to the left, but if I comment out unicodeSymbols.js:125 then it displays as a single font glyph and the ring is in the right place. (This only makes it display correctly in text mode, however, and prevents it from displaying in math mode)

I don't know much about unicodeSymbols.js, or how KaTeX uses fonts, but I'd propose that we assume that in text mode all the characters we want are going to be supported directly by the font. I think I'd try to fix this by:

modify unicodeScripts() to extend the definition of the Latin script to include all of Latin-1 and not just the extensions. So that Å, for example, is a supported codepoint.
Modify Parser.js:1036 so that it only does the unicodeSymbols substitutions in math mode and not in text mode.
I was going to say that the third step was to make Å look right in math mode by figuring out why was causing the ring to be mis-positioned. But it turns out that math mode Å has a special case in symbols.js so it doesn't get decomposed in math mode. So I guess just fixing these accented forms in text mode may be all that is needed. (The Czech u with the ring and Turkish I with the dot don't work in math mode, so there is nothing to fix there.)

Uh oh!

Poorly rendered Å #1066

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions