Randomize Fonts New

AnkiWeb addon 82628558

Randomizes card fonts during review only for notes and cards matching configurable criteria, letting users choose included fonts per language in Tools settings.
AI-generated summary; may contain mistakes.

appearancecard-templatesfork-or-reupload

Open on AnkiWeb Find alternatives

AnkiWeb

Votes
8 (πŸ‘ 5 Β· πŸ‘Ž 3)
Updated
2023-04-16
Anki versions
unknown
License
Not found (this does not mean that the addon has no license)
Virus scan
No ClamAV match A match does not prove malware. No match does not prove that the code is safe.
Languages
Python
Description language
en

Maintenance

abandoned

  • Last update or commit: 2023-04-16 (1295 days before the snapshot).

GitHub

No GitHub repository linked.

Will it work on my Anki?

Version branches
Min AnkiMax AnkiUpdated
2.1.0–2023-04-16
History across monthly snapshots

Loading…

Similar addons

Randomize Fonts archived

Randomizes the font of text using language-specific CSS classes, with per-language font selection and configurable card search criteria.

formattingappearancecard-templates

10 votes 24% approval πŸ‘ 5 Β· πŸ‘Ž 5 ⭐ 1 Updated 2021-03-19
Randomize Fonts (new) archived

Randomizes card fonts by configurable criteria such as deck name, success rate, tags, and language classes, letting users preview searches and choose enabled fonts per language.

appearance

5 votes 12% approval πŸ‘ 2 Β· πŸ‘Ž 3 ⭐ 1 Anki 2.1.1~ Updated 2023-12-18
Japanese Card Randomizer

Randomizes Japanese card fonts and optionally swaps hiragana/katakana, displays vertical text, and changes text size during review.

formattingappearance

15 votes 70% approval πŸ‘ 14 Β· πŸ‘Ž 1 ⭐ 6 Anki 2.1.49~ Updated 2022-06-17
Cookie monster

Enables cookie usage on cards, letting the question side set values like a randomly chosen font that the answer side can read, including on custom note types via scripts.

appearancecard-templates

17 votes 59% approval πŸ‘ 14 Β· πŸ‘Ž 3 Updated 2018-04-13

Description

Update/rewrite of my old addon: https://ankiweb.net/shared/info/1603486068 This one is "better" in that you can select which cards ought to have their fonts randomized depending on a bunch of different criteria: Note contains field with name X Note contains field with contents matching X Note contains field with contents of length X Note contains field with X many Kanji Note has tags X (and/or) Y (and/or) Z... Note's deck name matches X Note's type name matches X Card is in state X Card has a success rate <|<=|==|>=|>|!= X Card has been passed X times To configure: Go to Tools > Configure Random Fonts On the Search tab, check the box next to the criteria you would like to use, the fill out whatever values you'd like to use for that criteria On the "Configure Fonts" tab, disable any fonts which you don't want to be considered when a random font is chosen for that language. In your card template, add the name of the language that should be used as a class of the field. i.e. "<span class='Japanese'>{{Japanese}}</span>" Now, while you are reviewing, each card will be evaluated against your criteria. If it matches, the fonts will be randomized. Notes: * I do not control which fonts are available for each language, Qt does. If it decides that your font does not support Japanese characters, it will not appear under "Japanese" in the "Configure Fonts" tab. Maybe find a different language that that font does appear under and use that instead? * Forgive me if the UI/UX isn't that great. I'm not a designer and also I had this looking the way I wanted in Qt5, then the change to Qt6 changed things a lot. * If you want to see the name of the font which was randomly picked on each card, there is a hidden item with an ID of the name of the language that you can show with css. For example, "#JapaneseFontName { display: inline-block !important; }". Style this to your liking. * The full list of languages can be found in the dropdown on the "Configure Fonts" tab or here (Ignore the "QFontDatabase::" prefix): https://doc.qt.io/qt-6/qfontdatabase.html#WritingSystem-enum I'll get this up to GitHub soon. Let me know if you run into any issues or have any suggestions.