From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: extra line after switchtobodyfont
Date: Fri, 3 May 2013 09:43:45 +0200 [thread overview]
Message-ID: <05F640D1-3776-48FA-BBD9-95BA99812649@gmail.com> (raw)
In-Reply-To: <758AC4DD-17D4-4367-8F62-881240B22536@uva.nl>
Am 03.05.2013 um 09:34 schrieb "Meer, H. van der" <H.vanderMeer@uva.nl>:
> There is more to it then a preference for \crlf, typescript loading introduces a lot of spurious white, that not always can be made to disappear. I tracked it down to a macro in type-ini.mkvi:
>
> \def\font_typescript_process_typescript_file_and_store
> {*\expandafter\let\expandafter\t_font_typescripts\csname\??typescriptfiles\currenttypefile\endcsname
> A\ifx\t_font_typescripts\relax
> B\font_typescript_process_typescript_store_indeed
> C\fi
> D\the\t_font_typescripts}
>
> The ABCD*'s were added to see what happens. See the screen shot from one of my tests (<br/> results in \crlf but does not sit between text and fontswitch \switchtobodyfont). My guess is that the token register \t_font_typescripts is the source of the spaces, but I am not further than that. I have already mailed Hans Hagen about these findings.
The spaces in the output come from the line ending after the \definefontsynonym entry in the typescript and extra line in your other example from the empty lines between the typescript blocks and not from the macro above.
\starttext
A\crlf
B\crlf
\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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-05-03 7:43 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 [this message]
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
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=05F640D1-3776-48FA-BBD9-95BA99812649@gmail.com \
--to=schuster.wolfgang@gmail.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).