From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: news3@nililand.de
Subject: Re: manipulate ttf-fonts loaded with luatex
Date: Thu, 28 Oct 2010 16:59:34 +0200 [thread overview]
Message-ID: <4CC98FD6.2010100@wxs.nl> (raw)
In-Reply-To: <20101028133259.GA5857@khaled-laptop>
On 28-10-2010 3:33, Khaled Hosny wrote:
> On Thu, Oct 28, 2010 at 03:08:09PM +0200, Taco Hoekwater wrote:
>> On 10/28/2010 02:57 PM, Ulrike Fischer wrote:
>>>
>>> And when I have corrected the fontdata, is there a way (besides
>>> using a fea-file) to manipulate the fontdata so that the input "K"
>>> outputs the glyph "c140"?
>>
>> I have not followed this closely, bit it seems to me that the problem
>> is more likely caused by a fea file than that it is cured by it.
>
> It seems like the font is using that multiple code points for the same
> glyph some thing of TrueType, I'm not sure, but I recall FF
> documentation recommending against using it.
indeed there is some multiple mapping going on and as we're dealing with
sparse tables and loops over a hash we get a bit arbitrary matches when
there are multiple ...
there is also some pretty high altuni field present
if I look at the font in fontforge the chess symbols sit in latin slots
so it's in the font
if the font is okay, accessing by glyph name will work ok
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-10-28 14:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 10:37 Ulrike Fischer
2010-10-27 18:35 ` Aditya Mahajan
2010-10-27 20:01 ` Ulrike Fischer
2010-10-27 21:32 ` Aditya Mahajan
2010-10-28 8:34 ` Ulrike Fischer
2010-10-28 12:33 ` Hans Hagen
2010-10-28 12:57 ` Ulrike Fischer
2010-10-28 13:08 ` Taco Hoekwater
2010-10-28 13:29 ` Ulrike Fischer
2010-10-28 13:33 ` Khaled Hosny
2010-10-28 14:59 ` Hans Hagen [this message]
2010-10-28 15:37 ` Ulrike Fischer
2010-10-28 16:01 ` Hans Hagen
2010-10-28 17:08 ` Ulrike Fischer
2010-10-28 17:17 ` Hans Hagen
2010-10-28 17:48 ` Ulrike Fischer
2010-10-28 18:56 ` Hans Hagen
2010-11-02 15:16 ` Ulrike Fischer
2010-11-02 15:40 ` Hans Hagen
2010-10-28 19:35 ` Hans Hagen
2010-10-28 19:46 ` Khaled Hosny
2010-10-28 20:29 ` Hans Hagen
2010-10-28 15:48 ` Taco Hoekwater
2010-10-28 15:59 ` Khaled Hosny
2010-10-28 16:06 ` Hans Hagen
2010-10-28 16:29 ` Hans Hagen
2010-10-28 16:47 ` Ulrike Fischer
2010-10-28 17:03 ` taco
2010-10-28 19:48 ` Khaled Hosny
2010-10-28 13:10 ` Hans Hagen
2010-10-28 13:34 ` Ulrike Fischer
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=4CC98FD6.2010100@wxs.nl \
--to=pragma@wxs.nl \
--cc=news3@nililand.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).