[XeTeX] "Hoefler Text" XeLaTeX interface
Simon Spiegel
simon at simifilm.ch
Mon Oct 4 13:04:44 CEST 2004
My apologies for all the junk in my last mail.
>
> I have put together the first version of an XeLaTeX package which
> provides an easy interface to the rich Mac OS X font Hoefler Text. No
> more messing with \DeclareFontShape madness!
>
> It can't access everything Hoefler Text provides because I can't think
> of an easy way to get LaTeX to flexibly accept so many options. Anyway,
> better that you just look at the example file rather than listen to me
> rabbit on. I hope that something like this will become standard for
> many or all of the default Mac OS X fonts in the XeTeX distribution.
>
> (And for now it should eliminate the horrible difficulties people have
> trying to work out Apple's unfortunate naming schemes.)
>
> You can get instructions and download the whole thing from here:
> <http://www.mecheng.adelaide.edu.au/~will/tex/>
>
> (Unfortunately, there's no ins/dtx bundle. Once I learn how to write
> them, I might create a proper installer.)
>
> Please offer suggestions - I'm all ears!
>
> Will Robertson
This is great, thank you. Now of we could only automatize this, so that Will
hasn't to do this for every font there is. ;)
simon
--
Simon Spiegel
Mutschellenstr. 97
8038 Zürich
Telephon: ++41 1 481 48 52
Mobophon: ++41 76 459 60 39
-------------- next part --------------
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. Re: XeTeX fails on dragged PDF images (Bruno Voisin)
2. "Hoefler Text" XeLaTeX interface (Will Robertson)
3. Re: "Hoefler Text" XeLaTeX interface (Bruno Voisin)
4. Re: "Hoefler Text" XeLaTeX interface (Will Robertson)
5. Re: "Hoefler Text" XeLaTeX interface (Jonathan Kew)
6. Some thoughts regarding fonts (Simon Spiegel)
----------------------------------------------------------------------
Message: 1
Date: Mon, 4 Oct 2004 10:24:38 +0200
From: Bruno Voisin <bvoisin at mac.com>
Subject: Re: [XeTeX] XeTeX fails on dragged PDF images
To: Unicode-based TeX for Mac OS X <xetex at tug.org>
Message-ID: <D4C7586B-15DE-11D9-8774-000A95928A38 at mac.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Le 4 oct. 04, ? 04:24, Ross Moore a ?crit :
> OK, the [xetex] option to graphicx was not implicit.
> (I'll have to fix my graphics.cfg to make it so!)
Hi Ross,
What I did on my setup is replace, in color.cfg and graphics.cfg,
> % Select an appropriate default driver
> \begingroup
> \chardef\x=0 %
> % check pdfTeX
> \@ifundefined{pdfoutput}{}{%
> \ifcase\pdfoutput
> \else
> \chardef\x=1 %
> \fi
> }%
> % check VTeX
> \@ifundefined{OpMode}{}{%
> \chardef\x=2 %
> }%
> \expandafter\endgroup
> \ifcase\x
> % default case
> \ExecuteOptions{dvips}%
> \or
> % pdfTeX is running in pdf mode
> \ExecuteOptions{pdftex}%
> \else
> % VTeX is running
> \ExecuteOptions{vtex}%
> \fi
by
> % Select an appropriate default driver
> \begingroup
> \chardef\x=0 %
> % check pdfTeX
> \@ifundefined{pdfoutput}{}{%
> \ifcase\pdfoutput
> \else
> \chardef\x=1 %
> \fi
> }%
> % check VTeX
> \@ifundefined{OpMode}{}{%
> \chardef\x=2 %
> }%
> % check XeTeX
> \@ifundefined{XeTeXversion}{}{%
> \chardef\x=3 %
> }%
> \expandafter\endgroup
> \ifcase\x
> % default case
> \ExecuteOptions{dvips}%
> \or
> % pdfTeX is running in pdf mode
> \ExecuteOptions{pdftex}%
> \or
> % VTeX is running
> \ExecuteOptions{vtex}%
> \else
> % XeTeX is running
> \ExecuteOptions{xetex}%
> \fi
(Actually I put corrected copies inside
~/Library/texmf/tex/xetex/config/.)
I'm surprised there's no similar switch for hyperref.cfg, that for
XeTeX would load [dvipdfm] automatically.
On other topic, in your xetex.def, is one of the recognized extensions
for graphical files .sgi or .sga? (I must confess I don't know what
.psd, .mac, .sgi and .tga are.)
> % For a new graphics type, you can include a line here ...
> \@namedef{Gin at rule@.pdf}#1{{QTm}{QTm}{#1}}
> \@namedef{Gin at rule@.gif}#1{{QTm}{QTm}{#1}}
> \@namedef{Gin at rule@.jpg}#1{{QTm}{QTm}{#1}}
> \@namedef{Gin at rule@.mac}#1{{QTm}{QTm}{#1}}
> \@namedef{Gin at rule@.pict}#1{{QTm}{QTm}{#1}}
> \@namedef{Gin at rule@.png}#1{{QTm}{QTm}{#1}}
> \@namedef{Gin at rule@.psd}#1{{QTm}{QTm}{#1}}
> \@namedef{Gin at rule@.sgi}#1{{QTm}{QTm}{#1}}
> \@namedef{Gin at rule@.tga}#1{{QTm}{QTm}{#1}}
> \@namedef{Gin at rule@.tif}#1{{QTm}{QTm}{#1}}
>
> [...]
>
> % ... and add it's extension here
> \def\Gin at extensions{.pdf,.png,.jpg,.pict,.tif,.psd,.mac,.sga,.tga,.gif}
Bruno
------------------------------
Message: 2
Date: Mon, 4 Oct 2004 18:30:40 +0930
From: Will Robertson <will at guerilla.net.au>
Subject: [XeTeX] "Hoefler Text" XeLaTeX interface
To: XeTeX List <xetex at tug.org>
Message-ID: <DDBF4C4A-15E3-11D9-BE49-000A95E49032 at guerilla.net.au>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Hi all
I have put together the first version of an XeLaTeX package which
provides an easy interface to the rich Mac OS X font Hoefler Text. No
more messing with \DeclareFontShape madness!
It can't access everything Hoefler Text provides because I can't think
of an easy way to get LaTeX to flexibly accept so many options. Anyway,
better that you just look at the example file rather than listen to me
rabbit on. I hope that something like this will become standard for
many or all of the default Mac OS X fonts in the XeTeX distribution.
(And for now it should eliminate the horrible difficulties people have
trying to work out Apple's unfortunate naming schemes.)
You can get instructions and download the whole thing from here:
<http://www.mecheng.adelaide.edu.au/~will/tex/>
(Unfortunately, there's no ins/dtx bundle. Once I learn how to write
them, I might create a proper installer.)
Please offer suggestions - I'm all ears!
Will Robertson
------------------------------
Message: 3
Date: Mon, 4 Oct 2004 11:15:00 +0200
From: Bruno Voisin <bvoisin at mac.com>
Subject: Re: [XeTeX] "Hoefler Text" XeLaTeX interface
To: Unicode-based TeX for Mac OS X <xetex at tug.org>
Message-ID: <DE5EF7FE-15E5-11D9-8774-000A95928A38 at mac.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Le 4 oct. 04, ? 11:00, Will Robertson a ?crit :
> I have put together the first version of an XeLaTeX package which
> provides an easy interface to the rich Mac OS X font Hoefler Text. No
> more messing with \DeclareFontShape madness!
Hi Will,
Great work. I don't have time to test, unfortunately, but it looks like
it will make the font selection experience much simpler than my
time-consuming manual font declarations.
I wonder whether it's similar to what Jonathan had in mind when
writing, on the OS X TeX list:
> Le 3 oct. 04, ? 11:00, Jonathan Kew a ?crit :
>
>> What (some) people want, I think, is a XeLaTeX command such as:
>>
>> \NewFontFamily{hoefler}{"Hoefler Text"}
>>
>> that will automagically do the equivalent of Bruno's .fd
>> declarations. This is inherently difficult because of the wide
>> variation in the selection of styles and features available in
>> different font families, and the inconsistent organization and naming
>> of those that exist. I have a couple of ideas of how we might make
>> some progress, but there are limits to how far we can go, given the
>> creative freedom that font designers have.
Or was it some kind of adaptation of fontinst to AAT/OpenType and
XeLaTeX?
Bruno
------------------------------
Message: 4
Date: Mon, 4 Oct 2004 18:54:00 +0930
From: Will Robertson <will at guerilla.net.au>
Subject: Re: [XeTeX] "Hoefler Text" XeLaTeX interface
To: Unicode-based TeX for Mac OS X <xetex at tug.org>
Message-ID: <201214AA-15E7-11D9-BE49-000A95E49032 at guerilla.net.au>
Content-Type: text/plain; charset=US-ASCII; format=flowed
On 4 Oct 2004, at 6:45 PM, Bruno Voisin wrote:
> Great work. I don't have time to test, unfortunately, but it looks
> like it will make the font selection experience much simpler than my
> time-consuming manual font declarations.
> ...
> Or was it some kind of adaptation of fontinst to AAT/OpenType and
> XeLaTeX?
Ha ha ha! I wish. No, all manual labour very much inspired by your many
posted examples. Luckily, there are only a few fonts that complex (I
don't want to think about Zapfino!) so for most fonts it's fairly
straightforward. There's no point us all writing these awful .fd files,
so hopefully I can get the ball rolling by doing a fair few of them.
Best of luck,
Will
------------------------------
Message: 5
Date: Mon, 4 Oct 2004 10:43:19 +0100
From: Jonathan Kew <jonathan_kew at sil.org>
Subject: Re: [XeTeX] "Hoefler Text" XeLaTeX interface
To: Unicode-based TeX for Mac OS X <xetex at tug.org>
Message-ID: <D2E03350-15E9-11D9-94AA-000393BD674C at sil.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
On 4 Oct 2004, at 10:24 am, Will Robertson wrote:
> On 4 Oct 2004, at 6:45 PM, Bruno Voisin wrote:
>
>> Great work. I don't have time to test, unfortunately, but it looks
>> like it will make the font selection experience much simpler than my
>> time-consuming manual font declarations.
>> ...
>> Or was it some kind of adaptation of fontinst to AAT/OpenType and
>> XeLaTeX?
>
> Ha ha ha! I wish. No, all manual labour very much inspired by your
> many posted examples. Luckily, there are only a few fonts that complex
> (I don't want to think about Zapfino!) so for most fonts it's fairly
> straightforward. There's no point us all writing these awful .fd
> files, so hopefully I can get the ball rolling by doing a fair few of
> them.
>
For simpler cases, such as Palatino, I'm hoping we can make all this
work disappear. What I have in mind is adding features to XeTeX to make
it possible to discover the names of the style variants of a font
family, so that given the name "Palatino", for example, standard macros
could learn the correct names of the available styles. That's the only
thing that prevents auto-generation of the declarations in your
osxppl.fd file.
To some extent, even "standard" features such as Small Caps could be
auto-detected and supported, using the AAT/OT query primitives that
XeTeX already has. I'll probably have a go at writing such macros
sometime, if nobody else gets there first, but I'd like to get font
family discovery working first.
Full support of rich fonts with unique features will still require
manually-constructed .fd files, I expect, but many of the simpler cases
should become virtually painless.
JK
------------------------------
Message: 6
Date: Mon, 4 Oct 2004 11:36:10 +0200 (CEST)
From: Simon Spiegel <simon at simifilm.ch>
Subject: [XeTeX] Some thoughts regarding fonts
To: xetex at tug.org
Message-ID: <3176876.1096882570555.JavaMail.tomcatd at ente>
Content-Type: text/plain; charset="iso-8859-1"
Hi,
the discussion regarding fonts in LateX/XeTeX is highly interesting, and I want
to share my 0.02$. Just as a disclaimer: I'm neither a Tex-Pro nor a programmer,
but just an interested and fairly knowledgable LaTeX user who came to LaTeX
because no OSX of Framemaker exists.
When I started with LaTeX, I didn't understand anything about its handling of
fonts. I used a package a friend of mine put together and I still use it today.
I understand a bit more about fonts in LaTeX now, but I still doubt that I would
be able to install a complete new font for LaTeX. Entering XeTeX: From my point
of view, XeLaTeX is much an improvement in the handling of fonts, only few files
to edit, not 20 different formats to generate. Still, I think the siutation is
not perfect yet. One problem has directly to do with AAT/OpenType: In many cases
simply don't know what options a specific font offers. For example: After
fiddling around with Stempel Garamond LT Std for quite some time, I finally
understood that it just doesn't offer any swashes or alternative liguatures, in
my naivete I thought it just had to, being an OpenType font. To my knowlegde,
there is no tool, which will just display everything a font has to offer.
Another problem is that the syntax is different in XeLaTeX for OpenType and AAT
for accessing the font options, this was a source of confusion to me.
The last problem which I still don't know how to handle is the fact that
AAT/OpenType offers many options, LaTeX isn't prepared for. Take the different
italics in AdobeGaramond for example: one with swashes one without. I don't want
the swashed italics as standard italics font, it's too baroque, but I maybe want
to use it at certain places in a document. How do people deal with this
situation? And how about a font which offers all kind of weights, how can I
easily access all of them in one document (Maybe this is a trivial problem, I
just don't know it).
What would be the solution in a perfect world? Design a tool which shows all
options of a font, including ligatures, swashes, etc. Allow the user to select,
what options he wants for which style and generate the needed files for XeLaTex
based on the selection. This could even be included in frontends like TeXShop. I
do realize that this goes against TeX's philosophy to a certain extent, but it
would make the lifer for may users much more easier, and would also make XeTeX
more attractive.
simon
--
Simon Spiegel
Mutschellenstr. 97
8038 Z?rich
Telephon: ++41 1 481 48 52
Mobophon: ++41 76 459 60 39
-------------- next part --------------
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. New LaTeX encoding for XeTeX (Will Robertson)
2. XeTeX fails on dragged PDF images (Ross Moore)
3. Re: XeTeX fails on dragged PDF images (Will Robertson)
4. Re: XeTeX fails on dragged PDF images (Will Robertson)
5. Re: XeTeX fails on dragged PDF images (Ross Moore)
6. Re: I have broken XeTeX (Musa Furber)
7. Re: Upper Case numbers in Hoefler Text?? (Bruno Voisin)
----------------------------------------------------------------------
Message: 1
Date: Mon, 4 Oct 2004 11:01:05 +0930
From: Will Robertson <will at guerilla.net.au>
Subject: [XeTeX] New LaTeX encoding for XeTeX
To: XeTeX List <xetex at tug.org>
Message-ID: <0F8FEC08-15A5-11D9-BE49-000A95E49032 at guerilla.net.au>
Content-Type: text/plain; charset="us-ascii"
Hi all
Following up from thoughts I had last night about font selection, I
have put together some files to demonstrate how new font selection can
be made as backwards compatible as possible (as I see it), while still
remaining in the spirit of the LaTeX font selection scheme.
Put the attached bundle of files in a place XeTeX will find it, and try
the following minimal document to get a feel for what it does.
I'd like some comments; is what I've done overkill? I mean, so far
we've just been using the U encoding, but considering we are basing it
around something (XeTeX's hooks into Mac OS X), it seems sensible to
define it all properly.
Anyway, check it out - what do you think?
Regards,
Will
\documentclass{article}
\usepackage[OSX]{fontenc}
\usepackage{palatino}
\begin{document}
This is roman\par
\sffamily this is sans serif\par
\ttfamily this is fixed width
\end{document}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osxenc.zip
Type: application/zip
Size: 8023 bytes
Desc: not available
Url : http://tug.org/pipermail/xetex/attachments/20041004/88dfd66c/osxenc-0001.zip
------------------------------
Message: 2
Date: Mon, 4 Oct 2004 11:49:09 +1000
From: Ross Moore <ross at maths.mq.edu.au>
Subject: [XeTeX] XeTeX fails on dragged PDF images
To: Unicode-based TeX for Mac OS X <xetex at tug.org>
Message-ID: <9570C79A-15A7-11D9-92F7-00039391146A at maths.mq.edu.au>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Hi Jonathan,
Try the following test, using TeXShop and XeTeX.
1. create a new document for XeLaTeX (or open any other to which
we will add some extra LaTeX coding);
ensure you have the preamble line: \usepackage{graphicx}
2. open any existing TeXShop document and go to its PDF display window;
3. with the Cmd+Option keys down (Cmd = Apple), create a selection
rectangle;
4. with the Cmd+Option+Shift keys down, drag the selection to the open
document source from step 1. Some coding gets added, such as:
\includegraphics[]{../../../Library/TeXShop/DraggedImages/
texshop_image.pdf}
5. now "Typeset" with XeLaTeX.
Including the image fails as follows:
! LaTeX Error: Cannot determine size of graphic in
../../../Library/TeXShop/DraggedImages/texshop_image.pdf (no
BoundingBox).
See the LaTeX manual or LaTeX Companion for explanation.
Type H <return> for immediate help.
...
l.54 ...y/TeXShop/DraggedImages/texshop_image.pdf}
?
<../../../Library/TeXShop/DraggedImages/texshop_image.pdf> [1]
The same problem is manifest in a slightly different way using XeTeX
instead of XeLaTeX
-- change the \includegraphics[]{....} command to \XeTeXpdffile{....}.
Now the message is:
! Unable to load picture or PDF file
'{../../../Library/TeXShop/DraggedImages/texshop_image.pdf}'.
<to be read again>
\par
l.52
The problem must be based in XeTeX itself, or XeTeX not liking
something about the PDF used in the texshop_image.pdf ,
since...
a. pdfLaTeX and pdfTeX can include such images;
b. the directory location is not the issue;
c. nor is the _ in the name.
(These are things that I've already checked.)
Would others please verify these results.
Jonathan, do you have any ideas why this doesn't work ?
Cheers,
Ross
------------------------------------------------------------------------
Ross Moore ross at maths.mq.edu.au
Mathematics Department office: E7A-419
Macquarie University tel: +61 +2 9850 8955
Sydney, Australia fax: +61 +2 9850 8114
------------------------------------------------------------------------
------------------------------
Message: 3
Date: Mon, 4 Oct 2004 11:31:03 +0930
From: Will Robertson <will at guerilla.net.au>
Subject: Re: [XeTeX] XeTeX fails on dragged PDF images
To: Unicode-based TeX for Mac OS X <xetex at tug.org>
Message-ID: <3ED8AE88-15A9-11D9-BE49-000A95E49032 at guerilla.net.au>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Hi Ross
I checked your problem just then and experienced the exact same thing
as you, until I changed
\usepackage{graphicx}
to
\usepackage[xetex]{graphics}
Is the implicit behaviour expected?
Will
------------------------------
Message: 4
Date: Mon, 4 Oct 2004 11:36:23 +0930
From: Will Robertson <will at guerilla.net.au>
Subject: Re: [XeTeX] XeTeX fails on dragged PDF images
To: Unicode-based TeX for Mac OS X <xetex at tug.org>
Message-ID: <FD935DCF-15A9-11D9-BE49-000A95E49032 at guerilla.net.au>
Content-Type: text/plain; charset=US-ASCII; format=flowed
On 4 Oct 2004, at 11:31 AM, Will Robertson wrote:
> I checked your problem just then and experienced the exact same thing
> as you, until I changed
> \usepackage{graphicx}
> to
> \usepackage[xetex]{graphics}
I actually meant
\usepackage[xetex]{graphicx}
that second time.
Oops,
W
------------------------------
Message: 5
Date: Mon, 4 Oct 2004 12:24:14 +1000
From: Ross Moore <ross at maths.mq.edu.au>
Subject: Re: [XeTeX] XeTeX fails on dragged PDF images
To: Unicode-based TeX for Mac OS X <xetex at tug.org>
Message-ID: <7BF6B67E-15AC-11D9-92F7-00039391146A at maths.mq.edu.au>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Hi Will,
On 04/10/2004, at 12:06 PM, Will Robertson wrote:
> On 4 Oct 2004, at 11:31 AM, Will Robertson wrote:
>
>> I checked your problem just then and experienced the exact same thing
>> as you, until I changed
>> \usepackage{graphicx}
>> to
>> \usepackage[xetex]{graphics}
>
> I actually meant
> \usepackage[xetex]{graphicx}
> that second time.
OK, the [xetex] option to graphicx was not implicit.
(I'll have to fix my graphics.cfg to make it so!)
But the problem still persists for XeTeX,
using \XeTeXpdffile instead of \includegraphics ...
Oops, no -- it works, when the syntax is correct!
\XeTeXpdffile
"../../../Library/TeXShop/DraggedImages/texshop_image.pdf"
is the correct command, not
\XeTeXpdffile{../../../Library/TeXShop/DraggedImages/texshop_image.pdf}
.
Sorry for the false alarm.
Thanks Will.
Ross
>
> Oops,
> W
>
> _______________________________________________
> XeTeX mailing list
> postmaster at tug.org
> http://tug.org/mailman/listinfo/xetex
>
------------------------------------------------------------------------
Ross Moore ross at maths.mq.edu.au
Mathematics Department office: E7A-419
Macquarie University tel: +61 +2 9850 8955
Sydney, Australia fax: +61 +2 9850 8114
------------------------------------------------------------------------
------------------------------
Message: 6
Date: Mon, 4 Oct 2004 04:04:30 +0200
From: Musa Furber <musaf at runbox.com>
Subject: Re: [XeTeX] I have broken XeTeX
To: Unicode-based TeX for Mac OS X <xetex at tug.org>
Message-ID: <BA23D539-15A9-11D9-96DE-000D9350852C at runbox.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
On 3 Oct 2004, at 19:45, Will Robertson wrote:
> On 4 Oct 2004, at 3:00 AM, Robert Voogdgeert wrote:
>
>>> Segmentation fault
>> Wil,
>>
>> I'm far from a TeXnician, so I don't know whether it's related, but
>> the segmentation fault
>> was a problem Burno and I also expierenced too. There was a thread I
>> think some weeks ago.
>
> Ah yes. Turns out a *restart* is required for Mac OS X to forget about
> fonts that may have been installed. Or at least, it was for my case.
> Sorry for the noise, back to work now.
In some cases, one needs to clear out the font cache after removing the
font. Perhaps OS X startup clears the font cache upon reboot.
When I had this problem a few months back, removing the offending
font(s) and clearing the cache was enough to resolve the segmentation
fault error.
Jonathan: is this in the FAQ?
Regards,
Musa
------------------------------
Message: 7
Date: Mon, 4 Oct 2004 10:08:39 +0200
From: Bruno Voisin <bvoisin at mac.com>
Subject: Re: [XeTeX] Upper Case numbers in Hoefler Text??
To: Unicode-based TeX for Mac OS X <xetex at tug.org>
Message-ID: <99A441A4-15DC-11D9-8774-000A95928A38 at mac.com>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed
Le 4 oct. 04, ? 01:54, christopher ciotti a ?crit :
> I'm new to XeTeX (just a few hours) and I'm having some trouble
> putting together font def files. I wanted to make a few to represent
> the different flavors of Hoefler Text (they are based on an email from
> Bruno Voisin to the TeX on OSX mailing list). When I make a def for
> italic, proportional (or tabular) upper case numbers, I get the
> default old-style figures in everything but regular text (which works
> as expected). Can someone check this out for errors? Thanks in
> advance.
The problem is not with your declarations, but with Apple's shipping of
Hoefler Text: your names for the "Number Case" AAT feature are
consistent, but the ones Apple uses are completely irrational and
inconsistent. It's a bug which I think Jonathan Kew has reported to
Apple.
To get uppercase numbers, and other features, right, I had to open all
four Hoefler Text fonts (regular, black, italic and black italic) in
TextEdit, acces the Typography panel (Cmd-T then click on the scroll
wheel icon at the bottom left of the panel then Typography?), then
tediously find the names for each feature.
> %%%%%%%%%%%%%%
> \DeclareFontFamily{U}{hoeftxt}{}
> \DeclareFontShape{U}{hoeftxt}{m}{n} {<-> "Hoefler\space Text:
> Ligatures=Common\space Ligatures;
> Number\space Spacing=Proportional\space Numbers;
> Number\space Case=Upper\space Case\space Numbers;
> Character\space Alternates=Alternates"}{}
>
> \DeclareFontShape{U}{hoeftxt}{m}{it} {<-> "Hoefler\space Text\space
> Italic:
> Ligatures=Common\space Ligatures;
> Number\space Spacing=Proportional\space Number;
Missing "s" at "Number".
> Numbers\space Case=Upper\space Case\space Numbers;
Should be: "Number\space Case=Uppercase\space Numbers".
> Character\space Alternates=Alternates"}{}
Should be: "Character\space Alternatives=Normal\space Vertical\space
Position" (sic!).
~~
> \DeclareFontShape{U}{hoeftxt}{b}{n} {<-> "Hoefler\space Text\space
> Black:
> Number\space Spacing=Proportional\space Numbers;
> Number\space Case=Upper\space Case\space Numbers;
Should be: "Number\space Case=Diphthong\space Ligatures" (sic!).
> Character\space Alternates=Alternates"}{}
Should be: "Character\space Alternatives=Alternates".
~~
>
> \DeclareFontShape{U}{hoeftxt}{b}{it} {<-> "Hoefler\space Text\space
> Black\space Italic:
> Number\space Spacing=Proportional\space Numbers;
> Number\space Case=Upper\space Case\space Numbers;
Should be: "Number\space Case=Normal\space Vertical\space Position"
(sic!).
> Character\space Alternates=Alternates"}{}
Should be: "Character\space Alternatives=Lower\space Case\space
Numbers" (sic!).
~~
>
> \DeclareFontShape{U}{hoeftxt}{m}{sc} {<-> "Hoefler\space Text:
> Letter\space Case=Small\space Caps;
> Character\space Alternates=Alternates"}{}
>
> \DeclareFontShape{U}{hoeftxt}{b}{sc} {<-> "Hoefler\space Text\space
> Black:
> Letter\space Case=Small\space Caps;
> Character\space Alternates=Alternates"}{}
Should be: "Character\space Alternatives=Alternates".
~~
Sorry, my original post included (I think) the correct declarations,
but I didn't stress enough Apple's bugs and their fixes.
Bruno Voisin
------------------------------
_______________________________________________
XeTeX mailing list
XeTeX at tug.org
http://tug.org/mailman/listinfo/xetex
End of XeTeX Digest, Vol 7, Issue 9
***********************************
------------------------------
_______________________________________________
XeTeX mailing list
XeTeX at tug.org
http://tug.org/mailman/listinfo/xetex
End of XeTeX Digest, Vol 7, Issue 10
************************************
More information about the XeTeX
mailing list