From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Questions apon Questions
Date: Fri, 03 Aug 2012 12:24:25 +0200 [thread overview]
Message-ID: <501BA6D9.7050502@wxs.nl> (raw)
In-Reply-To: <709002D7-320C-4740-9BD1-45373277D8EE@web.de>
On 3-8-2012 10:18, Keith J. Schultz wrote:
> I have started going top down into the lua source in the normal MacTeX 2012
> distro. Just to learn how things are getting done.
>
> So here are my Questions
>
> 1) Is GDEF still not supported in font.loader
Afaik at the tex end we don't need information stored in GDEF tables.
> 2) Is GPOS still not supported in font.loader
GSUB and GPOS are supported as dropping any of them would render the
whole machinery useless.
> 3) Are there any Program Specifictions anywhere to be had
> and where
The luatex manual describes the tables. As the code comes from fontforge
you can use the fontforge manuals (and program) as reference.
> 4) Any Class diagrams, flow charts, UML or similar documentation
> and where for font manager and even Context or LuaTeX
The luatex manual. I'm working on a more detailed manual for font
handling in context (but as we sometimes go beyond what opentype
provides it will be somewhat specialized).
> 5) Any of 3 and 4 in the source distribution?
The luatex manual is.
> 6) Is the font.loader mainly in Lua or C? (I have not gotten that far yet?)
> (only a couple hours of work done)
C producing a lua table
> 7) Can I safely assume that at that there enough modularization in the code
> sothat I can work bottom up? That is add thing needed to the font.loader{} and
> font{}
I guess so, that is: if you start patching the loader you need to spawn
a separate entity of luatex (some derived work).
> 8) Is there any special natural language convention when discussing Context inorder to
> differentiate between OT-Font-Table and Lua-Tables and data structures?
One of the things that context does is normalize and optimize the raw
font data as provided by the loader. One can always print the tables (as
used in context, using the table serializer). The structure used is
rather stable. There are also hooks to kick in extra code (for instance,
context adds additional features.)
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:[~2012-08-03 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 8:18 Keith J. Schultz
2012-08-03 10:24 ` Hans Hagen [this message]
[not found] ` <10D2D244-4A5C-42B0-A3A3-76563E57554F@web.de>
2012-08-03 12:05 ` Hans Hagen
2012-08-03 17:05 ` Khaled Hosny
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=501BA6D9.7050502@wxs.nl \
--to=pragma@wxs.nl \
--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).