Closed pgmmpk closed 8 years ago
I don't think it works. Try doing:
\newfontfamily\churchslavonicfont[Script=Cyrillic,Ligatures=TeX,HyphenChar=_]{PonomarUnicode.otf}
after calling
\usepackage{churchslavonic}
@typiconman Try this. I do not understand why it works, but it seem to do the trick. Please confirm
It's still not working for me:
`................................................. . fontspec info: "defining-font" . . Font family 'PonomarUnicode.otf(0)' created for font 'PonomarUnicode.otf' . with options []. . . This font family consists of the following shapes: . . * 'normal' with NFSS spec.: . <->"[PonomarUnicode.otf]/ICU:script=latn;language=DFLT;" .................................................
! Missing \endcsname inserted.
FYI, I don't know if this is the desired behavior, but the \cuMarginMarkText
command redefines the subsequent \cuMarginMark
. Example:
\cuMarginMark{※} A small black mark \def\cuMarginMarkText#1{\cuKinovar{#1}} \cuMarginMark{※} A small red mark \def\cuMarginMarkText#1{\Huge \cuKinovar{#1}} \cuMarginMark{※} A huge red mark
Yes, this is as designed. Idea is the you define font/size/color of margin marks once - in the preamble and afterwards just use \cuMarginMark (local changes still possible via something like \cuMarginMark{{\tiny а}}).
Since you find it surprising, lets discuss alternatives. What would be a better interface to allow customization of font/size/color of margin marks?
No, I think this makes sense. It's just not clear from the documentation. We should document it.
\cuMarginMark{{\tiny а}}
makes sense as well; I think we should document it too.
@typiconman please check the latest changes to the docs:
https://github.com/slavonic/cu-tex/pull/41/commits/edf896f4c4ca289e87cbe19d9f8702601a17798b
Made a few spellings corrections and fixed a typo that was causing Make to error-out.
@typiconman I believe I found the solution for the underscore in font definition parameters. Please check