# [XeTeX] Mono-spaced fonts problem solved?

Brian Aydemir brian.aydemir at gmail.com
Wed Jul 15 00:12:05 CEST 2009

I was using XeLaTeX (XeTeXk, Version 3.1415926-2.2-0.999.6 (Web2C 7.5.7),
TeX Live 2008) recently and noticed this problem, or something similar, as
well.
In the minimal document below, the
final "Maybe?" does not align with the previous lines as I
expect.  This is the case for DejaVu Sans Mono (version 2.29),
Anonymous Pro (version 1.0), and Monaco (whatever came with Mac OS X).
Enabling \frenchspacing seems to fix this, but I haven't needed it before,
so this fix feels a bit odd to me.

Cheers,
Brian

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\documentclass[11pt,letterpaper]{article}

% \frenchspacing

\usepackage[no-math,quiet]{fontspec}
\setmonofont
[Renderer = ICU,
Scale    = MatchLowercase,
Kerning  = Off]
{Anonymous Pro}
\usepackage{url}

\begin{document}

\noindent
\texttt{
01234567890123456789012345678901234567890123456789 \\
Is the colon off: Maybe?
}

\end{document}

On Tue, Jul 14, 2009 at 16:21, Nikos Platis <nplatis at freemail.gr> wrote:

> He is probably referring to the same problem mentioned at least twice in
> this list. See for example the thread starting here:
> http://tug.org/pipermail/xetex/2009-April/012835.html
> and more directly this older message:
> http://tug.org/mailman/htdig/xetex/2009-March/012372.html
>
> I am wondering if this is solved indeed.
>
> Nikos
>
> On Tue, Jul 14, 2009 at 22:31, Jonathan Kew <jfkthame at googlemail.com>wrote:
>
>> On 14 Jul 2009, at 20:09, Luisa wrote:
>>
>>  Hi guys!
>>>
>>> I've been noticing strange behaviour of xetex when using monospaced
>>> fonts, actually, the offending behaviour only raises when  puncuation signs
>>> are present, it looks like xetex's adding extra space for them.
>>>
>>> I begun looking on the net for this, finding reports of the same problem
>>> within this same mailing list, but without solution a priori.
>>>
>>> So I wanted to ask if this has been solved already, or is it that the
>>> ones which have asked this are doing something wrong?
>>>
>>> Among other things, I've tried enabling frenchspacing, and even producing
>>> similiar texts with inkscape and plain tex at the beginign, so as to check
>>> the problem is not in the font itself (tried with different mono fonts
>>> anyway), etc.
>>>
>>
>> It's hard to be sure exactly what you mean without seeing an example, but
>> this sounds like it might be a font-metrics bug in the xdvipdfmx driver,
>> which was fixed in the source a month or so ago. So the version that ships
>> with TeX Live 2009 (currently being tested in preparation for release)
>> should solve this.
>>
>> JK
>>
>>
>
>
> --
> -----------------------------------------------------------------------
> Nikos Platis
> Lecturer                                    http://www.uop.gr/~nplatis/
> University of Peloponnese                        email:  nplatis at uop.gr
> Department of Computer Science and Technology      tel: +30 2710 372264
> -----------------------------------------------------------------------
> "The empires of the future are the empires of the mind." - W. Churchill
> -----------------------------------------------------------------------
>                New Textbook:  Graphics&  Visualization
>           http://www.akpeters.com/product.asp?ProdCode=2744
> -----------------------------------------------------------------------
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/xetex/attachments/20090714/bcb33a63/attachment-0001.html>