OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [docbook-apps] Epic with DocBook?



> I doubt the problem here is Epic, so I doubt telling him
> to move to another method will help.  Basically, it sounds
> like he needs to "get a little wetter" if he wants to be able
> to use a doctype like DocBook and he isn't willing to just
> use a pre-installed distributed version.  It isn't that hard,
> but one does have to be willing to go to a little effort to
> learn the basics.
>
> paul


I agree.

I learned Epic+DocBook pretty fast, including how to create custom doctypes from
just imitating Arbortext's out-of-the-box DocBook XML doctype. The regular
posters on this list can probably remember that it was just about a year ago
when I obviously knew _nothing_.

". . . long way baby!" (Well done Steve, very well done. Thank you. Thank you
very much.)

I monitor and/or participate in several mailing lists devoted to issues of
XML-authoring/SGML-authoring/structured-authoring/etc. Many authors new to
XML/SGML expect enterprise publishing software and/or XML/SGML tool chains to
work differently. It has been my experience to find that even tech pubs managers
who should know better have unrealistic expectations. Specifically, many tend to
think XML/SGML publishing and single-sourcing is much less expensive than it is,
and that it should require personnel with fewer technical skills (cheaper
people). When I speak to them about DocBook solutions, they frequently fail to
recognize the value provided by all the various DocBook-specific tools and
solutions.

Imagine developing and maintaining a complex DTD; creating formatting code for
various output targets using the latest technologies; implementing profiling,
text-insets, linking, etc.; converting legacy docs; storing the XML in a
repository; providing WYSIWYG XML authoring across the enterprise for authors
and SMEs; etc.; etc. It is not a cheap and easy undertaking.


Steve Whitlatch








>
> >
> > Subject: Re: I only want to get as wet as I have to - Re: docbook
> > Date: Sun, 08 May 2005 13:48:23 -0700
> > A little whine can lead to next steps [wish it was wine instead].
> >
> > Ok, so I downloaded the 4.1 schema/dtd for sgml from
> > http://www.oasis-open.org/docbook/sgml/4.1/txtindex.html. I
> > opened our spec, pointed it to where I had the dtd saved, and got
> > the following dtd compile error, suggestions? Can firewalls screw
> > things up?
> >
> > ej
> >
> > ------------
> >
> > Warning: Could not locate DTD entity '%dbnotn'
> >     Public Identifier: '-//OASIS//ENTITIES DocBook Notations
> > V4.1//EN'
> >     System Identifier: '(none)'
> >     No entry was found for the above public identifier
> >     in any of these files:
> >
> > /net/infobot.sfbay/usr/doctools/solbook/epic/epic5r1/doctypes/catalog
> >        /net/infobot.sfbay/usr/doctools/epic5.1/doctypes/catalog
> >        /net/infobot.sfbay/usr/doctools/epic5.1/doctypes/catalog
> >
> > Warning: Could not locate DTD entity '%dbcent'
> >     Public Identifier: '-//OASIS//ENTITIES DocBook Character
> > Entities V4.1//EN'
> >     System Identifier: '(none)'
> >     No entry was found for the above public identifier
> >     in any of these files:
> >
> > /net/infobot.sfbay/usr/doctools/solbook/epic/epic5r1/doctypes/catalog
> >        /net/infobot.sfbay/usr/doctools/epic5.1/doctypes/catalog
> >        /net/infobot.sfbay/usr/doctools/epic5.1/doctypes/catalog
> >
> > Warning: Could not locate DTD entity '%dbpool'
> >     Public Identifier: '-//OASIS//ELEMENTS DocBook Information
> > Pool V4.1//EN'
> >     System Identifier: '(none)'
> >     No entry was found for the above public identifier
> >     in any of these files:
> >
> > /net/infobot.sfbay/usr/doctools/solbook/epic/epic5r1/doctypes/catalog
> >        /net/infobot.sfbay/usr/doctools/epic5.1/doctypes/catalog
> >        /net/infobot.sfbay/usr/doctools/epic5.1/doctypes/catalog
> >
> > Warning: Could not locate DTD entity '%dbhier'
> >     Public Identifier: '-//OASIS//ELEMENTS DocBook Document
> > Hierarchy V4.1//EN'
> >     System Identifier: '(none)'
> >     No entry was found for the above public identifier
> >     in any of these files:
> >
> > /net/infobot.sfbay/usr/doctools/solbook/epic/epic5r1/doctypes/catalog
> >        /net/infobot.sfbay/usr/doctools/epic5.1/doctypes/catalog
> >        /net/infobot.sfbay/usr/doctools/epic5.1/doctypes/catalog
> >
> > Warning: Could not locate DTD entity '%dbgenent'
> >     Public Identifier: '-//OASIS//ENTITIES DocBook Additional
> > General Entities V4.1//EN'
> >     System Identifier: '(none)'
> >     No entry was found for the above public identifier
> >     in any of these files:
> >
> > /net/infobot.sfbay/usr/doctools/solbook/epic/epic5r1/doctypes/catalog
> >        /net/infobot.sfbay/usr/doctools/epic5.1/doctypes/catalog
> >        /net/infobot.sfbay/usr/doctools/epic5.1/doctypes/catalog
> >
> > Dtgen Parser Error:
> > While parsing file /home/earlj/temp/fsg-docbook-dtd/docbook.dtd:
> > The current document name must be declared as an element within
> > the DTD.
> > (The parser needs this declaration to know where the model begins.)
> > (err:10  line:118  pos:4482)
> > Compile failed - rc=36
> >
> > Dennis Grace
> >
> > Linux Distribution Documentation Liaison
> > IBM Linux Technology Center
> > (512) 838-3937  T/L 678-3937  Cell (512) 296-7830
> > dgrace@us.ibm.com
> >
> > Micel yfel de­ se unwritere.
> > (Bad writers do a lot of damage.)
> >                                 Ălfric of York
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> > For additional commands, e-mail:
> > docbook-apps-help@lists.oasis-open.org
> >
> >
>



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]