From: Carlos <linguafalsa@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
Date: Wed, 5 Jul 2023 13:05:32 -0400 [thread overview]
Message-ID: <cwf5pvcrvspimawmvm47oeeypvmatylxvji2j7ckthvgpsfrcx@55gfskt5h4qd> (raw)
In-Reply-To: <4797d8f4-1355-16ff-1a9f-943673060d7d@xs4all.nl>
On Wed, Jul 05, 2023 at 06:12:32PM +0200, Hans Hagen wrote:
> On 7/5/2023 5:53 PM, Carlos wrote:
> > On Wed, Jul 05, 2023 at 04:43:56PM +0200, Hans Hagen wrote:
> > > On 7/5/2023 3:18 PM, Carlos wrote:
> > > > \showmakeup on \TeX\ shows a
> > > >
> > > > tSP:3.282
> > > > THK:-1.721
> > > > H__E
> > > > X
> > > > HK:-1.291
> > > > SP:3.282
> > >
> > > no MWE includes so clueless
> >
> > \starttypescript[mylucidaserif]
> > \definefontsynonym[LucidaBrightRegular] [file:LucidaBrightRegular]
> > \definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic]
> > \definefontsynonym[LucidaBrightDemiBold] [file:LucidaBrightDemiBold]
> > \definefontsynonym[LucidaBrightDemiItalic] [file:LucidaBrightDemiItalic]
> > \stoptypescript
> Hm, isn't that this lucida rip off again? Maybe bad metricks then but I'm
> not going to look into that as the official TUG lucida opentype fonts
> perform okay.
>
> Hans
Coincidentally speaking, a while ago (as a matter of fact this was last week),
I was reading about a heated discussion that happened a few decades
ago in which you said:
«i don't know the difference between input and font encoding and i
don't know what tfm and afm files contain and what they are used for,
and i don't know how to implement and use the right font /char handling
macros etc etc; but i *do* know and listen when a user who actually
uses some glyphs complains about something»
And I don't want to stir up anything here either, but if the convention of
using non-official vs official fonts is the new de facto under lmtx,
I guess my opening question is invalid by all acounts
>
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | 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 / https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___________________________________________________________________________________
>
--
Help stamp out Mickey-Mouse computer interfaces -- Menus are for Restaurants!
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-07-05 17:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 13:18 Carlos
2023-07-05 13:32 ` Carlos
2023-07-05 13:46 ` Carlos
2023-07-05 14:43 ` Hans Hagen
2023-07-05 15:53 ` Carlos
2023-07-05 16:07 ` Carlos
2023-07-05 16:12 ` Hans Hagen
2023-07-05 16:38 ` Carlos
2023-07-05 16:52 ` Hans Hagen
2023-07-06 13:16 ` Carlos
2023-07-06 16:57 ` Carlos
2023-07-07 11:09 ` Carlos
2023-07-07 11:57 ` Hans Hagen via ntg-context
2023-07-05 17:05 ` Carlos [this message]
2023-07-05 17:37 ` Hans Hagen via ntg-context
2023-07-06 13:38 ` Carlos
2023-07-05 16:15 ` Alan Braslau via ntg-context
2023-07-05 17:12 ` Carlos
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=cwf5pvcrvspimawmvm47oeeypvmatylxvji2j7ckthvgpsfrcx@55gfskt5h4qd \
--to=linguafalsa@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).