TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Giving up on XML From:"Edgar D' Souza" <edgar -dot- b -dot- dsouza -at- gmail -dot- com> To:"David Neeley" <dbneeley -at- gmail -dot- com> Date:Fri, 16 Mar 2007 14:32:06 +0530
On 3/15/07, David Neeley <dbneeley -at- gmail -dot- com> wrote:
> While I am not Eric, may I ask a question?
Of course - and thanks for the multiple posts, and encouraging
off-list mails, too, David! That was very nice of you!
> Since Frame *can* create quite nice DocBook instances, and since it also
> handles illustrations with callouts, what is the question?
Can Frame output those illustrations + callouts to DocBook?
If yes, what are the tags it outputs for that particular purpose - to
include the image, and to locate the callout text, with (optionally) a
surrounding box, and (compulsorily) a pointer line + arrowhead
pointing to a specific location on the image?
I obviously haven't used Structured Frame, or I might have had a
clue... :-/ Sorry...
A lot of us TWs do callouts in Word and Frame. Before trying to jump
to DocBook, we want to know whether we can do certain familiar things
like callouts in Docbook directly, or whether we have to do the markup
in the bitmap itself and just include the image.
This is just one of the questions that many of us face, of course. The
beginning parts of the thread were statements that much of the
available documentation on DocBook is (as Eric's nice analogy to
racing cars and building engines goes) the nuts, bolts, cams and shims
view - while we're looking at it more from the user's point of view -
can we do this? If yes, how? If not, we can't move to DocBook unless
we can find a workaround.
Even examining Docbook for suitability for our own particular
requirements is an uphill task, given that we'd like a book or
documentation source that's task- or functionality-oriented, and
compares/associates stuff we regularly use in Word/Frame to how it
would be done in DocBook.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-