[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

518.0. "DOC$CONVERT incorrectly renames .ldf,.gdf" by COOKIE::JOHNSTON () Wed Jun 17 1987 12:50

The BL6 --> BL8 converter changes statements like
<include>(filename.ldf) to <include>(filename.sdml).

I am converting documents that I haven't looked at since December '86, and 
this is confusing; my first impression is that I must have had a .GNC
file there, when in fact it's a defs file that is no longer required.

I think the converter should either delete the <include>(xxx.ldf/.gdf)
syntax or leave the file type alone.  Of course, if the converter is going 
by the wayside for V1.0, this might be a moot issue at this point.



Rose
T.RTitleUserPersonal
Name
DateLines
518.1I reported something similarTLE::SAVAGENeil, @Spit BrookWed Jun 17 1987 15:418
    A similiar thing happened to one of the writers in our group.  She
    had an <include>(somethingorother.gdx) tag that was changed to .sdml.
    She had to manually reedit to change the file type back because
    the file contained essential data for her template.
    
    This should be looked into.  The majority of our writers have NOT
    begun to convert their files, so we'll need DOC$CONVERT for several
    months yet.
518.2CLOSUS::TAVARESJohn--Stay low, keep movingWed Jun 17 1987 16:4113
Really doesn't make much difference anyhow.  If you use the
<include> to bring in a global definitions file, the processor
blows up on that file.  The book says that you should use the
/symbols=filename.sdml switch on your command line to bring in
globals; I haven't gotten that to work yet, either.  Our system
just ignores the "/symbols="

Until it gets straightened out, I'm putting my defines at the top
of the first file that uses them; when I run the profile, or a
makebook, these defines get read into the .xref file.  Sometimes
this creates an error that says that "aardvark has been
defined twice and that I'm your last definition", or words to
that effect.  But it gets the job done...    
518.3/SYMBOLS gets ignored?CLOSET::KOHLBRENNERThu Jun 18 1987 09:567
    I'd sure like to know about a system that ignores the /SYMBOLS
    qualifier!   Can you supply some more detail?
    
    WHat baselevel?  What error messages?  etc.
    
    bill
    
518.4CLOSUS::TAVARESJohn--Stay low, keep movingThu Jun 18 1987 11:1624
I was running a book that was converted from bl6.  Of course, I
found out quickly that all that gdf and ldf stuff didn't work
anymore.  So I checked in the manual and found the /symbols
qualifier.  I renamed the gdf file .sdml, and put the /symbols
qualifier on the command line.  When I processed the document, it
said that the book names I defined in the globals file (yes, I
did change the defines to define_book_name) were undefined.  I
followed the manual to the letter.  Then I switched the \profile=
and \symbols= qualifiers on the command line, putting \symbols
first, thinking that maybe there was some reason why it wasnt
picking up the second qualifier.  Again it ignored the /symbols
and picked up the \profile.

When we had .gdf files, we put a standard bit of stuff at the top
about including the .gdf file only once.  This was to keep the
processor from picking the same stuff up when we do a bookbuild.
In the converted file, I both left that stuff in, and took it
out, no difference.  This is, I think, because the processor is
not going to that file at all.

Hope this is enough info....

I know that we are running bl8, but that's about all I know about
it.
518.5false alarm on /SYMBOLS qualifierCLOSET::KOHLBRENNERThu Jun 18 1987 18:3413
    re: .2 and .4 (/SYMBOLS qualifier not working)
    
    For those who are holding their breath to see under
    what conditions the /SYMBOLS qualifier did not work:
    
         Surprise!  It works...  
    
    ( A COM file supplied by someone else was dropping
      the /SYMBOLS qualifier -- hence it did not get a
      chance to work.   -  whew!)
    
    bill