You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"...for the Back Template you could alternatively make a copy of the Front Template, rather than referencing it through {{FrontSide}}, and then customize the Back Template to be totally different."
However, when you do that, the current cloze loses the special formatting that you are supposed to see.
The deletion characters substituted for the current cloze on the front, and the corresponding 'revealed' current cloze text on the back, are supposed to be bold and blue, by default anyway, on both sides of the card. This special formatting makes the cloze characters stand out from the rest of the text in the field. You can even change the formatting per side according to the instructions in issue #7 .
This works fine if you use the simplest Back template, like so:
<div id="back">
{{FrontSide}}
</div>
However, if you use a custom Back template instead distinct formatting is lost. This is so even in the sample deck, even using the example custom Back template given on the Instructions page:
Per the Instructions page (INSTRUCTIONS.md)
However, when you do that, the current cloze loses the special formatting that you are supposed to see.
The deletion characters substituted for the current cloze on the front, and the corresponding 'revealed' current cloze text on the back, are supposed to be bold and blue, by default anyway, on both sides of the card. This special formatting makes the cloze characters stand out from the rest of the text in the field. You can even change the formatting per side according to the instructions in issue #7 .
This works fine if you use the simplest Back template, like so:
However, if you use a custom Back template instead distinct formatting is lost. This is so even in the sample deck, even using the example custom Back template given on the Instructions page:
The text was updated successfully, but these errors were encountered: