ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Carlos <linguafalsa@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\
Date: Fri, 7 Jul 2023 07:09:27 -0400	[thread overview]
Message-ID: <3sizixnezhhtu4ffzyygsl32534xanmiw4x6lhudplwy63hcqc@tntqk4535x57> (raw)
In-Reply-To: <7j6llxkawlxrqt2rre3bzjrbbhztxfbg6gjnwdde36slhzanvo@pvknjxtdz7gq>

On Thu, Jul 06, 2023 at 12:57:57PM -0400, Carlos wrote:
> On Thu, Jul 06, 2023 at 09:16:58AM -0400, Carlos wrote:
> > On Wed, Jul 05, 2023 at 06:52:30PM +0200, Hans Hagen wrote:
> > > On 7/5/2023 6:38 PM, Carlos wrote:
> > > > 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
> > > > 
> > > > The first sentence is irrelevant. And a guess. Bad metrics is not the
> > > > culprit
> > > > 
> > > > if it were true, the same problem would be under lualatex, correct?
> > > 
> > > well, who knows what (me)tricks those fonts have embedded .. are these the
> > > official TUG lucida open type fonts? if so,
> > > 
> > > \setupbodyfont[lucida]
> > > 
> > > should just work (btw, you also don't set up math)
> > > 
> > > > But it's not there.
> > > I can't (and won't) check that as I don't have (lua)latex installed nor have
> > > those fonts. I also don't see where this \qquad is in your example.
> > 
> > 
> > Using the same fonts under lualatex yields \TeX\ without an issue. 
> > 
> > \documentclass{article}
> > 
> > \usepackage{unicode-math}
> > 
> > \defaultfontfeatures{Ligatures=TeX}
> > 
> > \setmainfont[
> >       ItalicFont=LucidaBrightItalic,
> >         BoldFont=LucidaBrightDemiBold,
> >   BoldItalicFont=LucidaBrightDemiItalic,
> >   ]{LucidaBrightRegular}
> > %
> > \setsansfont[
> >       ItalicFont=LucidaSansOblique,
> >         BoldFont=LucidaSansDemiBold,
> >   BoldItalicFont=LucidaSansDemiOblique,
> >   ]{LucidaSansRegular}
> > %
> > \setmonofont[
> > %      ItalicFont=LucidaTypewriterOblique,
> >         BoldFont=LucidaTypewriterBold,
> > %  BoldItalicFont=LucidaTypewriterBoldOblique,
> >   ]{LucidaTypewriterRegular}
> > 
> > \begin{document}
> > 
> > {\rm    \input{knuth}}
> > 
> > \textsf{\input{knuth}}
> > 
> > \end{document}
> > 
> > > 
> > > As for the \showmakup ... it is used extensively and afaiks there are no
> > > issues with it.
> > 
> > After running lualatex the problem dissappears. Or it seems like it. 
> > 
> 
> I take it back. It doesn't disappear. It's still there.  \showmakeup
> yields the right readings but yet the kerning is off on \TeX\.
> 
> With \showmakeup everything ‹seems› correct. I guess the readings
> output are correct, and also, amazingly, the horizontal kerning,
> as you aptly named it, for \TeX\
> 
> Not under lualatex. Everytihng seems fine there.
> 
> But I perfectly understand that there would not be any support for these
> fonts. Thanks though! 
> 
> (trying to send this message with an attachment as before but it wouldn't
> go through) 


In other words, and please, just ignore my message. 

But it seems as if \showmakeup masks the problem. Dont' get me wrong, I
find \showmakeup output as one of the best indicators out there. 

But if one were to say 

{\rm \qquad{\!\!\!\!\!\!\!\!\!\!\!hurt \TeX\ significantly}}

the readings are quite probably as accurate as readings can ever be, but
at the same time, \TeX\ is displayed perfectly, which shouldn't have. 

It really doesn't matter how many quad quad quad quad happened to be, or
how many negative spaces happened to be included, because it never gets
it quite right unless \showmakeup is used 

This is quite interesting actually. 

If, for example, with \showmakeup, one were to say within the same document 

\hbox to 1cm{\ss \input{knuth}}

or rather, \vbox to 1cm{\ss \input{knuth}} or whatever

\showmakeup displays it astonishingly correctly indeed

anyhow


___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2023-07-07 11:09 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 [this message]
2023-07-07 11:57                 ` Hans Hagen via ntg-context
2023-07-05 17:05       ` Carlos
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=3sizixnezhhtu4ffzyygsl32534xanmiw4x6lhudplwy63hcqc@tntqk4535x57 \
    --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).