From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Offset MP text with font change
Date: Mon, 29 Apr 2013 01:00:10 +0200 [thread overview]
Message-ID: <517DA9FA.5030007@wxs.nl> (raw)
In-Reply-To: <F74D6E1D-AB2C-40CD-888B-20D2FEBDB340@web.de>
On 4/29/2013 12:42 AM, Keith J. Schultz wrote:
> Hi Marco, All,
>
> agreed you can avoid the spaces by putting the usetypescript in the "preamble",
> but should not the loading of a typescript not bleed any spaces!
it's not the typescript that has the space but the file ... a typescript
file can have more than typescripts like definitions, documentation, etc.
In the past, one *always* had to load a typescript file explicitly but
at some point - out of convenience - the \setupbodyfont mechanism has
been extended to automatically load a typescriptfile with the same name
as the requested bodyfont. So, it's the price paid for convenience. And,
in most cases a bodyfont is not initialized in a \hbox.
> regards
> Keith.
>
> Am 28.04.2013 um 22:03 schrieb Marco Patzer <homerow@lavabit.com>:
>
>> On 2013–04–28 Keith J. Schultz wrote:
>>
>>> can someone explain to me why loading a file/typescript is
>>> producing spaces????
>>
>> The typescripts themselves are full of spaces and new lines. And you
>> really want those spaces for readability. TeX usually squashes
>> multiple spaces into one, but spaces still matter in many
>> circumstances, e.g. within an \hbox.
>>
>>> If the code that does load the file/s produced spaces for
>>> debugging purposes that is fine, but should not they actually
>>> going somewhere else?
>>
>> There's no code that produces spaces. The spaces are in the
>> typescript file.
>>
>>> Personally, I find it a bug if loading fonts or other files
>>> produces extraneous characters!
>>
>> This is usually not a problem, since typescripts are loaded in the
>> setup area. Even when loaded within the text area the spaces don't
>> cause problems. Loading an entire file within a box, like I did in
>> the example, is an unusual edge-case and there's a simple
>> workaround, see Wolfgangs answer.
>>
>> Except if there's an easy fix for that, I'm personally fine knowing
>> where the spaces are coming from and how to prevent them, which I do
>> now.
>>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
--
-----------------------------------------------------------------
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
___________________________________________________________________________________
prev parent reply other threads:[~2013-04-28 23:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 17:56 Marco Patzer
2013-04-28 18:04 ` Wolfgang Schuster
2013-04-28 18:37 ` Marco Patzer
2013-04-28 18:40 ` Wolfgang Schuster
2013-04-28 18:40 ` Keith J. Schultz
2013-04-28 20:03 ` Marco Patzer
2013-04-28 20:24 ` Hans Hagen
2013-04-28 22:42 ` Keith J. Schultz
2013-04-28 23:00 ` Hans Hagen [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=517DA9FA.5030007@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).