Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   1419 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

PREBUILD(1)							   PREBUILD(1)

NAME
       prebuild	 - Build PostScript prebuilt font file from bitmap description
       files

SYNOPSIS
       /usr/bin/prebuild fontname fonttype  fontuniqueid  fontcharactersetname
       bdffile ...

DESCRIPTION
       prebuild	 is  used  to build a binary file format known as the prebuilt
       file for use by the NEXTSTEP(tm) Window Server.	It takes  as  input  a
       number of standard Adobe Bitmap Description format files and produces a
       much more compact binary representation of the  bits  in	 those	files.
       The Bitmap Distribution Format files provided as input to prebuild must
       be given in order from smallest to largest.

       In Display PostScript, every  face  of  every  font  is	defined	 by  a
       PostScript  program  (see the PostScript® Language Reference Manual for
       more details on how to create a PostScript font).   In  order  for  the
       NEXTSTEP	 system	 to  use  a  font,  the	 font creator must provide the
       PostScript language file defining the outlines of the characters of the
       font,  and  an  Adobe Font Metrics (AFM) file describing separately the
       widths of those characters.

       In NEXTSTEP a font is stored in the filesystem  as  a  directory	 whose
       name  is	 that of the font, followed by a .font extension; for example,
       Helvetica-Oblique.font.	The .font directory must contain at least  the
       outline	and afm files for the font, and optionally the bitmap file for
       the font.  So, Helvetica-Oblique.font would contain  the	 outline  file
       Helvetica-Oblique,  the	AFM  file  Helvetica-Oblique.afm, and possibly
       Helvetica-Oblique.bepf (see below).  Some fonts also have AFM files for
       specific	 point	sizes  of  screen  bitmap  fonts; for example, Screen-
       Helvetica-Oblique.10.afm for 10-point Helvetica Oblique.

       In order for the window server to see a new font, it must be placed  in
       one  of	the  three  standard  Fonts  directories:  /NextLibrary/Fonts,
       /LocalLibrary/Fonts, or ~/Library/Fonts.

       prebuild outputs a file in the current directory whose name is the name
       of  the font followed by the suffix indicating the byte sex of the file
       (.bepf for big-endian files, and .lepf for little-endian files).	  This
       file should be placed in the same font's .font directory.

FILES
       /NextLibrary/Fonts/     location of NeXT-provided fonts
       /LocalLibrary/Fonts/    location of local fonts
       ~/Library/Fonts/	       location of user fonts

SEE ALSO
       screenafm(1)

BUGS
       prebuild should output both a .bepf and a .lepf file.

       fonttype and fontuniqueid are actually ignored.

NeXT Computer, Inc.		 July 14, 1992			   PREBUILD(1)

Vote for polarhome