Rebuild_doctype replacement

rpaisley · ‎Mar 09, 2007

It has been a while since I've written for help; long enough for the
company name to change (PTC now).

We are finally upgrading from Arbortext Author (aka Epic) 4.3 to 5.2 to
keep up to date. This is a UNIX installation. The way we are structured,
I have my DTDs in a CM system and they are extracted and compiled via
shell scripts to build the users environment. However, it seems the
"rebuild_doctype" command has been deleted. I've tried to replace it
with the "compile_doctype" command but, I get no compiled files nor does
it issue any sort of error messages. The type of thing I need to do is
change to the doctypes directory and run something similar to the
following (I've striped out some error checking):

for dtd in `ls -d *`
do
epic -c "compile_doctype '$dtd"
Done

I also tried it with the toptag option.

Does Epic still support "batch" DTD compilation?

Robert G. Paisley
Software Engineer
Northrop Grumman
"All truths are easy to understand
once they are discovered;
the point is to discover them."
- Galileo Galilei (1564-1642)

ebenton · ‎Mar 09, 2007

If they are XML DTDs they don't need to be compiled in 5.2.

lhales · ‎Mar 09, 2007

Robert,

If they are SGML files that need to be recompiled, you may want to go into the DOCTYPE directory and delete the PRO and PTD files. If Epic works the same in Unix as it does in Windows, it will recompile the DOCTYPE automatically.

Deleting the PRO and PTD files also has an advantage over the 'compile_doctype' command. When Epic recompiles the DOCTYPE using the 'compile_doctype' it does not do a forced recompile so any changes to external files (e.g., text entity files, etc) are not included in the recompile. When the PRO and PTD are missing, Epic reads all the associated files when it is recompiling.

Lynn

-----"Paisley, Robert" <-> wrote: -----

To: "arbortext-adepters" <adepters@maillist.arbortext.com>

rpaisley · ‎Mar 12, 2007

face="Goudy Old Style" color=#800000>Lynn,

face="Goudy Old Style" color=#800000>I pull the DTD, FOS, and ATD files into a
set of subdirectories (about 40) from my CM system (no PRO or PTD files at this
point) and try and batch compile the files. Since this is part of a process that
may be repeated several times in a month, I really need to have the ability to
compile these from the command line (UNIX). the "rebuild_doctype" command
allowed that but, I can not seem to get the same effect from the
"compile_doctype" command. In addition, if I edit a document without the
compiled DTDs my user is asked if the DTD should be complied and they are
normally never exposed to that aspect of SGML editing.

I
think I am missing something in the syntax differences between the use of
"recompile_doctype" and "compile_doctype" and so no PRO and PTD files are being
produced. The odd thing is, the command also produces no message to inform me if
there is an issue.

Robert G.
Paisley
Veritas
Vos Liberabit
(The truth shall set
you free)

From: Lynn Hales

Sent: Friday, March 09, 2007 1:41 PM
To:
adepters@arbortext.com
Subject: Re: Rebuild_doctype
replacement

Robert,

If they are SGML files that need to be recompiled, you may want to go into
the DOCTYPE directory and delete the PRO and PTD files. If Epic works the
same in Unix as it does in Windows, it will recompile the DOCTYPE
automatically.

Deleting the PRO and PTD files also has an advantage over the
'compile_doctype' command. When Epic recompiles the DOCTYPE using the
'compile_doctype' it does not do a forced recompile so any changes to external
files (e.g., text entity files, etc) are not included in the recompile.
When the PRO and PTD are missing, Epic reads all the associated files when it is
recompiling.

Lynn

-----"Paisley, Robert"
<-> wrote: -----

rpaisley · ‎Mar 12, 2007

class=369245315-12032007>Lynn, et al:

class=369245315-12032007>I dug deep, broke into and debugged the _dtgenui.acl
code that manages the DTD compilation and found the issue. Mine of course. The
setting "-noprompt" must be set to run on the command line or the script will
abort without message. As always thanks for the support so many of you
provide.

Robert G.
Paisley
"Beer is proof that God loves us and wants us to be
happy."
~ Benjamin Franklin

From: Paisley, Robert

Sent: Monday, March 12, 2007 7:18
AM
To: adepters@arbortext.com
Cc:
lhales@csc.com
Subject: RE: Rebuild_doctype
replacement

face="Goudy Old Style" color=#800000>Lynn,

face="Goudy Old Style" color=#800000>I pull the DTD, FOS, and ATD files into a
set of subdirectories (about 40) from my CM system (no PRO or PTD files at this
point) and try and batch compile the files. Since this is part of a process that
may be repeated several times in a month, I really need to have the ability to
compile these from the command line (UNIX). the "rebuild_doctype" command
allowed that but, I can not seem to get the same effect from the
"compile_doctype" command. In addition, if I edit a document without the
compiled DTDs my user is asked if the DTD should be complied and they are
normally never exposed to that aspect of SGML editing.

I
think I am missing something in the syntax differences between the use of
"recompile_doctype" and "compile_doctype" and so no PRO and PTD files are being
produced. The odd thing is, the command also produces no message to inform me if
there is an issue.

Robert G.
Paisley
Veritas
Vos Liberabit
(The truth shall set
you free)

From: Lynn Hales

Sent: Friday, March 09, 2007 1:41 PM
To:
adepters@arbortext.com
Subject: Re: Rebuild_doctype
replacement

Robert,

If they are SGML files that need to be recompiled, you may want to go into
the DOCTYPE directory and delete the PRO and PTD files. If Epic works the
same in Unix as it does in Windows, it will recompile the DOCTYPE
automatically.

Deleting the PRO and PTD files also has an advantage over the
'compile_doctype' command. When Epic recompiles the DOCTYPE using the
'compile_doctype' it does not do a forced recompile so any changes to external
files (e.g., text entity files, etc) are not included in the recompile.
When the PRO and PTD are missing, Epic reads all the associated files when it is
recompiling.

Lynn

-----"Paisley, Robert"
<-> wrote: -----