From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/91759 Path: news.gmane.org!not-for-mail From: Wolfgang Schuster Newsgroups: gmane.comp.tex.context Subject: Re: \setuphead[part] - special look Date: Mon, 22 Jun 2015 18:36:03 +0200 Message-ID: <55883973.1010502@gmail.com> References: <5587CCA2.9010806@gmail.com> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1892743296==" X-Trace: ger.gmane.org 1434991032 22748 80.91.229.3 (22 Jun 2015 16:37:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 22 Jun 2015 16:37:12 +0000 (UTC) To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Mon Jun 22 18:37:00 2015 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 1Z74iQ-0001Gm-S1 for gctc-ntg-context-518@m.gmane.org; Mon, 22 Jun 2015 18:36:58 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 2D0E21021B for ; Mon, 22 Jun 2015 18:36:58 +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 a2OjVTvjaVjF for ; Mon, 22 Jun 2015 18:36:57 +0200 (CEST) Original-Received: from balder.ntg.nl (localhost [IPv6:::1]) by balder.ntg.nl (Postfix) with ESMTP id 51AD310234 for ; Mon, 22 Jun 2015 18:36:20 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 4E704101FB for ; Mon, 22 Jun 2015 18:36:17 +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 4dRxxuLZoadc for ; Mon, 22 Jun 2015 18:36:15 +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 52E7F101E6 for ; Mon, 22 Jun 2015 18:36:15 +0200 (CEST) Original-Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) by filter4-ams.mf.surf.net (8.14.3/8.14.3/Debian-9.4) with ESMTP id t5MGaCHi026980 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Mon, 22 Jun 2015 18:36:12 +0200 Original-Received: by wicgi11 with SMTP id gi11so80949381wic.0 for ; Mon, 22 Jun 2015 09:36:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=nyYkH/LgLq0hBXn89ORj3PrktBD0CzvySFAdPntMPMU=; b=Uxee1T0I/qcp7hXyAlWpkaqt9FGYugJ+i9brJRgQCKsSMXQZsHb5CD4dxexKAg1qPc DgoznJDduU8m9sjGAYN+3Xqa2nNhB0U/bGgNGbB8771NqW5R5xW6G+eAB4czY8auXGwe mNFryCltUluTVBZga/RHkDNN4JmK3cfTa/39dRecs1n2RJqKPRcxIZ8KTHWWjJWZJwbJ cZ5e4PEXOl7ajhE5BrtAhSt32zlaqcGxTmVpreBrqE5+6vmO1L/HS2DLuuvWjD8fGkcJ xmklyMbpeg7UKRO25oAL4ZdHw01At6pBlmsh+Z0RQHi7GCv/xjPhNNQII2aGkAFGXLg2 +/uw== X-Received: by 10.180.91.107 with SMTP id cd11mr32350895wib.51.1434990972232; Mon, 22 Jun 2015 09:36:12 -0700 (PDT) Original-Received: from keima.localdomain (x2f2d253.dyn.telefonica.de. [2.242.210.83]) by mx.google.com with ESMTPSA id q4sm31314232wju.14.2015.06.22.09.36.06 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 22 Jun 2015 09:36:11 -0700 (PDT) User-Agent: Postbox 4.0.1 (Macintosh/20150514) In-Reply-To: X-Bayes-Prob: 0.0001 (Score 0, tokens from: ntg-context@ntg.nl, base:default, @@RPTN) X-CanIt-Geo: ip=2a00:1450:400c:c05::233; country=BE; region=Brussels Capital; city=Brussels; latitude=50.8466; longitude=4.3528; http://maps.google.com/maps?q=50.8466,4.3528&z=6 X-CanItPRO-Stream: uu:ntg-context@ntg.nl (inherits from uu:default, base:default) X-Canit-Stats-ID: 01OHsAcNU - 16bec98bf9e5 - 20150622 (trained as not-spam) Received-SPF: pass (filter4-ams.mf.surf.net: domain of schuster.wolfgang@gmail.com designates 2a00:1450:400c:c05::233 as permitted sender) receiver=filter4-ams.mf.surf.net; client-ip=2a00:1450:400c:c05::233; envelope-from=; helo=mail-wi0-x233.google.com; identity=mailfrom 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:91759 Archived-At: This is a multi-part message in MIME format. --===============1892743296== Content-Type: multipart/alternative; boundary="------------040609020108090101030504" This is a multi-part message in MIME format. --------------040609020108090101030504 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: quoted-printable > Proch=E1zka Luk=E1=B9 Ing. - Pontex s. r. o. > 22. Juni 2015 11:42 > Hello Wolfgang, > > thank you for the solution, it pretty systemic. > > Ad "Ad 2": There was no question as succeeded placing page number and=20 > name into the page gold ratio, so just mentioned as one of the=20 > features required. > > After some plying with your solution, I deduce: > > We have to derive a new alternative for "part" (here "partpage") as we=20 > CAN assign a new "renderingsetup" to this alternative but we CANNOT=20 > assign a rendering setup in the scope of \setuphead. > > IOW, there is no "\setuphead[part][renderingsetup=3Dpartpage]". > > If there was the option "\setuphead[part][renderingsetup=3Dpartpage]" w= e=20 > could simplify to: This method to set your own layout is also used by other command (e.g.=20 the list mechanism used for the table of contents) and the=20 \defineheadplacement has also a alternative key which is needed when you=20 want an inline heading (e.g. \setuphead[...][alternative=3Dtext]). > ---- > % No headalternative here > > \startsetups[partpage] > \startmakeup[part] > \headsetupspacing > \headnumbercontent > \blank[big] > \headtextcontent > \stopmakeup > \stopsetups > > \definemakeup > [part] > [align=3Dmiddle, > top=3D\vfill\vfill, > bottom=3D\vfill\vfill\vfill] > > \setuphead > [part] > [... > renderingsetup=3Dpartpage, > ... > ] > > ... > > ---- > > Am I right? > > (And, I understand that the aim is not to support all extraordinary=20 > request(s) in \setuphead by its keys/options - it is enough to have A=20 > way to get them, here using a "headalternative"...) The necessary key would be endless with each new layout and with the=20 \defineheadplacement command to create your own without adding=20 additional keys but you can also use the command key instead of=20 \defineheadplacement. The advantage of \defineheadplacement is that you=20 can better structure the code in the setups environment because you=20 don't have to worry about spaces. Wolfgang --------------040609020108090101030504 Content-Type: text/html; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable
= =20 22. Juni 2015=20 11:42
Hello=20 Wolfgang,

thank you for the solution, it pretty systemic.

Ad "Ad 2": There was no question as succeeded placing page number=20 and name into the page gold ratio, so just mentioned as one of the=20 features required.

After some plying with your solution, I deduce:

We have to derive a new alternative for "part" (here "partpage") as=20 we CAN assign a new "renderingsetup" to this alternative but we CANNOT=20 assign a rendering setup in the scope of \setuphead.

IOW, there is no "\setuphead[part][renderingsetup=3Dpartpage]".

If there was the option "\setuphead[part][renderingsetup=3Dpartpage]"= =20 we could simplify to:
This method to set your own layout is also used by other command (e.g.=20 the list mechanism used for the table of contents) and the=20 \defineheadplacement has also a alternative key which is needed when you want an inline heading (e.g. \setuphead[...][alternative=3Dtext]).
----
% No headalternative here

\startsetups[partpage]
=A0=A0 \startmakeup[part]
=A0=A0=A0=A0=A0=A0 \headsetupspacing
=A0=A0=A0=A0=A0=A0 \headnumbercontent
=A0=A0=A0=A0=A0=A0 \blank[big]
=A0=A0=A0=A0=A0=A0 \headtextcontent
=A0=A0 \stopmakeup
\stopsetups

\definemakeup
=A0[part]
=A0[align=3Dmiddle,
=A0 top=3D\vfill\vfill,
=A0 bottom=3D\vfill\vfill\vfill]

\setuphead
=A0[part]
=A0[...
=A0 renderingsetup=3Dpartpage,
=A0 ...
=A0]

...

----

Am I right?

(And, I understand that the aim is not to support all extraordinary=20 request(s) in \setuphead by its keys/options - it is enough to have A=20 way to get them, here using a "headalternative"...)
The necessary key would be endless with each new layout and with the=20 \defineheadplacement command to create your own without adding=20 additional keys but you can also use the command key instead of=20 \defineheadplacement. The advantage of \defineheadplacement is that you=20 can better structure the code in the setups environment because you=20 don’t have to worry about spaces.

Wolfgang
--------------040609020108090101030504-- --===============1892743296== 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= --===============1892743296==--