From: Hans Hagen <pragma@wxs.nl>
To: Khaled Hosny <khaledhosny@eglug.org>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>, news3@nililand.de
Subject: Re: manipulate ttf-fonts loaded with luatex
Date: Thu, 28 Oct 2010 18:06:04 +0200 [thread overview]
Message-ID: <4CC99F6C.8060204@wxs.nl> (raw)
In-Reply-To: <20101028155959.GA6201@khaled-laptop>
On 28-10-2010 5:59, Khaled Hosny wrote:
> As one of the luaotfload maintainers, I assure you that we never touch
> such low level code :) at least to stay compatible with ConTeXt (I
> really really have no interest in two incompatible OpenType
> implementations, so in regard to that luaotfload is not a real fork but
> ConTeXt code wrapped in some LaTeX palatable sweetener).
in that case it's fontforge that merges the two vectors (technically we
can have one glyph name representing two unicode points) using the
/C<num> logic that taco mentions; the best solution is to have sane
glyph names
> This either means it was fixed in later version of ConTeXt (our code is
> derived from the texlive version), or the ConTeXt variant is doing more
> stuff than what the plain one does.
it also relates to looping over the sparse tables ... sort of arbitrary
what comes first
but, as taco mentions, \char140 does give a king here; doesn't it in latex?
-----------------------------------------------------------------
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 16:06 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
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 [this message]
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=4CC99F6C.8060204@wxs.nl \
--to=pragma@wxs.nl \
--cc=khaledhosny@eglug.org \
--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).