Mention that you can put the unknown_morphs field on the back side

[Vilhelm-Ian]

What is the current documentation?

It dosen't mention you can do it. I have been thinking for some time about this. But always thought not to bother because of the triviality.

What changes do you suggest?

To avoid using the highlight feature and simply find out which words are unknown on the card, consider adding the "Unknown words field" to the back of the card template, as shown: {{Unknowns}}.

[HQYang1979]

Yes, basically I only want the Unknown highlighted. There is no need to highlight learning or more.

I think this alternative suffices.

[mortii]

@Vilhelm-Ian Where in the docs do you want this to be mentioned?

Yes, basically I only want the Unknown highlighted. There is no need to highlight learning or more.

@HQYang1979 instead of using all of these:

[morph-status=unknown] { color: #f75464; } /* red */
[morph-status=learning] { color: #8bb33d; } /* light-green */
[morph-status=known] { color: green; }

You can just use the unknown part and remove the others:

[morph-status=unknown] { color: #f75464; } /* red */

[HQYang1979]

You can just use the unknown part and remove the others: [morph-status=unknown] { color: #f75464; } / red /

Thank you. Yes I have been doing this.

[Vilhelm-Ian]

@mortii Maybe put it here It can help people not foot gun themselves

[mortii]

It can help people not foot gun themselves

:rofl:

Sure, i can add that.

[HQYang1979]

Putting the Focus here is nice. Thank you again. @Vilhelm-Ian

[mortii]

@Vilhelm-Ian 'Unknowns' is also and extra field so there is still the same foot shooting potential by using that instead... the only difference between the approaches is that the user does not have to set the css:

[morph-status=unknown] { color: #f75464; } /* red */
[morph-status=learning] { color: #8bb33d; } /* light-green */
[morph-status=known] { color: green; }

I'm not quite sure of the best way to convey this information. Maybe we should create a separate page for 'unknowns' to explain that too? I dunno.

[Vilhelm-Ian]

@mortii my point was they can set unkows on the back of the card so that they don't have to enable the css highlighting option at all

[mortii]

@mortii my point was they can set unkows on the back of the card so that they don't have to enable the css highlighting option at all

Oh, ok. So not to mitigate any foot shooting, but to not having to bother with css.

[Vilhelm-Ian]

Yes by not having to bother with css they won't accidently put the html in the wrong field

[mortii]

Yes by not having to bother with css they won't accidently put the html in the wrong field

A couple of days ago I was too hasty when switching back settings on my main anki profile after having worked on the dev profile, and i accidentially selected the japanese-field in unknowns and all the japanese sentences were replaced by the focus morph instead.

Using unknowns is not less risky in that sense (in fact I would have preferred to have the sentences overwritten by their highlighted html version instead of being replaced by a single morph), but not having to go through the extra step of adding css to card-templates is a valid point.

I'll add it to the docs shortly.

[Vilhelm-Ian]

@mortii This is what i mean. The only thing HQYang1979 wanted from using the syntax highlithing is so he can now which words are the unknowns in the sentence. Once I mentioned that he can edit the card template to show the unknown words. He stopped using syntax highlithing.

[mortii]

I think I will expand the guide to include a section for how to use each extra field, hopefully that will make it more clear that highlighting is not the only approach to this kind of setup.

[mortii]

@Vilhelm-Ian @HQYang1979 I updated the Extra Fields guide, is it understandable? Any suggestions for making it better?

[Vilhelm-Ian]

Looks good to me

[HQYang1979]

Looks good to me too. I am thinking make a video of Ankimorph on Youtube, something like MattvsJapan one, but I am of that procrastinating personality...

[Vilhelm-Ian]

Wait for it to finish development. It's still not ready for mass use

[mortii]

Great, I'll close this then.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.