From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Questions/Comments
Date: Tue, 11 Sep 2001 10:27:33 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20010911092040.025bd458@server-1> (raw)
In-Reply-To: <20010910185708.L14168@localhost>
Hi Marco
- The \setuppagenumbering command should provide a "strut" option
> to correctly cater for oldstyle digits: If no strut is
> inserted, the digits "dance" from page to page.
Ah, interesting. Since the height of a digit is about the height of a
strut, this has gone unnoticed! If you set the headertexts, you will notice
that they have a strut and that pagenumbers also get strutted so this bug
was rather obscured. Since i consider it a bug, i will default to struts
but provide a way to turn it off.
Now, what you can do is to set the style (letter) to \oldstyle\strut.
Alternatively you can add these lines to cont-new.tex (after \unprotect):
\unexpanded\def\@@plaatspaginanummer% called in empty tests
{\doif{\@@nmstatus\@@pnstatus}{\v!start\v!start}
{{\doif{\@@nmstrut}{\v!ja}{\strut}%
\@@nmcommando{\doattributes\??nm\c!letter\c!kleur
{\volledigepaginanummer}}}}}
\stelnummeringin
[c!strut=\v!ja]
it wil go into the next beta.
>- Protruding information should be provided for all the different
> quotation marks. (I understand that support for protrusion is
> in an early state of development.)
indeed, the named ones f possible, any input is welcom
>- Is there a way to define custom itemisations? I mean, can one
> define e.g. a enumeration inparaenum which transforms
>
> We distinguish the following classes of problems:
> \startinparaenum
> \item neglectable problems,
> \item easy problems,
> \item hard problems,
> \item interesting problems.
> \stopinparaenum
>
> into
>
> We distinguish the following classes of problems: (a) neglectable
> problems, (b) easy problems, (c) hard problems, (d) interesting
> problems.
\defineitemize is definitely on the todo list [even mentioned in
core-itm.tex -)] but i want to combine this with a redo of the itemize
module [i have a couple of more wishes]
for the moment, you can use \definestartstop
>- When typesetting capitals (like in acronyms), one would like to
> avoid "screaming" by decreasing the font size a little -- not
> much, just one point or so. Is there a way to switch to, say, a
> font with 90% the size of the current bodyfont? I could then
> write a macro \versal{} for my purposes.
There are several ways to accomplish this
(1) use \kap/\cap
(2) use a small caps font
(3) use a smaller typeface
(1) is not robust and (2) not flexible enough so given that you have a
recent context running you can create a new typeface.
Method (3) is the best since here you create a whole new instance of a
typeface but 90% scaled down of the main one:
\starttext
\showbaselines
\definetypeface [mainface] [rm] [serif] [palatino]
[default] [encoding=texnansi]
\definetypeface [versface] [rm] [serif] [palatino]
[default] [encoding=texnansi,rscale=.9]
\setupbodyfont[mainface]
\definestartstop
[Verse]
[style=versface]
\input tufte
\startVerse \input tufte \par \stopVerse
\input tufte
\stoptext
A fourth method [quick and dirty] is to simply define a font:
\definefont [ABitSmaller] [Serif sa .9]
\definestartstop
[Verse]
[style=ABitSmaller]
\input tufte
\startVerse \input tufte \par \stopVerse
\input tufte
or, better lookwing
\definestartstop
[Verse]
[style={\ABitSmaller\setupinterlinespace[.8]}]
>- In German, there are a lot of abbreviations that end with a
> colon, like usw. (und so weiter) etc. What is the correct way
> to define a synonym \USW which inserts the trailing colon only
> if no second colon is immediately following? I fiddled with
> \doifnextcharelse, but were not successful.
This is kind of tricky because capitalizing interferes with look ahead. I
can consider adding a hook but this is a delicate process
[not quickly hackable]
>- I suggest that the \digits mechanism should not trigger math
> mode automatically: In my document, I want to use oldstyle
> figures in text mode, while in math mode, upright figures shall
> appear. (PS. The \digitpowerseperator macro used in
> supp-num.tex should be named \digitpowerseparator, I guess.)
for the moment you can change:
\let\handlemathdigits\firstofoneargument
\let\handletextdigits\mathematics
\def\handledigits%
{\ifmmode
\handlemathdigits{\dohandledigits}%
\else
\dontleavehmode\hbox{\handletextdigits{\dohandledigits}}%
\fi
\egroup}
and
\let\handletextdigits\firstofoneargument
>- Do you think that the \digits mechanism can be generalised to
> cater for phone numbers, bank account numbers, postal codes,
> etc.? The correct typography for these is language dependent,
> as well, so it seems to be plausible to merge the mechanisms.
the simple digits is on the to do list of language related things, but for
phone numbers and alike, i need to wrap it into a high level interface. no
problem, but others must make me the lists of conventions -)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-09-11 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-10 16:57 Questions/Comments Marco Kuhlmann
2001-09-11 8:27 ` Hans Hagen [this message]
2001-09-11 11:29 ` Questions/Comments Marco Kuhlmann
2001-09-11 16:36 ` Questions/Comments Hans Hagen
2001-09-12 13:58 ` Questions/Comments Marco Kuhlmann
2001-09-14 11:10 ` Questions/Comments Hans Hagen
2001-09-14 19:39 ` Questions/Comments Marco Kuhlmann
2001-09-14 20:00 ` Questions/Comments Marco Kuhlmann
2001-09-17 16:34 ` Questions/Comments Hans Hagen
2001-09-17 16:30 ` Questions/Comments 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=5.1.0.14.1.20010911092040.025bd458@server-1 \
--to=pragma@wxs.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).