![](https://secure.gravatar.com/avatar/29c7bbff49b1599eddb2ec73fd9ffa6e.jpg?s=120&d=mm&r=g)
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
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 ___________________________________________________________________________________