From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Pablo Rodriguez <oinos@gmx.es>
Subject: Re: roadmap
Date: Tue, 15 May 2018 23:26:52 +0200 [thread overview]
Message-ID: <9a052dbd-97dd-f704-190d-f8347389775a@xs4all.nl> (raw)
In-Reply-To: <8e449c0a-6dba-341c-5b5b-33c46df483f4@gmx.es>
On 5/15/2018 9:17 PM, Pablo Rodriguez wrote:
> On 05/14/2018 05:17 PM, Hans Hagen wrote:
>> Hi,
>>
>> The ConTeXt meeting is - as usual - the right place and moment to
>> discuss the roadmap. We never had real binding roadmaps, more informal
>> ones. Anyway, here are some thoughts on the two main components: MkIV
>> and LuaTeX.
>>
>> ConTeXt MkIV:
>> [...]
>> - Check what additional features users want (miss) and decide to what
>> extent and with what priority we will put effort in this. We've reached
>> a point where interference prevents more complex extensions.
>
> Hans,
>
> I wonder whether it would be possible to implement a feature that you
> mentioned in the past.
>
> In order to avoid widow and orphan lines, you mentioned that it would be
> possible to automatically adapt the interline space for the page, so
> that it may have one more line to avoid orphans (when interline space is
> decreased) or it may move a line to the next page to avoid widows
> (increasing the interline space in the present page).
>
> Would it be possible to add this feature to ConTeXt?
actually it was something that came up when talking with Hermann Zapf
years ago: he suggested to just vertically scale the text area (i
actully implemented that an hour later) ... his opinion was that only a
very small percentage of readers will notice (at that time we did
experiments with hz, the expansion in pdftex: in fact nobody noticed
that too, real interesting was that texies commented on all kind of
things related to how tex is supposed to work: a clear demonstration
that the average user knows what the virtues of tex are but not really
sees it)
> I have another feature request for notes, but I would like to know
> whether the feature to avoid widow and orphan lines can be implemented
> in ConTeXt.
you can always ask ... giving it priority is another matter
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-05-15 21:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 15:17 roadmap Hans Hagen
2018-05-14 19:36 ` roadmap Henning Hraban Ramm
2018-05-14 21:26 ` roadmap Hans Hagen
2018-05-15 9:01 ` roadmap MF
2018-05-14 22:52 ` roadmap Henri Menke
2018-05-14 23:34 ` roadmap Hans Hagen
2018-05-16 5:38 ` roadmap Henri Menke
2018-05-16 6:24 ` roadmap Joseph Canedo
2018-05-16 7:28 ` roadmap Hans Hagen
2018-05-14 23:41 ` roadmap luigi scarso
2018-05-15 19:17 ` roadmap Pablo Rodriguez
2018-05-15 21:26 ` Hans Hagen [this message]
2018-05-16 15:18 ` roadmap Pablo Rodriguez
2018-05-16 19:14 ` roadmap Fabrice L
2018-05-17 13:06 ` roadmap Hans Hagen
2018-05-17 14:24 ` roadmap Mohammad Hossein Bateni
2018-05-17 15:47 ` roadmap Otared Kavian
2018-05-17 16:50 ` roadmap Hans Hagen
2018-05-15 6:15 roadmap Christoph Reller
2018-05-15 6:23 ` roadmap luigi scarso
2018-05-15 6:36 ` roadmap Hans Hagen
2018-05-15 14:46 roadmap Christoph Reller
2018-05-15 14:51 ` roadmap luigi scarso
2018-05-18 9:54 roadmap Christoph Reller
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=9a052dbd-97dd-f704-190d-f8347389775a@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).