Re: Still don't understand how to switch fonts in the new context

[Olya Briginets <bolya@ukrpost.net>]

Hello Hans,

Hans Hagen wrote:
> 
> Hi,
> 
> I have problem specifying font encoding: it works only until font switching
> >command. I write (the example from Willi Egger):
> >
> >   \setupencoding[default=ec]
> >   \setupbodyfont[pos,ber]
> >   \enableencoding[ec]
> >   \enableregime[windows]
> >
> >   \starttext
> >
> >   \Adiaeresis Ä\"Argerlicher Fall.

[skipped]

> You can add the following code to cont-new.tex (assuming you use pdfetex)

[skipped]

> You can now say something like
> 
> \message{\tracedfontname{Serif}} and see what font name is actually used
> and where in the chain the encoding is set.

I did it and get
  Serif -> Times-Roman -> ec-utmr8a [ec] -> ptmr8t 
just what I expected, so it seems that it's all OK with fonts. 
It seems to me that the problem is not with fonts, but either with encodings or
with font switching commands, like \tf, \tfa etc. 

One more time: 
after \setupencoding[default=ec] \setupbodyfont[pos,ber] fonts seems to be
correct, but commands like \Adiaeresis are -- well, not undefined, but seems not
defined correctly. 
If I write 
  \enableencoding[ec], 
or if I write directly in my document
  \definecharacter Adiaeresis      196
and so on, it helps, but only up to next font switching command.
\tf spoils encoding again, so I need \enableencoding[ec] again.

> The last name in the row should be defined in a map file and mapped onto a
> real filename. Either this map file is loaded runtime, or the entry should
> be in your local pdftex map file.

I checked both pdf and dvi output (with dvitype utility), and revealed that the
fonts there are what I expected, but instead of, say, A or U with diaeresis
(umlaut) I got A or U, combined with the character with code 127 -- I mean,
instead of all umlauts, tildes, grave and acute accents, char 127 are used. I
have no idea why.

> Now, if there is no [ec] in this chain, you're not using ec, which means
> some error in the setup.

It seems that _fonts_ are ec, but definitions from enco-ec don't work.
In fact, it seems that some of definitions in \fonstrategies somehow switches
font to default encoding or something else, but I'm not able to dig so deep.

> Once you've sorted out what you want / need, we can add some entries to
> typescripts useful for your language

Currently I'm just trying to make system work with already supported languages
and fonts, e.g. deutch and urw fonts. I know that simple \setupbodyfont[ber,pos]
did work in previous ConTeXt versions. 

> Hans

Olya