From MacOSX-TeX@email.esm.psu.edu Mon Dec 30 21:50:52 2002
Received: from email.esm.psu.edu ([130.203.247.204]) by engrmail1.engr.psu.edu with Microsoft SMTPSVC(5.0.2195.5329);
Mon, 30 Dec 2002 20:01:56 -0500
Date: Mon, 30 Dec 2002 20:00:01 -0500
Subject: MacOSX-TeX Digest #525 - 12/30/02
From: "TeX on Mac OS X Mailing List"
To: "TeX on Mac OS X Mailing List"
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Sender:
Precedence: Bulk
List-Software: LetterRip Pro 4.0 by LetterRip Software, LLC.
List-Subscribe:
List-Digest:
List-Unsubscribe:
Return-Path: MacOSX-TeX@email.esm.psu.edu
Message-ID:
X-OriginalArrivalTime: 31 Dec 2002 01:01:56.0905 (UTC) FILETIME=[37343190:01C2B068]
MacOSX-TeX Digest #525 - Monday, December 30, 2002
downloading enhanced-carbon-emacs
by
Re: [OS X TeX] downloading enhanced-carbon-emacs
by "Enrico Franconi"
Re: [OS X TeX] downloading enhanced-carbon-emacs
by "Martin Stokhof"
Re: [OS X TeX] downloading enhanced-carbon-emacs
by "Martin Costabel"
format
by "Yves Surrel"
Re: [OS X TeX] format
by "Gerben Wierda"
Using Mac fonts in TeX
by "Gerben Wierda"
Re: [OS X TeX] format
by "Yves Surrel"
Re: [OS X TeX] Using Mac fonts in TeX
by "Adrian Heathcote"
Re: [tex-live] Using Mac fonts in TeX
by "Gerben Wierda"
Re: [OS X TeX] Using Mac fonts in TeX
by "Bruno Voisin"
Re: [OS X TeX] Updates for TeX Programs and TeX Foundation
by "Piet van Oostrum"
Re: [OS X TeX] Re: [tex-live] Using Mac fonts in TeX
by "William Adams"
Re: [OS X TeX] Using Mac fonts in TeX
by "Larry Staton Jr."
Re: [OS X TeX] Using Mac fonts in TeX
by "Bruno Voisin"
Re: [OS X TeX] Using Mac fonts in TeX
by "Piet van Oostrum"
Re: [OS X TeX] Using Mac fonts in TeX
by "William Adams"
Re: [OS X TeX] Using Mac fonts in TeX
by "Larry Staton Jr."
Re: [OS X TeX] Re: [tex-live] Using Mac fonts in TeX
by "Gerben Wierda"
Re: [OS X TeX] Re: [tex-live] Using Mac fonts in TeX
by "Bruno Voisin"
Re: [OS X TeX] Using Mac fonts in TeX
by "Gerben Wierda"
Re: [OS X TeX] Re: [tex-live] Using Mac fonts in TeX
by "William Adams"
Re: [OS X TeX] Using Mac fonts in TeX
by "Bruno Voisin"
Re: [OS X TeX] Re: [tex-live] Using Mac fonts in TeX
by "Gerben Wierda"
Re: [OS X TeX] Re: [tex-live] Using Mac fonts in TeX
by "Bruce D'Arcus"
Error: too many unprocessed floats
by "Edward M. Roche"
Re: [OS X TeX] Error: too many unprocessed floats
by "Piet van Oostrum"
Re: [OS X TeX] Error: too many unprocessed floats
by "Ross Moore"
----------------------------------------------------------------------
Subject: downloading enhanced-carbon-emacs
From:
Date: Mon, 30 Dec 2002 16:00:21 +0900
First, I'd like to thank to everyone in this list who contributes
valuable information on TeX.
I tired to download enhaced-carbon-emacs-2.1.dmg to install it in my
mac(OS X 10.2). When I click it, it is downloaded as a text in my web
browser not as a file. My mouse has no right click button.
I think that it is not a good way to download it as a text.
Would you please tell me how to download it as a file?
Happy new year to every one in this list.
----------------------------------------------------------------------
Subject: Re: [OS X TeX] downloading enhanced-carbon-emacs
From: "Enrico Franconi"
Date: Mon, 30 Dec 2002 09:12:22 +0000
On December 30, haksan@mac.com writes:
> I tried to download enhaced-carbon-emacs-2.1.dmg to install it in my
> mac(OS X 10.2). When I click it, it is downloaded as a text in my
> web browser not as a file. My mouse has no right click button.
To get the contextual menu, right-click and control-click are equivalent.
cheers
-- e.
Enrico Franconi - franconi@inf.unibz.it
Free University of Bozen-Bolzano - http://www.inf.unibz.it/~franconi/
Faculty of Computer Science - Phone: (+39) 0471-315-642
I-39100 Bozen-Bolzano BZ, Italy - Fax: (+39) 0471-315-649
----------------------------------------------------------------------
Subject: Re: [OS X TeX] downloading enhanced-carbon-emacs
From: "Martin Stokhof"
Date: Mon, 30 Dec 2002 10:12:53 +0100
Try holding down the control key while clicking and select "Download
Link Target".
Martin Stokhof
On Monday, December 30, 2002, at 08:00 AM, haksan@mac.com wrote:
> First, I'd like to thank to everyone in this list who contributes
> valuable information on TeX.
>
> I tired to download enhaced-carbon-emacs-2.1.dmg to install it in my
> mac(OS X 10.2). When I click it, it is downloaded as a text in my web
> browser not as a file. My mouse has no right click button.
> I think that it is not a good way to download it as a text.
>
> Would you please tell me how to download it as a file?
>
> Happy new year to every one in this list.
>
>
> -----------------------------------------------------
> Mac TeX info, resources, and news can be found at:
>
> -----------------------------------------------------
> List archives can be found at:
>
> -----------------------------------------------------
> See message headers for list info.
> -----------------------------------------------------
>
>
----------------------------------------------------------------------
Subject: Re: [OS X TeX] downloading enhanced-carbon-emacs
From: "Martin Costabel"
Date: Mon, 30 Dec 2002 10:43:23 +0100
Martin Stokhof wrote:
> Try holding down the control key while clicking and select "Download
> Link Target".
And don't worry if it downloads as text file (at least with Mozilla). It
will be OK.
--
Martin
----------------------------------------------------------------------
Subject: format
From: "Yves Surrel"
Date: Mon, 30 Dec 2002 12:18:25 +0100
--=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D_-1170875389=3D=3D_ma=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
Content-Type: text/plain; charset=3D"iso-8859-1" ; format=3D"flowed"
Content-Transfer-Encoding: quoted-printable
I have a problem about formats with the last GW teTeX distribution
(installed with i-Installer):
=3D46ile to compile:
%&latex
\documentclass[12pt]{article}
\begin{document}
This is a trial
\end{document}
The latex format exists and is found:
% kpsewhich latex.fmt
/usr/local/teTeX/share/texmf.local/web2c/latex.fmt
but tex doesn't take into acount the first line %&latex:
% tex myfile
This is TeX, Version 3.14159 (Web2C 7.3.8)
(./myfile.tex
! Undefined control sequence.
l.2 \documentclass
[12pt]{article}
? x
No pages of output.
Transcript written on myfile.log.
Interactively:
tex
This is TeX, Version 3.14159 (Web2C 7.3.8)
**myfile
(./myfile.tex
! Undefined control sequence.
l.2 \documentclass
[12pt]{article}
?
but (interactively specifying the format):
% tex
This is TeX, Version 3.14159 (Web2C 7.3.8)
**&latex myfile
(./myfile.tex
LaTeX2e <2001/06/01>
=3D2E..etc working OK...
The line "tex -fmt=3D3Dlatex myfile" works, but is exclusive of using the
-ini flag to create other custom formats.
With the fink distribution, I get the right result:
% kpsewhich latex.fmt
/sw/share/texmf.local/web2c/latex.fmt
% tex myfile
This is TeX, Version 3.14159 (Web2C 7.3.1)
(myfile.tex
LaTeX2e <1999/12/01> patch level 1
=3D2E..etc working OK...
What is wrong?
--
Yves Surrel
Professeur, chaire d'instrumentation (chair of instrumentation)
Conservatoire national des arts et m=3DE9tiers (CNAM)
Institut national de m=3DE9trologie (BNM-INM)
292, rue St-Martin
75141 Paris Cedex 03 - France
tel +33 (0)1 40 27 22 59
fax +33 (0)1 40 27 23 27
http://www.cnam.fr/instituts/inm
http://www.cnam.fr/instrumesure
--=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D_-1170875389=3D=3D_ma=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
Content-Type: text/html; charset=3D"iso-8859-1"
Content-Transfer-Encoding: quoted-printable
format
I have a problem about formats with the last GW teTeX
distribution (installed with i-Installer):
File to compile:
%&latex
\documentclass[12pt]{article}
\begin{document}
This is a trial
\end{document}
The latex format exists and is found:
% kpsewhich latex.fmt
/usr/local/teTeX/share/texmf.local/web2c/latex.fmt
but tex doesn't take into acount the first line
%&latex:
% tex myfile
This is TeX, Version 3.14159 (Web2C 7.3.8)
(./myfile.tex
! Undefined control sequence.
l.2 \documentclass
[12pt]{article}
? x
No pages of output.
Transcript written on myfile.log.
Interactively:
tex
This is TeX, Version 3.14159 (Web2C 7.3.8)
**myfile
(./myfile.tex
! Undefined control sequence.
l.2 \documentclass
[12pt]{article}
?
but (interactively specifying the format):
% tex
This is TeX, Version 3.14159 (Web2C 7.3.8)
**&latex myfile
(./myfile.tex
LaTeX2e <2001/06/01>
...etc working OK...
The line "tex -fmt=3D3Dlatex myfile" works, but is
exclusive of using the -ini flag to create other custom formats.
With the fink distribution, I get the right result:
% kpsewhich latex.fmt
/sw/share/texmf.local/web2c/latex.fmt
% tex myfile
This is TeX, Version 3.14159 (Web2C 7.3.1)
(myfile.tex
LaTeX2e <1999/12/01> patch level 1
...etc working OK...
What is wrong?
--
Yves Surrel
Professeur, chaire d'instrumentation (chair of instrumentation)
Conservatoire national des arts et m=3DE9tiers (CNAM)
Institut national de m=3DE9trologie (BNM-INM)
292, rue St-Martin
75141 Paris Cedex 03 - France
tel +33 (0)1 40 27 22 59
fax +33 (0)1 40 27 23 27
http://www.cnam.fr/instituts/inm
http://www.cnam.fr/instrumesure
--=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D_-1170875389=3D=3D_ma=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D--
----------------------------------------------------------------------
Subject: Re: [OS X TeX] format
From: "Gerben Wierda"
Date: Mon, 30 Dec 2002 12:57:34 +0100
On Monday, Dec 30, 2002, at 12:18 Europe/Amsterdam, Yves Surrel wrote:
> What is wrong?
I recall that the whole %-stuff in Web2C has changed recently because
it was in conflict with the official standard and gave problems in
various circumstances. The Fink version of TeX is pretty old (Web2C
7.3.1) and your version is newer.
There is a new variable in texmf.cnf that sets this behaviour:
parse_first_line. It is default set to false, but you can add a line
parse_first_line =3D t
in /usr/local/teTeX/texmf.cnf to get the original (faulty) behaviour).
G
----------------------------------------------------------------------
Subject: Using Mac fonts in TeX
From: "Gerben Wierda"
Date: Mon, 30 Dec 2002 12:58:40 +0100
From: Gerben Wierda
Date: Mon Dec 30, 2002 12:46:47 Europe/Amsterdam
To: macosx-tex@email.esm.psu.edu (TeX on Mac OS X Mailing List)
Cc: texlive@tug.org, pdftex@tug.org
Subject: Using Mac fonts in TeX
I am preparing an i-Installer i-package that will detect Mac fonts on
your system and convert them for use with TeX. I have some trouble
getting this to work. I have a map file:
% [BEG ] -- Created by ttf2tex v0.6 on 2002-12-30 00:20:20
mgsl16t GillSans-Light
Date: Mon, 30 Dec 2002 13:18:57 +0100
>On Monday, Dec 30, 2002, at 12:18 Europe/Amsterdam, Yves Surrel wrote:
>
>>What is wrong?
>
>I recall that the whole %-stuff in Web2C has changed recently
>because it was in conflict with the official standard and gave
>problems in various circumstances. The Fink version of TeX is pretty
>old (Web2C 7.3.1) and your version is newer.
>
>There is a new variable in texmf.cnf that sets this behaviour:
>parse_first_line. It is default set to false, but you can add a line
>
> parse_first_line =3D t
>
>in /usr/local/teTeX/texmf.cnf to get the original (faulty) behaviour).
>
>G
>
Thank you very much for the answer.
If this behaviour is faulty, what should be the right one to obtain
the same result, in particular to have both initex and an existing
format?
--
Yves Surrel
Professeur, chaire d'instrumentation (chair of instrumentation)
Conservatoire national des arts et m=E9tiers (CNAM)
Institut national de m=E9trologie (BNM-INM)
292, rue St-Martin
75141 Paris Cedex 03 - France
tel +33 (0)1 40 27 22 59
fax +33 (0)1 40 27 23 27
http://www.cnam.fr/instituts/inm
http://www.cnam.fr/instrumesure
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Using Mac fonts in TeX
From: "Adrian Heathcote"
Date: Mon, 30 Dec 2002 23:32:17 +1100
Gerben
There is a map file and a sty file but this
>
>
> LaTeX Font Warning: Font shape `OT1/mgs/m/n' undefined
> (Font) using `OT1/cmr/m/n' instead on input line 20.
may be because there is no .fd file. When the .fd file is missing or
inaccurate this is the kind of error message I've got. The .fd file
needs to be in the same directory as the .sty file.
Adrian Heathcote
----------------------------------------------------------------------
Subject: Re: [tex-live] Using Mac fonts in TeX
From: "Gerben Wierda"
Date: Mon, 30 Dec 2002 13:37:46 +0100
On Monday, Dec 30, 2002, at 13:10 Europe/Amsterdam, Vladimir Volovich
wrote:
> "GW" =3D=3D Gerben Wierda writes:
>
> GW> I have created a file gillsans.sty:
>
> GW> \def\fileversion{1} \def\filedate{2002/12/30}
> GW> \ProvidesPackage{gillsans}[\filedate\space\fileversion \space
> GW> PSNFSS LaTeX2e package loading Gill Sans]
> GW> \renewcommand{\sfdefault}{mgs} \endinput
>
> GW> But when I try \usepackage{gillsans} and \textsf{Some text} I get
>
> GW> LaTeX Font Warning: Font shape `OT1/mgs/m/n' undefined (Font)
> GW> using `OT1/cmr/m/n' instead on input line 20.
>
> GW> which clearly is what I do not want. I am able to produce a
> GW> testfont page for GillSans by choosing font mgsr16t, so it seems
> GW> that my gillsans.sty is in error. Can someone in the know about
> GW> TeX and fonts clear this up for me?
>
> you need to create FD files, e.g. t1mgs.fd and ot1mgs.fd which will
> make the fonts known to latex.
These are available.
> also note that you described the fonts
> in the map file as having T1 encoding, while you tried to use them in
> your latex file in OT1 encoding. so either you have to create
> (virtual) fonts for OT1 encoding too, or use the fonts only with
> \usepackage[T1]{fontenc}
This worked.
How does one create these virtual fonts?
G
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Using Mac fonts in TeX
From: "Bruno Voisin"
Date: Mon, 30 Dec 2002 13:37:22 +0100
Le lundi, 30 d=E9c 2002, =E0 12:58 Europe/Paris, Gerben Wierda a =E9crit =
:
> I am preparing an i-Installer i-package that will detect Mac fonts on=20=
> your system and convert them for use with TeX. I have some trouble=20
> getting this to work. I have a map file:
This is a great idea. I think that's what most long-term Mac users of=20
TeX are missing with TeX on Mac OS X. This would also be a great=20
breakthrough in making TeX recognized as a word processing "option" on=20=
the Mac platform, for those coming from the desktop publishing and=20
WYSYWYG worlds.
> This map file has been added to the And I have created a file=20
> gillsans.sty:
>
> \def\fileversion{1}
> \def\filedate{2002/12/30}
> \ProvidesPackage{gillsans}[\filedate\space\fileversion
> \space PSNFSS LaTeX2e package loading Gill Sans]
> \renewcommand{\sfdefault}{mgs}
> \endinput
>
> But when I try \usepackage{gillsans} and \textsf{Some text} I get
>
> LaTeX Font Warning: Font shape `OT1/mgs/m/n' undefined
> (Font) using `OT1/cmr/m/n' instead on input line 20.
>
> which clearly is what I do not want. I am able to produce a testfont=20=
> page for GillSans by choosing font mgsr16t, so it seems that my=20
> gillsans.sty is in error. Can someone in the know about TeX and fonts=20=
> clear this up for me?
I'm rather confused. It looks like the .fd file (normally ot1mgs.fd)=20
called for by your gillsans.sty does not define the OT1/mgs/m/n=20
declination, or defines it to be substituted by OT1/cmr/m/n.
On CTAN I saw two sets of files for GillSans fonts:
- One for Adobe Gill Sans, with gillsans.sty saying
\ProvidesPackage{gillsans}[1998/07/06:
PSNFSS v.2 LaTeX package loading adobe GillSans. S. Rahtz]
\renewcommand{\sfdefault}{pgs}
\endinput
and ot1pgs.fd saying
%Filename: ot1pgs.fd
%Created by: tex Fam_4466
%Created using fontinst v1.800
%THIS FILE SHOULD BE PUT IN A TEX INPUTS DIRECTORY
\ProvidesFile{ot1pgs.fd}
[1998/07/06 Fontinst v1.800 font definitions for OT1/pgs.]
\DeclareFontFamily{OT1}{pgs}{}
\DeclareFontShape{OT1}{pgs}{m}{n}{
<-> pgsr7t
}{}
- The other for Monotype Gill Sans saying
\ProvidesPackage{gillsans}[1998/07/06:
PSNFSS v.2 LaTeX package loading monotype GillSans. S. Rahtz]
\renewcommand{\sfdefault}{mgs}
\endinput
and ot1mgs.fd saying
%Filename: ot1mgs.fd
%Created by: tex Fam_19196
%Created using fontinst v1.800
%THIS FILE SHOULD BE PUT IN A TEX INPUTS DIRECTORY
\ProvidesFile{ot1mgs.fd}
[1998/07/06 Fontinst v1.800 font definitions for OT1/mgs.]
\DeclareFontFamily{OT1}{mgs}{}
\DeclareFontShape{OT1}{mgs}{m}{n}{
<-> mgsr7t
}{}
Did you use any of these? Or did you use fontinst to create new ones?=20
Or is ttf2tex (I don't know what this is) creating these files as part=20=
of an automated process?
Bruno=
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Updates for TeX Programs and TeX Foundation
From: "Piet van Oostrum"
Date: 30 Dec 2002 14:44:14 +0100
>>>>> Gerben Wierda (GW) writes:
GW> Both TeX Programs (Experimental) and TeX Foundation i-Packages have =
been
GW> updated. TeX Foundation is now based on teTeX 2002/12/25 and TeX =
Programs
GW> (Experimental) is based on TeX Live development @ 2002/12/27. These
GW> releases are release candidates for a definitive release somewhere in =
the
GW> coming weeks, so I would like to hear some test results.
This now works on Mac OSX 10.1.5. But I haven't used it heavily.
--
Piet van Oostrum
URL: http://www.cs.uu.nl/~piet [PGP]
Private email: P.van.Oostrum@hccnet.nl
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Re: [tex-live] Using Mac fonts in TeX
From: "William Adams"
Date: Mon, 30 Dec 2002 09:14:26 -0500
Bruno had said:
>>also note that you described the fonts
>>in the map file as having T1 encoding, while you tried to use them in
>>your latex file in OT1 encoding. so either you have to create
>>(virtual) fonts for OT1 encoding too, or use the fonts only with
>>\usepackage[T1]{fontenc}
and Gerben replied:
>This worked.
>How does one create these virtual fonts?
Fontinst, or the appropriate invocation of afm2tfm (there's a switch,
``-v'' to make a vpl which can then be converted to a .vf using
vptovf)
William
--
William Adams, publishing specialist
voice - 717-731-6707 | Fax - 717-731-6708
www.atlis.com
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Using Mac fonts in TeX
From: "Larry Staton Jr."
Date: Mon, 30 Dec 2002 09:18:37 -0500
Yes! I am a legal professional recently introduced to TeX. WordPerfect
and Word just don't cut it for lengthy pleadings. The only drawback is
that I like to use Century Schoolbook for my pleadings and I am
struggling to get it to work. Any work on getting fonts to work
seamlessly in TeX would be greatly appreciated.
On Monday, Dec 30, 2002, at 07:37 US/Eastern, Bruno Voisin wrote:
> I think that's what most long-term Mac users of TeX are missing with
> TeX on Mac OS X. This would also be a great breakthrough in making TeX
> recognized as a word processing "option" on the Mac platform, for
> those coming from the desktop publishing and WYSYWYG worlds.
>
--
Larry Staton Jr.
E-mail/iChat: statonjr@mac.com
AIM: lstatonjr
Brought to you by Mail on Mac OS X
Public PGP Key available upon request
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Using Mac fonts in TeX
From: "Bruno Voisin"
Date: Mon, 30 Dec 2002 15:35:42 +0100
Le lundi, 30 d=E9c 2002, =E0 15:18 Europe/Paris, Larry Staton Jr. a =
=E9crit :
> Yes! I am a legal professional recently introduced to TeX. WordPerfect=20=
> and Word just don't cut it for lengthy pleadings. The only drawback is=20=
> that I like to use Century Schoolbook for my pleadings and I am=20
> struggling to get it to work. Any work on getting fonts to work=20
> seamlessly in TeX would be greatly appreciated.
As regards New Century Schoolbook: it should work straight out of the=20
box, in LaTeX. Putting
\usepackage{newcent}
at the beginning of your document should switch to New Century=20
Schoolbook as the serif font, Avant Garde as the sans serif font and=20
Courier as the monospaced font. Should work in TeXShop + teTeX=20
normally, and I think it used to work also in Textures. See=20
/Library/teTeX/share/texmf/doc/latex/psnfss/psnfss2e.pdf in case you're=20=
using teTeX.
Hope this helps,
Bruno Voisin
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Using Mac fonts in TeX
From: "Piet van Oostrum"
Date: 30 Dec 2002 15:52:45 +0100
>>>>> "Larry Staton Jr." (LS) writes:
LS> Yes! I am a legal professional recently introduced to TeX. WordPerfect =
and
LS> Word just don't cut it for lengthy pleadings. The only drawback is =
that I
LS> like to use Century Schoolbook for my pleadings and I am struggling to =
get
LS> it to work. Any work on getting fonts to work seamlessly in TeX would =
be
LS> greatly appreciated.
For New Century Schoolbook this is easy:
\renewcommand{\rmdefault}{pnc}
But you are right: in general in can be a pain.
--
Piet van Oostrum
URL: http://www.cs.uu.nl/~piet [PGP]
Private email: P.van.Oostrum@hccnet.nl
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Using Mac fonts in TeX
From: "William Adams"
Date: Mon, 30 Dec 2002 10:16:44 -0500
Larry Staton Jr. said:
>Yes! I am a legal professional recently introduced to TeX.
>WordPerfect and Word just don't cut it for lengthy pleadings.
>The only drawback is that I like to use Century Schoolbook
>for my pleadings and I am struggling to get it to work.
>Any work on getting fonts to work seamlessly in TeX
>would be greatly appreciated.
RTFM.
/texmf/doc/latex/base/fntguide.dvi mentions nfss in Section 1.1
Unfortunately, /texmf/doc/tex-inputs where the nfss docs should be
seems to be missing from my tex-distribution.... Gerben?
Anyway, New Century Schoolbook is one of the core, LaserWriter ``gang
of 35''
Here's a minimal example of how to do this.
\documentclass{article}
\usepackage{newcent}
\begin{document}
This is in New Century Schoolbook.
\end{document}
You can also use the ``ncs'' style option for some packages I believe.
William
--
William Adams, publishing specialist
voice - 717-731-6707 | Fax - 717-731-6708
www.atlis.com
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Using Mac fonts in TeX
From: "Larry Staton Jr."
Date: Mon, 30 Dec 2002 10:21:44 -0500
Brilliant! Thank you very much.
Of course, with all the recent talk of ConTeXt on this list, I've been
investigating ConTeXt and learning fonts in ConTeXt is just too much
right now.
Thanks again.
On Monday, Dec 30, 2002, at 09:35 US/Eastern, Bruno Voisin wrote:
> As regards New Century Schoolbook: it should work straight out of the
> box, in LaTeX. Putting
>
> \usepackage{newcent}
--
Larry Staton Jr.
E-mail/iChat: statonjr@mac.com
AIM: lstatonjr
Brought to you by Mail on Mac OS X
Public PGP Key available upon request
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Re: [tex-live] Using Mac fonts in TeX
From: "Gerben Wierda"
Date: Mon, 30 Dec 2002 16:44:50 +0100
On Monday, Dec 30, 2002, at 15:14 Europe/Amsterdam, William Adams wrote:
> Fontinst, or the appropriate invocation of afm2tfm (there's a switch,
> ``-v'' to make a vpl which can then be converted to a .vf using > =
vptovf)
Everybody is really helpful, but I do not understand generic
instructions like these. I have .ttf fonts, how does afm2tfm or
fontinst help?
G
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Re: [tex-live] Using Mac fonts in TeX
From: "Bruno Voisin"
Date: Mon, 30 Dec 2002 17:02:17 +0100
Le lundi, 30 d=E9c 2002, =E0 16:44 Europe/Paris, Gerben Wierda a =E9crit =
:
> On Monday, Dec 30, 2002, at 15:14 Europe/Amsterdam, William Adams=20
> wrote:
>
>> Fontinst, or the appropriate invocation of afm2tfm (there's a switch,=20=
>> ``-v'' to make a vpl which can then be converted to a .vf using >=20
>> vptovf)
>
> Everybody is really helpful, but I do not understand generic=20
> instructions like these. I have .ttf fonts, how does afm2tfm or=20
> fontinst help?
This is all for PostScript fonts, you're right: fontinst (a collection=20=
of TeX files) and afm2tfm (a binary executable) create the TFM, VF, STY=20=
and FD files necessary for using a given PostScript font with TeX,=20
given the AFM files accompanying this font. There might be similar=20
utilities for TTF fonts, but it's beyond my present knowledge.
I think the support files for the MarVoSym font were created this way:=20=
somebody converted the original TTF font to PFB format, Y&Y added hand=20=
hinting (and donated it to the community), and the LaTeX support files=20=
were created from there.
Bruno Voisin=
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Using Mac fonts in TeX
From: "Gerben Wierda"
Date: Mon, 30 Dec 2002 17:07:24 +0100
On Monday, Dec 30, 2002, at 13:37 Europe/Amsterdam, Bruno Voisin wrote:
> Le lundi, 30 d=E9c 2002, =E0 12:58 Europe/Paris, Gerben Wierda a =E9crit=
:
>
>> I am preparing an i-Installer i-package that will detect Mac fonts on =
=20
>> your system and convert them for use with TeX. I have some trouble =20=
>> getting this to work. I have a map file:
>
> This is a great idea. I think that's what most long-term Mac users of =20=
> TeX are missing with TeX on Mac OS X. This would also be a great =20
> breakthrough in making TeX recognized as a word processing "option" on =
=20
> the Mac platform, for those coming from the desktop publishing and =20
> WYSYWYG worlds.
>
>> This map file has been added to the And I have created a file =20
>> gillsans.sty:
>>
>> \def\fileversion{1}
>> \def\filedate{2002/12/30}
>> \ProvidesPackage{gillsans}[\filedate\space\fileversion
>> \space PSNFSS LaTeX2e package loading Gill Sans]
>> \renewcommand{\sfdefault}{mgs}
>> \endinput
>>
>> But when I try \usepackage{gillsans} and \textsf{Some text} I get
>>
>> LaTeX Font Warning: Font shape `OT1/mgs/m/n' undefined
>> (Font) using `OT1/cmr/m/n' instead on input line 20.
>>
>> which clearly is what I do not want. I am able to produce a testfont =20=
>> page for GillSans by choosing font mgsr16t, so it seems that my =20
>> gillsans.sty is in error. Can someone in the know about TeX and fonts =
=20
>> clear this up for me?
>
> I'm rather confused. It looks like the .fd file (normally ot1mgs.fd) =20=
> called for by your gillsans.sty does not define the OT1/mgs/m/n =20
> declination, or defines it to be substituted by OT1/cmr/m/n.
>
> On CTAN I saw two sets of files for GillSans fonts:
>
> - One for Adobe Gill Sans, with gillsans.sty saying
>
> \ProvidesPackage{gillsans}[1998/07/06:
> PSNFSS v.2 LaTeX package loading adobe GillSans. S. Rahtz]
> \renewcommand{\sfdefault}{pgs}
> \endinput
>
> and ot1pgs.fd saying
>
> %Filename: ot1pgs.fd
> %Created by: tex Fam_4466
> %Created using fontinst v1.800
>
> %THIS FILE SHOULD BE PUT IN A TEX INPUTS DIRECTORY
>
> \ProvidesFile{ot1pgs.fd}
> [1998/07/06 Fontinst v1.800 font definitions for OT1/pgs.]
>
> \DeclareFontFamily{OT1}{pgs}{}
>
> \DeclareFontShape{OT1}{pgs}{m}{n}{
> <-> pgsr7t
> }{}
>
> - The other for Monotype Gill Sans saying
>
> \ProvidesPackage{gillsans}[1998/07/06:
> PSNFSS v.2 LaTeX package loading monotype GillSans. S. Rahtz]
> \renewcommand{\sfdefault}{mgs}
> \endinput
>
> and ot1mgs.fd saying
>
> %Filename: ot1mgs.fd
> %Created by: tex Fam_19196
> %Created using fontinst v1.800
>
> %THIS FILE SHOULD BE PUT IN A TEX INPUTS DIRECTORY
>
> \ProvidesFile{ot1mgs.fd}
> [1998/07/06 Fontinst v1.800 font definitions for OT1/mgs.]
>
> \DeclareFontFamily{OT1}{mgs}{}
>
> \DeclareFontShape{OT1}{mgs}{m}{n}{
> <-> mgsr7t
> }{}
>
> Did you use any of these? Or did you use fontinst to create new ones? =20=
> Or is ttf2tex (I don't know what this is) creating these files as part =
=20
> of an automated process?
Actually, I do not understand more than 10% of the entire font business =20=
and I do not have the time to learn it all. But what I did was run =20
ttf2tex, which created and installed the map file (in a wrong location, =20=
but I am going to fix that), installed .fd files for T1 and TS1 =20
encoding. So I did not use any of these. I did notice that my stuff =20
works with T1 encoding turned on.
This whole font business is too complicated and I cannot spare the time =20=
to really get fluent in this. I want to support the use of the Mac =20
fonts but for that I do need support from people who can tell me =20
*exactly* what needs to be done.
ttf2tex installs for GillSans:
/usr/local/teTeX/share/texmf.local/fonts/afm/monotype/gillsans
/usr/local/teTeX/share/texmf.local/fonts/afm/monotype/gillsans/=20
mgsb16.afm
/usr/local/teTeX/share/texmf.local/fonts/afm/monotype/gillsans/=20
mgsbi16.afm
/usr/local/teTeX/share/texmf.local/fonts/afm/monotype/gillsans/=20
mgsl16.afm
/usr/local/teTeX/share/texmf.local/fonts/afm/monotype/gillsans/=20
mgsli16.afm
/usr/local/teTeX/share/texmf.local/fonts/afm/monotype/gillsans/=20
mgsr16.afm
/usr/local/teTeX/share/texmf.local/fonts/afm/monotype/gillsans/=20
mgsri16.afm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsb16c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsb16t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsb8c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsb8t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsbc8c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsbc8t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsbi16c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsbi16t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsbi8c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsbi8t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsbo16c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsbo16t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsbo8c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsbo8t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsl16c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsl16t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsl8c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsl8t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgslc8c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgslc8t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsli16c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsli16t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsli8c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsli8t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgslo16c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgslo16t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgslo8c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgslo8t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsr16c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsr16t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsr8c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsr8t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsrc8c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsrc8t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsri16c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsri16t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsri8c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsri8t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsro16c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsro16t.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsro8c.tfm
/usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
mgsro8t.tfm
/usr/local/teTeX/share/texmf.local/fonts/truetype/monotype/gillsans
/usr/local/teTeX/share/texmf.local/fonts/truetype/monotype/gillsans/=20
mgsb16.ttf
/usr/local/teTeX/share/texmf.local/fonts/truetype/monotype/gillsans/=20
mgsbi16.ttf
/usr/local/teTeX/share/texmf.local/fonts/truetype/monotype/gillsans/=20
mgsl16.ttf
/usr/local/teTeX/share/texmf.local/fonts/truetype/monotype/gillsans/=20
mgsli16.ttf
/usr/local/teTeX/share/texmf.local/fonts/truetype/monotype/gillsans/=20
mgsr16.ttf
/usr/local/teTeX/share/texmf.local/fonts/truetype/monotype/gillsans/=20
mgsri16.ttf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsb8c.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsb8t.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsbc8c.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsbc8t.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsbi8c.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsbi8t.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsbo8c.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsbo8t.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsl8c.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsl8t.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgslc8c.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgslc8t.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsli8c.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsli8t.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgslo8c.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgslo8t.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsr8c.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsr8t.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsrc8c.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsrc8t.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsri8c.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsri8t.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsro8c.vf
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsro8t.vf
so everything seems to be there.
> and ot1mgs.fd saying
>
> %Filename: ot1mgs.fd
> %Created by: tex Fam_19196
> %Created using fontinst v1.800
>
> %THIS FILE SHOULD BE PUT IN A TEX INPUTS DIRECTORY
>
> \ProvidesFile{ot1mgs.fd}
> [1998/07/06 Fontinst v1.800 font definitions for OT1/mgs.]
>
> \DeclareFontFamily{OT1}{mgs}{}
>
> \DeclareFontShape{OT1}{mgs}{m}{n}{
> <-> mgsr7t
> }{}
I copied this to my test dir and after I changed mgsr7t to mgsr16t or =20=
mgsr8t I can typeset with pdflatex with normal OT1 encoding active. Not =20=
that I have an inklinkg of what I am doing. There is no OT1 support in =20=
ttf2tex, it seems.
G
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Re: [tex-live] Using Mac fonts in TeX
From: "William Adams"
Date: Mon, 30 Dec 2002 11:10:06 -0500
Gerben had said:
>>Everybody is really helpful, but I do not understand generic
>>instructions like these. I have .ttf fonts, how does afm2tfm
>>or fontinst help?
and Bruno replied:
>This is all for PostScript fonts, you're right: fontinst
>(a collection of TeX files) and afm2tfm (a binary executable)
>create the TFM, VF, STY and FD files necessary for using a
>given PostScript font with TeX, given the AFM files accompanying
>this font. There might be similar utilities for TTF fonts,
>but it's beyond my present knowledge.
My apologies, I'd thought it'd've been obvious to use ttf2afm
in addition to afm2tfm
William
--
William Adams, publishing specialist
voice - 717-731-6707 | Fax - 717-731-6708
www.atlis.com
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Using Mac fonts in TeX
From: "Bruno Voisin"
Date: Mon, 30 Dec 2002 18:22:46 +0100
Le lundi, 30 d=E9c 2002, =E0 17:07 Europe/Paris, Gerben Wierda a =E9crit =
:
> Actually, I do not understand more than 10% of the entire font =20
> business and I do not have the time to learn it all. But what I did =20=
> was run ttf2tex, which created and installed the map file (in a wrong =20=
> location, but I am going to fix that), installed .fd files for T1 and =20=
> TS1 encoding. So I did not use any of these. I did notice that my =20
> stuff works with T1 encoding turned on.
>
> This whole font business is too complicated and I cannot spare the =20
> time to really get fluent in this. I want to support the use of the =20=
> Mac fonts but for that I do need support from people who can tell me =20=
> *exactly* what needs to be done.
For PS fonts, the "CTAN" LaTeX mechanism works as follows (using Adobe =20=
Gill Sans as an exemple):
- The STY file tells that the sans-serif font is pgs. At this stage pgs =20=
is just a name, a "logical" font, an "abstract" concept, which is not =20=
yet associated with any TFM (metric) or PFB (outline) file.
- The FD files defines the association of this font with TFM files. For =20=
example it tells that the font pgs in OT1 encoding/medium =20
series/upright shape, that is OT1/pgs/m/n, corresponds to the TFM file =20=
pgsr7t.tfm.
- The TFM and VF files are the trickiest part of the business:
pgsr8r.tfm is the "raw" metric file, in 8R or TeXBase1 encoding;
pgsr7t.tfm is the OT1 form of the above, re-mapped from 8R using the VF =20=
file pgsr7t.vf;
pgsr8t.tfm is the T1 form of the above, re-mapped from 8R using the VF =20=
file pgsr8t.vf.
There are many variants, such as files ending in 8c which are fake =20
small caps variants obtained by PS trickery etc. TS1 encoding =20
corresponds to the text companion fonts complementing T1 encoding.
- The MAP file defines the association of the 8R TFM file with the =20
actual PFB or PFA font. For example the line
pgsr8r GillSans "TeXBase1Encoding ReEncodeFont " <8r.enc ttf2tex installs for GillSans:
>
> /usr/local/teTeX/share/texmf.local/fonts/afm/monotype/gillsans
> /usr/local/teTeX/share/texmf.local/fonts/afm/monotype/gillsans/=20
> mgsb16.afm
> /usr/local/teTeX/share/texmf.local/fonts/afm/monotype/gillsans/=20
> mgsbi16.afm
> [snip]
> /usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans
> /usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
> mgsb16c.tfm
> /usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
> mgsb16t.tfm
> /usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
> mgsb8c.tfm
> /usr/local/teTeX/share/texmf.local/fonts/tfm/monotype/gillsans/=20
> mgsb8t.tfm
> [snip]
> /usr/local/teTeX/share/texmf.local/fonts/truetype/monotype/gillsans
> /usr/local/teTeX/share/texmf.local/fonts/truetype/monotype/gillsans/=20=
> mgsb16.ttf
> /usr/local/teTeX/share/texmf.local/fonts/truetype/monotype/gillsans/=20=
> mgsbi16.ttf
> [snip]
> /usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans
> =
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsb8c.vf
> =
/usr/local/teTeX/share/texmf.local/fonts/vf/monotype/gillsans/mgsb8t.vf
>
> [snip]
>
> I copied this to my test dir and after I changed mgsr7t to mgsr16t or =20=
> mgsr8t I can typeset with pdflatex with normal OT1 encoding active. =20=
> Not that I have an inklinkg of what I am doing. There is no OT1 =20
> support in ttf2tex, it seems.
I'm fairly lost in all these font tools, afmtotfm, afm2tfm, freetype, =20=
pfaedit, ttf2tex etc. =46rom the above it seems that ttf2tex manipulates =
=20
not only 8-bit but also 16-bit (Unicode?) fonts. If that's the case, =20
then I don't know to what extent the concepts described earlier apply =20=
to these fonts.
Bruno Voisin
PS Something I did not mention: afm2tfm, I think, from the dvips =20
distribution, creates directly TFM and VF files from an AFM file; =20
fontinst manipulates only ASCII files, and thus it creates PL and VPL =20=
files to be then converted to their binary TFM and VF forms using =20
pltotf and vptovf.
Hope this helps,
Bruno=
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Re: [tex-live] Using Mac fonts in TeX
From: "Gerben Wierda"
Date: Mon, 30 Dec 2002 19:06:26 +0100
On Monday, Dec 30, 2002, at 17:10 Europe/Amsterdam, William Adams wrote:
> My apologies, I'd thought it'd've been obvious to use ttf2afm
> in addition to afm2tfm
As things stand now, it seems ttf2tex does almost everything I need,
except:
- provide .sty files
- provide for OT1 encoding
what Bruno posted was a very simple .fd file (only for Gill Sans
regular). But I just found out that I do not need a sty file at all. I
can just say
\begin{document}
\fontencoding{T1}\fontfamily{mgs}\selectfont
and I get everything (except math of course) in GillSans
G
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Re: [tex-live] Using Mac fonts in TeX
From: "Bruce D'Arcus"
Date: Mon, 30 Dec 2002 10:16:29 -0800
In the sty file I use I specify the T1 encoding, which is missing in the
one you posted.
On Mon, 30 Dec 2002 19:06:26 +0100, "Gerben Wierda"
said:
> On Monday, Dec 30, 2002, at 17:10 Europe/Amsterdam, William Adams wrote:
>
> > My apologies, I'd thought it'd've been obvious to use ttf2afm
> > in addition to afm2tfm
>
> As things stand now, it seems ttf2tex does almost everything I need,
> except:
>
> - provide .sty files
> - provide for OT1 encoding
>
> what Bruno posted was a very simple .fd file (only for Gill Sans
> regular). But I just found out that I do not need a sty file at all. I
> can just say
>
> \begin{document}
> \fontencoding{T1}\fontfamily{mgs}\selectfont
>
> and I get everything (except math of course) in GillSans
>
> G
>
>
> -----------------------------------------------------
> Mac TeX info, resources, and news can be found at:
>
> -----------------------------------------------------
> List archives can be found at:
>
> -----------------------------------------------------
> See message headers for list info.
> -----------------------------------------------------
>
>
--
http://fastmail.fm - A fast, anti-spam email service.
----------------------------------------------------------------------
Subject: Error: too many unprocessed floats
From: "Edward M. Roche"
Date: Mon, 30 Dec 2002 14:40:13 -0500
Hi. I'm working on a document and after months of work, it now is giving
the ``too many unprocessed floats'' error. I changed the type size to 10
from 12 points, and it is OK,but I'm wondering if anyone has any
practical advice on how to deal with this problem? Is it caused by too
many tables too close together? Note: Most of them have the [h] variable
after the \table entry.
Would appreciate some advice.
Thanks and happy holidays to everyone.
Ed Roche
Manhattan
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Error: too many unprocessed floats
From: "Piet van Oostrum"
Date: 30 Dec 2002 21:32:44 +0100
>>>>> "Edward M. Roche" (EMR) writes:
EMR> Hi. I'm working on a document and after months of work, it now is =
giving
EMR> the ``too many unprocessed floats'' error. I changed the type size to =
10
EMR> from 12 points, and it is OK,but I'm wondering if anyone has any =
practical
EMR> advice on how to deal with this problem? Is it caused by too many =
tables
EMR> too close together? Note: Most of them have the [h] variable after =
the
EMR> \table entry.
I hope you mean: after \begin{table}
You should never use [h], as this gives latex no possibility to do
something sensible if it doesn't fit. At least also include a p, i.e. =
[hp].
If that doesn't help look in
http://www.cs.uu.nl/~piet/floats
--
Piet van Oostrum
URL: http://www.cs.uu.nl/~piet [PGP]
Private email: P.van.Oostrum@hccnet.nl
----------------------------------------------------------------------
Subject: Re: [OS X TeX] Error: too many unprocessed floats
From: "Ross Moore"
Date: Tue, 31 Dec 2002 08:10:51 +1100 (EST)
Hello Ed,
> Hi. I'm working on a document and after months of work, it now is giving =
> the ``too many unprocessed floats'' error. I changed the type size to 10 =
> from 12 points, and it is OK,but I'm wondering if anyone has any
> practical advice on how to deal with this problem? Is it caused by too
> many tables too close together?
Either too many tables, or too many figures, or too many of both.
TeX is trying to solve an optimisation problem on where to place
the tigures and tables, but not leave too much white space on pages,
nor overfill pages.
There are parameters which affect how much room is allowed between
floats and the surrounding text, and what percentage of a page is
required to be text. These rules can make it very hard to discover
decent solutions to the layout problem, when no really good solution
exists.
> ... Note: Most of them have the [h] variable
> after the \table entry.
> Would appreciate some advice.
Using [!h] often works well, since the ! means that some of
the more delicate constraints can be ignored, hence more possible
solutions are considered to be acceptable.
Using [!hp] is a lot more flexible, when you don't mind having pages
that contain *only* figures and tables, with no surrounding text at all;
perhaps 2 or more on the same page.
> Thanks and happy holidays to everyone.
Hope this helps,
Ross Moore
> Ed Roche
> Manhattan
>
>
>
> -----------------------------------------------------
> Mac TeX info, resources, and news can be found at:
>
> -----------------------------------------------------
> List archives can be found at:
>
> -----------------------------------------------------
> See message headers for list info.
> -----------------------------------------------------
>
----------------------------------------------------------------------
End of MacOSX-TeX Digest
-----------------------------------------------------
Mac TeX info, resources, and news can be found at:
-----------------------------------------------------
List archives can be found at:
-----------------------------------------------------
See message headers for list info.
-----------------------------------------------------