From: Henning Hraban Ramm <hraban@fiee.net>
Subject: Re: font encodings (glyph lossed with Gentium in T5)
Date: Sat, 21 Jan 2006 21:45:37 +0100 [thread overview]
Message-ID: <55E6D609-60DB-47D6-B780-6BC6EE1B28F6@fiee.net> (raw)
In-Reply-To: <e5d3f2650601211126k78f55f8fo565b45bd0c2cf7eb@mail.gmail.com>
Am 2006-01-21 um 20:26 schrieb VnPenguin:
>> Ok, Gentium is now online including t5 encoding. (That's not yet
>> mentioned on the page.)
>
> Just tested your package. I loss a glyph which I dont know the name.
> Its shot is at :
> http://people.vnoss.org/~vnpenguin/pub/shots/gentium-dd.png
>
> It seems that you use Gentium 1.01. With Gentium 1.02 in my box, I
> could use this glyph no problem (the shot was done with Gentium 1.02
> in Leafpad editor).
>
> I try to replace your ttf by 1.02 release by modifying map file. But
> this does not help. Maybe we need to recreate files with 1.02 ?
Sorry, I missed that update. Just downloaded it and created the files
anew (now online), but no change.
I guess the strike-through d should be in slot 31; probably an
encoding problem.
I guess I should update ConTeXt, another encoding problem in ec was
fixed.
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-21 20:45 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 [this message]
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
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=55E6D609-60DB-47D6-B780-6BC6EE1B28F6@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).