ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "J. P. Ascher via ntg-context" <ntg-context@ntg.nl>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: "J. P. Ascher" <jpa4q@virginia.edu>,
	"mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Fallback fails for Linux Libertine O to Junicode over private area, debugging?
Date: Fri, 07 Jan 2022 16:39:20 -0500	[thread overview]
Message-ID: <m04k6f9q02.fsf@virginia.edu> (raw)
In-Reply-To: <18457453-f38b-e2dc-3e6c-68a59f48781c@xs4all.nl>

> in that case you can best use a rather bare font i.e. no features at
> all apart from kerning and use dynamic features grouped
>
> in lmtx there are other tricks too
>
> \noleftligaturing
> \norightligaturing
> \noligaturing
>
> and other conbtrols like
>
> \noleftkerning
> etc

This is very useful.  I'm thinking of writing an environment that
switches: I like keeping the ease of typing normal characters, rather
than getting glyphs directly, because it's easier to proof on screen in
the editor.

>> writing about reproduced in my work and thus now can in the historical
>> item itself.
>
> one aspect is how ligatures are made: some fonts have single shapes,
> others use replacements and kerning of (then) multiple shapes

I think you wrote about this somewhere else and it got me interested in
physical type from my period: it looks like some printers did some of
the same things, sometimes!  You might have a box of pre-composed
ligatures, or not; you might take a knife to some letters to tweak them
for specific uses, or not; you might even shave wrong-sized letters to
fit them in where they don't belong.  Those shaved down letters could
end up back with their siblings, now shifting around during printing, or
they could be tossed.

The pre-composed ligatures might most often be made on matrices struck
with the same punches as for the non-ligatured glyphs, but typefounders
might re-strike matries now and then, so you might end up with slightly
different pre-composed ligatures in different, or even the same, fount
of type.  It's nuts!

Fred Smeijers writes about this a little bit in *Counterpunch*, but
I had already started thinking about it because of ConTeXt.

I wouldn't have known to look if it weren't for the typographical
education you and your colleagues pass around; so, thank you again!

___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2022-01-07 21:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 15:18 J. P. Ascher via ntg-context
2022-01-07 16:52 ` Youssef Cherem via ntg-context
2022-01-07 16:59   ` J. P. Ascher via ntg-context
2022-01-07 18:33     ` Hans Hagen via ntg-context
2022-01-07 17:10 ` Hans Hagen via ntg-context
2022-01-07 18:55   ` J. P. Ascher via ntg-context
2022-01-07 19:19     ` Hans Hagen via ntg-context
2022-01-07 21:39       ` J. P. Ascher via ntg-context [this message]
2022-01-07 22:01         ` Why mtxrun fails ? Jean-Pierre Delange via ntg-context
2022-01-07 22:40           ` Otared Kavian via ntg-context
2022-01-07 23:00           ` Youssef Cherem via ntg-context
2022-01-08  0:42             ` Jean-Pierre Delange via ntg-context
2022-01-08  0:48               ` Jean-Pierre Delange via ntg-context
2022-01-08  0:45             ` Jean-Pierre Delange via ntg-context
2022-01-08  8:05           ` juh via ntg-context
2022-01-08 10:42         ` Fallback fails for Linux Libertine O to Junicode over private area, debugging? Hans Hagen via ntg-context
2022-01-07 18:23 ` Hans Hagen via ntg-context
2022-01-07 19:11   ` J. P. Ascher via ntg-context

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=m04k6f9q02.fsf@virginia.edu \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.nl \
    --cc=jpa4q@virginia.edu \
    /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).