From: Hans Hagen <pragma@wxs.nl>
Cc: ConTeXt mailing list <ntg-context@ntg.nl>
Subject: Re: Still don't understand how to switch fonts in the new context / ec versus 8r
Date: Mon, 27 Aug 2001 09:56:26 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20010827095301.02b83460@server-1> (raw)
In-Reply-To: <3B88A3FF.D33C8AFA@ukrpost.net>
At 10:23 AM 8/26/2001 +0300, Olya Briginets wrote:
>However, I still wonder why the old method did not work.
>After
> \definetypeface[tms][rm][serif][times][default][encoding=ec]
> \usetypescript[berry][ec]
> \setupbodyfont[serif,tms]
>I got that \characterencoding is @default@, not @ec@, while
>\usetypescript[berry][ec] implies that \Adiaeresis is \@ec@Adiaeresis, not
>\@default@Adiaeresis.
>I guess this is because some @@fontencoding becomes @default@ while defining
>typeface in such a way, despite [encoding=ec].
>I see inconsistency here. Or there isn't?
maybe, in any case, if so, i will run into it and repair it, for the momen
tuse the working versions
>I want to learn a way to use some cyrillic fonts, maybe in different
>encodings,
>and make it as seamless as possible, that's why I'd wish to do it the *right*
>way, not just working somehow.
sure, but then forget about the berry naming and go the ec-* or 8r-* or
t2a-* way since then at least you *know* what the encodings involved are.
The mapping to berry is just there for good old times sake and i'm not
going to extend that list of names myself; we should do it in such a way
that users kind of understand what is happening.
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
prev parent reply other threads:[~2001-08-27 7:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 10:15 Still don't understand how to switch fonts in the new context Olya Briginets
2001-08-21 13:45 ` Hans Hagen
2001-08-21 19:59 ` Olya Briginets
2001-08-22 12:06 ` Hans Hagen
2001-08-22 18:28 ` Olya Briginets
2001-08-23 16:17 ` Hans Hagen
[not found] ` <5.1.0.14.1.20010823181735.0256b7d0@server-1>
[not found] ` <3B858F30.4DF1A13B@ukrpost.net>
2001-08-24 8:04 ` Still don't understand how to switch fonts in the new context / ec versus 8r Hans Hagen
2001-08-26 7:23 ` Still don't understand how to switch fonts in the new context / ecversus 8r Olya Briginets
2001-08-27 7:56 ` Hans Hagen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.1.0.14.1.20010827095301.02b83460@server-1 \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).