The Kanji Colorizer works great for Kanji, but when I add Hiragana or Katakana I get English letters in the Diagram field. I changed the digrammed-charters to all and I still get English letters.
Sorry I missed this earlier. There isn’t currently a setting for what you want (displaying kana but not English letters). It seems like it would be a good feature but I’m not sure when I’ll have time to add it.
If you are still interested, then a workaround in this particular case might be to move the HTML to your template instead of having it in the field.
So, I did check what it says but I dont really if it’s correctly set.
What I know is that it was working really well few days ago and now not anymore.
Actually, it’s not working anymore for new cards I create
but still for the old ones. Both have the same fields and are the same note type
I updated Anki recently but I don’t remember if it was one week or one month.
Thank you.
Macbook pro, mac os 10.14.6
Anki 2.1.54
Addons : japanese support - postpone card review - reset card scheduling
Kanji Colorizer (up to date)
I created a new deck with a new note type, with exactly the same fields.
Kanji colorizer is now working for the new cards I created in that new deck but still not in the other ones.
So i found a solution. Thank you for your help
been trying to set source and destination for fields to see if it ever sets the diagram automatically, but nothing seems to work, and the add on config doesn’t even display the code anymore, just the options, so I have no idea if it’s the version that’s messing it up or something else
ankiPoke: Hi. Yes, that should have put stroke order diagrams into the destination field. The first thing I can think of to check is whether your model, dst-field, and src-field are set correctly in the config.
I agree this addon could be more user friendly. I wrote it 12 years ago when anki was different and I was not a very experienced programmer, and I’ve had varying amounts of time and attention for maintaining it since then. I might or might not have some time to work on that this summer.
Anyone: I am at least going to be able to more reliably respond to contributions than I have. (I just noticed that there were some PRs a couple years ago that I didn’t get to and forgot about; those are on my ToDo list now.) A better guide would be a great way for someone to contribute without needing programming knowledge. It could be a pull request or if you’re not comfortable with Github you could email it to me or post it here.
Hi, your add-on is great, thank you!
Could you add a setting in the config section of the add-on with which we can exclude some symbols (like comma) on the generation of the stroke order diagrams?
I have listed in some kanji more than 1 character separated by a comma, therefore every time I have inadvertently selected that field it generates commas. I can’t deactivate the add-on or set “overwrite-dest” to false since I haven’t finished on modifying cards.
Fortunately the add-on doesn’t read parentheses, which I use often in that field to add different reading(s) of the same kanji (I’m using RTK so the definition of kanji is not always binary).
Thanks
It would be really nice if you can also add a setting to put a background color when creating the diagrams. I know that one can go on the styling section of a card to put ‘white’ but it would be great to have this white background already in the field on Browser since with the grey Anki background the kanji stroke orders are difficult to read. Thanks!
edit:
I found a workaround to put white background or other colour combining the “Advanced Copy Fields”, the “Rename Media”, and occasionally the “OpenInExternalEditorRenameDuplicate for ImageAudioVideo WinLinux” add-ons with this code:
<img src=“{{Image Name Field}}.svg” style=“background-color: white”.>
(without the last dot)
I created 2 new fields, for the image name and for the new reference in which I put this code
Sorry I dropped this. You’ve probably either figured it out or moved on, but I wanted to say this in case it helps other people:
The model name needs to contain the world “Japanese”.
When I wrote the addon, I was modeling it after the behavior of the Japanese plugin. In hindsight this was a terrible choice. If I do any active work on this at some point that’s a thing I should get rid of. And I would accept a pull request that removes that.