From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/108503
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: jbf <roma83537@gmail.com>
Newsgroups: gmane.comp.tex.context
Subject: short filler rule either side of a text
Date: Tue, 25 Aug 2020 11:32:02 +1000
Message-ID: <e9a09850-a058-d65b-4854-a235d2c07b07@gmail.com>
Reply-To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7670570436051327122=="
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="8952"; mail-complaints-to="usenet@ciao.gmane.io"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Original-X-From: ntg-context-bounces@ntg.nl Tue Aug 25 03:32:35 2020
Return-path: <ntg-context-bounces@ntg.nl>
Envelope-to: gctc-ntg-context-518@m.gmane-mx.org
Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl)
	by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <ntg-context-bounces@ntg.nl>)
	id 1kANpD-0002Ee-4M
	for gctc-ntg-context-518@m.gmane-mx.org; Tue, 25 Aug 2020 03:32:35 +0200
Original-Received: from localhost (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 836F71842D8;
	Tue, 25 Aug 2020 03:32:11 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
	by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id y2_j5uRtn_8R; Tue, 25 Aug 2020 03:32:10 +0200 (CEST)
Original-Received: from zapf.ntg.nl (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id AD955184302;
	Tue, 25 Aug 2020 03:32:10 +0200 (CEST)
Original-Received: from localhost (localhost [127.0.0.1])
 by zapf.ntg.nl (Postfix) with ESMTP id 4D143184302
 for <ntg-context@ntg.nl>; Tue, 25 Aug 2020 03:32:10 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
 by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id EbIL0GdIfudC for <ntg-context@ntg.nl>;
 Tue, 25 Aug 2020 03:32:09 +0200 (CEST)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.210.177;
 helo=mail-pf1-f177.google.com; envelope-from=roma83537@gmail.com;
 receiver=<UNKNOWN> 
Original-Received: from mail-pf1-f177.google.com (mail-pf1-f177.google.com
 [209.85.210.177])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits))
 (No client certificate requested)
 by zapf.ntg.nl (Postfix) with ESMTPS id 37E491842D8
 for <ntg-context@ntg.nl>; Tue, 25 Aug 2020 03:32:09 +0200 (CEST)
Original-Received: by mail-pf1-f177.google.com with SMTP id u128so6037176pfb.6
 for <ntg-context@ntg.nl>; Mon, 24 Aug 2020 18:32:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=to:from:subject:message-id:date:user-agent:mime-version
 :content-language;
 bh=zpKNDJQ7S6AMxoRVgK1ER4xQVIHbPjnrqRj7q+9EL0Y=;
 b=HZ2kY+TSJ52BwvsN3xzsT1Db69WdTE1y8Fh5yXgHdvwYm9V7taaX3DyO1JKLFSzGJl
 Y4RVA6MP2uDAzbtn6sEUDTCMBJ8Z0wgU8tDskjIWALAWIEz3vB5+TFMTwtNjtSV1yCDa
 TYb7ZemxMHbYSONzLB9Bh3MJLUL21viWKGG8CAsplir4AvikS9ELwx/JNr5DLyjcJ6zG
 PaULQFDre9IJ2BVG9xR/Zo93QgvxFQoi7OPZDI0GFIzZ667Hmsv0jP8g2KFMpmLlwTvA
 eByzpal3VdW0jhfn8iHIPm/C1tD/iCAU83VXtxdGdCt6AoOrHM9tLyaULZSOs4UyeBlq
 vhqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:to:from:subject:message-id:date:user-agent
 :mime-version:content-language;
 bh=zpKNDJQ7S6AMxoRVgK1ER4xQVIHbPjnrqRj7q+9EL0Y=;
 b=W63tgfsfABCW/Pr19QgMNvgXnE/FHhCFZuRkpgTkhrZVEDJ5aMEn62I+MMui0pAGxV
 OJPd7qD11k0uS60ktwn7WdXE0e6qsVLrK3YEP/Q1cUy2Ea9y+pzF3XNCT+dOm6PWe71e
 0RzAHyXWp99iMg4FIgAsjkrnhwLM7vNQ/wwHLQrSSYABZOF4UlL8fXYh7d25zO9by4jJ
 Ierzh30cBSAqxs4qspr76l8Z8zNGnicdAkSNEjdNaUZK1v99vC1tofPwBEvjd0/uqGKD
 yEQOG/W7Hlce6NCdNaaq58UkDPvw2rZS8r0PqqKT+lQLJEmiEbwlMpjh7Q4INa923any
 jw3Q==
X-Gm-Message-State: AOAM533yBiV/hXtfT1lVjXKZRrmhE0vLKLa4lPudQrOUumTFLvzLdwGZ
 VVdaCccGBBdjMZWEV1rWL06Ixq3T4pSmmg==
X-Google-Smtp-Source: ABdhPJxfAhrsdLxZCUPmIhT8ez9Dr1CpGlD2NxjIJ74f3JnrvnUNFhPGHxRKQgNwX/EyZIGtBhO9HQ==
X-Received: by 2002:a17:902:aa89:: with SMTP id
 d9mr4670549plr.192.1598319126223; 
 Mon, 24 Aug 2020 18:32:06 -0700 (PDT)
Original-Received: from [192.168.0.100] ([120.21.220.27])
 by smtp.gmail.com with ESMTPSA id v78sm13663308pfc.121.2020.08.24.18.32.04
 for <ntg-context@ntg.nl>
 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
 Mon, 24 Aug 2020 18:32:05 -0700 (PDT)
Content-Language: en-US
X-BeenThere: ntg-context@ntg.nl
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: mailing list for ConTeXt users <ntg-context.ntg.nl>
List-Unsubscribe: <https://mailman.ntg.nl/mailman/options/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=unsubscribe>
List-Archive: <http://mailman.ntg.nl/pipermail/ntg-context/>
List-Post: <mailto:ntg-context@ntg.nl>
List-Help: <mailto:ntg-context-request@ntg.nl?subject=help>
List-Subscribe: <https://mailman.ntg.nl/mailman/listinfo/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=subscribe>
Errors-To: ntg-context-bounces@ntg.nl
Original-Sender: "ntg-context" <ntg-context-bounces@ntg.nl>
Xref: news.gmane.io gmane.comp.tex.context:108503
Archived-At: <http://permalink.gmane.org/gmane.comp.tex.context/108503>

This is a multi-part message in MIME format.
--===============7670570436051327122==
Content-Type: multipart/alternative;
 boundary="------------022767F310CCCAD891B8BE62"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------022767F310CCCAD891B8BE62
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

I know it is possible to get a rule to act as a filler either side of, 
say, a chapter head text by using \definefiller with alternative=rule 
and, as explained in an earlier post 
<https://tex.stackexchange.com/questions/497352/context-heading-text-surrounded-by-lines/497389#497389>, 
define a left and right version. So, for example, for the left version:

\definefiller
   [ChapterLeftRule]
   [ChapterRule]
   [left=\zerowidthnobreakspace,
    right=\quad]

This gives me a rule that extends to the margins. What if I want the 
rule to be, say, 2 cm either side of my centered header text? I tried 
experimenting by replacing left=\zerowidthnobreakspace with 
left=\quads[3] and that did shorten the rule somewhat, but when I did 
the same for the other side, it did not balance correctly. So maybe I 
need to deal with the 'left=' differently to achieve the desired 
result... or try an entirely different method!

Of course, I don't want the rule at the baseline, but raised, as the 
original stackexchange 
<https://tex.stackexchange.com/questions/497352/context-heading-text-surrounded-by-lines/497389#497389> 
example gives. Any clues?

Julian


--------------022767F310CCCAD891B8BE62
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>I know it is possible to get a rule to act as a filler either
      side of, say, a chapter head text by using \definefiller with
      alternative=rule and, as explained in an <a
        moz-do-not-send="true"
href="https://tex.stackexchange.com/questions/497352/context-heading-text-surrounded-by-lines/497389#497389">earlier
        post</a>, define a left and right version. So, for example, for
      the left version:</p>
    <p>\definefiller<br>
        [ChapterLeftRule]<br>
        [ChapterRule]<br>
        [left=\zerowidthnobreakspace,<br>
         right=\quad]</p>
    <p>This gives me a rule that extends to the margins. What if I want
      the rule to be, say, 2 cm either side of my centered header text?
      I tried experimenting by replacing left=\zerowidthnobreakspace 
      with left=\quads[3] and that did shorten the rule somewhat, but
      when I did the same for the other side, it did not balance
      correctly. So maybe I need to deal with the 'left=' differently to
      achieve the desired result... or try an entirely different method!</p>
    <p>Of course, I don't want the rule at the baseline, but raised, as
      the original <a moz-do-not-send="true"
href="https://tex.stackexchange.com/questions/497352/context-heading-text-surrounded-by-lines/497389#497389">stackexchange</a>
      example gives. Any clues?</p>
    <p>Julian<br>
    </p>
  </body>
</html>

--------------022767F310CCCAD891B8BE62--

--===============7670570436051327122==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz
dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h
aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s
aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv
IGh0dHA6Ly9jb250ZXh0LmFhbmhldC5uZXQKYXJjaGl2ZSAgOiBodHRwczovL2JpdGJ1Y2tldC5v
cmcvcGhnL2NvbnRleHQtbWlycm9yL2NvbW1pdHMvCndpa2kgICAgIDogaHR0cDovL2NvbnRleHRn
YXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCg==

--===============7670570436051327122==--