Support thread for my KLC deck.
Feel free to ask any questions, report mistakes, make suggestions, …
… and of course, a thumbs-up on the deck page is appreciated as well 
.
Hello! Firstly: thank you for an amazing deck. I’ve got a problem with the front-side kanji not appearing on subsequent reviews. As in: the first time a card appears, there is the usual big kanji there. But then on following days, the kanji doesn’t appear, and instead there is just the key meaning displayed. On the back-side, the kanji appears normally (with the multicoloured stroke order). I realise this may be intentional; it would be a useful setup for someone learning how to produce the kanji from memory. But I’m just trying to learn how to recognise them. The problem is the same on my PC and Android device. Thanks for your help. 
Hey, thanks for your review!
I’m not sure, but what you’re describing sounds like the second card type appearing. You may have seen that there are two:
- Recall: Meaning → Kanji (& Reading)
- Recognition: Kanji → Meaning & Reading
For new cards, I think I set it to first introduce all Recall cards, and then start the Recognition ones. That’s rendered moot however if you changed the order as I describe at the end of the deck’s AnkiWeb description.
Anyway, about to your issue: The most obvious behavior at play I can think of is Anki’s default burying of remaining related cards (→ different ones generated from the same note) when they’re scheduled for the same day. If you somehow hit only the Recall cards, that’ll have buried the Recognition ones, and may have given the impression that the latter are missing.
(Said behavior can be changed at: Main window → click on 
next to the deck →Options → set “Bury related new cards until the next day” as desired)
But whatever it is, since you already hinted you’re not interested in the Recall cards (understandable, not least as having both quickly consumes a lot of review time better left for vocab&co.):
You can just suspend them and Anki will ignore them entirely in the future.
- from Anki’s main window, open the card browser (“Browse” in the top bar’s middle, or press b)
- just left of the search bar, check that the the display mode is cards/C (click to toggle if it’s note/N)
- use card:recall as search query (add deck:{your deckname} if there happens to be another which uses recall as a template name)
- select all cards (e.g.: click a row, then hit Ctrl+a)
- either right-click on the selection & pick Toggle Suspend from the menu, or hit Ctrl+j to trigger that
I hope that resolves your issue, feel free to write if it doesn’t.
Thank you so much for this deck. It works perfectly along with Kodanasha. I’ve been using this deck until card number 986. After that all the card are not displaying the large colored stroke order kanji. I am using Anki Droid but I am having the same issue on Anki Web. I get the error - Card content error: failed to load. I have tried troubleshooting and looking online for help but not sure how to resolve this issue. Thanks again for making this deck.
hiya, really like the deck! I was wondering about mnemonics. I know you have previously said that you haven’t included them for copyright reasons. However, I was wondering if you could tell me how to ‘hypothetically’ manually add mnemonics to all the cards?
Hi. Thanks for putting so much time into this excellent deck. I was wondering if you might give permission to extract some of the data for use in a non-Anki project. It may come to nothing, but I have been contemplating writing an app to aid learning kanji through writing. I already wrote tools to create a database from KanjiDic, KanjiVG and JMDict extracts. That should work but, since I bought the book, the KKLC presentation order, keywords and selected vocabulary seem ideal.
Hi, thanks for the question and sorry for not responding sooner.
I’m afraid that regarding the KKLC content itself, that question must to be addressed to the KKLC’s author, Andrew Scott Conning.
But as far as just the deck’s presentation and its use of non-commercial resources is concerned, if it’s done non-commercial like Anki (and with attribution to Anki & the deck), feel free to go ahead.
1 Like
I’ve got an issue. The Kanji itself does not appear, on front or back, when using AnkiWeb. It shows when using the Anki App (Mac/PC), but not in any web browser on Mac or Windows (Firefox/Chrome-based). From using the web inspector, it seems like the Kanji is present (but not visible) in the background but the elements in front are opaque. Sometimes the very bottom of the kanji can be seen poking out. Do you know what’s going on? Are other people able to use this deck on AnkiWeb? I tried deleting the deck and then re-downloading and reimporting, but the situation is the same.
Hi @nwwt, thanks for the Deck! I’ve been using it for the last 1,5 months and I love it!
Unfortunately in the latest version of Anki (or atleast 25.09.4) there are problems with the SVG images since they updated something. Could you have a look at this (if you’re still alive here lol)
Thanks!
1 Like
@dae Hello Damien, I’ve been getting a bunch of reports about this, yet I haven’t followed Anki development for a while…
If possible, could you please point me to the relevant recent change so I can take a deeper look?
In recent releases, there were some new security errors logged to the console, whereas with the current git HEAD the deck now renders with stroke numbers shown permanently, in an undesired style:
The diagrams are included as tags, with the files linking to a shared CSS file.
For years, the rendering (showing various cursor movement) was:
Damien is no longer involved in the development of Anki (at least not as much as before). @abdo is the most active developer I’ve seen on this forum.
Why don’t you simply use svg files as in the first deck? You can use a font to display the characters without stroke numbers, or make a copy of each svg without numbers if it doesn’t increase the deck size that much.
If the reports you’re getting are that it happened in the security patch releases of 25.09.3 and 25.09.4, then the scope of the changes was relatively small –
2 Likes
@nwwt Check the changes in the mediasrv.py file specifically.
The main branch doesn’t have the security fixes yet, but I’m not sure about the rendering changes. It might be due to the Qt upgrade.
2 Likes
The transitions (hiding of the stroke numbers), as shown in the GIF, are not possible with a statically included SVG (i.e., using img instead of object). Since one is learning the kanji and not the numbers, the latter are only shown when needed; this is a key feature of the deck. The Recognition card actually does make use of a font on its front side.
It’s indeed from .3–.4; the warnings are CSP-related ones:
JS error /06feb.svg:1 Refused to load the stylesheet ‘http://127.0.0.1:42641/_svg.css’ because it violates the following Content Security Policy directive: “default-src ‘none’”. Note that ‘style-src-elem’ was not explicitly set, so ‘default-src’ is used as a fallback.
JS error /06feb.svg:1 Refused to apply inline style because it violates the following Content Security Policy directive: “default-src ‘none’”. Either the ‘unsafe-inline’ keyword, a hash (‘sha256-ShQ8F48XVaFgzaaMKdV45fMsPw8BL5q1bEYYIVuGITQ=’), or a nonce (‘nonce-…’) is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the ‘unsafe-hashes’ keyword is present. Note also that ‘style-src’ was not explicitly set, so ‘default-src’ is used as a fallback.
(The latter repeats 39 times.)
I’ll check whether there’s some way to alleviate this quite intrusive restriction.
I logged an issue for this: