#jp-mining-note (jpmn) Errors (Font and Misc. Error Codes)

1 messages · Page 1 of 1 (latest)

foggy goblet
#

I've been trying to get the jp-mining-note note type to work and after transferring the cards I've already made (previously used animecards) I'm getting some error messages that I can't figure out how to troubleshoot. Additionally, I'm not getting the right font to display in several of the card's fields (such as the front/example sentences), despite it appearing correctly in other fields (such as the definitions). This is particularly bad because I was able to pin down that it's displaying a font that is meant for Chinese, so it's displaying the equivalent hanzi characters instead of kanji characters, leading to some pretty jarring differences between what is actually supposed to be displayed. I've included a screenshot of what I'm seeing, and I'd appreciate some help with getting this sorted out. For further context, I've been trying to follow the guide at https://xelieu.github.io/jp-lazy-guide/setupAnki/#__tabbed_2_4 for the general set up of Anki, and https://arbyste.github.io/jp-mining-note/importing/ to swap the pre-existing animecards over to the new format

anki_bXAUfdZUSL.jpg anki_QosRP76oDz.jpg
Transfer Existing Notes - jp-mining-note

Documentation for the jp-mining-note project.

Setup: Anki - Lazy Guide

JP Immersion Tool Lazy Guide

royal veldt
#

if you search up tech support, there are dozens of this issue and you just need to update the note

foggy goblet
#

Thanks! I don't know why but somehow the issue fixed itself it seems, without me updating the note at all (in fact the issue started when I updated the note part way through the setup as I had to do it in multiple sittings and an update just happened to drop while I was working on it)

foggy goblet
#

Actually nevermind the issue is still persisting on cards with pitch accents lol

#

Seems like the errors are related to something about the way the cards are trying to handle displaying the pitch accents with the usual line/bar notation near the top of the card, because the error only appears on cards with defined pitch accents, and the text will display in kana but without the pitch accents shown above the words

#

I have checked and I am currently on the latest version (v0.12.0.0-prerelease-12) as the JPMN Manager tool says there's no updates available, and I believe I've followed all of the steps properly to create the card

lucid plume
#

follow the steps written on the link xelieu gave you

foggy goblet
#

Ah ok my bad sorry for that! This setup has been a bit more complicated than I'm used to since I found it through a different site initially lol

20240213_144815.jpg
foggy goblet
#

Ok I've mostly managed to fix everything now, finally got around to going through the update page and following it, and while the errors have all gone away, I am finding that the pitch accents aren't being generated properly, as all of them are being generated as if they have a pitch accent of [0], despite having gone through and updated AJT Japanese, modified the config file, ran the batch command to get rid of the old AJTWordPitch entries, and then ran the command to batch add the new entries

#

Sorry for how long this is taking to finish fixing on my end and everything, navigating the directions is a little confusing since the directions to update the note type itself through Anki says to go to the original website and follow those directions, which then appear to conflict with those given on this site

foggy goblet
#

Strangely, this seems to be working correctly for new cards that I create, such as the one shown here

image.png
covert sparrow
#

@royal veldt do you have any idea how i can tranfer Animecard NoteType with full definition of 4-5 dictionaries into JPMN notetype with primary,secondary, extra definition ?

royal veldt
#

this is similar to animecards with just more fields

covert sparrow
#

I mean. When transfer this to JPMN note. All the definition of old notetype turn into first definition field in JPMN. It make the note so long and wierd. Can you fix this and break definition into primary def and secondary def