templates: cyphar: minor readme updates
Some of the configuration bits were not fully explained (or were wrong in the case of JaPitch). Signed-off-by: Aleksa Sarai <cyphar@cyphar.com>
This commit is contained in:
parent
c74cf02026
commit
d032a63988
|
@ -73,6 +73,13 @@ can add to it manually in the browser.
|
||||||
|
|
||||||
![yomichan settings](yomichan_settings.webp)
|
![yomichan settings](yomichan_settings.webp)
|
||||||
|
|
||||||
|
By using `{cloze-prefix}<b>{cloze-body}</b>{cloze-suffix}` for `SentKanji`, the
|
||||||
|
targeted word will be automatically highligted. If you prefer to do the
|
||||||
|
highlighting yourself (or don't want to highlight the target word on the card
|
||||||
|
front), use `{sentence}` instead. Note that Yomichan can be a bit peculiar when
|
||||||
|
deciding how much of a conjugated verb counts as "part" of the verb, so double
|
||||||
|
check that you're happy with the automatic highlighting.
|
||||||
|
|
||||||
## Japanese Support settings
|
## Japanese Support settings
|
||||||
|
|
||||||
If you use the [Japanese Support add-on][anki-jpn], make sure to modify
|
If you use the [Japanese Support add-on][anki-jpn], make sure to modify
|
||||||
|
@ -118,7 +125,14 @@ word "Japanese" in its name, please add the note type name to `"noteTypes"`.
|
||||||
As with the Japanese Support add-on, you need to add the right field to
|
As with the Japanese Support add-on, you need to add the right field to
|
||||||
`srcFields`. However, because the JaPitch add-on writes to `VocabPitchPattern`
|
`srcFields`. However, because the JaPitch add-on writes to `VocabPitchPattern`
|
||||||
you don't need to modify `dstFields`. And instead of adding `SentFurigana`, you
|
you don't need to modify `dstFields`. And instead of adding `SentFurigana`, you
|
||||||
want to add `VocabFurigana`.
|
want to add `VocabKanji`. I also would set `regenerateReadings` to true because
|
||||||
|
JaPitch provides more information than Yomichan.
|
||||||
|
|
||||||
|
Note that this can lead to extra readings being generated, and you cannot
|
||||||
|
currently force it to only use the correct reading by setting the source field
|
||||||
|
to `VocabFurigana` (doing so will lead to an entirely wrong reading to be
|
||||||
|
generated because it treats the furigana as a separate word, breaking up the
|
||||||
|
expression into multple parts).
|
||||||
|
|
||||||
Your final config should look something like this:
|
Your final config should look something like this:
|
||||||
|
|
||||||
|
@ -137,7 +151,7 @@ Your final config should look something like this:
|
||||||
"srcFields": [
|
"srcFields": [
|
||||||
"Expression",
|
"Expression",
|
||||||
"Kanji",
|
"Kanji",
|
||||||
"VocabFurigana"
|
"VocabKanji"
|
||||||
],
|
],
|
||||||
"styles": {
|
"styles": {
|
||||||
"ꜜ": "ꜜ",
|
"ꜜ": "ꜜ",
|
||||||
|
|
Loading…
Reference in a new issue