ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Script to automatically generate typescripts
Date: Fri, 4 Jun 2010 18:19:16 +0200	[thread overview]
Message-ID: <AANLkTilJ_IuhuOP4k6PBpZIgojlISBH1aVJBCphxASAD@mail.gmail.com> (raw)
In-Reply-To: <4C092512.8010200@uni-ulm.de>

On Fri, Jun 4, 2010 at 18:08, Michael Murphy wrote:
> On 04/06/2010 12:00, Mojca Miklavec wrote:
>>
>> Just note: you can get an enormous amount of font information with luatex.
>
> If you can get so much information out of LuaTeX, why do we need typescripts
> in the first place?

1.) The typescripts have been written long before LuaTeX existed.
2.) The typescripts still work is almost exactly the same way as they did before
3.) Your can read a lot of information about a specific font (which
features are available, which glyphs exist etc. etc. etc.), but that
still doesn't give you any information about which fonts you want to
combine together and which features you want to use.

Take Antykwa Półtawskiego. It comes as regular/italic, in 4 weights
(light, normal, medium, bold), in 5 widths (extended, semi-extended,
normal, semi-condensed, condensed), about 5 encodings for MKII. You
need to tell to ConTeXt somehow whether you want to combine light and
medium or normal weight and bold, or maybe normal with semi-extended
bold, you may want the size to adapt automatically when you change
font size. There is also no reliable way to determine which fonts
belong together. You still need to assign a font with a variant
somehow.

Reading info about a font doesn't really solve the problem of "being
able to automatically assign rm, bf, bi etc.", but I admit that there
*IS* room for improvement for font handling mechanism in a more
user-friendly way (and lua can be of enormous help of course).

Mojca
___________________________________________________________________________________
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-06-04 16:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 16:51 Michael Murphy
2010-06-04  7:32 ` luigi scarso
2010-06-04  8:03   ` Mojca Miklavec
2010-06-04  8:23     ` luigi scarso
2010-06-04 10:27       ` Hans Hagen
2010-06-04  8:37     ` Hans Hagen
2010-06-04  8:50       ` luigi scarso
2010-06-04  9:52         ` Michael Murphy
2010-06-04 10:00           ` Mojca Miklavec
2010-06-04 10:08             ` luigi scarso
2010-06-04 16:08             ` Michael Murphy
2010-06-04 16:19               ` Mojca Miklavec [this message]
2010-06-04 18:33               ` Hans Hagen
2010-06-04 10:01           ` luigi scarso
2010-06-04 10:21           ` Mojca Miklavec
2010-06-04 10:25             ` Hans Hagen
2010-06-04 10:29             ` luigi scarso
2010-06-04 11:16               ` Khaled Hosny
2010-06-04 16:05                 ` Michael Murphy
2010-06-04 14:12           ` Vnpenguin
2010-06-07 10:59 ` Thomas Floeren
     [not found] <mailman.1395.1275590320.4277.ntg-context@ntg.nl>
2010-06-03 21:33 ` Vyatcheslav Yatskovsky
2010-06-03 22:40   ` Michael Murphy
     [not found] <mailman.1411.1275638618.4277.ntg-context@ntg.nl>
2010-06-04  9:26 ` Vyatcheslav Yatskovsky

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=AANLkTilJ_IuhuOP4k6PBpZIgojlISBH1aVJBCphxASAD@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --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).