ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach
Date: Fri, 18 Aug 2023 20:58:58 +0200	[thread overview]
Message-ID: <9d92bde9-2101-dfa6-e50d-112dc704d37b@gmail.com> (raw)
In-Reply-To: <nf4c5cb5aryewtmo7umojrjk76y275yfkrtb7y4s2pylid2hob@ba2vwa7457pm>

[-- Attachment #1: Type: text/plain, Size: 716 bytes --]

Hi,

1. Learn to two provide a working minimal example which shows the problem.

2. The example below results in a correct output for \TEX.

\setuplayout[width=16cm]
\showmakeup

\starttext

Thus, I came to the conclusion that the designer of a new
system must not only be the implementer and first
large||scale user; the designer should also write the first
user manual.

\setupbodyfont[12.895pt]

{\ss The separation of any of these four components would have
hurt \TeX\ significantly. If I had not participated fully in
all these activities, literally hundreds of improvements
would never have been made, because I would never have
thought of them or perceived why they were important.\par}

\stoptext

Wolfgang


[-- Attachment #2: test.pdf --]
[-- Type: application/pdf, Size: 21362 bytes --]

[-- Attachment #3: 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
___________________________________________________________________________________

  reply	other threads:[~2023-08-18 19:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18  9:39 [NTG-context] " Carlos
2023-08-18 16:20 ` [NTG-context] " Mikael Sundqvist
2023-08-18 18:17   ` Carlos
2023-08-18 18:54     ` [NTG-context] unsubscribe Thomas Floeren via ntg-context
2023-08-18 18:26   ` [NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach Carlos
2023-08-18 18:48     ` Carlos
2023-08-18 18:58       ` Wolfgang Schuster [this message]
2023-08-19 13:32         ` Carlos
2023-08-19 14:06           ` Mikael Sundqvist
2023-08-20 13:38           ` Wolfgang Schuster
2023-08-20 15:51             ` Carlos
2023-08-20 16:41               ` Wolfgang Schuster
2023-08-20 16:58                 ` Hans Hagen via ntg-context
2023-08-20 16:41               ` Hans Hagen
2023-08-21 12:22                 ` Carlos
2023-08-21 12:55                   ` Thomas A. Schmitz
2023-08-18 21:24       ` Hans Hagen

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=9d92bde9-2101-dfa6-e50d-112dc704d37b@gmail.com \
    --to=wolfgang.schuster.lists@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).