From: "Tom" <Tom@tuxedo-press.com>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: \stretched in chapter titles in MKII
Date: Mon, 21 Feb 2011 19:18:40 -0500 [thread overview]
Message-ID: <010901cbd226$0f0ea7c0$2d2bf740$@com> (raw)
In-Reply-To: <4C335769.8030604@googlemail.com>
Tom Benjey
717-258-9733 voice
717-243-0074 fax
blog: www.TomBenjey.com
The code that follows works fine in MKII but doesn't stretch the chapter
title in MKIV. What must I change? Also, I want to convert the chapter
number to text before stretching it. Has anything been done to the routines
that convert numerals to alpha characters since last summer?
Thanks,
Tom
-----Original Message-----
From: ntg-context-bounces@ntg.nl [mailto:ntg-context-bounces@ntg.nl] On
Behalf Of Wolfgang Schuster
Sent: Tuesday, July 06, 2010 12:19 PM
To: mailing list for ConTeXt users
Subject: Re: [NTG-context] \stretched in chapter titles in MKII
Am 05.07.10 21:15, schrieb Tom:
> I am trying to stretch two lines of text to the same width for use as a
> chapter head.
> I have two major problems:
>
> 1. The second line of text is appended to the end of the first line
> instead
> of being placed below it.
>
> 2. I get errors when using #1 and #2 as values, i.e {Chapter #1} and {#2}.
> Because of these errors I have hardcoded the values in the example that
> follows:
\define[1]\ChapterTextStretch {\line{\stretched{#1}}}
\define[1]\ChapterNumberStretch{\determineheadnumber[chapter]\ChapterTextStr
etch{Chapter
\currentheadnumber}}
\setuphead
[chapter]
[alternative=middle,
textstyle=sansbold,
numberstyle=sans,
deeptextcommand=\ChapterTextStretch,
deepnumbercommand=\ChapterNumberStretch]
\starttext
\chapter{Test Chapter Title}
\input knuth
\stoptext
Wolfgang
____________________________________________________________________________
_______
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
____________________________________________________________________________
_______
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-02-22 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 19:15 Tom
2010-07-06 14:00 ` Tom
2010-07-06 14:06 ` Wolfgang Schuster
2010-07-06 16:18 ` Wolfgang Schuster
2010-07-06 17:52 ` Tom
2010-07-07 2:12 ` Tom
2011-02-22 0:18 ` Tom [this message]
2011-02-22 8:39 ` Wolfgang Schuster
2011-02-22 13:42 ` Tom
2011-02-22 22:14 ` Wolfgang Schuster
2011-02-23 12:13 ` Tom
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='010901cbd226$0f0ea7c0$2d2bf740$@com' \
--to=tom@tuxedo-press.com \
--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).