Installing Epic Editor

[unknown1]

Hi all,

I am installing Epic Editor to some users PC and I have to give them access to FOSI stylesheet and DTD located on a server.

How do I give them access to these files? Can I add those files to a catalog and then include the catalog in the "File Locations" "Catalogs" path?

Thanks in advance for your help and input!

Regards,
Horace Burke

[ebenton]

Yes. You are correct. Add the PUBLIC identifier of your DTD to a catalog file, along with the path to the DTD (either absolute or relative to the catalog). Then make the users' PCs catalog path value point to the catalog file.

[jamesisin]

Lynn,

You neglected to include a link to an image of your hair loss problem.


James

On 2/7/07, Lynn Hales <
lhales@csc.com> wrote:
Horace,

I agree, with Ed.Just to add my two cents here.

Catalogs are probably one of the most misunderstood useful tools in the
Epic (comes from the good old days of SGML).A catalog path issue can

cause one to loose their hair (just look at me).

As I said, catalogs were an integral part of SGML, but were "deprecated"
in XML in favor of using the SYSTEM identifier.There are two identifier
types in both SGML and XML.They are the SYSTEM (the one REQUIRED by XML)

and the PUBLIC.The SYSTEM identifier provides system specific locations
for supporting files and usually has a relative or specific path to the
file.This works fine as long as you are on the desired system (or can

access it).However if one places an absolute path in SYSTEM identifier
and your system does not have that path, then you are _______ (fill in the
blank with your favorite euphonium for being caught between the rock and

hard place).

The PUBLIC identifier provides a unique identifier that can be compared to
other PUBLIC identifiers in a catalog (or other simlair functioning file)
with the LOCAL SYSTEM identifier (path) as part of the catalog entry.


OASIS put out a TR a few years ago that updated the original SGML catalog
functionality.They added (and Epic supports this) the ability for a
CATALOG file to reference another CATALOG.This way you can have a master

catalog containing the paths to your DOCTYPES and then have a DOCTYPE
catalog for each DOCTYPE without having to add to your catalog path. Real
simply, in your master catalog reference the catalog path for each

doctype, the catalog is read and the appropriate catalog file is accessed.


This is very, very helpful when you consider that catalog entries are
FIFO, (First In, First Out).So (read been there done that) if you have

more than one entry for a particular catalog requirement (say DTD) in one
or more catalogs, the FIRST one encountered is read (even if it is wrong).


Read the on line help about CATALOGs.They are really a godsend when use

properly.Even the XML world is beginning to see the need for catalogs
and OASIS has an XML catalog TR.

Lynn

[lhales]

Horace,

I agree, with Ed. Just to add my two cents here.

Catalogs are probably one of the most misunderstood useful tools in the
Epic (comes from the good old days of SGML). A catalog path issue can
cause one to loose their hair (just look at me).

As I said, catalogs were an integral part of SGML, but were "deprecated"
in XML in favor of using the SYSTEM identifier. There are two identifier
types in both SGML and XML. They are the SYSTEM (the one REQUIRED by XML)
and the PUBLIC. The SYSTEM identifier provides system specific locations
for supporting files and usually has a relative or specific path to the
file. This works fine as long as you are on the desired system (or can
access it). However if one places an absolute path in SYSTEM identifier
and your system does not have that path, then you are _______ (fill in the
blank with your favorite euphonium for being caught between the rock and
hard place).

The PUBLIC identifier provides a unique identifier that can be compared to
other PUBLIC identifiers in a catalog (or other simlair functioning file)
with the LOCAL SYSTEM identifier (path) as part of the catalog entry.

OASIS put out a TR a few years ago that updated the original SGML catalog
functionality. They added (and Epic supports this) the ability for a
CATALOG file to reference another CATALOG. This way you can have a master
catalog containing the paths to your DOCTYPES and then have a DOCTYPE
catalog for each DOCTYPE without having to add to your catalog path. Real
simply, in your master catalog reference the catalog path for each
doctype, the catalog is read and the appropriate catalog file is accessed.


This is very, very helpful when you consider that catalog entries are
FIFO, (First In, First Out). So (read been there done that) if you have
more than one entry for a particular catalog requirement (say DTD) in one
or more catalogs, the FIRST one encountered is read (even if it is wrong).


Read the on line help about CATALOGs. They are really a godsend when use
properly. Even the XML world is beginning to see the need for catalogs
and OASIS has an XML catalog TR.

Lynn

[lhales]

James,

Sorry, but every time I try to capture the loss for posterity, the
reflection from the chrome dome whites out the image and nothing but a big
glare shows up. 🙂

Lynn