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:eric -dot- dunn -at- ca -dot- transport -dot- bombardier -dot- com To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Fri, 16 Mar 2007 14:05:05 -0500
Sean Hower wrote:
> Honestly, though, I think a great deal of frustration comes from
> the lack of an out-of-the-box, end-to-end solution for using
> docbook and all that goes along with it (tools, stylesheets,
> parsers, blah blah blah) to create documentation. And I'm
> talking about something as simple as performing a single
> install to get everything working. I never found anything like that and
it was really
> my own stubburness, and desire not to be defeated by software,
> that got me to the point that I had everything working. I
> could be wrong on this, of course, but this issue should also be
Yes it should be addressed. But then the users must be aware of the
paradigm and realise that the system used will be akin to using a
FrameMaker or Word template As-Is out of the box with no modification.
The frustration that surfaces immediately after getting the system working
is that the system chosen doesn?t conform to the work at hand, when the
choice of an out-of-the-box solution requires that the users accept to
conform their work to the tool.
And both those frustrations arise while ignoring the often vast
differences between the final "end-to-end" implementations involving
current tools and various difficulties experienced while getting those
tools up-to-speed. We give great allowances and are selectively forgetful
of the sins of the devils we know.
> There is one thing that is really apparent though, people still
> don't understand XML or what it should be used for. I'm not sure,
> though, that diving into the technical details to clarify technical
> points would be helpful to someone who hasn't grasp some of the
> high-level concepts. Any discussion should be framed in a
> common reference otherwise you're (and I don't mean you specifically)
> speaking in gibberish and the audience will just tune out
> and miss the important stuff. Right?
Yes, right. But...
You can?t allow the common reference to be a misrepresentation. There?s a
basic minimum that needs to be learned. The relationship between XML,
DTDs, implementations, and Tools would, IMO, be that bare minimum.
Because only once that is understood can it be determined if the problems
or misunderstandings lie in configuring/installing a tool, understanding
the structure of a specific implementation (HTML, DITA, Docbook), or else
Chris Borokowski wrote:
> Bingo! There's no NCSA Mosaic for XML yet.
Yes there is. IE will display XML. So will FireFox. Now XML conforming to
which structure and how it?s formatted, that?s another thing. It displays
HTML, right? And there are XML compliant instances of HTML.
Although unfortunately the example page is an article that goes a little
too much into under-the-hood details for many. I chose it just because it
was the first hit in Google .
If anybody facetiously points out that the XML isn?t handled the same in
all browsers or that all can?t handle it, I have but one question: When
did all browsers finally implement HTML in the same way and support all
the optional specifications?
This e-mail communication (and any attachment/s) may contain confidential
or privileged information and is intended only for the individual(s) or
entity named above and to others who have been specifically authorized to
receive it. If you are not the intended recipient, please do not read,
copy, use or disclose the contents of this communication to others. Please
notify the sender that you have received this e-mail in error by reply
e-mail, and delete the e-mail subsequently. Please note that in order to
protect the security of our information systems an AntiSPAM solution is in
use and will browse through incoming emails.
Ce message (ainsi que le(s) fichier/s), transmis par courriel, peut
contenir des renseignements confidentiels ou protégés et est destiné à
l?usage exclusif du destinataire ci-dessus. Toute autre personne est par
les présentes avisée qu?il est strictement interdit de le diffuser, le
distribuer ou le reproduire. Si vous l?avez reçu par inadvertance,
veuillez nous en aviser et détruire ce message. Veuillez prendre note
qu'une solution antipollupostage (AntiSPAM) est utilisée afin d'assurer la
sécurité de nos systems d'information et qu'elle furètera les courriels
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-