From: Henning Hraban Ramm <hraban@fiee.net>
Subject: Re: font encodings (glyph lossed with Gentium in T5)
Date: Sun, 22 Jan 2006 13:36:27 +0100 [thread overview]
Message-ID: <5F13FD74-D1DB-44CF-A50E-8D473B042752@fiee.net> (raw)
In-Reply-To: <e5d3f2650601212303jced2575ia2db4f1094003c4f@mail.gmail.com>
Am 2006-01-22 um 08:03 schrieb VnPenguin:
> ...
> ){/work/apps/teTeX/share/texmf-local/fonts/enc/dvips/vntex/t5.enc}
> </work/apps/
> teTeX/share/texmf-local/fonts/truetype/sil/gentium/genr102.ttf
> Warning: pdfetex (file /work/apps/teTeX/share/texmf-local/fonts/
> truetype/sil/ge
> ntium/genr102.ttf): glyph `dcroat' not found
>>
> Output written on test-gentium.pdf (1 page, 25034 bytes).
> Transcript written on test-gentium.log.
>
> The glyph "dcroat" was not found :( I think there is problem in
> Gentium fonts with this glyph.
Yes, I saw that.
For pdfTeX's tool ttf2afm doesn't see a lot of letters in some fonts
I guess pdfTeX's code for accessing letters in TT fonts is somewhat
broken.
Or something in ConTeXt, I don't know.
E.g. if I install the Junicode fonts with texfont, the t5 table is
half empty. If I create the AFMs with FontForge, it's mostly filled,
but I get some of the glyph ... not found' warnings, i.e. it can
access some more characters, but still not all.
But *all* of the characters should be there (they *are* in the font!).
'dcroat' (striked-through d) is a typical case.
Please, any of the wizards, what can we do?
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://contextgarden.net
http://www.cacert.org (I'm an assurer)
next prev parent reply other threads:[~2006-01-22 12:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 19:26 VnPenguin
2006-01-21 20:45 ` Henning Hraban Ramm
2006-01-21 21:48 ` Henning Hraban Ramm
2006-01-21 22:13 ` VnPenguin
2006-01-21 22:54 ` Henning Hraban Ramm
2006-01-22 7:03 ` VnPenguin
2006-01-22 12:36 ` Henning Hraban Ramm [this message]
2006-01-22 12:53 ` VnPenguin
2006-01-22 13:44 ` Thomas A. Schmitz
2006-01-22 15:02 ` VnPenguin
2006-01-30 17:11 ` VnPenguin
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=5F13FD74-D1DB-44CF-A50E-8D473B042752@fiee.net \
--to=hraban@fiee.net \
--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).