From: Taco Hoekwater <taco@elvenkind.com>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: strange behaviour with \scale
Date: Fri, 01 Jul 2005 22:37:00 +0200 [thread overview]
Message-ID: <42C5A96C.9070903@elvenkind.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0507012219001.20279@gaston.free.fr>
Peter Münster wrote:
> On Fri, 1 Jul 2005, Mojca Miklavec wrote:
>
>
>>If you need a solution: use {\ Draft\ }
>
>
> Thanks a lot! I didn't think about this kind of space at all...
>
>
>>If you need the reason: wait for the expert(s)
>
>
> I don't need it, but it would certainly be interesting ;)
From looking at it quickly, it seems sometimes the output routine
is called when the ~ command has the 'normal' definition, and
sometimes when it has TaBlE's definition. These do not produce
identical results (~ in TaBlE has the width of a 'zero' digit).
I'm not sure why this happens, though.
Taco
next prev parent reply other threads:[~2005-07-01 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 15:35 Peter Münster
2005-07-01 17:26 ` Mojca Miklavec
2005-07-01 20:20 ` Peter Münster
2005-07-01 20:37 ` Taco Hoekwater [this message]
2005-07-02 14:46 ` Hans Hagen
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=42C5A96C.9070903@elvenkind.com \
--to=taco@elvenkind.com \
--cc=mojca.miklavec.lists@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).