From: "Meer, H. van der" <H.vanderMeer@uva.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: extra line after switchtobodyfont
Date: Thu, 2 May 2013 12:09:47 +0000 [thread overview]
Message-ID: <0275CB18-F5E4-47F7-85CF-B03DCFD4EF90@uva.nl> (raw)
In-Reply-To: <20130502104810.GE663@homerow>
Indeed, adding \usetypescriptfile[euler]\usetypescript[euler] before \starttext makes the extra vertical spacing go away in a simple test file. But that doesn't solve my problem, because I am typesetting xml data wherein a font change can be dictated from the inside. See the example code (supporting modules not included):
\startbuffer[font]
<?xml version="1.0" encoding="UTF-8"?>
<root>
First line.<br/>
<fontswitch family="euler">
Font switch here.
</fontswitch><br/>
Last line.
</root>
\stopbuffer
\xmlprocessbuffer{root}{font}{}
There is no way to have the typescript loaded before the \starttext, because it is not known what fonts will be called up by the xml. And loading it from within the data processed is too late.
I therefore conclude that this typescript problem should be fundamentally solved, instead of resorting to a subterfuge as loading things beforehand to avoid - what seems to me - coding mistakes.
Hans van der Meer
On 2 May 2013, at 12:48 PM, Marco Patzer <homerow@lavabit.com> wrote:
> On 2013–05–02 Meer, H. van der wrote:
>
>> A call to \switchtobodyfont introduces extra vertical spacing as can be seen in the example.
>> Is this intentional or is it something like a % missing somewhere in a macro?
>
> Loading the typescript in the setup area should get rid of the
> space.
>
> See http://www.ntg.nl/pipermail/ntg-context/2013/072892.html
>
> Marco
> ___________________________________________________________________________________
> 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
___________________________________________________________________________________
prev parent reply other threads:[~2013-05-02 12:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 10:38 Meer, H. van der
2013-05-02 10:40 ` Meer, H. van der
2013-05-02 21:17 ` Wolfgang Schuster
2013-05-03 7:34 ` Meer, H. van der
2013-05-03 7:43 ` Wolfgang Schuster
2013-05-03 9:19 ` Meer, H. van der
2013-05-03 10:28 ` Wolfgang Schuster
2013-05-03 11:06 ` Meer, H. van der
2013-05-03 11:40 ` Meer, H. van der
2013-05-03 14:06 ` Meer, H. van der
2013-05-04 7:21 ` Aditya Mahajan
2013-05-04 9:20 ` Meer, H. van der
2013-05-04 11:09 ` Sietse Brouwer
2013-05-04 16:59 ` Wolfgang Schuster
2013-05-07 20:11 ` Hans Hagen
2013-05-07 23:29 ` Hans Hagen
2013-05-03 7:57 ` Wolfgang Schuster
2013-05-02 10:48 ` Marco Patzer
2013-05-02 11:00 ` Meer, H. van der
2013-05-02 12:09 ` Meer, H. van der [this message]
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=0275CB18-F5E4-47F7-85CF-B03DCFD4EF90@uva.nl \
--to=h.vandermeer@uva.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).