Conference vaxuum::document_ft

    If the logo is created as a sixel file it can be called into the
    document with the <FIGURE_FILE> tag. 
    
    Sixel files can be edited to control their horizontal placement in the
    output. By varying the point in the .GNC file at which the figure is
    called and the amount of figurespace that's given, the figure (logo)
    can be made to appear almost anywhere in the output. 
    
    I created a CUPSS logo for our group, and it's being used in headers
    and footers. Contact me via mail if you would like to see examples of
    the sixel and .GNC files. 
    
    
    				Lance

    That is fine for ln03 output. Has anyone done a DEC logo for the
    postscript output. I have a postscript file that draws a DEC logo,
    bu what we really need is to have it set up as an element of a 
    postscript font.
    
    Ken Serack
    

    The DEC logo on the copyright page is the 'boxed' format, like the
    signs out front, when done in postscript.  So, its around somewhere.
    
    jack

    
    I've been doing it in BL06 in the following manner:
    
<CENTER_LINE>(<INCLUDE_TEX_FILE>(digital.lgo))
    
    where the TEX file DIGITAL.LGO is: 
    
\declogo                  
    
    but when I run this in BL07 I get the following:
    
(ENDOTRON$ROOT:[REHOR]LOGO.TEX;4 (DOC$ROOT:[TEX.FORMATS]DOC$STARTUP.TEX;1 (NL:[
].TEX;) (DOC$ROOT:[TEX.FORMATS]TAG$GENERAL.DTP;1 (DOC$ROOT:[TEX.FORMATS]TAG$STA
NDARD_FONTS.LN;1)) (DOC$ROOT:[TEX.LN03.FONTS]LN03CHARS.TEX;1)) (ENDOTRON$ROOT:[
REHOR]DIGITAL.LGO;1
%TEX-E-TEXERROR, Error found by TeX

%TEX-I-ONPAGE, on page [1]

%TEX-I-OUTFILENAME, 'endotron$root:[rehor]LOGO.DVI_LN3'
.
l.1 \declogo
            
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.

))
No pages of output.
%TEX-I-PAGESOUT, 0 pages written.

%TEX-I-OUTFILENAME, 'endotron$root:[rehor]LOGO.DVI_LN3'

     

    The \declogo macro is no longer defined in system definitions in
    T1.0. You have to add the definition to your doctype. There's a pointer
    to this in the release notes...
    
    Michael

    From the old DOCUMENT notes file:

               <<< VAXUUM::W7_:[NOTES$LIBRARY]DOCUMENT.NOTE;4 >>>
                     -< Old Versions of DOCUMENT *Only*! >-
================================================================================
Note 369.0                   Where is Digital Logo?                    6 replies
NACHO::ROSENBERG                                      4 lines  22-SEP-1986 11:35
--------------------------------------------------------------------------------

    Can somebody tell me how to put the Digital logo on the copypage.
    Is there an existing Digital Logo file that can be used as an Icon?
                                                                     
    

               <<< VAXUUM::W7_:[NOTES$LIBRARY]DOCUMENT.NOTE;4 >>>
                     -< Old Versions of DOCUMENT *Only*! >-
================================================================================
Note 369.1                   Where is Digital Logo?                       1 of 6
CLOSET::ANKLAM                                        9 lines  22-SEP-1986 19:00
                                 -< \declogo >-
--------------------------------------------------------------------------------

    
    
    There is no icon file. The DEC logo is produced from the TeX
    macro \declogo. We don't provide any explicit tag that writes it
    to the output file, but you should be able to create one. (I have
    had this request before, and will try to include it as a 'local
    special' in the next release.
    
    patti anklam

--------------------------------------------------------------------------------

    Well...?  :-)
							-- Nina

    
    Yes, you're right I forgot. Until I get it into an internal release,
    if you really need it you can define it yourself using
    
    <define>(DECLOGO\^Tdeclogo^B^E)
    
    where ^T, ^B and ^E are really the control characters
    CTRL/T, CTRL/B and CTRL/E. You should put this a file that you specify
    with /INCLUDE on the command line.
    
    Note that what you get is what you get. You cannot change the size;
    when you use it, it may do funny things to where related text is
    set; it doesn't appear in running titles (because it is too big).
    Support for it is not high on my list.
    
     You must have the definition of \declogo someplace. (In 
    the DEC internal kit, it's in CUP$LOCAL_ELEMENTS.TEX; you may need
    to define this file as DOC$LOCAL_ELEMENTS.) I will try to think
    of somewhere to put it in the local kit (there's no tag definition
    file corresponding to DOC$LOCAL_ELEMENTS...)
    
    patti
    

                                     
    
    
    I have a .LN3 DEC logo file which could be called into a .GNC file as
    an icon or figure. If this is useful to you contact me.
    
    				Lance 

    Is the logo feature suppored on the LPS40?
    
    

    
    It was not very precise for me to call the file I was refering to a
    .LN3 file. It is a sixel file that is formatted for output on an LN03.
    It was produced in GRED and processed through RENDER. RENDER can also
    process files for output on LN03PLUS and Postscript devices. I haven't
    tried the latter but I'm pretty sure it works.
    
    
    				Lance 

    
    the definition in use via CUP$LOCAL_ELEMENTS doesn't print the
    DEC logo as we are used to seeing it (white letters on black
    background), it merely boxes the letters to give them a distinctive
    appearance. We need to look further into font/character generative
    for post script devices.
    
    -pa

    Is it not true that the POSTSCRIPT version of the DEClogo is the
    correct corporate logo? After all, the signs out front of the buildings
    do not show white letters on a dark background.
    
    jack

    
    You could be right. I know that there is (yet another) committee
    at work on a 'corporate identity program'. Perhaps they will have
    a word on the logo.. 

    I have a copy of a 1980 edition of the Corporate Identification
    Manual (found in a trash bin one day) and it gives a lot of
    detail about the corporate logo.  It also gives a lot of 
    unacceptable variations.
    
    In 1980, it gave some acceptable variations, one of which was
    the standard lowercase letters in outlined boxes.  That is,
    the background is light, the box outline is dark, the inside
    of the box is light and the letter is dark.
    
    I've no idea of what the latest word is - haven't been around
    to trashbins lately.
    
    

    I've noticed that if I print an .LN03 file on the LPS40, the logo
    is printed white on black boxes, while the .POST version produces
    the black on black outlined boxes.  This shows that it's possible
    to get either version on the LPS40, though it doesn't say anything
    about how easy it is for Document to generate it.
    
    I think that the white on solid black is as close as a black & white
    printer can come to the white on blue, which is what official
    stationery uses.  Of course, the Legal Department may wish to express
    an official opinion.
    
       Gary

>   I think that the white on solid black is as close as a black & white
>   printer can come to the white on blue, which is what official
>   stationery uses.
    
I've seen official stationery with white on grey...


--Brian (who's calmly waiting for the dust to settle)

    I think Jack is pushing for the OUTLINEd logo for an alterior motive.
    Is it possible that he's right?  That everything really does have
    an outline?
    
    -tl
    

    the "old" corporate identification manual doesn't specify
    the colors for the logo, it merely says that there are only
    two colors.  The "background" color, and the solid box color.
    The letters which are cut out of the solid box should be the
    same as the surrounding background.  So you can have a black
    box over a white background, in which case the letters are
    white, or a blue box on gray paper, in which case the letters
    are gray.  But you can not have white letters on a black box
    on grey paper.
    
    

    BTW, I'm as guilty as anyone.  OUTLINE does it open boxes on all
    printers except POSTSCRIPT where it does it with BLACK boxes.
    
    Actually, I would prefer the outlined box approach because that's
    the only one that can be done on pin printers like the LA50, LA100,
    LA210, etc, and I generally vote for consistency.
    
    We got both BLUE and GREY stationary down here.  Some of us don't
    carry any Civil War grudges any more.
    
    Jack

    
    A trademark attorney in the Law Dept. told me that a Peter Phillips
    was 'in charge' of the Digital logo. Something to do with Corporate
    Identity (scary, huh!). 
    
    Anyhow, the OFFICIAL Digital trademark is with the letters themselves
    being the same color as the background (white page = white letters), and
    the boxes around the letters are supposed to be _filled in_ with a
    contrasting color.                                  
    
    				Lance

    If so, I presume that the POSTSCRIPT version of the logo then needs
    to get changed sometime.
    
    jack

    Right.
    
    Lee

    Maybe I'm missing something.  I'm also fairly new so bare with me.
    I can't seem to get a logo on my title page.  I don't know how to
    get the logo out of CUP$LOCAL_ELEMENTS.  Can someone give me a clue?
    
    By the way, I'm running V1.0.
    
    I also have the logo file sent out by Lance (GNUVAX::LIBRARIAN)
    and couldn't get that to work either.  I tried the <ICON> and the
    <INCLUDE> tags with no luck.
    
    Mike
    

    
    see .7 (I will try to get this into the internal kit post-V1)

    I have always included graphics into Document using the <figure_file>
    tag. Below is a BL.7 sample which I just tested and should work
    correctly. If you still have problems contact me via MAIL and I'll try
    to help.
    
    I can also tell you how to control the horizontal and vertical position
    of the logo on the output page. 
    
    
    				Lance

    
    
<p>
This is text that appears above the figure.
<figure>(This is the Digital logo)
<figure_file>(ln03\dec_logo.ln3\2)
<endfigure>
This is text that appears below the figure.
    

    For those of you that would like to try the DEC logo that in the
    file mention in .7, you might try what I did.  This logo is one
    of the best I've seen.
    
    Edit the .TEX file and insert a \declogo where you would like it
    to appear.  Works great for me but when doing this you must format
    it using :
    
    $ DOC/NOTAG file doctype dest
    
    For an added thrill :-) try inserting the \copyrightline macro in
    your copyright page.
    
    Mike
    

    
    
    So, what is the final word on the PostScript DEC logo? Is is fixed
    for V1.0, so that it is not the outlined boxes? If not, our writers
    need to know what the plans are.
    
    Thanks,
    Ken Serack

    I just wanted to mention one thing about the DEC logo in PostScript
    implementations I have seen so far.  It isn't totally correct.  It 
    appears what is happening is that the Helvetica typeface is being 
    used.  Well, most folks probably wouldn't notice, but our logo's
    typeface is not Helvetica. In fact, it isn't any standard typeface 
    I can find.  My guess is that it was originally rendered by hand.  
    That would mean the only way to faithfully reproduce the logo in 
    PostScript would be to scan it (using *at least* 1200 dpi), or to 
    recreate it using a tool such as Adobe Illustrator (which I think 
    would be best because it allows for resolution idenpendent scaling).
    
    Our group will be getting Adobe Illustrator sometime in the near
    future, and one of the first jobs I have in mind is to do a proper
    version of our logo.  If this would be of use to the DOCUMENT
    developers please send me MAIL and we can work out the details.
   
    -- Craig
    

    Designing the logo as a PostScript font shouldn't be too hard,
    should it?
    
    --Andrew

        like any other problem it is a SMOP.
        
        
        
        Simple Matter of Programming.
        
        Feel free to do it...
        
        q
        

    Re .30:
    
    I hope the VAX DOCUMENT developers aren't taking this as lightly
    as you seem to be.  An *accurate*, high quality corporate logo for 
    PostScript output should not be something that is left to whoever has 
    the time to do it.  It should be done by the DOCUMENT developers, 
    approved by corporate graphics (or whoever has responsibility for 
    making sure we present our corporate identity in a consistent and high
    quality fashion), and officially released to all VAX DOCUMENT users.
    
    I hope I don't offend anyone, but I've got to say that the beating
    our logo has taken over that past few years is pretty sad.  Without
    leaving my chair I can find four different versions of our logo
    which have been published, and only one of them is correct (according
    to the version of the Corporate Identification Manual I have). 
    
    I'll admit that I've committed this sin as well.  The latest version
    of the DECwest Illustration Guide contains an imperfect version of our 
    logo available in our GRED library.  Even though it's the best one 
    currently available for PostScript output, it still isn't as good as 
    it should be.  I have just deleted it, and am going to wait until we 
    can produce a correct version, or one is provided for us.  I hope 
    others will do the same.
    
    Could anyone from CUP Engineering provide an update on the approach
    that is being taken to provide an accurate logo for PostScript
    output?

    I'll get off my soapbox now, thanks for listening.
    
    -- Craig

             <<< SYS$SYSDEVICE:[NOTES$LIBRARY]POSTSCRIPT.NOTE;1 >>>
                                -< PostScript >-
================================================================================
Note 26.0                    PostScript Digital Logo                   2 replies
PAUPER::LOMICKA                                      49 lines  13-SEP-1985 17:22
--------------------------------------------------------------------------------

^P *** Change to real control-P and use with ascii.ps to execute example below.

% digital_logo.ps by Roy Lomicka, September 13, 1985 
% 
% adapted from similar program by Brian Reid, Stanford 
% 
% refinements to better match the artwork in the DEC
% Identification Manual supplied by Scott Robinson

/digital-logo-font /Helvetica-Bold findfont 
[35 34 div .65 mul 0 0 .75 0 0] makefont def

/box-width 35 34 div .405 mul def
/box-pitch box-width .85 div def

/digital-logo-box { 
  gsave 
    box-pitch box-width sub 2 div -.225 rmoveto
    box-width 0 rlineto 
    0 1 rlineto box-width neg 0 rlineto 
    closepath fill 
  grestore 
  gsave
    dup stringwidth pop box-pitch exch sub 2 div 0 rmoveto 
    1 setgray 
    show
  grestore
  box-pitch 0 rmoveto
} def 

/digital-logo {
  % draws digital logo with left baseline point at current point with
  % specified height using current color for boxes and white letters 
  % and moves current point in x direction by about 3.433 times height
    currentfont exch % save font 
      matrix currentmatrix exch % save matrix
        dup scale 
        digital-logo-font setfont 
        0 1 6 {(digital) exch 1 getinterval digital-logo-box} for 
      setmatrix % restore matrix
    setfont % restore font
} def 

% example of mixing logo with ascii text
5 characters-per-inch
ascii
Our logo (^P *** Change to real control-P.
24 point digital-logo ascii
) contains 7 letters. 

    I just took a look at the logo posted in .32.  It's very close,
    but still not correct.  Close comparison with the official logo
    will reveal that the "t" is quite a bit different, as are the curved
    portions of the "d" and "g".  The weight of all the letters is a
    bit too heavy as well.  These are the same problems I had with the
    logo we did in GRED, and they all stem from using the Helvetica
    typeface.
    
    This version is *much* better than the one currently being provided
    for DOCUMENT's PostScript output (the code is shorter than the
    GRED version too), and could serve as a replacement until a 
    truly correct logo can be provided (don't forget to add the "TM" 
    though).
    
    -- Craig   

    I have heard from a source in TBU that they are working on an
    officially-supported DEC logo for PostScript.  I don't know what
    approach they are taking, but since they are the central source
    of fonts and PostScript support for the corporation, I suspect they
    are committed to doing it right.
    
    --Mark