Conference vaxuum::document_ft

    
    I wasn't aware that there was an AMGR for the lineprinter/mail/
    terminal output. (Does PICMODE work for the line printer? --please
    excuse my ignorance of this program.) Does anyone know of such
    a font file? We don't seem to have it here.
    
    patti
    

It's generally not a good idea to mix TeX files from elsewhere with DOCUMENT's
 TeX files.  AMGR.TFM will be found in somebody's TEX$FONTS directory (there's
  one in VAXUUM""::SYS_:[TEX.FONTS], for example) but it's no good without a
   corresponding font file, and I don't think such a beast exists for DOCUMENT's
    DVC$LPRSHR device converter (the one that does mail and terminal output).

Font files supplied with DOCUMENT are not interchangeable with those used in
 plain TeX or LaTeX.  We're going with a different encoding scheme.
  <_Jym_>

    Re: .2
    
>    Font files supplied with DOCUMENT are not interchangeable with those used in
> plain TeX or LaTeX.  We're going with a different encoding scheme.

Does this mean that the $5000 royalty I've paid to Compugraphics (via
    the SDC) for the Complete office font pkg for the Ln03 is of no
    value for DOCUMENT and I must pay Compugraphics another exhorbitant
    fee for the same fonts but in another format.
    
    Michael

    Ahhhh.....
    
    And I thought PICMODE was something from the same development group
    as DOCUMENT. So now, on the basis that PICMODE is different and 
    will (probably - maybe????) loose support before long (given the font 
    changes you mention), what will we be able to use for doing similar 
    style graphics (to PICMODE). 

    Regards
    Kevin M

   > ... I must pay Compugraphics another exhorbitant
   > fee for the same fonts but in another format.

There are substantial differences in the font packages for DOCUMENT and
DECpage, differences which go beyond "a different encoding" for "the same
fonts". We're using a wider range of point sizes and weights than are found
in the COMPLETE OFFICE kit (6,8,9,10,11,12,14,18,24,30,36pt roman, bold, 
italic and bold italic), and also include several publishing characters
(e.g. bullets and em- and en-dashes) in all of the fonts. In addition, we
provide a full set of monospaced fonts (7,8,9,16pt roman, bold, italic, bold
italic). And as far as I know, the internal transfer cost should only be
around $1300. A bargain...

--Brian

    re: .4 A number of people have requested that the DOCUMENT group
    look into PICMODE as a Version 1.n feature. We will do this. I suspect
    that support will continue informally, and we (DOCUMENT group) won't
    do anything that will prohibit its use.
    
    patti anklam
    

    Re: .5
    
    Thanks Brian $1300 internal isn't all that bad -- it just seems
    that fonts (mgmt and licensing) are sometimes out of control in
    this company when you look at it across products...
    
    Michael

    Re: .7
    
    > ... it just seems
    > that fonts (mgmt and licensing) are sometimes out of control in
    > this company when you look at it across products...
    
    Unfortunately, that's the state of the publishing world everywhere.
    Fonts are an art and, as such, good fonts are precious creations.
    People who own such things hold them close to their vests, guard
    them jealously, and charge big fees to use them.  Therefore, fonts
    are not standardized between type manufacturers -- or even among 
    companion products from the same manufacturer.
    
    To keep the royalty costs down, font users (like DECpage
    and VAX DOCUMENT) try to identify the set of characters, sizes and 
    faces they need for their target markets, and offer only those fonts.
    
    Add to that the fact that we use terminals, workstations, etc.,
    that were not necessarily designed to be good typographic preview
    stations (putting it mildly), and you get some idea what a hodge-podge
    the font world is at present.
    
    There is some work among national and international standards groups
    to make things more uniform but, of course, that gets a lot more
    support from those who *want* the fonts than from those who *have*
    the fonts.
    

    I hate to revisit this dead horse... but AMGR has reared its ugly head
    again in the form of PICMODE.  I have DOCUMENT V1.0 on two different
    machines. The PICMODE picture works on one but not the other.  The log
    below is what shows up. 

    Background -- This worked before V1.0 was installed.  After
    installation I started getting the error on our local VAX.  I copied
    the AMGR files from the other VAX (also with V1.0) and now it works.
    BUT, the VAX I copied the AMGR fonts from doesn't work (the log
    is from there).  What the heck?
    
    BTW:  What is the status of PICMODE?  Is it supported?  Can we
    legitimately use it in DOCUMENT?  Internally of course.  If not,
    what is replacing it?  
    
    thanks,
    Dave P
    
[ C o n t e n t s   G e n e r a t i o n ]...
[ T e x t   F o r m a t t i n g   C o n t e n t s ]...
%TEX-I-IDENT, V1.0
%TEX-I-PAGESOUT, 3 pages written.
-TEX-I-OUTFILENAME, 'disk$:[abcd]PROFILE_CONTENTS.DVI_LN03'
[ D e v i c e   C o n v e r s i o n ]...
%DVC-I-IDENT, DVC$LN03 V1.0
%DVC-W-FONTERROR, error in font 
DOC$ROOT:[TEX.LN03.FONTS]AMGR.NFT;
-DVC-W-BADFONT, font file bad -- using blanks
-DVC-I-INPUTFILE, input file is: 
DISK$:[abcd]PROFILE.DVI_LN03
%DVC-I-INCLUDING, including input file: 
DISK$:[abcd]PROFILE_CONTENTS.DVI_LN03;
%DVC-W-IGNORING, ignoring included input file 
DISK$:[abcd]PROFILE_INDEX.DVI_LN03;
-DVC-W-NOINCLUDE, cannot open included file
-DVC-I-INPUTFILE, input file is: 
DISK$:[abcd]PROFILE.DVI_LN03
-DVC-I-ONPAGE, on page [1] 
%DVC-I-PAGESOUT, 32 pages written to file: 
DISK$:[abcd]PROFILE.LN03
[ C o n t e n t s   D e v i c e   C o n v e r s i o n ]...
%DVC-I-IDENT, DVC$LN03 V1.0
%DVC-I-PAGESOUT, 3 pages written to file: 
disk$:[abcd]PROFILE_CONTENTS.LN03
$ exit ($status + (0 * f$verify(verify_context))) ! SYS$SCRATCH:DOC$PROFILE.TMP - End
  abcd        job terminated at 28-JUL-1987 14:57:38.49

    

 It sounds as if the file containing the AMG fonts is currupt. I'd
 suggest you copy them once again from 
      TALLIS::S1:[TEX.FONTS]AMG*.TFM  DOC$LN03_FONTS:*.TFM
      TALLIS::S1:[TEX.LN03DIR]AMG*.*  DOC$LN03_FONTS:*.NFT

(they should be addressable by TEX$FONTS and TEX$LN03DIR names for
the device/directory if the above is not correct - otherwise try us
on IJSAPL).

From Flavio Rose, who made Picmode, I was told Picmode was free, unsupported
and could even be given to customers on this "as-is" basis, e.g. for
those using LaTeX

Theo

    I figured it had to be something obvious like that, but I didn't
    know where to find an extra set of fonts.
    
    I got an AMGR.NFT and and AMGR.TFM and the world appears to be 
    happy again.
    
    Thanks,
    Dave P