From: Adam Lindsay <atl@comp.lancs.ac.uk>
Subject: Re: extra space after variant
Date: Fri, 02 Dec 2005 18:48:09 +0000 [thread overview]
Message-ID: <439096E9.8080003@comp.lancs.ac.uk> (raw)
In-Reply-To: <439052AD.8020000@wxs.nl>
Hans Hagen wrote:
> Hans van der Meer wrote:
>
>> When I code:
>> abc {\variant[xyz] pqr}
>> I find extra space typeset between "abc" and "pqr".
>>
>> This extra space is absent when I code
>> abc {\variant[xyz]pqr}
>> Thus the space in the source between ] and pqr makes a difference in
>> the result.
>>
>> Clearly visible in:
>> abc {\variant[xyz] pqr} abc {\variant[xyz]pqr}\crlf
>> abc {\Var[xyz]pqr} abc {\Var[xyz] pqr}\crlf
>>
>> I would think that this should not happen.
>>
>> The whitespace goes away by inserting an \ignorespaces in the variant-
>> definition.
>> \def\variant[#1]% slow
>> {\dosetscaledfont
>> \expanded{\definedfont
>> [\truefontname{\fontstringA\fontstylesuffix\fontvariant
>> \fontstringA{#1}}
>> at \scaledfont]}\ignorespaces}
>>
>>
>> Still using version 2005-11-14, forget this if already corrected in
>> the latest version of the 30th.
>
>
> before we do that ... do others agree (taco, adam ...)?
>
> we don't want compatibility issues -)
>
> btw, a better sulution is to use \ignoreimplicitspaces:
>
> \def\ignoreimplicitspaces
> {\doifnextcharelse\relax\relax\relax}
>
> abc {x\variant[xyz]\space pqr} abc {\variant[xyz]pqr}\crlf
> abc {\variant[xyz]\space pqr} abc {\variant[xyz]pqr}\crlf
> abc {\variant[xyz] pqr} abc {\variant[xyz]pqr}\crlf
> abc {\variant[xyz]{x} pqr} abc {\variant[xyz]pqr}\crlf
>
> otherwise you run into problems with macros that want to insert a space
> explicitly
I like it, because the implementation bug was a bit annoying to me
sometimes.
Also, thanks for the fix for adapting sizes, back a few months. It means
that the EC Companion/TS1 support can now become feasible. Shall I try
to nudge that forward again?
The biggest issue is probably in typescripts and font synonyms -- should
they directly support Berry names, seeing as that's where people will be
getting these TS1 fonts?
adam
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk
Lancaster University, InfoLab21 +44(0)1524/510.514
Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2005-12-02 18:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 14:04 Hans van der Meer
2005-12-02 13:57 ` Hans Hagen
2005-12-02 18:35 ` Taco Hoekwater
2005-12-02 19:22 ` Adam Lindsay
2005-12-02 20:13 ` Taco Hoekwater
2005-12-04 21:03 ` Hans Hagen
2005-12-05 12:36 ` Adam Lindsay
2005-12-02 18:48 ` Adam Lindsay [this message]
2005-12-04 21:05 ` 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=439096E9.8080003@comp.lancs.ac.uk \
--to=atl@comp.lancs.ac.uk \
--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).