ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Startparagraph oddities
Date: Fri, 29 Aug 2014 13:39:45 +0200	[thread overview]
Message-ID: <54006681.4040008@wxs.nl> (raw)
In-Reply-To: <53FFABA8.1090000@rik.users.panix.com>

On 8/29/2014 12:22 AM, Rik Kabel wrote:
> There appears to be an inconsistency in the implementation of
> \startparagraph. When it is used with one argument (or two by my reading
> of the source) it defines \stopparagraph with a terminal \endgraf, yet
> with no arguments this is not done. Strangely (to me) it also appears to
> insert a line-break before \startparagraph[]. The example below
> demonstrates these issues.
>
> I would expect to have \endgraf inserted with each \stopparagraph
> regardless of the argument count.
>
> There is also a wiki issue with overloading of the command name
> \startparagraph. The existing command entry points to the paragraphs
> mechanism for setting up parallel paragraphs in columns. There is also a
> \startParagraph command described for the t-pararef module. There is no
> mention of \startparagraph in the \startsection page, which might be an
> appropriate place. Perhaps some Wikipedia-style disambiguation mechanism
> is needed.
>
>     \starttext
>     \startparagraph
>     One
>     \stopparagraph
>     \startparagraph
>     Twee
>     \stopparagraph
>     \startparagraph
>     Drie
>     \stopparagraph
>     \startparagraph[]
>     One
>     \stopparagraph
>     \startparagraph
>     Twee
>     \stopparagraph
>     \startparagraph
>     Drie
>     \stopparagraph
>     \stoptext

fixed in next beta

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2014-08-29 11:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28 22:22 Rik Kabel
2014-08-29 11:39 ` Hans Hagen [this message]

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=54006681.4040008@wxs.nl \
    --to=pragma@wxs.nl \
    --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).