ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt meeting Lua tutorials
Date: Wed, 25 Aug 2010 11:17:13 +0200	[thread overview]
Message-ID: <4C74DF99.10604@wxs.nl> (raw)
In-Reply-To: <CD9F07F9-89AB-47A1-9F95-7AA20C554D21@st.estfiles.de>

On 25-8-2010 10:05, Steffen Wolfrum wrote:
>
> Am 24.08.2010 um 20:37 schrieb Oliver Buerschaper:
>
>>> Hi all,
>>>
>>> Today I started preparations for my activities at the ConTeXt meeting.
>>>
>>> There are two small lua tutorials in the program, and I am looking
>>> for input on both. There is one that is supposed to be a general
>>> beginner's introduction, and one specifically about fonts.
>>>
>>> For both, I am looking for input on what subjects I should cover?
>>>
>>> Since both tutorials will end up as articles/wiki pages, it makes
>>> sense to ask everybody on the list for input (but requests by actual
>>> attendees will be scored considerably higher).
>>
>> Perhaps some example to modify a font at runtime? I don't know whether that's possible at all, but if yes, it would be great to see how one could modify kerning tables etc. Often a font needs to be groomed but its license places some restrictions on modifying the file itself...
>
>
> +1

This is somewhat tricky. Actually I had a mechanism for that but I 
discarded the code. However there will be a feature like that some day 
as it needs a rather tight integration in the core of context's font 
handling. (btw, there is a feature for type 1 fonts that adds 'missing' 
kerns based on shape codes).

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
___________________________________________________________________________________


  reply	other threads:[~2010-08-25  9:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-21 11:48 Taco Hoekwater
2010-08-21 12:43 ` luigi scarso
2010-08-22 14:37 ` Henning Hraban Ramm
2010-08-23 13:47   ` Hans Hagen
2010-08-23 14:37     ` Henning Hraban Ramm
2010-08-23 16:37 ` Mojca Miklavec
2010-08-23 18:22   ` Taco Hoekwater
2010-08-23 21:39     ` luigi scarso
2010-08-24  3:31     ` David Rogers
2010-08-23 22:36 ` Aditya Mahajan
2010-08-24 18:37 ` Oliver Buerschaper
2010-08-25  8:05   ` Steffen Wolfrum
2010-08-25  9:17     ` Hans Hagen [this message]
2010-08-25 10:46       ` John Haltiwanger
2010-08-25 10:46       ` Khaled Hosny
2010-09-01 19:34         ` Steffen Wolfrum
     [not found]       ` <98D0BF51-278A-4DE1-8834-283DD2E035B5@post.werksatz.com>
     [not found]         ` <4C74E444.5040501@wxs.nl>
     [not found]           ` <530D2CCA-5CE5-45BB-A407-640108712EFC@post.werksatz.com>
2010-08-25 11:11             ` Hans Hagen

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=4C74DF99.10604@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).