| You don't need anything to do with MAKESDF FOR BL7. MAKESDF was a pre-BL7
program that generated .LDF and .GDF files (local definitions and global
definitions). The PROFILE does this for you now, creating a .XREF file that
performs the same function as the .LDFs and .GDFs, only *much* better.
If you try to do anything with MAKESDF, you are *regressing*.
Remember, DSR2GNC converts .RNO files to BL6 .GNC files. You then have to run
the .GNC files through DOC$CONVERT which converts them to BL8.
To the world at large: if you are converting original BL6 files to BL8,
you should go into your files and delete any references to .LDFs and .GDFs
before running the DOC$CONVERT program. If you don't, DOCUMENT will rename
those files to .SDML files.
Rose
|
|
Note: All examples in the following text assume that you are using
Peter Wiitenan's unofficial DSR2GNC conversion program.
1 Be sure the DOC$CONVERT program is on your system and that you
have a pointer to it. DOC$CONVERT was installed in DOC$LOCAL_
TOOLS:DOC$CONVERT_06_FILES.EXE. If a pointer to DOC$CONVERT
isn't system-defined, you can define a pointer in your
login.com file; for example:
$ DOC$CONVERT:=="$COOKIE::DOC$LOCAL_TOOLS:DOC$CONVERT_06_FILES.EXE"
The dollar sign ($) preceding the file spec indicates that the
file is of an .EXE type and should be "run" (similar to the @
sign, which indicates a .COM file should be executed such as
@login).
2 Be sure the DSR2GNC program is on your system and that you have
a pointer to it.
3 Keep a hard copy of your .MEM file nearby. You'll want to refer
to it occasionally to see how the final output was formatted
in DSR.
4 Break up any large documents into smaller documents; at the
very least, be sure that each file contains at most one
Chapter. Breaking the files up will make conversions easier
and put the files in the right format for a DOCUMENT PROfile,
which you will create later.
5 Be sure each file processes without error when you run it
through DSR. Any errors at the DSR level will only multiply
as you take your file through the conversion process.
6 Depending on whose DSR2GNC program you have, auto paragraphs
may or may not be replaced by <P> tags. (Peter's instructions
say that auto paragraphs are retained, but they weren't when I
ran it. This may have something to do with the fact that the
.AUTO PARA command was called into my .RNO file versus being
locally coded.)
You can test auto paragraph retention by observing where a
paragraph should be in the .RNO file, then running it through
DSR2GNC and noticing whether a <P> tag was inserted. When you
execute DSR2GNC, do not specify the .RNO file type (for Peter's
version, anyway):
$ @DSR2GNC MY_DSR_FILE
If no <P>s were inserted where they should have been, edit
your .RNO file so that auto paragraphs are replaced by the .b
command. In EDT, you would do it like this:
GOLD SUBSTITUTE
OLD: <CR><CR>
NEW: <CR>.B<CR>
GOLD 1000 <ENTER>
It will be easier for you to delete any extraneous <P>s than it
will be for you to add them later.
7 When you run DSR2GNC, ignore any error messages such as "7
diagnostic messages reported" or "error activating image MAKE_
IMAGE_MASK". I believe MAKE_IMAGE_MASK is associated with
MAKESDF, a BL6, now obsolete program used to help resolve
cross-references.
8 DSR2GNC saves your .RNO file and creates (in Peter's version
running on my system, anyway) two BL6 .GNC files, which in BL8
are called .SDML files. The two .GNC files are exactly the same
files, so you can delete one of them.
9 Edit the remaining .GNC file, deleting the <INCLUDE>(FILE_
NAME.LDF) and <INCLUDE>(FILE_NAME.GDF) tags that DSR2GNC
created. These tags were required in versions prior to BL07.
For example, if your file was called MY_FILE.RNO, DSR2GNC
created two tags and put them at the top of MY_FILE.GNC:
<include>(my_file.ldf)
<include>(my_file.gdf)
10 Execute DOC$CONVERT. This program converts the BL6 .GNC file to
a BL8 .SDML file.
$ DOC$CONVERT MYFILE
DOC$CONVERT also saves the .GNC file and creates a .GNC_6LIS
file. The .GNC_6LIS file contains some messages that you might
find interesting; but it is not needed for any processing, so
you can delete it at any time you wish.
11 Delete the .GNC files. By default, BL8 looks for a .GNC file
to process before it looks for an .SDML file. The .GNC files
in this case will be BL6 versions, and they will not run under
BL8.
12 Process the .SDML file for any doctype and destination; for
example:
$ DOCUMENT MY_FILE S.S TERMINAL
13 At this point, you will have to start debugging your file,
so pay attention to the error messages you get. If you get
messages about a <DELIMITER> tag, you'll be looking for
problems to correct in nested lists. The <DELIMITER> tag itself
can be deleted; there is no such thing.
14 When each file is processing to your satisfaction, create a
PROfile for the document.
Lest anyone think I was picking on Peter's program (gee that
sounds odd); I wasn't...it's a good stop-gap solution to
converting the files. Peter has said in these notes that it's
an old program and there might be a few problems. I've pointed
out the problems that I've run into. Hope this saves a bit of hair
pulling on for someone else.
Rose
|
|
I meant I was running BL7 now and wanted to use DSR2GNC (the one referenced
in this conference) to convert a DSR document to DOCUMENT (which I LOVE).
I remember reading DSR2GNC saying it converted to BL6 and required MAKESDF.
Since I have BL7 and it dosen't have MAKESDF, I thought I could borrow it
for the conversion. Apparently I don't need it anyway. So I thought
I would need to "regress" to BL6 (from BL7) to get DSR2GNC to work.
Thanks .4! just what I was looking for. I do have DOC$CONVERT on BL7
so I assume it will convert the DSR2GNC output (BL6) to BL7 ?
I just ran DSR2GNC:
DSR2GNC--I--Version 0.05-0
DSR2GNC--I--FOP, Opening file - DSR2GNC.INI
***DSR2GNC--E--ILC, Illegal command: NAST
Current line: .NAST
***DSR2GNC--E--MLM, Missing .LEFT MARGIN command at EOF
Current line:
DSR2GNC--I--ERRORS, 709 diagnostic messages reported
*ex$$
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\MAKESDF\
I do have the .GNC file!!!
Thanks again!
John
|