\def\LaTeX{L\raise.42ex\hbox{\sc\kern-.45em A}\kern-.15em\TeX}
\let\latex=\LaTeX
\def\fLaTeX{L\raise.42ex\hbox{\sc\kern-.39em A}\kern-.10em\TeX}
\font\sc=cmr7
\def\it{\fam\itfam\font\sc=cmti7 \tenit}
\def\bf{\fam\bffam\font\sc=cmbx7 at 7pt\tenbf}
\def\bul{\leavevmode\llap{\vrule height.5em width.5em depth0pt\hskip.5em}} 

\def\Textures{{\it Textures}}
\let\textures=\Textures
\def\amstex{{\the\textfont2 A}\kern-.1667em\lower.5ex\hbox
 {\the\textfont2 M}\kern-.125em{\the\textfont2 S}-\TeX}
\def\ams{{\the\textfont2 A}\kern-.1667em\lower.5ex\hbox
 {\the\textfont2 M}\kern-.125em{\the\textfont2 S}}

\font\Bsym=cmbsy10 at 28pt
\font\bbsym=cmbsy10 at 18pt
\def\amstexb{{\bbsym A}\kern-.1667em\lower.5ex\hbox
 {\bbsym M}\kern-.125em{\bbsym S}-\TeX}
\def\amsb{{\bbsym A}\kern-.1667em\lower.5ex\hbox
 {\bbsym M}\kern-.125em{\bbsym S}-\TeX}
\def\amsB{{\Bsym A}\kern-.1667em\lower.5ex\hbox
 {\Bsym M}\kern-.125em{\Bsym S}}

\font\bsym=cmbsy10 at 10.5pt
\def\amstexbh{{\bsym A}\kern-.1667em\lower.5ex\hbox
 {\bsym M}\kern-.125em{\bsym S}-\TeX}
\def\amsbh{{\bsym A}\kern-.1667em\lower.5ex\hbox
 {\bsym M}\kern-.125em{\bsym S}}

\hoffset-.25in
\voffset-.25in

%%%%%%%%%%%%%%%%%% makes everything 
% verbatim Macro % between | and |
%%%%%%%%%%%%%%%%%% be verbatim

\def\makeordinary{\catcode`\&=12 \catcode`\{=12
  \catcode`\}=12 \catcode`\#=12 \catcode`\\=12 \catcode`\$=12
  \catcode`\_=12 \catcode`\^=12 \catcode`\%=12 \catcode`\~=12}

\catcode`\|=\active
\def|{\bgroup\makeordinary\obeylines\obeyspaces\tt%
  \def|{\egroup}}

%%%%%%%%%%%%%%%%%%
%endverbatimMacro%
%%%%%%%%%%%%%%%%%%

\newdimen\pagemargin \pagemargin=1cm
\newdimen\pageheight \pageheight=255mm
\advance\pageheight by -2\pagemargin

\newdimen\pagewidth \pagewidth=190mm
\advance\pagewidth by -2\pagemargin

\newdimen\headcolumn \headcolumn=.3\pagewidth
\newdimen\bodycolumn \bodycolumn=.7\pagewidth

\vsize\pageheight % already includes top/bottom margin

\raggedbottom

\pretolerance=1000
\hyphenation{typeset typeset-ter typeset-ting Modern
Post-Script Textures Classic Hyper-Card pro-gram-mable}

\clubpenalty=10000
\widowpenalty=\clubpenalty
\hyphenpenalty=100
\doublehyphendemerits=10000000

\hsize=\pagewidth
\topskip 20pt
\leftskip=\headcolumn
\parskip=.5\baselineskip
\rightskip0pt plus .1\hsize

\emergencystretch .05\hsize

%%%%%

\font\chapterfont=TimesB at 18pt
\font\headfont=TimesB at 12pt
\font\subfont=Times at 10pt
\font\pagefont=TimesB at 10.5pt
\font\bignumfont=TimesB at 20pt
\font\tt=cmtt10 at 11pt
\font\bodyfont=Times at 10.5pt
\font\tenit=TimesI at 10.5pt
\font\tenbf=TimesB at 10.5pt
\font\met=logo10 at 12pt
\font\tmfont=cmr17 at 4.5pt
\def\tm{\raise4pt\hbox{\tmfont TM}}
\font\btmfont=cmbx12 at 6pt
\def\btm{\raise4.5pt\hbox{\btmfont TM}}

\def\chaptertype{\chapterfont\font\sc=TimesB at 12pt
 \let\latex=\fLaTeX\baselineskip26pt\spaceskip0pt}
\def\headtype{\headfont\font\sc=TimesB at 6.5pt
 \let\latex=\fLaTeX\baselineskip 13pt\spaceskip0pt}
\def\subtype{\subfont\baselineskip 13pt}
\def\bodytype{\bodyfont\baselineskip 13pt}
\def\headpar{\rightskip30pt plus4em\parindent0pt}
\let\subpar=\headpar
\def\bodypar{\rightskip0pt plus4em\parindent0pt}

\bodytype
\parindent=0pt

\def\chapter#1#2\par{{\vfill\eject\leftskip=0pt\hsize\pagewidth
 \null\vskip-15pt\chaptertype\noindent{#1}\hfill % \uppercase
 {\headfont Written #2}\par
 \baselineskip13pt\null\hrule height 1pt\null
 \null\vskip-2\baselineskip}}

\def\head#1#2\par{%
{\leftskip=0pt
 \setbox0=\vtop{\hsize\headcolumn\headtype\headpar\noindent#1\par}
 \dp0=0pt
 \null\null\hrule\null\nobreak
 \hbox{\box0\vtop{\hsize\bodycolumn\bodyfont\bodypar
 \noindent\ignorespaces#2\par}}\vskip4pt}} % the 4pt is a kludge - bs

\def\itemhead#1{%
{\leftskip=0pt
 \setbox0=\vtop{\hsize\headcolumn\headtype\headpar\noindent#1\par}
 \dp0=0pt
 \null\null\hrule\null\nobreak
 \hbox{\box0\vtop{\hsize\bodycolumn\bodyfont\bodypar
 }}\vskip-16pt}} % the 4pt is a kludge - bs

\def\sub#1#2\par{%
{\leftskip=0pt\setbox0=\vtop{\hsize\headcolumn\subtype\subpar\noindent#1\par}
 \dp0=0pt
 \vskip12pt\hrule height.2ptwidth\headcolumn\null\nobreak
 \hbox{\box0\vtop{\hsize\bodycolumn\bodyfont\bodypar
 \noindent\ignorespaces#2\par}}}}

\def\itemsub#1{%
{\leftskip=0pt\setbox0=\vtop{\hsize\headcolumn\subtype\subpar\noindent#1\par}
 \dp0=0pt
 \vskip12pt\hrule height.2ptwidth\headcolumn\null\nobreak
 \hbox{\box0\vtop{\hsize\bodycolumn\bodyfont\bodypar
 }}\vskip-\baselineskip}}

\def\bignumbox#1{\vbox to 0pt{\vss
 \hrule\hbox to 1.5\baselineskip{\vrule\hss\vbox to 1.5\baselineskip{
 \vss
 \bignumfont\hbox{#1}
 \vss
 }\hss\vrule}\hrule}}
\def\bignum#1{\vskip3.5\baselineskip\goodbreak\vskip-3.5\baselineskip
 \leavevmode\hangindent=2.\baselineskip\hangafter=-2\smash{%
 \hbox to 0pt{\hss\lower\baselineskip\bignumbox{#1}\hskip.5\baselineskip
 }}\ignorespaces}
%\let\item=\bignum

\newbox\leftbox
\def\makepage{\vtop{\hbox to\pagewidth{\the\headline}\box255}}
\newif\ifleft
\lefttrue
\output{\shipout\makepage\advancepageno}

\def\emptychapter{\null\vskip-\parskip\vskip-2\baselineskip}
\def\emptyhead{\null\vskip2\baselineskip}

\input psfig.sty
\input pix.tex

%%%%%%%%%%%%%%%%%%%%%%%%%
%  Begin Text           %
%%%%%%%%%%%%%%%%%%%%%%%%%


\chapter{The Blue Sky FAQ List}
{August 1994(mildly updated March '95)}

\head{Contents}
This list is divided into these main headings:

{$\bullet$}General

{$\bullet$}Fonts

{$\bullet$}Pictures

{$\bullet$}Printing

{$\bullet$}Formats

{$\bullet$}Miscellaneous.  

Of course these subjects may overlap, so look in related areas if you
don't find your problem in the place you'd expect (e.g. a printing
problem may be caused by a font problem).

Each question and answer are preceded by a short list of keywords which
roughly describe the problem addressed and make searching for specific
problems (e.g. with the Find$\ldots$ feature in Textures) easier.

If none of these items helps, and the Textures User Guide doesn't help, write
us at <help@bluesky.com> and give us your name, Textures serial number,
Macintosh model, Adobe Type Manager (ATM) version number, printer information
(manufacturer, model, and amount of RAM), a description of the problem, and
the events leading up to the problem.

%%%%%%%%%%%%%%%%
%  General     %
%%%%%%%%%%%%%%%%
\head{General}

\sub{Textures requirements, system requirements}
Q. What do I need to run Textures? Does Textures support
virtual memory? Is Textures 32bit clean? Does Textures support AppleEvents? 

A. Textures (1.6 and 1.7) requirements:

All of the following are true of Classic Textures 1.6 and 1.7, and may or
may not be true of earlier versions.

1. Requires at the least 2400K partition, so your Macintosh should have 4 megabytes of
RAM (2.5 M minimum) if you're running System 7.  Textures 1.7 runs best with 3500 to
4000K.

2. Requires Macintosh operating System 6.0.5 or later

3. Is fully System 7 compatible
 
4. Is 32-bit clean
 
5. Can be run in virtual memory
 
6. Supports the core Apple Events
 
7. Runs on all current production Macintoshes
 
8. Runs on any out-of-production Macintosh that meets criteria 1 and 2
above
 
9. Does not require a math coprocessor, but will make use of it
if one is installed. (A math coprocessor does not provide noticeably
faster performance.)

\sub{Textures and System 7.5}
Q. Does Textures run under System 7.5?  What about QuickDraw GX?

A. Textures runs fine under System 7.5.  At this time,
we recommend {\it against} running Textures with QuickDraw GX
because the PostScript font converter doesn't correctly convert
some of the CM PostScript fonts, rendering them unusable.  QuickDraw GX compatibility is on ``the short list''
now, and we expect to have a solution soon.  


\sub{PowerPC, native}
Q. When will Blue Sky Research have a version of
Textures available that works in native mode on the
PowerMac? 

A. Now!  We are currently shipping a very fast PPC native code Textures
(four times faster than emulation).
The PPC upgrade is \$100 (from Textures 1.7).

\sub{Excalibur, spellchecker}
Q. I can't figure
out how to get Excalibur started. Can you help me?

A. It's shipped in an .sea (self-extracting archive) file, so first you
have to expand Excalibur and its associated files. To expand the archive,
double-click on that file and tell the Mac where to save the
expanded material (inside the Textures folder is as good a place as any).
Once that expansion is finished, throw away the .sea file, since
you won't be needing it again.

Open the newly expanded Excalibur folder, where you will find a ReadMe
file and a file called `Excalibur-manual.tex'.
Although that last file wasn't created with Textures,
you can open it by launching Textures and selecting
`Excalibur-manual.tex' with the Open command.
Typesetting the document with the \LaTeX{} format will
give you all the instructions you'll need to get the
most out of Excalibur.

Double-clicking the Excalibur program should briefly show the Excalibur
splash screen (a black rectangle with the application name, version, and
who wrote it) and then bring up a standard Macintosh dialog box,
which asks you to select the file you want to spell
check. (Since two applications don't have write access to a file at
the same time, you should close the document with Textures before
you ask Excalibur to spell check it.) Excalibur will quickly spell check
the document according to the dictionary(ies) you have chosen and flag
any questionable words. Depending on how you have your preferences set
(in the options menu), you can get it to flag or ignore certain types of
items.

Since you can't add words to Excalibur's standard dictionary, new words
are added by creating your own dictionary and adding words there.
Excalibur will spell check your document according to the
dictionary(ies) you have chosen in the Dictionaries menu.

\sub{Defaults, Customizing}
Q. Can I make Textures remember my preferences?  I like to have Flash Mode
off, the \LaTeX{} format selected, and the Typeset window set to ``Actual
Size."

A. It is possible with Textures 1.5 or later.
Start with a new untitled document and set it up exactly the way
you want all of your new untitled documents to look (\LaTeX{}
selected, Wrap on, etc.). Save the document with the name Defaults in
your TeX formats folder. If you put text into the Defaults document
and typeset it, you can even set preview window location and view
size. The next time you launch Textures, it will set up your new
untitled document (no text in the Edit window, of course) with all
the same settings as your Defaults document.

Please note that this applies only to new documents. When you open an
existing Textures document that already has attributes set, Textures will use
the document's settings rather than those of the Defaults document. In
addition, if you open with Textures a `text only' document created by a
different editor or word processing program, it also will take on the
attributes of the Defaults document.

\sub{Input path, Pathnames}
Q. How do I specify an explicit path for an input file?

A. You may specify either an absolute path, starting with the name
of your hard drive and naming each folder down to the file itself,
or specify a relative path that begins with the current directory.

Although the Macintosh can accept folder and file names that contain
spaces, \TeX{} considers a space to be the end of the file/path name and
will look no further for your file if it encounters a space. Also
remember that files containing an input with an explicit path are not
likely to be transportable (without modification) to another system.

On the Macintosh the connecting character for paths is the colon (:).
Visualize a structure like the following, with the hard drive at the ``top''
level and the desired input file at the ``bottom'' level:

   {\parskip 2 pt

   {\parindent 62 pt {\bf Harddrive} (the root level)}
   
   {\parindent 64 pt {\bf FolderA} (a folder on the harddrive)}
   
   {\parindent 47 pt {\bf FolderB---FolderD} (two folders inside FolderA}
               
   {\parindent 22pt {\bf FolderC} (a folder inside FolderB)}
       
   {\bf myinput.tex} (the desired file)} 

where the only variable is the location of the file ``myfile.tex'',
which contains an input statement for the file ``myinput.tex''.

An example of an absolute input path might be

|\input Harddrive:FolderA:FolderB:FolderC:myinput.tex|

A relative path begins with a colon to indicate the current directory
(the one containing the document being typeset). You might use

|\input :FolderB:FolderC:myinput.tex|

if the file ``myfile.tex'' is in FolderA.

If an input file is in an adjacent folder, you may wish to ``back
up'' one or more folders. Use a colon for each level. You might use

|\input ::FolderB:FolderC:myinput.tex|

if the current directory is FolderD, where FolderD and FolderB are
both inside FolderA.

It's much easier, of course, to just place the input file in either
the folder containing the file being typeset or in the \TeX{} inputs
folder. Textures will automatically find the file in either
location.  Textures 1.7 will do recursive folder searching
automatically.


\sub{Textures  Preferences file}
Q. I noticed after installing Textures that there is a Textures
Preferences file in the System  Folder. What is this file used for?

A.  The preferences file contains macros for the Plain \TeX{} format, if you
have installed any.

Default settings are an entirely separate issue, and are handled by
way of a Textures document called Defaults and placed in the TeX
formats folder. (see ``default'')

\sub{PostScript file, Platforms}
Q. How do I make a PostScript file from my Textures Document?

A. Go to ``Print . . .'' in the File menu.  Choose ``PostScript File''
as destination instead of printer.  The file will be created.

\sub{PostScript file, Fonts, Platforms, LaserWriter}
Q. If I create a PostScript file using my print driver, how do I get
the fonts to be included?

A. The laserwriter driver 7.x series does it whether 
you want it to or not.  The LaserWriter driver 8.1.1 allows you to specify
font inclusion, in the ``Print . . .'' dialog.

\sub{Printing, Edit window, Log window}
Q. How do I tell Textures to print just the Edit window?

A. Close the typeset window, then print; or take it out of Flash mode, make
the Edit window active, then print.

(These also work for printing the TeX Log window.)

%%%%%%%%%%%%%%%%%
% Fonts'n'stuff %
%%%%%%%%%%%%%%%%%
\head{Fonts, General}

\sub{PostScript fonts, fonts, installation, location}

 Q. When I tried to install PostScript fonts I received from Blue Sky
Research, I got really confused. I just dropped the fonts onto the
System Folder, but Textures couldn't seem to find them. My screen
display looks terrible! Where does Textures look for these fonts?

A. {\bf  Where PostScript fonts should be installed is entirely dependent
on which System version you have and which version of ATM}. And
Textures, quite honestly, never looks for/at the printer fonts at
all. (All the font magic with PostScript fonts is handled via System
calls.) So long as Textures has metric information to typeset with,
the application is happy. Poor screen display or printer output
doesn't make {\bf you} very happy, though.

Please note that ATM installation usually has no effect on
PostScript printer output. Screen display and non-PostScript
printer output are the only things you can expect to improve by
changing versions of ATM and/or moving PostScript/printer/outline
fonts between the System Folder, Extensions, or Fonts folders.

{\bf The rule of thumb is that you should always install the screen
bitmap fonts (we ship these in a font suitcase) that were shipped
with your PostScript printer fonts exactly according to Apple's
guidelines for the operating system version on your Macintosh. And
you should always install the PostScript/printer/outline fonts
(these are the ones that, when viewed by icon, look square with
horizontal lines and a slanted uppercase A) according to where the
Adobe Type Manager software will look for them}.

\sub{CM/PS fonts, hiding, fonts}

Q. Is it possible to hide the CM/PS fonts from other applications?

A. Yes, it's possible. Item 2, below, describes how to do it. Be sure
you read the note that goes along with that description, though,
before choosing that alternative. Choices 1, 3, 4 or 5 may be more
appropriate for your needs.

{\parindent=1em
\item{1} You can, of course, remove any
of the Computer Modern fonts you don't need. You should note,
however, that the \LaTeX{} format in particular uses a lot of CM fonts.
You can get the list of fonts in use in any document by selecting
Show Fonts from the File menu and clicking the ``Only fonts in use''
checkbox. (This checkbox is available in the Textures 1.6 (and 1.7) dialog
box, but not in the dialog boxes of earlier versions.) The following fonts
are particularly rarely used: cmdunh10, cmff10, cmfi10, cmfib8,
cminch, cmvtt10.

\item{2} To make the Computer Modern fonts visible only to Textures
and not to other applications, you can place the CM/PS Screen fonts
suitcase file in the ``\TeX{} fonts'' folder. (You must place the
{\bf suitcase file} itself in the \TeX{} fonts folder; if you place the
individual fonts loose in the folder, Textures will not find them.)
If you do this, the Computer Modern fonts will be visible only to
Textures, not to other applications. {\bf Do not move} the printer
font files (listed by kind as ``System Extension'' or ``PostScript
Font'' under System 7.0 and 7.1, respectively) to the ``\TeX{} fonts''
folder.

{\bf IMPORTANT NOTE:} If you choose option 2, you must also turn off
background printing. Placing your fonts in the \TeX{} fonts folder will
prevent the use of background printing, because the fonts will not be
available to the Macintosh print spooler. Turn off background
printing in the Chooser.

\item{3} Adobe Type Reunion, available from Adobe Systems, will
condense the Computer Modern fonts from 75 fonts to only 16
``families,'' with sub-menus showing the remainder. You can further
reduce this list by removing the rarely-used fonts listed in item 1,
above.

\item{4} Suitcase, from Fifth Generation Systems/Symantec, lets you
access (or remove access to) fonts at will. If you put the PostScript
outlines and the CM/PS Screen Fonts suitcase into one folder and
``open'' the CM/PS Screen fonts suitcase, your applications, ATM, and
your printer driver will have access to the fonts. You can remove
access to the fonts by ``closing'' the CM/PS Screen fonts suitcase.

\item{5} WYSIWYG Menus, from Now Software, combines fonts into
families the same way Adobe Type Reunion does. It allows you to
choose which ones will appear in the Fonts menu of any program. This
can be used to hide as many of the CM/PS fonts as desired. It also
allows you to rearrange the order in which fonts are listed in the
Fonts menu so you can put the most commonly used fonts on top.

\item{6} get our ``hidefonts'' package from our ftp server
<ftp.bluesky.com>.  This will make the cm fonts invisible and
unavailable to other applications, and will allow you to use background
printing.

\sub{Sli\TeX, \LaTeX{}, preview, ATM}

Q. Why are my Sli\TeX{} and \LaTeX{} fonts so ugly? The fonts lasy, lacircle,
etc. come out blocky.

A. The trouble is that the old screen fonts don't work with the new ATM:
ATM>3.  The solution is to get the new versions from us.  They're on
our ftp server <ftp.bluesky.com> in /pub/fonts.

\sub{wrong/missing fonts, pictures}
Q. When I include a document from KaleidoGraph and print it out, the graph
looks fine but the fonts in it come out wrong.  What do I do to fix this?

A. You need to download the fonts in question to the printer
manually.  Textures versions <1.7 don't automatically do this (this is a good reason to upgrade!)
: to do it, use Adobe's Downloader font utility, Apple's LaserWriter utility, or Apple's
Font Utility. Then choose ``download fonts'' option.  

Textures 1.7 does this automatically.

\sub{ligature, bitmap}

Q. Why does my fl ligature come out wrong?  (I'm using System 7 and bitmap
fonts.)

A. This is a bug with the way System 7 handles char 13, the
carriage return.  The fix is to either upgrade to PostScript fonts or
to switch back to System 6.0.7.

\sub{greek, lowercase, bold}

Q. How can I get bold lower-case Greek letters?

A. Knuth didn't create those (for some good reason?)
so you need the font ``boldgreek'' and the metrics
{\bf and} the definitions.  Some of these are available from 
us on our ftp server <ftp.bluesky.com>

\sub{fonts, metrics, new}

Q. How do I use font [anyfont] with Textures?

A. 1) Get the metrics from us for that font or

2) create the metrics yourself with Edmetrics.  Make sure that
the font is properly installed.

\head{Fonts:ATM}

\sub{PowerPC, preview, ATM 3.6 ATM 3.8}
Q. I have Textures installed on my PowerMac. It prints properly on
my PostScript printer, but the screen typeset preview looks terrible.
What's wrong?

A. Be sure you have Adobe Type Manager version 3.6 or later
installed. We use ATM to render screen display for our Computer
Modern PostScript fonts, and earlier versions of ATM may not work
correctly on the PowerMac.  ATM 3.8 is native for the PPC and will
noticibly improve your performance.

\sub{ATM  problems}

Q. Where does ATM look for fonts?
Which version of ATM do I need?

A. Since most people don't know what those locations are for all versions of
ATM (and the individual you connect with at Adobe Technical Support may
not be able to tell you), we've included a brief list below.

ATM 1.2: Do {\bf not} use this version of ATM with Textures or any of
our PostScript fonts! Upgrade!

ATM 2.0: Only looks for PostScript/printer/outline fonts loose in the
System Folder. Will {\bf not} find fonts that are nested in any other
folder (Extensions, Fonts). (Note for System 7 users: ATM 2.0 is not
32-bit clean and will crash any application that invokes its use
while your Macintosh has 32-bit addressing enabled.)

ATM 2.0.2, 2.0.3: Will look for PostScript/printer/outline fonts
loose in the System Folder or in the System 7 Extensions folder. Will
{\bf not} find printer/outline fonts that are in the System 7.1 Fonts
folder.

ATM 3.0, SuperATM 3.5 or 3.6: Identifies the specific System version
your Macintosh is using and looks only in one specific location for
PostScript/printer/outline fonts. These versions of ATM expect to see
the PostScript fonts loose in the System folder on a System 6
installation, in the System Folder's Extensions folder on a System
7.0 or 7.0.1 installation, or in the System Folder's Fonts folder on
a System 7.1 installation.

ATM 3.5 (on a machine running System 7.1) looks for fonts in the extensions
folder in the System folder.

Be sure to restart your Macintosh after moving fonts from one
location to another.

\sub{ATM, square bracket}

Q. Why is the lower bar of my square bracket missing 
at some sizes?

A. This is an ATM problem, and shouldn't affect printing. You may choose
to get a newer ATM or live with it (since it's only on the screen). You may
also choose to replace your fonts with newer versions. (The Computer Modern
fonts are available from us in Type 1 PostScript form.)

\head{Fonts:MathTime}

\sub{MathTime, fonts, calligraphy}

Q. How do I use calligraphic characters with MathTime fonts and
\LaTeX?

A. MathTime has no calligraphic characters of its own and must
therefore borrow the characters from Computer Modern. Place the line

|\Calligraphic{cmsy10}{cmsy7}{cmsy5}|

between the documentstyle declaration and the |\begin{document}|
statement if you need to use |\cal|. (This line can be built into your
\LaTeX-Times format if you use calligraphic characters frequently.)

\sub{mathtime, incomplete, preview}

Q. I have installed Textures and MathTime fonts as instructed.
Screen display of large math operators is incomplete; I only see the
top half of the characters. What's wrong?

A. You must have received one of the very early copies of the
Textures update with MathTime before we discovered the screen display
problem. This problem can easily be corrected by a new MathTime
screen fonts suitcase, which is available by anonymous FTP from
ftp.bluesky.com in the /pub/fonts directory.

Once you receive the new suitcase, remove the screen fonts MTEX 10,
MTSY 10, and RMTMI 10 that came with your original disk (these will
be in the System suitcase with System 7, the MathTime screen fonts
suitcase will be in the System Folder's Fonts folder if you're using
System 7.1, and the suitcase will be loose in the System folder if
you're using System 6 and didn't install the screen fonts with
Font/DA Mover) and install the replacements that are in the new
suitcase. Restart your Macintosh, and the screen display problem will
be gone.

\sub{Textures1.6, mathtime, diacritics}

Q. I received a copy of the Textures update with MathTime fonts
that was shipped in mid-June. When I use MathTime fonts with Plain
TeX, all the diacritic characters are positioned correctly. When I use
MathTime fonts with \LaTeX, though, diacritic characters seem to be
out of position. Is there a fix for this?

A. |\skewchar| values in the lfonts.tex file we distributed for
MathTime fonts use in mid-June were incorrect. This was fixed in
October 1993, and copies of the revised version were shipped free of
charge to all customers who had purchased MathTime fonts from Blue
Sky Research. If you own our MathTime PostScript fonts and did not
receive your updated version, contact sales@bluesky.com with your
serial number and registration information.

\sub{\LaTeX{}, mathtime, missing characters}

Q. I'm using MathTime fonts with \LaTeX{} and have built a new
\LaTeX{} format incorporating these fonts according to your
instructions. When I try to use special footnote symbols like the
dagger and doubledagger, I get a message in the \TeX log saying that
these characters are missing. How do I get these symbols?

A. Certain symbols within \LaTeX{} are ``hard-coded'' values that
needed to be changed, and we neglected to change them in early
shipments of Textures 1.6 with MathTime fonts. We have now changed
them in the files lfonts.tex and lplain.tex so the symbols dagger,
doubledagger, Section, and Paragraph work correctly. This was fixed
in October 1993, and copies of the revised version were shipped free
of charge to all customers who had purchased MathTime fonts from Blue
Sky Research. If you own our MathTime PostScript fonts and did not
receive your updated version, contact sales@bluesky.com with your
serial number and registration information.

We do not currently have a fix for this problem if you are using NFSS
\LaTeX{} with the mathtime.sty file.  We may have a new version for
\LaTeX 2$\epsilon$ soon.

\sub{mathtime, ligatures}

Q. Why, with MathTime fonts, do the ligatures come
out as AE . . . .?

A. Because with 1.6 the mappings are new. (except for CM)
Retypeset the document in Textures 1.6.

\head{Fonts:Lucida}

\sub{lucida, brace}

Q. How do I get the closing brace in lbr and lstr to
work?

A. Change the mapping (with edmetrics) for 

1) QuickDraw from ``Roman->Macintosh8bit'' to ``Typewriter->MacStandard''
and

2) PostScript from ``Roman->MacintoshStandard'' to
``Typewriter->MacintoshStandard.''

You may have to rebuild formats that use the fonts and
retypeset.

\sub{Lucida, preview, delta}

Q. Why do the delta and omega symbols come out as
blocks on my screen? (with lucida fonts)

A. There's a screen display problem with Lucida
fonts --> a fixed version should be available.

\sub{lucida, closing brace}

Q. When I typeset a closing brace |}| in lstr (also in lbr I think) I
 get a closing double quote '' in my print out. I looked at the
character tables provided with the lucida fonts and it shows that
lstr has a double quote in position "7D where the standard \TeX{} font
has the right brace |}|. In lstr the right brace is in position "7C.
Now a bit of strangeness. When I use the PopChar utility included
with the Lucida fonts it indicates the the right brace of lstr is in
position "7D. 

How do I set up the Lucida fonts so that they will print |}| instead
of '' ?

A. The encoding for the lstr font isn't correct if you're using it as a
substitute for CMTT10. What you're getting is the Hungarian umlaut instead of
the close curly brace.

The way you fix this is to open the ``LucidaBright Mac Metrics''
suitcase with EdMetrics dated at least October 15,1993. (The newest
version is on the ftp server.) Open ``lstr'' so you can edit the font mapping.
Change the QuickDraw map from ``Roman->Macintosh8bit'' to
``Typewriter->Macintosh''; change the PostScript map from
``Roman->MacintoshStandard'' to ``Typewriter->MacintoshStandard''; and leave
``MacintoshStandard'' as the PostScript encoding.

Once you've finished this operation, the problem should be corrected. If
you've built any formats that use the lstr font, you may need to rebuild them
and retypeset your document to get correct display. If you're using any of
the other LucidaSans-Typewriter faces in this same context (as a substitute
for CM typewriter faces), you'll need to change those, as well.

\head{Fonts:AMS}

\sub{AMS-\LaTeX, fonts, metrics}

Q. I'm trying to use AMS-\LaTeX{} with your AMS PostScript
fonts. The source files call for sizes of the AMSFonts
that aren't in the AMS/PS set. How can I get this to
work?

A. We have a new metrics suitcase you should use to replace the one we
shipped with our AMS/PS fonts. (The new suitcase is available by
anonymous FTP from ftp.bluesky.com in the /pub/fonts directory.) Please
remove the ``AMS/PS metrics'' suitcase from the ``\TeX fonts'' folder
and put the new suitcase (un-binhexed and unstuffed, of course) into
the ``\TeX fonts'' folder in its place. Restart Textures, rebuild your
AMS-\LaTeX{} format using the original sources, and all should be well.
The ``AMS/PS VF metrics'' suitcase is a superset of the ``AMS/PS
metrics'' suitcase you received earlier. It contains metrics for the
AMS/PS fonts for the 34 that exist, plus virtual font metrics for the
remaining 55. (These scale existing PostScript fonts to sizes called
for in the AMS-\LaTeX{} macros that aren't part of the AMS/PostScript
set.) These metrics are not appropriate for use with Textures
versions prior to 1.6, since those versions did not support virtual
fonts.

\sub{ams, real numbers}

Q. How do I get the symbol for the set of 
Real numbers?

A. This is called the ``blackboard bold R'' and is in the AMS.PS fonts
package.  You can either 1) buy that from us or 2) get the bitmap
version for free from AMS.

\sub{AMS-\LaTeX, fonts}

Q. Why don't I have the fonts I need?
AMS-\LaTeX calls for fonts I don't have.
I'm using ams/ps metrics.

A. We've got 34 of the 89 fonts available in 
PS form, and metrics for the others (as well
as virtual fonts.)  You need the font package
from us as well as Textures>1.6.

You need the ams/ps vf metrics.

\sub{ams, symbols, fonts}

Q. How do I use the ams symbol fonts
with Textures?

A. At the beginning of your \LaTeX{} file you
should type:

|\input amssym.def|

|\input amssym.tex|

\sub{ams, bitmap, printing}

Q: Why don't my AMS bitmap fonts print out?

A: There's a problem with the Mac System setup and
bitmap  fonts -- if your monitor is set to 8- or 16-bit
color, the bitmap fonts won't print.  Change the
setting and your job should work.


\head{Fonts:SliTeX}

\sub{slitex, bold, italic}

Q. When I use both bold and italic faces in my SliTeX
document, some of the bold characters appear to be
italicized and italic characters sometimes appear to be
bold. What's wrong?

A. SliTeX PostScript printer fonts LCMSS8, LCMSSB8, and
LCMSSI8 dated August 27, 1991, can give this type of
display. Printer fonts dated December 2, 1992, provide
correct display. Replacement fonts are available free
on request to registered owners of our Classic Textures
package.

\sub{slitex, preview, spacing}

Q. My Sli\TeX{} documents print correctly on my PostScript
printer, but sometimes there are no spaces between
words in the typeset preview. How can I get correct
screen display?

A. The Sli\TeX{}screen fonts suitcase dated December 4,
1992, gives incorrect screen preview. A screen fonts
suitcase that provides proper screen display is
available by anonymous FTP from ftp.bluesky.com in the
/pub/fonts directory.

\sub{slitex, ATM3.6, preview}

Q. My Sli\TeX{} documents print correctly on my PostScript
printer, but I've noticed that the screen display is
jagged and blocky. I remember that when I first
installed them, they previewed properly. What went
wrong?

A. Sli\TeX{} PostScript printer fonts LCMSS8, LCMSSB8, and
LCMSSI8 dated August 27, 1991, can give this type of
display when used with Adobe Type Manager 3.0 or later.
Printer fonts dated December 2, 1992, provide correct
display. Replacement fonts are available free on
request to registered owners of our Classic Textures
package.

%%%%%%%%%%%%%%
%  Pictures  %
%%%%%%%%%%%%%%

\head{Pictures}

\sub{pictures, EPS, special}

Q. How do I include pictures in my Textures documents?

A. The method we recommend, which works with popular drawing
programs like Adobe Illustrator, Deneba Canvas, Aldus Freehand, and
MacDraw Pro, among others, is to save the drawing in EPS
(Encapsulated PostScript) format (with a one-word filename), place
the file in the same folder as the Textures document you want to
include it in, and use the |\special{illustration . . .}| command as
described in our User's Guide.

If you plan to use this method, there are several macros (available
from Blue Sky Research at no charge; also available by anonymous
FTP from ftp.bluesky.com in the /pub/graphics directory) that will
read the EPSF commented bounding box information and scale and/or
center the illustrations for you. This can be quite handy if you're
planning to include a lot of illustrations in your documents.

A second method allows you to select and copy objects from a drawing
program's window and paste them into the Textures picture window,
using the |\special{picture . . .}| command to bring them into the
typeset version of your document.

A third method is to save your drawing in PICT format (again with a
one-word filename), place the file in the same folder as the Textures
document you want to include it in, and use the |\special{pictfile .
. .}| command.

All three methods can include an optional scaled phrase (e.g.,
|\special{illustration flowchart scaled 750}|), which uses the TeX
standard of 1000 for actual size. A note of caution, however: scaling
either pictures in the Textures picture window or PICT files can
produce less-than-attractive results. For best results, use EPSF
files and a PostScript printer.

\sub{pictures, EPS, preview}

Q. I created an EPS file with a graphics package on another platform
and moved it to my Macintosh. Why doesn't the graphic preview in the
Textures typeset window?

A. When an EPS graphic is incorporated into a Textures document,
Textures will display the graphic in the typeset window if there's a
screen preview already attached to the document. Textures does
{\bf not} read the EPS file and translate it to QuickDraw for display
on a non-PostScript output device like your screen or a non-PostScript
printer. (Most other Macintosh applications don't do this, either.)

There are applications for sale (Freedom of Press Lite and T-Script
Basic, to name two of those that are commonly available) that do EPSF
to QuickDraw translations and more. If you need to print your EPS
files to a non-PostScript printer, you may find it worth the money to
buy such a program and worth the time to convert your files. It may
not be possible to produce a combination file that includes both EPSF
(for the PostScript printer) and QuickDraw (for screen preview).

According to customer report, there is also a free utility called
``ps2eps-mac'' available on Unix systems which produces a MacBinary
file with a PICT conversion of the illustration in the resource fork
of the file. We hear it works fine with Textures, producing a
reasonable preview inside the typeset text.


\sub{psfig, unix, eps}

Q. How do I use an eps file in my \TeX/\LaTeX{} document?
Why doesn't psfig work?

A. The unix and Macintosh versions of psfig.sty
are {\bf different}.  You need the correct one, 
available via ftp <ftp.bluesky.com> in the directory /pub/graphics.

\sub{psfig, preview}

Q. How can I get a correct preview with 
psfig?

A. We have an earlier version (that some would probably call obsolete,
but it's perfectly functional) that I made the Textures changes to,
that is not so ``complete'' but does in fact put the preview in the
right place.

If you would like the older version, you can pick it up from our
ftp server in ftp.bluesky.com//pub/graphics/psfig1.6

\sub{rotating, pictures}

Q. I can't get the ``rotating.sty'' style option to work with
Textures, even though Textures is one of the drivers explicetly
supported by that style. I'm using Textures 1.6 and rotating.sty
1.9. The basic rotation package ``rotate.sty'' (which is used in rotating.sty)
works fine.

Q. Rotating.sty prints fine, but doesn't look right on the screen!

A. Your problem can be solved by inserting the line
 
|\or|

immediately before the line that says

|\typeout{Process .DVI file with Pubps}|

You might try using the psfig macro package as well -- it will
rotate and scale EPS graphics, and is available from us at 
<ftp.bluesky.com> in /pub/graphics.

2) There's no way to rotate elements in the screen display
in the current version of Textures.

\sub{pictures, unix}

Q. Why doesn't Textures work with my Unix picture macros? These
macros work fine on my Unix system.

A. The Macintosh and Unix systems need different versions of the
picture macros.  You can get the Mac versions from us at
<ftp.bluesky.com>.

%%%%%%%%%%%%%%%%
% Printing     %
%%%%%%%%%%%%%%%%
\head{Printing}

\sub{printing, stylewriter, postage stamp}

Q. I've purchased a StyleWriter II, and I'm having problems when I
print my Textures documents on it. Tops of some large characters are
cut off, slashes don't get printed through negated relations (for
example, |\neq| looks like =), and after printing the document the
fit-to-window preview shows the document as being about the size of a
postage stamp in the upper left corner of an extremely large piece of
paper. Is there any cure for these problems?

A. Apple has fixed the first two problems with their 1.2 version of
the StyleWriter II driver. You should be able to get the new driver
from your Apple dealer. Tell the dealer it's available on AppleLink
at:

AppleLink Services:Apple Products:Apple SW Updates:Macintosh:Printing
Software:StyleWriter II (1.2)

The last problem is also a bug in the driver.  This problem also exists
in Apple's Personal LaserWriter driver.  The only way to get the
proper typeset window back is to copy all the text into a new untitled
window and retypeset.


\sub{printers, memory, LaserWriter 300}

Q. Can the Apple Personal LaserWriter 300 be used successfully  with
Textures or is the printer simply too small for practical use? 
What about the Apple LaserWriter Select 300?

A. The Apple Personal LaserWriter 300 is a QuickDraw Printer, so it's
memory constraints don't matter.

The Apple LaserWriter Select 300 will work fine with Textures and
our Computer Modern PostScript fonts if you increase its memory from
the default 512K to 4.5MB.

Our understanding (which you should confirm with your Apple dealer)
is that this printer has 512K soldered onto the mother board and has
only one SIMM slot. That SIMM slot reportedly takes either a 1MB or a
4MB SIMM. Since 1.5MB total RAM won't be enough to handle the fonts
TeX uses, upgrading the memory to 4.5MB would be the only feasible
choice.

\sub{TI, printers}

Q. Why can't I print to my TI microlaser
pro from Textures?  It works with Microsoft Word!

A. The TI driver doesn't work with Textures,
but the Apple driver (LaserWriter 8.2) will.
This is often a good solution---use an Apple driver instead of the one that came with the printer.

\sub{printing, memory, time}

Q. Why does my computer take so long to print?

A. The answer is probably that your printer doesn't have enough
memory.  >4 megabytes is recommended, especially for \LaTeX{} documents
(which include a lot of fonts).

Another thing that can make printing take a long time is having 
the ``unlimited downloadable fonts'' box checked in the print . . .
options dialog box. (This won't work with the LaserWriter Driver version
8.2.)

{\bf For more info, see ``Textures and Postscript Printers.''}

\sub{Laserwriter 7.1.2, printing}

Q. How can I fix my printing problems?
I'm using the Laserwriter driver 7.1.2.

A. You can get the Laserwriter 8.2 driver
from apple:  <ftp.support.apple.com> under
/dts/mac/sys.soft/imaging/
This driver is much more reliable for large PostScript
files. 

\sub{rasters, fonts, missing}

Q. Why do I get a ``no memory for rasters'' error message
when I try to print? 

A. You are missing a font that your document calls for.
To determine which one it is, choose the ``show fonts''
item from the file menu, click the ``only fonts in use''
button, and search through those until you find one that says
``no face installed''.  Remove that font definition from your
document and all should be well.

%%%%%%%%%%%%%%%
%  Formats    %
%%%%%%%%%%%%%%%
\head{Formats}

\sub{formats, preview, times}

Q. I made a "Times" format with Textures 1.5,
and when I use it with 1.6 I get screwy characters.
What do I do?

A. We changed the font-mapping and metrics information
in Textures 1.6.  What you need to do is
rebuild the old format with the new Textures and retypeset
the old documents.

\sub{manmac, manfnt}

Q. Why do I get an error when I use the manmac format?
It asks for the font "manfnt"

A. We don't have the manfnt font available, but we do have metrics
available for most of those characters (in the LOGO fonts).

(Most people comment out the line asking for the manfnt font)

\sub{\LaTeX, begin}

Q. When I typeset my \LaTeX{} file, I get a \TeX{} log error message that
says '! Missing |\begin{document}|.' The |\begin{document}| line
{\bf is} present. What's wrong?

A. You have a filename with spaces (2 or more words). The Macintosh
(and Textures) allow a user to give a document a filename containing
spaces (My Book, for example). Giving a \LaTeX{} document a filename
containing spaces will cause the \TeX{} log error message 'Missing
|\begin{document}|.' If you get this error, simply rename your
document with a single word filename (e.g., My\_Book), and typeset the
document again.

\sub{\LaTeX, Box, Diamond}

Q. Why don't the \LaTeX{} |\Box| and |\Diamond|
symbols look good?

A. The problem is old PostScript fonts which don't work well with 
ATM 3.0 or later.  Email help@bluesky.com for the new versions.

\sub{\LaTeX 2$\epsilon$, CTAN}

Q. Where do I get \LaTeX 2$\epsilon$?
How do I install it?
Does it work with Textures?

A. You can now purchase \LaTeX 2$\epsilon$ from us with Textures
1.7.  Included will be a precompiled format, a way to
run new and old versions of \LaTeX{} side-by-side, four
PostScript fonts, and a book.  (email help@bluesky.com for
installation instructions for older versions.)

%%%%%%%%%%%%%%%%%
% Miscellaneous                          %
%%%%%%%%%%%%%%%%%
\head{Miscellaneous}

\sub{alpha, appleevents, remote}

Q. I prefer to use the Alpha editor, and I've heard
it's possible to typeset Alpha documents by controlling
Textures 1.6.3 or 1.7 remotely. How do I use the Alpha
interface with Textures?

A. The current interface is as follows. You can insert the three
lines at the bottom of the commented section in a Textures/Alpha
script file.

{\parskip 0 pt \noindent

\# This script installs a Textures menu with one item, Typeset,

\# that typesets the contents of the current window.

\# Textures must be already active; it is not launched by this script.

\# To install this script, select "Load Window" in the Alpha/Edit
menu. 

\#

\# The Textures/Alpha interface is driven by the Alpha "dosc" TCL
command, 

\# which sends an Apple Event of class 'misc', type 'dosc' to
a target 

\# application. The 'dosc' (do script) event supplies a
script parameter, 

\# which is interpreted by Textures as \TeX{} source
code to be typeset. 

\# In the sample below, "-c '*TEX'" refers to the
Textures application 

\# signature; "-s [getText 0 [maxPos]]" sends the
full text of the current 

\# window as the script, and "-r" indicates
that no reply is expected. 

\#

\# We will appreciate suggestions on the interface, and contributions

\# of Alpha scripts that exploit it effectively.

\#

|proc GoTeX {menu item}|

\hskip 1em|  {dosc -c '*TEX' -s [getText 0 [maxPos]] -r}|

|menu -n Textures -p GoTeX {Typeset}|

|insertMenu Textures|
}


\sub{emacs, editors}

Q. I've got emacs and I'd like to use it with 
Textures.  How do I do it?

A. You must have version 1.13b2 (or later) of emacs, and the
instructions for controlling Textures through Apple Events 
are in the file "Textures.el" in the "Lisp" directory.

\sub{error, \TeX{} save temp, not enough room}

Q. I get the error message: 'I'm having trouble with
\TeX{} save temp, not enough room'. What's wrong?

A. In general the only time you would see this message
is when you are trying to typeset a Textures file that
is on a locked floppy disk or a floppy or hard disk
that has run out of available space. Less frequently,
the document itself is locked. The solution, of course,
is to typeset and save to an unlocked volume with lots
of free space. 

\sub{edmetrics, System 6, crashing}

Q. I received a copy of the EdMetrics font metrics
editing utility with my copy of Textures 1.6, but it
crashes when I try to use it on my System 6 Macintosh.
Is there a fix for this problem?

A. A new copy of EdMetrics is now available that runs under System 6.
It's available by anonymous FTP from ftp.bluesky.com in the
/pub/utilities directory.

\sub{macros, cleanup, preferences}

Q. I've been playing around with the Macros menu in
Textures. Now I'm ready to get serious, but I would
like to clean out all the stuff already in the menu.
How do I do that?

A. There are three ways to remove the contents of the
Macros menu:

1) You can put together a file containing entries you'd
like to use in your macros menu and paste the entries
into the menu using the Macros/Edit/Paste Menu command;
the new menu will replace all the old stuff you've
already got in there;

2) You can Edit/Copy a carriage return character from a
text file and then Macros/Edit/Paste Menu; that will
effectively replace all the old stuff with a carriage
return, which doesn't do anything (except wipe out the
old menu, of course);

3) If these macros are for Textures' built-in Plain
format, you can find the Textures Preferences file in
the System Folder's Preferences folder and throw it
away; that's where the Macros Menu for the Plain format
(and {\bf only} the Plain format) is stored.

FYI---The Macros Menus for \LaTeX, \amstex, and all
formats other than Plain are stored as a resource
within the format file, so only options 1 and 2 will
work to delete old menu information for them.

\sub{macros, \LaTeX, samples}

Q. Where should the \LaTeX{} Macros Menu file (in the
Sample \LaTeX{} Menu folder) be installed?

A. Copy the file anywhere onto your hard disk, then
open the file with Textures. Select the \LaTeX{} format,
select all of the text in the sample file, copy, and
use the Macros menu's Paste Menu function to attach the
menu to the \LaTeX{} format. The macros in the sample will
then be available immediately for use in your \LaTeX{}
documents.

\sub{insertion point, macros}

Q. Why doesn't the setting of the insertion point
in my macros work?  It appears in the wrong place!
I have Textures version 1.6.2.

A. This is a known problem, and a replacement disk can
be sent to you -- call or write us and we'll send you Textures
1.6.3, or you can upgrade to  Textures
1.7.

\sub{postage stamp, memory, errors}

Q. I get an error message when I $\bullet$ open my document
$\bullet$ typeset my document $\ldots \bullet$ my document appears as
a postage stamp. What can I do?

A. Often problems associated with the typeset portion
of a document (the resource fork) can be fixed by simply
pasting the contents of the edit window into a new
document and retypesetting. 

\sub{printing, system, shared printer, crash}

Q. My Mac keeps crashing when I try to print ---
and I'm using the 8.1.1 driver!  What's wrong?

A. If the stylewriter 1.2 driver and the shared
printer software are both installed along with the
laserwriter driver, printing and System failures can
occur.  Removing the shared printer software and/or
upgrading to the fixed stylewriter driver should help.

\sub{NeXT, CR}

Q. How do I convert CR to line feed for Mac-to-NeXT
conversion?

A. There's a program called tr for Unix users.

\sub{NeXT, metrotools}

Q. Can I convert my Mac PostScript fonts into NeXT format?

A. MetroTools <emailinfo@metrosoft.com> does this very
well.  Price = \$69.

\sub{Framemaker, cmvtt10}

Q: Framemaker gives me an error message about ``Bad Font Family'' in
reference to cmvtt10.


A:  This is a Font ID conflict, since they
mention resource ID 26537. Basically, bitmap fonts in
the Mac system are known by a 16-bit resource ID
number; it's quite possible, when you have lots of
fonts, for these ID numbers to collide between font
suitcases.   (Two distinct fonts with the same resource
ID numbers.)  It would be nice if they told you what
the {\bf other} font is...

There are a few commercial tools, such as those that
come with Suitcase, that will resolve Font ID conflicts
by reassigning one of the IDs.  If you're using System
7.1, it's ``supposed to'' do this automatically (I
think) for all fonts in the Fonts folder.  Any System 7
version can also be used to (semi-automatically)
resolve ID conflicts by (manually) dropping *all* your
bitmap fonts into *one* suitcase; this forces conflict
resolution to happen for all fonts in that suitcase, so
it works for all fonts.

If you have ResEdit, you can snoop your font suitcases
looking for another FONT (or NFNT) resource with ID
26537, to get an idea of where to apply the fix.
A genuine pain; perhaps the simplest solution is to
take out cmvtt10, since it's very rarely used.


}
\vskip1.25in

\font\namefont=Times at 10pt
\baselineskip=14pt
\parskip=0pt
\def\own{\namefont 
Blue Sky Research, 534 SW Third Avenue,
Portland, Oregon 97204 U.S.A.}

\hskip0pt\hbox to \bodycolumn{\own}
\hbox to \bodycolumn{\namefont 800/622-8398 \hfill 503/222-9571 \hfill
Fax: 503/222-1643}

\bye