2010/9/22 Philip Taylor (Webmaster, Ret'd) p.tay...@rhul.ac.uk
P.S. This may be a more elegant solution :
[...]
\def\implementTIPAtextx#1{\scantokens{#1\endinput}\egroup}
Thank you, Phil: that certainly is.
2010/9/22 Philip Taylor (Webmaster, Ret'd) p.tay...@rhul.ac.uk
Ross Moore
2010/9/22 Heiko Oberdiek heiko.oberd...@googlemail.com
#1 is a (without blank space), \scantokens then reads
a new line aEOL and EOL is converted to {blank space}...
Thank you for the TeXnical explanation, Heiko, although I must confess I can
only follow it up to a point... ;-)
In the
2010/9/22 Ulrike Fischer ne...@nililand.de
Am Wed, 22 Sep 2010 14:35:22 +0100 schrieb Paolo Matteucci:
In the meantime the problem seems to be fixed:
*File List*
[...]
fontspec.sty2010/08/01 v2.0c Advanced font selection for
[...]
But you seem to be using fontspec 2.0c
2010/9/22 Ulrike Fischer ne...@nililand.de
xunicode has changed the definition of \implementTIPAtextx. It is
now (in 0.95)
\expandafter\ifx\csname scantokens\endcsname\relax
\def\implementTIPAtextx#1{#1\egroup}
\else
\def\implementTIPAtextx#1{\scantokens{#1}\egroup}
\fi
Reverting to
Hi all. I’ve updated my TexLive distribution today, and started noticing
that, if you invoke the tipa package with xltxtra (and hence fontspec and
xunicode) loaded, you get an extra trailing space just before the end of the
\textipa environment.
Minimal example:
% !Mode:: TeX:UTF-8
%xelatex
