* Taco's Font Installation Tutorial (was Re: Newbie's question)
@ 2000-04-27 11:44 Christopher G D Tipper
0 siblings, 0 replies; 2+ messages in thread
From: Christopher G D Tipper @ 2000-04-27 11:44 UTC (permalink / raw)
Cc: ConTeXt Mailing List
Here's Taco's font tutorial. If you are doing Truetype you will have to get pdfTeX to recognise the fonts. The instructions I used were http://quantum.bitp.kiev.ua/radamir/ttf-tex.htm They are not perfect, but I figured it out eventually...
----- Original Message -----
From: "Taco Hoekwater" <taco.hoekwater@wkap.nl>
To: <ctipper@hol.gr>
Cc: <ntg-context@ntg.nl>
Sent: Tuesday, April 11, 2000 2:32 PM
Subject: Font tutorial (Re: Truetype fonts in ConTeXt)
>
> >>>>> "Christopher" == Christopher G D Tipper <ctipper@hol.gr> writes:
>
> Christopher> I'd like to use Microsoft's TrueType font 'Verdana'
> Christopher> as a headline font in my ConTeXt documents, and I was
>
> Here is the basic approach:
>
> 1. You need to create a file called font-xxx.tex, where xxx is a short
> code for the font in question. For verdana, the best would be
> font-ver.tex. This file will contain the Context definitions for the
> verdana family (more below).
>
> 2. In the source document, you do \setupbodyfont[ver].
> This command makes Context load font-ver.tex
>
> For a 'real' document, you would rather do this:
>
> \setupbodyfont[ber,pos,ver]:
>
> font-pos: defines Times/Helv/Courier in an indirect way
> font-ber: maps this indirection to Karl Berry TFM names
> (default is Y&Y style TFM names)
> font-ver: this will overwrite the definitions for 'ss'
> (order is important: ver,pos would overwrite your verdana
> with helvetica from 'font-pos').
>
> 3. You need the font metrics and the actual font files.
> (And you need to know the TFM names to write the defn. file)
>
> 4. You need pdftex.map entries for these fonts.
> (you had those already, yes? Otherwise, you need to read
> the pdftex manual)
>
>
> So far the theory.
>
>
> Here is a basic, template-like font-xxx.tex, that you can use to fill
> in the needed definitions for font-ver.tex:
>
> % TEMPLATE
>
> \definefontsynonym [@FONTFAMILYNAME@-Roman] [@TFMNAME1@] [encoding=@ENC@]
> \definefontsynonym [@FONTFAMILYNAME@-Italic] [@TFMNAME2@] [encoding=@ENC@]
> \definefontsynonym [@FONTFAMILYNAME@-Slanted] [@TFMNAME3@] [encoding=@ENC@]
> \definefontsynonym [@FONTFAMILYNAME@-Bold] [@TFMNAME4@] [encoding=@ENC@]
> \definefontsynonym [@FONTFAMILYNAME@-BoldItalic] [@TFMNAME5@] [encoding=@ENC@]
> \definefontsynonym [@FONTFAMILYNAME@-BoldSlanted][@TFMNAME6@] [encoding=@ENC@]
> \definefontsynonym [@FONTFAMILYNAME@-Caps] [@TFMNAME7@] [encoding=@ENC@]
>
>
> \definefontsynonym [@FONTFAM@] [@FONTFAMILYNAME@-Roman]
> \definefontsynonym [@FONTFAM@Bold] [@FONTFAMILYNAME@-Bold]
> \definefontsynonym [@FONTFAM@Italic] [@FONTFAMILYNAME@-Italic]
> \definefontsynonym [@FONTFAM@Slanted] [@FONTFAMILYNAME@-Slanted]
> \definefontsynonym [@FONTFAM@BoldItalic] [@FONTFAMILYNAME@-BoldItalic]
> \definefontsynonym [@FONTFAM@BoldSlanted] [@FONTFAMILYNAME@-BoldSlanted]
> \definefontsynonym [@FONTFAM@Caps] [@FONTFAMILYNAME@-Caps]
>
> \definebodyfont [14.4pt,12pt,11pt,10pt,9pt,8pt,7pt,6pt,5pt] [rm] [default]
> \definebodyfont [14.4pt,12pt,11pt,10pt,9pt,8pt,7pt,6pt,5pt] [ss] [default]
> \definebodyfont [14.4pt,12pt,11pt,10pt,9pt,8pt,7pt,6pt,5pt] [tt] [default]
>
> \endinput
>
> % END TEMPLATE
>
> In the Above file, replace with the following
> (always remove my double quotes):
>
> @FONTFAMILYNAME@ -> the 'textual' font family name, in your case
> "Verdana"
> @TFMNAME1..7@ -> The seven possible different TFM file names
> I don't know these for verdana, but for Times
> in EC encoding, (as example) these would be:
>
> "ptmr8t"
> "ptmri8t"
> "ptmro8t"
> "ptmb8t"
> "ptmbi8t"
> "ptmbo8t"
> "ptmrc8t"
>
> If some of them are missing, just duplicate
> something else.
>
>
>
> @ENC@ -> The encoding for this particular TFM file.
> For karl berry TFM names, the basic rule is:
>
> xxxxx8t -> replace with "ec"
> xxxxx8y -> replace with "texnansi"
> xxxxx7t -> delete "[encoding=....]" completely
>
> Context doesn't want to guess this from the file
> name, since that would give problems with symbolic
> fonts.
>
> @FONTFAM@ -> One of "Serif" (\rm), "Sans" (\ss) or "Mono" (\tt)
>
>
>
> And that's all there is to it, actually.
>
>
> %% optional remark below.
>
> Just in case you are wondering, these lines:
>
>
> \definefontsynonym [@FONTFAMILYNAME@-Caps][@TFMNAME7@] [encoding=@ENC@]
> \definefontsynonym [@FONTFAM@Caps] [@FONTFAMILYNAME@-Caps]
>
> *can* be merged into
>
> \definefontsynonym [@FONTFAM@Caps] [@TFMNAME7@] [encoding=@ENC@]
>
> however, the basic idea is that you can split this definition into two
> separate files (right after the tfm defs) so that you can have Font
> Family name definitions that do not depend on the actual tfm file
> names.
>
> To put it another way: One special file should ideally define all of
> the TFM file name <-> Font Family Name mappings that are available on
> your local system, and the other font-XXX.tex would contain only the
> second part of the template above.
>
> In fact, that is precisely what font-ber.tex does for a number of
> standard PostSCript fonts. But these definitions could also be in
> cont-usr.tex, for example.
>
> Hope this makes sense. If not, let me know.
>
> Christopher> For the future, Adobe Acrobat
> Christopher> comes distributed with the Lucida Bright family of
> Christopher> fonts in TrueType, and I'd like to be able to use
> Christopher> these.
>
> Short answer provided by Hans, but until Adobe actually starts
> shipping I wouldn't trust it. They'll probably use the 'Printer-disk'
> version of the TTFs, and these are not particularly good nor do they
> contain all of the characters.
>
> Greetings, Taco
>
> --
> Taco Hoekwater taco.hoekwater@wkap.nl
> Kluwer Academic Publishers -- Pre Press --
> Achterom 119, 3311 KB Dordrecht, The Netherlands tel. 31-78-6392550
> ---------------------------------------------------------------------
>
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Taco's Font Installation Tutorial (was Re: Newbie's question)
@ 2000-04-27 12:20 Christopher G D Tipper
0 siblings, 0 replies; 2+ messages in thread
From: Christopher G D Tipper @ 2000-04-27 12:20 UTC (permalink / raw)
Cc: ConTeXt Mailing List
> Here's Taco's font tutorial. If you are doing Truetype you will have to get pdfTeX to recognise the
> fonts. The instructions I used were http://quantum.bitp.kiev.ua/radamir/ttf-tex.htm They are not
> perfect, but I figured it out eventually...
The link is broken now. I have pdf of this article, but if anyone knows where it has moved I'd be very interested.
Christopher
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2000-04-27 12:20 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-04-27 11:44 Taco's Font Installation Tutorial (was Re: Newbie's question) Christopher G D Tipper
2000-04-27 12:20 Christopher G D Tipper
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).