From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: Rik Kabel via ntg-context <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: [NTG-context] Change in flushleft alignment?
Date: Thu, 1 Jun 2023 08:26:57 +0200 [thread overview]
Message-ID: <f9bc9216-596c-7b13-6e87-899677fef608@fiee.net> (raw)
In-Reply-To: <6fa2a9fb-042d-137b-d871-74e50318c577@rik.users.panix.com>
Am 01.06.23 um 04:17 schrieb Rik Kabel via ntg-context:
> Previously (May 7) flushleft paragraphs were as wide as possible within
> the text area. Now (May 30) they appear to be re-wrapped to a much
> narrower width.
>
> Here is the same paragraph, showing the difference:
>
> and
>
> It looks like every paragraph has been run through par.
>
> This does not seem to create paragraphs with more lines, but they create
> a very odd, choppy page. It does not prevent hyphenation, and sometimes
> introduces it where none was present before.
>
> Did I miss a change?
I found the same problem with a \definedescription; a workaround was to
add "wide,hyphenated" to the alignment.
Hraban
___________________________________________________________________________________
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-06-01 6:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 2:17 Rik Kabel via ntg-context
2023-06-01 6:26 ` Henning Hraban Ramm via ntg-context [this message]
2023-06-01 7:02 ` Hans Hagen via ntg-context
2023-06-01 17:21 ` Rik Kabel 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=f9bc9216-596c-7b13-6e87-899677fef608@fiee.net \
--to=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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).