ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: future versions
Date: Tue, 24 Jul 2018 22:30:06 +0200	[thread overview]
Message-ID: <2cf3a131-d25b-2a0d-67f8-450709717b45@gmx.es> (raw)
In-Reply-To: <83409155-cf0a-118b-3f80-d7bac8b1ef91@xs4all.nl>

On 07/24/2018 08:43 PM, Hans Hagen wrote:
> [...] 
> It's not my intention to implement each possible feature as core feature 
> (no one would document it anyway). Also, as development is basically a 
> spare time effort, don't expect complex commercially interesting niches 
> to come for free either as in that case one can wait till I a find a 
> reason for implementing it for fun or development is driven by a project.

Hans,

if that were possible, I would like to make two proposals (that come
from the roadmap thread
[https://mailman.ntg.nl/pipermail/ntg-context/2018/091512.html]). It
took me two months to catch up.

I think it could be interesting to have the implementation of vertical
scaling (as Hermann Zapf suggested to you) to avoid orphan an widows in
MkIV (https://mailman.ntg.nl/pipermail/ntg-context/2018/091541.html).

As mentioned in the past
(https://mailman.ntg.nl/pipermail/ntg-context/2018/091525.html), I would
like to have notes that handle automatically page registers.

Unfortunately, I cannot attend the ConTeXt Meeting. But the notes with
automatic page registers may qualify as unusual usage of ConTeXt. These
are relevant for language-learning texts (such as
https://geoffreysteadman.com/platos-crito/).

Many thanks for your excellent work with ConTeXt, LuaTeX and MetaPost,

Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2018-07-24 20:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24 18:43 Hans Hagen
2018-07-24 19:07 ` Hans van der Meer
2018-07-24 20:35   ` Pablo Rodriguez
2018-07-24 20:30 ` Pablo Rodriguez [this message]
2018-07-24 21:02 ` Idris Samawi Hamid ادريس سماوي حامد
2018-07-24 23:21   ` Hans Hagen
2018-08-21  8:00     ` future versions - synctex Procházka Lukáš Ing.
2018-08-21  8:33       ` Hans Hagen
2018-08-21 13:04         ` Aditya Mahajan
2018-08-21 13:19           ` Hans Hagen
2018-08-21 14:46             ` Aditya Mahajan
2018-08-21 15:17               ` Hans Hagen
2018-07-25  1:29 ` future versions Rik Kabel
2018-07-25  8:19   ` Henning Hraban Ramm
2018-07-25 13:50     ` Rik Kabel
2018-07-25 16:06       ` Hans Hagen
2018-07-25 16:18       ` Alan Braslau
2018-07-25 17:01         ` Hans Hagen
2018-07-25 11:36   ` Hans Hagen
2018-07-25  7:45 ` Robert Zydenbos
2018-07-25 10:03   ` Richard Mahoney | Indica et Buddhica
2018-07-25 12:50     ` Hans Hagen
2018-07-25 13:12       ` Weber, Matthias
2018-07-25 17:50         ` Hans Hagen
2018-07-25 20:22           ` Henning Hraban Ramm
2018-07-25 11:38   ` 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=2cf3a131-d25b-2a0d-67f8-450709717b45@gmx.es \
    --to=oinos@gmx.es \
    --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).