An important question so we can figure out where this might need to be fixed – Is this the same or different from studying this card on Anki Desktop?
Your templates aren’t the problem.
I believe this is related to Unicode normalization. The way Anki does it is described in the manual – Adding/Editing - Anki Manual. I’m not familiar with Russian accenting at all, but does that sound similar?
How are you typing the character –
(a) non-normalized (a character plus an added accent)? – I think it won’t be able to match, and you’ll need to enter it as a normalized character instead.
(b) normalized (single character that includes accent)? – then I suspect the type-answer logic is stripping that out somehow, when it strips out the formatting.
Since it’s happening in Desktop as well, it probably needs Desktop-side attention.
According to this handy tool – What Unicode character is this ? – both of those stress marks are separate characters. [Or at least they were by the time they made it through the forum to me.]
Am I right in understanding that this stress mark can be applied to pretty much any character – or at least any vowel character – in Russian? I’m not sure that stress marks like this are able be normalized in the way we usually think of it happening. If letter-with-the-stress-mark isn’t a separate character that exists in Unicode, there’s nothing to normalize that to – it just needs to be matched-as-entered.
@dae This has got to be a text-matching hurdle that the general programming community has already faced, right?
It is handled correctly on things like an accented ‘a’, which has its own entry in the unicode tables. Э́ does not appear to have its own unicode entry, so it can only be made from two separate codepoints.
Any ideas what is happening to this type-answer then? It seems like if it is separate codepoints throughout, it should (1) match as separate codepoints, and (2) remain displayed as a composed character.