[XeTeX] Unsubscribe

Kate Hayes khayes at ppi2pass.com
Wed Aug 22 15:28:41 CEST 2007



-----Original Message-----
From: xetex-bounces at tug.org [mailto:xetex-bounces at tug.org] On Behalf Of
xetex-request at tug.org
Sent: Wednesday, August 22, 2007 3:00 AM
To: xetex at tug.org
Subject: XeTeX Digest, Vol 41, Issue 25

Send XeTeX mailing list submissions to
	xetex at tug.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://tug.org/mailman/listinfo/xetex
or, via email, send a message with subject or body 'help' to
	xetex-request at tug.org

You can reach the person managing the list at
	xetex-owner at tug.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of XeTeX digest..."


Today's Topics:

   1. lmsans font [was: from teTeX-3.0 to TeXLive 2007] (Mike Maxwell)
   2. Re: lmsans font [was: from teTeX-3.0 to TeXLive 2007]
      (Will Robertson)
   3. Re: lmsans font [was: from teTeX-3.0 to TeXLive 2007]
      (Jonathan Kew)
   4. Re: lmsans font [was: from teTeX-3.0 to TeXLive 2007]
      (Bruno Voisin)
   5. Re: lmsans font [was: from teTeX-3.0 to TeXLive 2007]
      (Bruno Voisin)
   6. Re: from teTeX-3.0 to TeXLive 2007 (Peter Dyballa)
   7. Re: from teTeX-3.0 to TeXLive 2007 (Bruno Voisin)


----------------------------------------------------------------------

Message: 1
Date: Tue, 21 Aug 2007 22:56:57 -0400
From: Mike Maxwell <maxwell at umiacs.umd.edu>
Subject: [XeTeX] lmsans font [was: from teTeX-3.0 to TeXLive 2007]
To: Unicode-based TeX for Mac OS X and other platforms <xetex at tug.org>
Message-ID: <46CBA5F9.7020304 at umiacs.umd.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed

Akira Kakuto wrote:
>> In order to try to understand that, I have been looking at  
>> fontspec.sty and could not find any explicit call to a specific font  
>> file such as lmroman10-regular(.otf).
> 
> Please see font definition files in  xelatex/euenc/lm.

That gives me a clue to a problem I've been having.  I'm converting 
DocBook files to xetex, using DBlatex and then doing a bit of hand 
munging (which can be automated once I figure out what works), then 
running xetex on it.  One of the munging tasks is to add the ff. lines:
           \usepackage{fontspec}
           \setmainfont{Charis SIL}
This font is a Latin font that also includes the IPA characters, and 
includes (among other things) bold glyphs.

But I'm still getting the following warning msg:
    Missing character: There is no ? in font [lmsans10-bold]!
In case the missing char doesn't show up in your email, it's an IPA 
character.  It is present in the Charis SIL font, but apparently not in 
the lmsans font.  The warnings appear to be triggered on section titles, 
and indeed for this particular section, the IPA character is missing in 
the PDF.

What I can't figure out is why, when I've told it to use the Charis SIL 
font, it still insists on using the lmsans font in section headings. 
(Most everywhere else, it's using the Charis font.)  The quoted email 
above supplies a hint; the font definition files in xelatex/euenc/lm are 
apparently supplying that font name.  But under what circumstances do 
they get called, and more importantly, how can I override that?  (And 
what does 'euenc' mean?  Greek for "good encoding"?)
----------


-- 
	Mike Maxwell
	maxwell at umiacs.umd.edu
	"Theorists...have merely to lock themselves in a room
	with a blackboard and coffee maker to conduct their business."
	--Bruce A. Schumm, Deep Down Things


------------------------------

Message: 2
Date: Wed, 22 Aug 2007 13:19:08 +0930
From: "Will Robertson" <wspr81 at gmail.com>
Subject: Re: [XeTeX] lmsans font [was: from teTeX-3.0 to TeXLive 2007]
To: "Unicode-based TeX for Mac OS X and other platforms"
	<xetex at tug.org>
Message-ID:
	<27990a880708212049g5cd03643ud7f81854de65b2dc at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On 8/22/07, Mike Maxwell <maxwell at umiacs.umd.edu> wrote:
> What I can't figure out is why, when I've told it to use the Charis SIL
> font, it still insists on using the lmsans font in section headings.

Only you can know that -- we don't know what your document looks like!
If you can send through a *minimal* example demonstrating the problem,
we'll likely be able to fix the problem.

> (And what does 'euenc' mean?  Greek for "good encoding"?)

:) The "EU" suffix (for

"Experimental Unicode") was suggested to me by Frank Mittelbach when I
said we needed some LaTeX encodings to play with in XeTeX. Since this
layer is largely invisible to the average user, I don't mind the
slightly cryptic name.

Cheers,
Will


------------------------------

Message: 3
Date: Wed, 22 Aug 2007 08:21:13 +0100
From: Jonathan Kew <jonathan_kew at sil.org>
Subject: Re: [XeTeX] lmsans font [was: from teTeX-3.0 to TeXLive 2007]
To: Unicode-based TeX for Mac OS X and other platforms <xetex at tug.org>
Message-ID: <B797EA25-A125-426D-B0A1-0C1FCE393F6A at sil.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed


On 22 Aug 2007, at 4:49 am, Will Robertson wrote:

> On 8/22/07, Mike Maxwell <maxwell at umiacs.umd.edu> wrote:
>> What I can't figure out is why, when I've told it to use the  
>> Charis SIL
>> font, it still insists on using the lmsans font in section headings.
>
> Only you can know that -- we don't know what your document looks like!
> If you can send through a *minimal* example demonstrating the problem,
> we'll likely be able to fix the problem.

This means that the document class you're using formats section  
headings in the sans serif family. So you need to either change this  
(I'm sure there are packages for customizing this; try sectsty,  
perhaps), or else tell fontspec to load a sans serif font that  
includes all the characters you need (using \setsansfont in addition  
to \setmainfont).

Of course, the "sans" font doesn't have to be truly sans.... a quick  
workaround would be to load Charis SIL for the sans family as well as  
the main family!

JK



------------------------------

Message: 4
Date: Wed, 22 Aug 2007 10:08:13 +0200
From: Bruno Voisin <bvoisin at mac.com>
Subject: Re: [XeTeX] lmsans font [was: from teTeX-3.0 to TeXLive 2007]
To: Unicode-based TeX for Mac OS X and other platforms <xetex at tug.org>
Message-ID: <EB7ECD47-A218-4C6C-8D1B-7560BAF582BA at mac.com>
Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed

Le 22 ao?t 07 ? 04:56, Mike Maxwell a ?crit :

> [...]
>            \usepackage{fontspec}
>            \setmainfont{Charis SIL}
> [...]
>
> But I'm still getting the following warning msg:
>     Missing character: There is no ? in font [lmsans10-bold]!
> In case the missing char doesn't show up in your email, it's an IPA
> character.  It is present in the Charis SIL font, but apparently  
> not in
> the lmsans font.  The warnings appear to be triggered on section  
> titles,
> and indeed for this particular section, the IPA character is  
> missing in
> the PDF.
>
> What I can't figure out is why, when I've told it to use the Charis  
> SIL
> font, it still insists on using the lmsans font in section headings.

There must be something in the class file or one of the style files  
used by your document which says that section titles are in \sffamily 
\bfseries -- or \textsf{\textbf{. \setmainfont sets only the font for  
the serif family (Times-like), you need \setsansfont for setting the  
font for the sans-serif family (Helvetica-like), and \setmonofont for  
setting the font for the monospaced family (Courier-like).

You would need something like:

\usepackage{fontspec,xunicode,xltxtra}
\defaultfontfeatures{Mapping=tex-text,Scale=MatchLowercase}
\setmainfont{Charis SIL}
\setsansfont{Charis SIL}
\setmonofont{Courier}  % or whichever monospaced font of your liking

That said, it would be even better to use a truly sans-serif font for  
\setsansfont, and instead to redefine the section command in your  
class file to avoid titles using sans-serif. Something like, in the  
preamble of your document:

\makeatletter
\renewcommand{\subsection}{\@startsection{subsection}{2}{0pt}%
   {-2.25ex plus -1ex minus -.2ex}{1ex plus .2ex}%
   {\centering\normalfont\normalsize\itshape}}
\makeatother

Namely, take the \section command definition from your class file,  
copy it, paste it in the preamble of your document, sandwiched  
between \makeatletter and \makeatother, replace \newcommand if any by  
\renewcommand, and then erase the \sffamily or \textsf{ instruction  
which must be hanging out somewhere.

Hope this helps,

Bruno Voisin


------------------------------

Message: 5
Date: Wed, 22 Aug 2007 10:11:19 +0200
From: Bruno Voisin <bvoisin at mac.com>
Subject: Re: [XeTeX] lmsans font [was: from teTeX-3.0 to TeXLive 2007]
To: Unicode-based TeX for Mac OS X and other platforms <xetex at tug.org>
Message-ID: <403AB2CE-527E-4EB7-8F69-96B2E7418287 at mac.com>
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed

Le 22 ao?t 07 ? 09:21, Jonathan Kew a ?crit :

> This means that the document class you're using formats section
> headings in the sans serif family. So you need to either change this
> (I'm sure there are packages for customizing this; try sectsty,
> perhaps), or else tell fontspec to load a sans serif font that
> includes all the characters you need (using \setsansfont in addition
> to \setmainfont).
>
> Of course, the "sans" font doesn't have to be truly sans.... a quick
> workaround would be to load Charis SIL for the sans family as well as
> the main family!

Just finding your message after sending mine, saying exactly the  
same. Sorry for wasting bandwidth, should have read the whole thread  
before answering!

Bruno Voisin



------------------------------

Message: 6
Date: Wed, 22 Aug 2007 10:55:20 +0200
From: Peter Dyballa <Peter_Dyballa at Web.DE>
Subject: Re: [XeTeX] from teTeX-3.0 to TeXLive 2007
To: Unicode-based TeX for Mac OS X and other platforms <xetex at tug.org>
Message-ID: <E1948930-B754-495F-87A8-DA244CAABA3D at Web.DE>
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed


Am 20.08.2007 um 19:32 schrieb Pablo Rodr?guez:

> BTW, the other issue with page size seems to be that XeLaTeX overrides
> the geometry page size specifications if dvipdfm is the selected  
> driver
> for geometry:
>
> \documentclass[12pt]{article}
> \usepackage[dvipdfm,a5paper]{geometry}
> \begin{document}
> Hi, this is a test.
> \end{document}
>
> This might also be a bug.

No, it's not. XeTeX writes a \special into the XDV file: pdf:pagesize  
width 423.94606pt height 597.50787pt. Both xdv2pdf and xdvipdfmx seem  
to read, understand, and apply this.

Don't trust so much what you see in some viewer. These programmes are  
often too dumb to read useful parameters from the PDF file and act in  
some inflexible default way. Use pdfinfo to check the reality!

--
Mit friedvollen Gr??en

   Pete

Increase the size of your bike by at least *five* inches!




------------------------------

Message: 7
Date: Wed, 22 Aug 2007 11:33:32 +0200
From: Bruno Voisin <bvoisin at mac.com>
Subject: Re: [XeTeX] from teTeX-3.0 to TeXLive 2007
To: Unicode-based TeX for Mac OS X and other platforms <xetex at tug.org>
Message-ID: <203ABECA-D4B1-4B0F-9870-5B72E4F962F6 at mac.com>
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed

Le 22 ao?t 07 ? 10:55, Peter Dyballa a ?crit :

> Am 20.08.2007 um 19:32 schrieb Pablo Rodr?guez:
>
>> BTW, the other issue with page size seems to be that XeLaTeX  
>> overrides
>> the geometry page size specifications if dvipdfm is the selected
>> driver
>> for geometry:
>>
>> \documentclass[12pt]{article}
>> \usepackage[dvipdfm,a5paper]{geometry}
>> \begin{document}
>> Hi, this is a test.
>> \end{document}
>>
>> This might also be a bug.
>
> No, it's not. XeTeX writes a \special into the XDV file: pdf:pagesize
> width 423.94606pt height 597.50787pt. Both xdv2pdf and xdvipdfmx seem
> to read, understand, and apply this.

I'm not sure that's true any longer. XeTeX now uses the same  
\pdfpagewidth and \pdfpageheight primitives as pdfTeX, and as a  
consequence TeXLive-2007 includes a special configuration file tex/ 
xelatex/xetexconfig/geometry.cfg which, when read by XeLaTeX,  
specifies the pdftex driver.

On my Mac:

theo9mc182:~ bvoisin$ kpsewhich --progname=xelatex geometry.cfg
/usr/local/texlive/2007/texmf-dist/tex/xelatex/xetexconfig/geometry.cfg

As a consequence, don't specify the dvipdfm option. Let TeXLive-2207'  
intelligent XeTeX integration take care of selecting the appropriate  
geometry driver file for you.

Bruno Voisin


------------------------------

_______________________________________________
XeTeX mailing list
XeTeX at tug.org
http://tug.org/mailman/listinfo/xetex


End of XeTeX Digest, Vol 41, Issue 25
*************************************



More information about the XeTeX mailing list