Re: [NTG-context] Cyrillic glyphs display problem with standalone ConTeXt distribution under win32
Hello everyone, Great thanks to Mojca Miklavec, that was definitely a font problem. Using antykwa-torunska did solve it.
\usetypescript[modern-base][t2a] \setupbodyfont[modern]
Latin modern doesn't have cyrillic letters.
I took the code from wiki. It was for cm-super font package, included in the distribution. Is there a problem with this package in mswincontext.zip?.. Best regards, Vladimir Smirnov
On 5/7/06, Vladimir Smirnov wrote:
Hello everyone,
Great thanks to Mojca Miklavec, that was definitely a font problem. Using antykwa-torunska did solve it.
\usetypescript[modern-base][t2a] \setupbodyfont[modern]
Latin modern doesn't have cyrillic letters.
I took the code from wiki. It was for cm-super font package, included in the distribution. Is there a problem with this package in mswincontext.zip?..
I'm only guessing now, but it might be that cm[whatever] maps to lm[whatever] even at the places where cm-super fonts should be used, which means that the code used to work until Latin Modern replaced Computer Modern. Another (not really probable) possibility is that latin modern is preloaded and interferes with loading new encoding from "almost the same family". If I figure anything out, I'll report it, but Hans or others probably know better how to handle with this than I do. Mojca
Mojca Miklavec wrote:
On 5/7/06, Vladimir Smirnov wrote:
Hello everyone,
Great thanks to Mojca Miklavec, that was definitely a font problem. Using antykwa-torunska did solve it.
\usetypescript[modern-base][t2a] \setupbodyfont[modern]
Latin modern doesn't have cyrillic letters.
I took the code from wiki. It was for cm-super font package, included in the distribution. Is there a problem with this package in mswincontext.zip?..
I'm only guessing now, but it might be that cm[whatever] maps to lm[whatever] even at the places where cm-super fonts should be used, which means that the code used to work until Latin Modern replaced Computer Modern.
Another (not really probable) possibility is that latin modern is preloaded and interferes with loading new encoding from "almost the same family".
If I figure anything out, I'll report it, but Hans or others probably know better how to handle with this than I do.
\starttext \usetypescript [serif,sans,mono,math] [computer-modern] [default,name,size,t2c] \usetypescript [map] [computer-modern] [t2c] \usemathcollection[default] \setupbodyfont[modern] \dorecurse{200}{\char\recurselevel\space \space} \stoptext this does not work here because i don't have the full cm super installed (i can add a reasonable subset to the less and less minimal distribution) (there are quite some cyr related definitions in the typescripts but what encoding makes most sense?) ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Vladimir Smirnov wrote:
Hello everyone,
Great thanks to Mojca Miklavec, that was definitely a font problem. Using antykwa-torunska did solve it.
\usetypescript[modern-base][t2a] \setupbodyfont[modern]
Latin modern doesn't have cyrillic letters.
I took the code from wiki. It was for cm-super font package, included in the distribution. Is there a problem with this package in mswincontext.zip?..
can you make some test files? - utf-8 encoded - your prefered font encoding - your input encoding Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (3)
-
Hans Hagen -
Mojca Miklavec -
Vladimir Smirnov