Cloze Cards¶
With Single & Multiline Cards the text of both the front and back of each card is specified.
With cloze cards a single text is specified, together with an identification of which parts of the text should be obscured.
The front of the card is displayed as the text with (one or more) cloze deletions obscured.
Cloze Deletions¶
A part of the card text is identified as a cloze deletion by surrounding it with the cloze delimiter.
Single Cloze Deletion¶
By default, the cloze delimiter is ==, and a simple cloze card would be:
Displayed when reviewed
Initial View
The first female prime minister of Australia was [...]
After Show Answer Clicked
The first female prime minister of Australia was Julia Gillard
Multiple Cloze Deletions¶
If the card text identifies multiple parts as cloze deletions, then multiple cards will be shown for review, each one occluding one deletion, while leaving the other deletions visible.
For instance, the following note:
Card 1 Initial View
The first female [...] of Australia was Julia Gillard
Card 2 Initial View
The first female prime minister of Australia was [...]
After Show Answer Clicked (same for both cards)
The first female prime minister of Australia was Julia Gillard
These two cards are considered sibling cards. See sibling cards regarding the Bury sibling cards until the next day scheduling option.
Cloze Types¶
Simplified Clozes¶
Simplified Clozes are the Cloze Type we have been using so far. They keep working as before, but now you can add hints to them. That means each card will occlude one deletion, showing its hint if available, while leaving the other deletions visible.
For instance, the following note:
Will generate two cards, with the following fronts:
This [...] doesn't need to have number on clozesThis note doesn't need to have [hint] on clozes
And both will have the same back:
Classic Clozes¶
Classic Clozes are the same as Simplified Clozes, but they also have a sequence number used to sort and group deletions.
For instance, the following note:
This is a ==cloze==^[a hint][^1]. This is ==too, but without hint==[^2]. And this one is asked ==together with the first cloze==[^1].
Will generate two cards, with the following fronts:
This is a [a hint]. This is too, but without hint. And this one is asked [...].This is a cloze. This [...]. And this one is asked together with the first cloze.
And both will have the same back:
This is a cloze. This is too, but without hint. And this one is asked together with the first cloze.
Generalized Cloze Overlapping¶
The Cloze Overlapping Generalization allows you to dictate the behavior of each deletion individually. Each deletion has its own set of actions that indicate how it will behave on each card:
afor ask (hide the deletion answer in the front of the card while showing it in the back).hfor hide (hide the deletion answer both in the front and back of the card).sfor show (show the deletion answer both in the front and back of the card).
For instance, the following note:
==Some context for items 2 and 4, but that could spoil items 1 and 3. Note that this doesn't even need to be asked==[^hshs]
.
- ==Item 1==[^ashh]
- ==Item 2==[^hash]
- ==Item 3==[^hhas]
- ==Item 4==[^hhha]
In this example, 4 cards will be generated, where items 1 to 4 will be asked sequentially. When asking Item 1, all other text will be hidden. When asking Item 2, just the Item 1 and the context will be displayed. When asking Item 3, only the Item 2 will be displayed. Finally, when asking Item 4, both the Item 3 and the context text will be displayed.
Custom Cloze Patterns¶
You can now create your own Cloze Patterns. For instance, to emulate Anki-like clozes (e.g., {{1::text::hint}}), simply add the following pattern to your settings:
Brackets [] delineate where the sequence number and hint will be placed, along with any additional characters of your choice (e.g., the :: in the example above). Clozecraft automatically generates a regex pattern based on your custom pattern. Sequence numbers are identified by finding numbers between brackets, hints by finding the word hint in brackets, and the deleted text by finding the word answer.
Here are some examples of custom patterns:
| Explanation | Pattern in the Settings | Simplified Cloze Usage | Numbered Cloze Usage | Generalized Cloze Overlapping Usage |
|---|---|---|---|---|
| Anki-Like Pattern | {{[123::]answer[::hint]}} |
Brazilians speak {{Portuguese}}Or, with hint: Brazilians speak {{Portuguese::language}} |
Brazilians speak {{1::Portuguese}}Or, with hint: Brazilians speak {{1::Portuguese::language}} |
Brazilians speak {{a::Portuguese}}Or, with hint: Brazilians speak {{a::Portuguese::language}} |
| Highlighted pattern with hint and sequencer in footnotes. | ==answer==[^\\[hint\\]][\\[^123\\]] |
Brazilians speak ==Portuguese==Or, with hint: Brazilians speak ==Portuguese==^[language] |
Brazilians speak ==Portuguese==[^1]Or, with hint: Brazilians speak ==Portuguese==^[language][^1] |
Brazilians speak ==Portuguese==[^a]Or, with hint: Brazilians speak ==Portuguese==^[language][^a] |
Warning
Make sure that your custom cloze patterns do not conflict with other flashcard separators.
For instance, the Anki-Like pattern {{[123::]answer[::hint]}} conflicts with the default single line flashcard separator ::.
Warning
You can use brackets as part of your pattern, but you need to escape them with \\.
For instance, in the pattern ==answer==[^\\[hint\\]][\\[^123\\]], the brackets inside the outer brackets are escaped (^\\[hint\\] & \\[^123\\]).
In your settings, you can add multiple patterns at once, separating them with a new line:
Then, you can use them in your notes:
This note has both ==highlighted clozes==[^1] and {{2::anki like clozes}}
And this note has both ==highlighted clozes==^[footnote hint][^1] and {{2::anki like clozes::anki like hint}}
Warning
Remember, deletions must be of the same Cloze Type. You can't mix, for instance, a Classic Cloze with a Simplified Cloze in the same note, as they employ different ways to sort and identify the cards.