ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Stefan Wachter <Stefan.Wachter@gmx.de>
Subject: Why uses Context 8r encoding used instead of the specified ec encoding?
Date: Tue, 08 Feb 2005 20:55:39 +0100	[thread overview]
Message-ID: <4209193B.7070300@gmx.de> (raw)

Hi all!

Fonts are driving my crazy! I have the following document that clearly 
states that the font encoding should be "ec". Yet, somewhere behind the 
scenes the ec-encoded font uhvr8t is mapped into the 8r-encoded font 
uhvr8r.

Can someone reveal this deep secret?

Best regards,
--Stefan

PS: The pdfmapline instruction cause the uhvr8r font not to be embedded. 
Doing so proves that Context really uses the uhvr8r font and not the 
uhvr8t font.

\enableregime[il1]
\setupencoding[default=ec]
\setupoutput[pdftex]
\usetypescriptfile[pdf-typescript.tex]
\usetypescript[pdf]
\setupbodyfont[MyHelvetica,sans,20pt]
\setupheadertexts[]
\pdfoptionpdfminorversion 4
\starttext
\pdfmapline{=uhvr8r Helvetica "TeXBase1Encoding ReEncodeFont" <8r.enc}
This is a test.
\stoptext

With the typescriptfile pdf-typescript.tex:

\starttypescript [sans] [xhelvetica] [name]
  \writestatus{x}{y}
  \definefontsynonym [Sans]            [uhvr8t]  [encoding=ec]
  \definefontsynonym [SansBold]        [uhvb8t]  [encoding=ec]
  \definefontsynonym [SansItalic]      [uhvro8t] [encoding=ec]
  \definefontsynonym [SansSlanted]     [uhvro8t] [encoding=ec]
  \definefontsynonym [SansBoldItalic]  [uhvbo8t] [encoding=ec]
  \definefontsynonym [SansBoldSlanted] [uhvbo8t] [encoding=ec]
  \definefontsynonym [SansCaps]        [uhvr8t]  [encoding=ec]
\stoptypescript

\starttypescript [pdf]
  \definetypeface [MyHelvetica] [ss] [sans] [xhelvetica] [default] 
[encoding=ec]
\stoptypescript

             reply	other threads:[~2005-02-08 19:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08 19:55 Stefan Wachter [this message]
2005-02-09 14:11 ` Taco Hoekwater
2005-02-09  9:27   ` Hans Hagen
2005-02-09 11:54   ` Stefan Wachter
2005-02-09 12:12     ` Hans Hagen
2005-02-09 12:24     ` Thomas A.Schmitz
2005-02-15  8:27       ` Stefan Wachter
2005-02-09 17:23 ` Hans Hagen
2005-02-10 12:56   ` Christopher Creutzig
2005-02-10 14:02     ` Hans Hagen

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=4209193B.7070300@gmx.de \
    --to=stefan.wachter@gmx.de \
    --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).