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 09:32:51 -0400 [thread overview]
Message-ID: <fcmrqytmrcyirpt2ghob6wnphdxfnobhr63cgeqgiq3ly5sl7c@f6fbipcdbrgl> (raw)
In-Reply-To: <hr55oaxlc4fehocetww7nzpr65htpx2xhgnqrh3ndbcsr3ekn2@yup2lnctrlrp>
[-- Attachment #1: Type: text/plain, Size: 3872 bytes --]
On Wed, Jul 05, 2023 at 09:18:35AM -0400, Carlos wrote:
> \showmakeup on \TeX\ shows a
>
> tSP:3.282
> THK:-1.721
> H__E
> X
> HK:-1.291
> SP:3.282
>
> I assume that SP stands for space. Correct me if I'm wrong
>
> After reading some of the manuals that mention \showmakeup with and
> without [spaces] and so forth, I couldn't find any more info related
> to this.
>
> If anyone can provide me more information as to what does HK means there?
>
> Anyhow
>
> If I were to have, say, a control _word_ such as \TeX\, the sequence of
> TeX kerning is thrown off. The only remedy would be to have a a \qquad
> preceding the control sequence e.g., {\qquad
> \TeX\ significantly} to sort of ameliorate this side-effect. But then
> again. Spacing is off. e.g.,
>
> The separation of any of these four components would have
> hurt {\qquad\TeX\ significantly}. If I had not participated fully in
>
> But it's interesting that \showmakeup, kerning and spaces would
> display what's to be expected. And yet, the aformentioned set of
>
> tSP:3.282
> THK:-1.721
> H__E
> X
> HK:-1.291
> SP:3.282
>
> is accurate nevertheless. And a very nice implementation at that,
> but one I fear can't be included on a final document either.
>
> With that being said, the introduction of a \qquad, in addition to
> \showmakeup with, say, redundancy aside, whatever is preceding the \TeX\
> alongside the file would also introduce a space where no space was ever
> there before.
>
> Because of all of this, and unfortunately, \showmakeup is not quite helpful
> here either. Although it does so displays the amount of spaces and
> so forth, any addition of a \qquad also adds a very subtle unwanted
> space.
>
> And since we're looking here, I pressume, solely for accuracy and
> perfection, we're left here with neither: zero, zip. It evaporates.
>
>
> --
> Dear Emily:
> I'm still confused as to what groups articles should be posted
> to. How about an example?
> -- Still Confused
>
> Dear Still:
> Ok. Let's say you want to report that Gretzky has been traded from
> the Oilers to the Kings. Now right away you might think rec.sport.hockey
> would be enough. WRONG. Many more people might be interested. This is a
> big trade! Since it's a NEWS article, it belongs in the news.* hierarchy
> as well. If you are a news admin, or there is one on your machine, try
> news.admin. If not, use news.misc.
> The Oilers are probably interested in geology, so try sci.physics.
> He is a big star, so post to sci.astro, and sci.space because they are also
> interested in stars. Next, his name is Polish sounding. So post to
> soc.culture.polish. But that group doesn't exist, so cross-post to
> news.groups suggesting it should be created. With this many groups of
> interest, your article will be quite bizarre, so post to talk.bizarre as
> well. (And post to comp.std.mumps, since they hardly get any articles
> there, and a "comp" group will propagate your article further.)
> You may also find it is more fun to post the article once in each
> group. If you list all the newsgroups in the same article, some newsreaders
> will only show the article to the reader once! Don't tolerate this.
> -- Emily Postnews Answers Your Questions on Netiquette
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
--
As of next Tuesday, C will be flushed in favor of COBOL.
Please update your programs.
[-- Attachment #2: Screenshot_20230701_030306.png --]
[-- Type: image/png, Size: 17399 bytes --]
[-- Attachment #3: Screenshot_20230701_030044.png --]
[-- Type: image/png, Size: 37961 bytes --]
[-- Attachment #4: Type: text/plain, Size: 495 bytes --]
___________________________________________________________________________________
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 13:32 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 [this message]
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
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=fcmrqytmrcyirpt2ghob6wnphdxfnobhr63cgeqgiq3ly5sl7c@f6fbipcdbrgl \
--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).