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 13:55:55 -0500	[thread overview]
Message-ID: <m0lezr9x9m.fsf@virginia.edu> (raw)
In-Reply-To: <5330d88e-5641-3c9f-7c97-a944153796dc@xs4all.nl>

On Fri, Jan 07 2022, 18:10:39 +01 Hans Hagen <j.hagen@xs4all.nl> wrote:
> On 1/7/2022 4:18 PM, J. P. Ascher via ntg-context wrote:
>> Hi, all,
>> I'm a long time lurker (on gmane), first time poster. First, thank

[...]

>> Any ideas?
> when you use a complex font (in this case with lots of ligatures)
> doing a fallback can interfere with these features especially when
> they have been put in the private areas which are basically
> 'undefined'
>
> you're accessing an st ligature directly but normally you will do that
> by enabling a font feature

Thank you Hans, for your response, and your years of hard work on many
great manuals and code!

I'm doing that deliberately, but for my own peculiar reason: I'm working
on transcribing 17c texts in terms of the typographical sorts available
in the physical founts of their print shop.  I.e. I usually disable all
ligatures and only manually put in a ligature when the physical type was
a ligatured one, as best I can tell.  Not every shop had the same founts
and not every compositor used every available ligature in the same shop.

My bigger technical problem is that I need to combine paragraphs of
normally typeset prose with other paragraphs where I don't want the
typesetting engine to change a single glyph, or too much of
the spacing.

I pulled it off for my dissertation with a bunch of hacks, like the
above, which proved to me that it could actually work.  From the readers
I've had, it seems that as you read more of the prose, you start
noticing that the description is different in subtle ways and
eventually--I hope--learn to see the evidence of typesetting that I'm
writing about reproduced in my work and thus now can in the historical
item itself.

But, I think that the actual solution is a real font for this.  I'm just
making hacks between appointments--I can afford the time away from the
treadmill of applications to do it correctly right now.

Sometimes, I wonder if a monospace, like DejaVu's, with the extra glyphs
would make the distinction between prose and description clearer, but
I'll have to wait until I have an occasion to try that too.

I'd be curious if anyone else has seen someone trying something similar.

yrs,
-jp
___________________________________________________________________________________
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 18:55 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 [this message]
2022-01-07 19:19     ` Hans Hagen via ntg-context
2022-01-07 21:39       ` J. P. Ascher via ntg-context
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=m0lezr9x9m.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).