From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: extra line after switchtobodyfont
Date: Wed, 08 May 2013 01:29:19 +0200 [thread overview]
Message-ID: <51898E4F.9060703@wxs.nl> (raw)
In-Reply-To: <51895FE3.3000603@wxs.nl>
On 5/7/2013 10:11 PM, Hans Hagen wrote:
> On 5/4/2013 6:59 PM, Wolfgang Schuster wrote:
>>
>> Am 04.05.2013 um 09:21 schrieb Aditya Mahajan <adityam@umich.edu>:
>>
>>> On 2013-05-03, at 7:36 PM, "Meer, H. van der" <H.vanderMeer@uva.nl>
>>> wrote:
>>>
>>>> Seems finally solved (sigh). I cleaned out all files loading
>>>> typescripts on the fly.
>>>> - typescript macros ending in ] at the end of a line have now ]% at
>>>> the end of the line
>>>> - empty lines have been removed for clarity
>>>> - all files now have \endinput at the end.
>>>>
>>>> The files changed fit in a 54KB zip and I can send them if
>>>> Hans/Wolfgang/.. wants to incorporate them in the next beta.
>>>
>>> I haven't followed this thread in detail, but an alternative is to
>>> redefine \starttypescript etc. to use a different catcode regime so
>>> that new lines and spaces are ignores (similar to
>>> \starttexdefinition, etc)
>>
>>
>> A better method is to ignore the endlinechar when typescript files are
>> loaded.
>>
>> \newcount\savedendlinechar
>>
>> \starttext
>>
>> Line 1\crlf
>> \savedendlinechar\endlinechar \endlinechar\minusone
>> \switchtobodyfont[pagella]
>> \endlinechar\savedendlinechar
>> Line 2
>>
>> \stoptext
>
> in fact, that should happen automatically but maybe i messed up something
(1) i adapted \loadfoundtypescriptfile (order of things, more robust)
(2) i adapted type-imp-pagella (had series of two defs per line which
introduced the spaces)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-07 23:29 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 [this message]
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=51898E4F.9060703@wxs.nl \
--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).