From: Rik Kabel via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Rik Kabel <ConTeXt@rik.users.panix.com>
Subject: [NTG-context] Change in flushleft alignment?
Date: Wed, 31 May 2023 22:17:48 -0400 [thread overview]
Message-ID: <6fa2a9fb-042d-137b-d871-74e50318c577@rik.users.panix.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 496 bytes --]
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?
--
Rik
[-- Attachment #1.2.1: Type: text/html, Size: 951 bytes --]
[-- Attachment #1.2.2: B0OBikLAIe0RAbwd.png --]
[-- Type: image/png, Size: 28966 bytes --]
[-- Attachment #1.2.3: SlrhMU3fZB3ppsbh.png --]
[-- Type: image/png, Size: 20015 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 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 reply other threads:[~2023-06-01 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 2:17 Rik Kabel via ntg-context [this message]
2023-06-01 6:26 ` Henning Hraban Ramm via ntg-context
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=6fa2a9fb-042d-137b-d871-74e50318c577@rik.users.panix.com \
--to=ntg-context@ntg.nl \
--cc=ConTeXt@rik.users.panix.com \
/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).