[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::document_ft

Title:DOCUMENT T1.0
Notice:**New notesfile (DOCUMENT.NOTE) now available (see note 897)**
Moderator:CLOSET::ADLER
Created:Mon Feb 09 1987
Last Modified:Thu Oct 31 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:897
Total number of notes:4397

48.0. "How does T1.0 convert...." by GRAMPS::ANGELONE (Ghostwriter) Tue Mar 03 1987 09:28

    One of the capabilities of Version T1.0 was to convert .GNC
    files to an ASCII file (I thought).  Is this so and how do
    I do it ???????????
    
    
    Rick A
T.RTitleUserPersonal
Name
DateLines
48.1MAILCLOSET::ANKLAMTue Mar 03 1987 09:295
    
    Use the MAIL destination. 
    
    patti
    
48.2GRAMPS::ANGELONEGhostwriterTue Mar 03 1987 14:4816
    Thanks.
    
    Finally got our copies of the USER'S GUIDE (Part I and II).
    
    I used "DOCUMENT/DEVICE_CONVERT fielname DOCTYPE MAIL"
    and it produced a filename.TXT file (but I had to go look for
    it, DOCUMENT did not tell me it produced the .TXT file)
    
    
    ALSO PATTI.............could you look at my note #46.
    Reply #1 ask for an example but I do not how to give.
    All I know is that a file that runs perfect in GENERAL will
    go off the page in other DOCTYPES.
    
    
    Rick A
48.3Also TERMINALSTAR::ETZELMikeWed Mar 04 1987 13:025
    I've used the TERMINAL output device also. Unlike MAIL, TERMINAL
    bolds headings and so forth using escape sequences. It also seems 
    to print fine on an LN03--haven't tried it on other printers.
    
    
48.4hardcopy terminals, tooVAXUUM::DEVRIESUndetected errors will not be fixedWed Mar 04 1987 13:307
    The TERMINAL output will print fine on all DEC printers (I know
    of) except line printers (since these don't do graphic renditions 
    on command).  Printers whose native tongue is PostScript require
    an ANSI translator, of course, but that's a standard part of the
    package for DEC expanding line of PostScript printers.
    
    (I suspect this won't print on PLOTTERS.)
48.5Didn't work on my printers...COOKIE::JOHNSTONFri Mar 06 1987 14:486
I tried printing a .TT file on the LN01, LN03, and line printer without 
success.  The text is not formatted; it runs all together.  Are there 
certain qualifiers you must specify to print a .TT file?


Rose
48.6CUPOLA::HAKKARAINENAstray into the futureFri Mar 06 1987 15:315
    No special qualifiers are needed to print the .tt file on the LN0x
    printers. (Wierd stuff will probably happen on the line pinter.)
    
    The same file that looks correct when TYPEd on your terminal looks
    jumbled when PRINTed?
48.7Yes, it's jumbled on an LN03COOKIE::JOHNSTONFri Mar 06 1987 16:1412
Yes, it looks jumbled.  I just tried it again.  FYI, I am typing

$ LN03 filename.tt

LN03 resolves to PRINT/QUEUE=LN03_N23/PASSALL/NOFEED/NOTIFY


Also, I copied the .tt file from one cluster to another before printing 
it.


Rose
48.8Remove /PASSALL and /NOFEEDRTOADB::CAAHANSHans Bachner, ADG MunichMon Mar 09 1987 09:267
    Well, it's just a guess ...
    
    Remove the /PASSALL and /NOFEED qualifiers from your PRINT command
    when printing files without the special LN03 <ESC>-stuff.
    
    Good luck,
    	Hans
48.9May still need the NOFEEDATLAST::BOUKNIGHTEverything has an outlineMon Mar 09 1987 11:315
    I agree with the PASSALL qualifier, remove it. However, you may
    still need the NOFEED qualifier if DOCUMENT has been counting lines
    for you and putting in FFs.
    
    jack
48.10the less said, the betterVAXUUM::DEVRIESUndetected errors will not be fixedMon Mar 09 1987 16:085
    I print .TT files without either /PASSALL or /NOFEED qualifiers,
    and it works fine here.  Most of our queues have /FEED as a default
    characteristic of the queue, if that matters to anyone.
    
    mark