ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Thomas A.Schmitz <thomas.schmitz@uni-bonn.de>
Subject: font mystery
Date: Sun, 5 Oct 2003 11:15:54 +0200	[thread overview]
Message-ID: <85F5C8D8-F714-11D7-A8F9-00039318D414@uni-bonn.de> (raw)
In-Reply-To: <a06002002bba4c150bfb1@[217.184.17.30]>

My brain is spinning, I hope somebody can help me. I am trying to 
create a new font (with pfaedit), and things seem to be working well. i 
now have most uppercase and lowercase characters. When I run "pdftex 
testfont *Myfont *\table *\bye," I get all the glyphs I created. When I 
do the same with tex or pdfetex, I get all the glyphs I created. When I 
produce a simple testfile for ConteXt, some of the glyphs (specifically 
some of the uppercase characters) are simply missing. But pdfetex can 
create them! What am I doing wrong??? Here's my simple file:

\definefontsynonym[Greekfont][Myfont]

\definefont[MySecondFont][Greekfont]

\starttext

\MySecondFont abcdefghijklmnopqrstuwxyz

A D E F G H J K M N O P Q R S T U Z

\stoptext

On the pdf, I get all the lowercase glyphs + A G O P Q R T Z, but not 
the other glyphs, all of them defined, all of them present in my 
testfont.pdf. The log doesn't show any warning vel. sim. I tried 
playing around with several encodings both in pfaedit (I used Adobe 
Standard, TeX8r, iso 8859) and my tex-file (I tried 8r, texnansi, ec), 
all to no avail. Does anybody have a clue what's going wrong here? It 
almost looks like ConteXt is using some old cache instead of the just 
created tfm and pfb files, but where would that be? I am completely 
baffled!

Best

Thomas

  reply	other threads:[~2003-10-05  9:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-04 19:02 Footnotes Steffen Wolfrum
2003-10-05  9:15 ` Thomas A.Schmitz [this message]
2003-10-05 10:46 font mystery Thomas A.Schmitz
2003-10-08  9:07 Thomas A.Schmitz
2003-10-10 17:05 ` Patrick Gundlach

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=85F5C8D8-F714-11D7-A8F9-00039318D414@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.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).