From: Patrick Gundlach <pg@levana.de>
Subject: Re: total font/encoding confusion
Date: Tue, 12 Mar 2002 10:43:01 +0100 [thread overview]
Message-ID: <02031210430100.00352@levana> (raw)
In-Reply-To: <5.1.0.14.1.20020311013702.02b331f8@server-1>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 726 bytes --]
Hello out there...
> > how should I use the \ShowFont command? (Module fnt-01)
>
> that one is used in the files that are generated by texfont and not
> useful outside that context.
Oh, I see. \showfonts already does exactly what I want :)
> strange, maybe due to the " being active? Are you in "german doublequote
> mode"?
Yes I am. And keeping the \mainlanguage in its original state solves this
problem. Thanks. But One strange thing though:
% output=pdf
%\setupcolors[state=start]
\setupencoding[default=ec]
\starttext
\showfont[Serif at 12pt]
\stoptext
see the second line: colors are off as a default? But the above gives me
blue numbers and a red box around the glyphs.
--
Viele Grüße,
Patrick Gundlach
prev parent reply other threads:[~2002-03-12 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-09 21:02 Patrick Gundlach
2002-03-09 21:36 ` Patrick Gundlach
2002-03-11 0:38 ` Hans Hagen
2002-03-12 9:43 ` Patrick Gundlach [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=02031210430100.00352@levana \
--to=pg@levana.de \
/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).