From: Brecht Machiels <brecht@mos6581.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: specific document layout with ConTeXt
Date: Mon, 29 Dec 2008 19:52:30 +0100 [thread overview]
Message-ID: <49591C6E.2000300@mos6581.org> (raw)
In-Reply-To: <5AB74AE9-7A78-40E3-B2A5-E27DEDBC4F93@gmail.com>
Wolfgang Schuster wrote:
> Am 29.12.2008 um 18:55 schrieb Brecht Machiels:
>
>> Hello,
>>
>>> I used LuaTeX for the document, to use it with pdfTeX you need a few
>>> additional settings.
>>> - replace \usetypescript[postscript] with \usetypescript[postscript][ec]
>>> - if you use a older ConTeXt version, add \usetypescriptfile[type-gyr]
>>> to the style file
>>> - add \enableregime[utf] to the sample document
>>
>> Both solutions worked (once I got 'texexec --lua' working anyway).
>>
>> In your original style file, you put:
>> \setupbodyfontenvironment [9pt][interlinespace=10pt]
>>
>> I assume this should set the interline spacing of the Abstract section
>> to 10pt? This doesn't work however. I assume this is because the style
>> option to \definestartstop[abstract] does not change the bodyfont, and
>> thus not the interline spacing.
>>
>> I have tried using \setupinterlinespace in the
>> \definestartstop[abstract], but to no avail.
>
>
> \definestartstop
> [abstract]
> [style={\switchtobodyfont[9pt]\bf}]
I had also tried this... but this results in some weird effects. Using:
\setupbodyfontenvironment [9pt][interlinespace=10pt]
it does not seem to change the interline spacing (when comparing it to
\setupbodyfontenvironment [9pt][interlinespace=12pt]
)
Trying to see what is going on, I try:
\setupbodyfontenvironment [9pt][interlinespace=20pt]
and I get something that cannot be correct:
http://homes.esat.kuleuven.be/~bmachiel/rfic/template.pdf
Any ideas?
Brecht
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-12-29 18:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-28 23:56 Brecht Machiels
2008-12-29 15:45 ` Wolfgang Schuster
2008-12-29 17:55 ` Brecht Machiels
2008-12-29 18:09 ` Wolfgang Schuster
2008-12-29 18:52 ` Brecht Machiels [this message]
2008-12-29 19:06 ` Wolfgang Schuster
[not found] <mailman.3940.1230479853.19169.ntg-context@ntg.nl>
2009-01-05 8:20 ` richard.stephens
2009-01-05 13:44 ` Aditya Mahajan
-- strict thread matches above, loose matches on Subject: below --
2008-12-28 1:36 Brecht Machiels
2008-12-28 14:00 ` Martin Schröder
[not found] ` <alpine.LNX.2.00.0812281040040.16071@nqv-yncgbc>
2008-12-28 16:06 ` Wolfgang Schuster
2008-12-28 19:40 ` Aditya Mahajan
2008-12-28 19:04 ` John Devereux
2008-12-28 19:50 ` Aditya Mahajan
2008-12-28 21:42 ` Andrea Valle
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=49591C6E.2000300@mos6581.org \
--to=brecht@mos6581.org \
--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).