From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/88997 Path: news.gmane.org!not-for-mail From: Wolfgang Schuster Newsgroups: gmane.comp.tex.context Subject: Re: \startitem and \startparagraph Date: Sat, 18 Oct 2014 13:13:48 +0200 Message-ID: References: <54406AAD.3090509@rik.users.panix.com> <5440CA53.9060206@wxs.nl> <5441319C.1090205@rik.users.panix.com> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Content-Type: multipart/mixed; boundary="===============1634303509==" X-Trace: ger.gmane.org 1413630872 26376 80.91.229.3 (18 Oct 2014 11:14:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 18 Oct 2014 11:14:32 +0000 (UTC) To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Sat Oct 18 13:14:27 2014 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from balder.ntg.nl ([5.39.185.229]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XfRxq-0007Yj-If for gctc-ntg-context-518@m.gmane.org; Sat, 18 Oct 2014 13:14:26 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 027FD101E3 for ; Sat, 18 Oct 2014 13:14:26 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id IzfAheAwBdrF for ; Sat, 18 Oct 2014 13:14:24 +0200 (CEST) Original-Received: from balder.ntg.nl (localhost [IPv6:::1]) by balder.ntg.nl (Postfix) with ESMTP id A440E101E6 for ; Sat, 18 Oct 2014 13:13:56 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 430BB101E6 for ; Sat, 18 Oct 2014 13:13:53 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HCukACY5SHc3 for ; Sat, 18 Oct 2014 13:13:52 +0200 (CEST) Original-Received: from filter4-ams.mf.surf.net (filter4-ams.mf.surf.net [192.87.102.72]) by balder.ntg.nl (Postfix) with ESMTP id 0A9FF101E3 for ; Sat, 18 Oct 2014 13:13:52 +0200 (CEST) Original-Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by filter4-ams.mf.surf.net (8.14.3/8.14.3/Debian-9.4) with ESMTP id s9IBDpIZ019972 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Sat, 18 Oct 2014 13:13:51 +0200 Original-Received: by mail-wi0-f171.google.com with SMTP id em10so3840436wid.4 for ; Sat, 18 Oct 2014 04:13:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:message-id:mime-version:subject:date:references :to:in-reply-to; bh=43cndhkGEUDf4iLZFi7ikOrHqXAc/N7fyJ9vlv2mRRo=; b=X85Ta1uR/dm426rHtzQcxig5cZCpJ1Xa2MPZWSPdjeOZCua0wtIOGKn3VJAmOl1rEw tuRHqlAncnaU4LDAK0ncXbsRYdBhz7gxgMGPaKiYVC5XPl5j/zZL/JlDY4H9VXslZo3U mw0ExWTcQkPvUJwZ3ap8Xhj3j9nQOPlWWtDB0P15FDwh0ZFd2I9eiJIJesDZ9Q+9f8Hc bHVijnVEzzsIFN1a+LC8aHVo8mX/UeqT7TW8WPxCaNQPI6DpvvNKTi4MrBVuZgXrE+4H K6u02NwURXg0ZUBgK85dnHve7uNnC3JzPiQVNFtoin+7qy68jmW2SB5HnZmSY5P+463Y KSyQ== X-Received: by 10.180.76.41 with SMTP id h9mr5563229wiw.40.1413630831133; Sat, 18 Oct 2014 04:13:51 -0700 (PDT) Original-Received: from keima.localdomain (x2f2a2ee.dyn.telefonica.de. [2.242.162.238]) by mx.google.com with ESMTPSA id pc8sm4869072wjb.36.2014.10.18.04.13.49 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 18 Oct 2014 04:13:50 -0700 (PDT) In-Reply-To: <5441319C.1090205@rik.users.panix.com> X-Mailer: Apple Mail (2.1990.1) X-Bayes-Prob: 0.0001 (Score 0, tokens from: ntg-context@ntg.nl, base:default, @@RPTN) X-CanIt-Geo: ip=2a00:1450:400c:c05::22b; country=IE X-CanItPRO-Stream: uu:ntg-context@ntg.nl (inherits from uu:default, base:default) X-Canit-Stats-ID: 01N4zdP6k - 61046bf8eb62 - 20141018 (trained as not-spam) X-Scanned-By: CanIt (www . roaringpenguin . com) X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.16 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl Original-Sender: "ntg-context" Xref: news.gmane.org gmane.comp.tex.context:88997 Archived-At: --===============1634303509== Content-Type: multipart/alternative; boundary="Apple-Mail=_83EED43D-2DE8-4378-950F-83B62D40505D" --Apple-Mail=_83EED43D-2DE8-4378-950F-83B62D40505D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > Am 17.10.2014 um 17:11 schrieb Rik Kabel = : >=20 > On 2014-10-17 03:50, Hans Hagen wrote: >> On 10/17/2014 3:02 AM, Rik Kabel wrote: >>> What is the proper way to delimit paragraphs within an itemized list >>> using \start..\stop tagging (as for epub and such)? When I wrap >>> paragraphs with \startparagraph..\stopparagraph within the >>> \startitem..\stopitem, there is an unwanted newline inserted between = the >>> bullet and the item text. >>>=20 >>> Or, is it not recommend to wrap paragraphs that are in enumerations? >>>=20 >>> I ask because http://wiki.contextgarden.net/Epub_Sample suggests = =E2=80=9CMake >>> sure to tag all your structural elements with \start...-\stop..., = e.g. >>> \startchapter, but even \startparagraph!=E2=80=9D I also note the = appearance of >>> \startcontent..\stopcontent and \stopcaption..\startcaption and = such, >>> suggesting to me that semantic tagging may be a useful thing to add = to >>> new documents in order to support new output formats. >>>=20 >>> \starttext >>> \startitemize >>> \startitem >>> \startparagraph >>> Item one paragraph one. >>> \stopparagraph >>> \startparagraph >>> Item one paragraph two. >>> \stopparagraph >>> \startparagraph >>> Item one paragraph three. >>> \stopparagraph >>> \stopitem >>> \startitem >>> \startparagraph >>> Item two paragraph one. >>> \stopparagraph >>> \startparagraph >>> Item two paragraph two. >>> \stopparagraph >>> \startparagraph >>> Item two paragraph three. >>> \stopparagraph >>> \stopitem >>> \stopitemize >>=20 >> \starttext >> \startitemize >> \startitem >> \bpar >> Item one paragraph one. >> \epar % \stopparagraph >> \bpar >> Item one paragraph two. >> \epar >> \bpar >> Item one paragraph three. >> \epar >> \stopitem >> \startitem >> \bpar >> Item two paragraph one. >> \epar >> \bpar >> Item two paragraph two. >> \epar >> \bpar >> Item two paragraph three. >> \epar >> \stopitem >> \stopitemize >> \stoptext >>=20 > Thank you, Hans, for that. >=20 > Can you explain when \startparagraph..\stopparagraph should be = preferred for tagging, and when \bpar..\epar? There is clearly a = difference between them. \starttext The \tex{bpar} and \tex{epar} commands only add tags for the begin and = end of the paragraph in the exported content: \startitemize \startitem \input ward \stopitem \startitem \bpar \input ward \epar \stopitem \stopitemize When you use the \tex{startparagraph} and \tex{stopparagraph} commands = \CONTEXT\ forces the end of the previous paragraph before it add the tags for the = export: \startitemize \startitem \par \input ward \par \stopitem \startitem \startparagraph \input ward \stopparagraph \stopitem \stopitemize \stoptext > Is there any setup associated with \bpar..\epar as there is = \defineparagraph for \startparagraph..\stopparagraph? No, the commands add only the tags when you use the export function. Wolfgang= --Apple-Mail=_83EED43D-2DE8-4378-950F-83B62D40505D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Am 17.10.2014 um 17:11 schrieb Rik Kabel <context@rik.users.panix.com>:

On 2014-10-17 03:50, Hans Hagen wrote:
On 10/17/2014 3:02 AM, = Rik Kabel wrote:
What = is the proper way to delimit paragraphs within an itemized list
using \start..\stop tagging (as for epub and such)? When I = wrap
paragraphs with \startparagraph..\stopparagraph = within the
\startitem..\stopitem, there is an unwanted = newline inserted between the
bullet and the item text.

Or, is it not recommend to wrap paragraphs = that are in enumerations?

I ask because http://wiki.contextgarden.net/Epub_Sample suggests = =E2=80=9CMake
sure to tag all your structural elements = with \start...-\stop..., e.g.
\startchapter, but even = \startparagraph!=E2=80=9D I also note the appearance of
\startcontent..\stopcontent and \stopcaption..\startcaption = and such,
suggesting to me that semantic tagging may be a = useful thing to add to
new documents in order to support = new output formats.

   \starttext
   \startitemize
      \startitem
        \startparagraph=
          Ite= m one paragraph one.
        \stopparagraph<= br = class=3D"">        \startparagraph=
          Ite= m one paragraph two.
        \stopparagraph<= br = class=3D"">        \startparagraph=
          Ite= m one paragraph three.
        \stopparagraph<= br class=3D"">      \stopitem
      \startitem
        \startparagraph=
          Ite= m two paragraph one.
        \stopparagraph<= br = class=3D"">        \startparagraph=
          Ite= m two paragraph two.
        \stopparagraph<= br = class=3D"">        \startparagraph=
          Ite= m two paragraph three.
        \stopparagraph<= br class=3D"">      \stopitem
   \stopitemize

\starttext
\startitemize
 \startitem
   \bpar
     Item one paragraph one.
   \epar % \stopparagraph
   \bpar
     Item one paragraph two.
   \epar
   \bpar
     Item one paragraph three.
   \epar
 \stopitem
 \startitem
   \bpar
     Item two paragraph one.
   \epar
   \bpar
     Item two paragraph two.
   \epar
   \bpar
     Item two paragraph three.
   \epar
 \stopitem
\stopitemize
\stoptext

Thank you, Hans, = for that.

Can you explain when = \startparagraph..\stopparagraph should be preferred for tagging, and = when \bpar..\epar? There is clearly a difference between them.

\starttext

The = \tex{bpar} and \tex{epar} commands only add tags for the begin and = end
of the paragraph in the exported content:

\startitemize
  = \startitem
    \input ward
  = \stopitem
  \startitem
    \bpar = \input ward \epar
  = \stopitem
\stopitemize

When = you use the \tex{startparagraph} and \tex{stopparagraph} commands = \CONTEXT\
forces the end of the previous paragraph before it = add the tags for the export:

\startitemize
  = \startitem
    \par \input ward = \par
  \stopitem
  = \startitem
    \startparagraph \input ward = \stopparagraph
  = \stopitem
\stopitemize

\stoptext

Is there any setup = associated with \bpar..\epar as there is \defineparagraph for = \startparagraph..\stopparagraph?

No, the commands add only the tags when you = use the export function.

Wolfgang
= --Apple-Mail=_83EED43D-2DE8-4378-950F-83B62D40505D-- --===============1634303509== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv IGh0dHA6Ly90ZXguYWFuaGV0Lm5ldAphcmNoaXZlICA6IGh0dHA6Ly9mb3VuZHJ5LnN1cGVsZWMu ZnIvcHJvamVjdHMvY29udGV4dHJldi8Kd2lraSAgICAgOiBodHRwOi8vY29udGV4dGdhcmRlbi5u ZXQKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX18= --===============1634303509==--