From: Willi Egger <w.egger@boede.nl>
Subject: Re: \setupmarginrules
Date: Tue, 28 Mar 2006 16:49:47 +0200 [thread overview]
Message-ID: <44294D0B.6030702@boede.nl> (raw)
In-Reply-To: <44285105.1060902@seznam.cz>
Hi Vit!
Thanks for this patch. Do you know why the rulethickness must be given
in integer dimension. e.g. 2.5pt will cause an error, telling that a
wrong dimension is used.
Willi
Vit Zyka wrote:
>frantisek holop wrote:
>
>
>>hmm, on Sun, Mar 26, 2006 at 10:12:01PM +0200, Vit Zyka said that
>>
>>
>>
>>>>\defineparagraphs [poem][n=2]
>>>>\setupparagraphs [poem][1][width=.25\textwidth]
>>>>\setupparagraphs [poem][2][rule=on]
>>>>
>>>>\setupmarginrules [rulethickness=5pt]
>>>>
>>>>
>>>this sets rules for margins. I guess the solution
>>>
>>>\setupparagraphs [poem][2][rule=on,rulethickness=5pt]
>>>
>>>
>>sorry, i forgot to add, that i tried this one also :)
>>seemed logical, but the result is the same.
>>
>>-f
>>
>>
>
>OK, there is a patch (with minor correction):
>
>-----------------------------------------------------------
>\defineparagraphs [poem][n=2,distance=20pt]
>\setupparagraphs [poem][1][width=.25\textwidth]
>\setupparagraphs [poem][2][rule=on,rulethickness=10pt]
>
>\unprotected
>\def\doalinealijn#1#2%
> {\doifelsevalue{\??al#2\the\alteller\c!rule}\v!on
> {\dimen2=#1\relax
> \hskip.5\dimen2
>% \hskip-\linewidth
> \hskip-.5\getvalue{\??al#2\the\alteller\c!rulethickness}% VZ
>% \vrule\!!width\linewidth
> \vrule\!!width\getvalue{\??al#2\the\alteller\c!rulethickness}% VZ
> \hskip-.5\getvalue{\??al#2\the\alteller\c!rulethickness}% VZ
> \hskip.5\dimen2}
> {\hskip#1}}
>
>\starttext
>\startpoem
>\input knuth
>\nextpoem
>\input knuth
>\stoppoem
>\stoptext
>-----------------------------------------------------------------
>
>for distro it also should be accompanied by
>
> \c!rulethickness=\linewidth,
>
>in \def\dodefineparagraphs[#1][#2]%
>
>Vit
>_______________________________________________
>ntg-context mailing list
>ntg-context@ntg.nl
>http://www.ntg.nl/mailman/listinfo/ntg-context
>
>
next prev parent reply other threads:[~2006-03-28 14:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 23:53 \page inside a block frantisek holop
2006-03-16 10:38 ` Hans Hagen
2006-03-16 21:50 ` frantisek holop
2006-03-16 22:17 ` Aditya Mahajan
2006-03-16 22:27 ` Thomas A. Schmitz
2006-03-16 22:57 ` frantisek holop
2006-03-17 18:49 ` Willi Egger
2006-03-26 19:42 ` \setupmarginrules (was: Re: \page inside a block) frantisek holop
2006-03-26 20:12 ` \setupmarginrules Vit Zyka
2006-03-26 20:41 ` \setupmarginrules frantisek holop
2006-03-27 20:54 ` \setupmarginrules Vit Zyka
2006-03-28 14:49 ` Willi Egger [this message]
2006-03-28 15:05 ` \setupmarginrules Taco Hoekwater
2006-03-28 15:10 ` \setupmarginrules Vit Zyka
2006-03-28 15:14 ` \setupmarginrules Taco Hoekwater
2006-03-28 16:58 ` \setupmarginrules Vit Zyka
2006-03-28 17:13 ` \setupmarginrules Hans Hagen
2006-03-30 19:18 ` \setupmarginrules Willi Egger
2006-03-28 16:42 ` \setupmarginrules Hans Hagen
2006-03-28 17:12 ` \setupmarginrules Hans Hagen
2006-03-28 18:55 ` \setupmarginrules Vit Zyka
2006-03-28 21:44 ` \setupmarginrules frantisek holop
2006-03-29 8:14 ` \setupmarginrules 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=44294D0B.6030702@boede.nl \
--to=w.egger@boede.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).