ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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: Fri, 3 May 2013 11:40:17 +0000	[thread overview]
Message-ID: <DA9DC11B-9F35-4E06-AB78-1BE4B894D45A@uva.nl> (raw)
In-Reply-To: <7DF6795D-D2FD-428F-B13E-7274EDDDAC1A@uva.nl>


[-- Attachment #1.1: Type: text/plain, Size: 3371 bytes --]

This might be interesting. The example I gave before was now typeset with type-imp-euler.mkiv cannibalized to \endinput in the very first line. Then there are no spurious spaces and 5 executions of the recursive loop from \t_font_typescripts.
Thus, even though in type-imp-euler.mkiv all empty lines were removed, all intermediate spaces removed, all macros ended in ]% en texgyre not loaded, there is still spurious space. From the log I see that there are requests for [mono][modern] etc.

In order to locate these I have reduced the euler file to one define:
\starttypescript[euler]%
\definetypeface[euler][\s!mm][\s!math][euler][\s!default]%
\quittypescriptscanning
\stoptypescript

Now I get one  or possibly two spurious spaces. But I cannot easily find which typescript file is involved. Do you know this? Exerpt from the log:

++++++++        >
fonts           > request: [euler] [] []
fonts           > auto load typescript file 1: [euler]
fonts           > request: [euler] [] []
(/Users/hansm/TeX/texmf/tex/context/base/type-imp-euler.mkiv)
fonts           > match: [euler]
fonts           > define: [euler] [mm] [math] [euler]
fonts           > request: [math] [euler] [name]
fonts           > auto load typescript file 2: [euler]
fonts           > request: [math] [euler] [name]
fonts           > request: [math] [default] [size]
fonts           > match: [math] [default] [size]
fonts           > defining > font with asked name 'unknown' is not found using lookup 'file'
fonts           > defining > unknown font 'unknown', loading aborted
fonts           > defining > unable to define 'unknown' as 'euler-10pt-mm-mb--3'
fonts           > defining > font with asked name 'unknown' is not found using lookup 'file'
fonts           > defining > unknown font 'unknown', loading aborted
fonts           > defining > unable to define 'unknown' as 'euler-10pt-mm-mb--2'
fonts           > defining > font with asked name 'unknown' is not found using lookup 'file'
fonts           > defining > unknown font 'unknown', loading aborted
fonts           > defining > unable to define 'unknown' as 'euler-10pt-mm-mb--1'
--------        >


By the way. Is it correct that alone \definetypeface, \definefontsynonym, \starttypescriptcollection must be closed by ]% while for example \starttypescript[] seems to do no harm?

Hans van der Meer



On 3 May 2013, at 1:06 PM, "Meer, H. van der" <H.vanderMeer@uva.nl<mailto:H.vanderMeer@uva.nl>> wrote:


On 3 May 2013, at 12:28 PM, Wolfgang Schuster <schuster.wolfgang@gmail.com<mailto:schuster.wolfgang@gmail.com>>
wrote:
Do you mean the missing % after \doifsomething etc.? These lines don’t need a % because TeX gobbles the spaces between the arguments.

I wasn't aware of that, but will remember.

Any idea how further? More from \loadfontgoodies[lm]? To what file does that resolve?

The commands loads lm.lfg


The somewhat simpleminded idea of adding \ignorespaces at the end of the \definetypeface macro and friends, will not work I am afraid.
Is there a possibilty to remove all whitespace from the tokens in \t_font_typescripts or prevent them from entering? Perhaps in the lua end?
Or is it possible to assign to all whitespace characters (space, tab, newline) a category code 9 when reading/processing the typescript definitions?

Hans van der Meer




[-- Attachment #1.2: Type: text/html, Size: 6445 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2013-05-03 11:40 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 [this message]
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=DA9DC11B-9F35-4E06-AB78-1BE4B894D45A@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).