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.
> I don't know if this is true. There's a difference between creating styles with the intent of using those styles to provide a
> structure, and defining the structure itself.
For those of us not working with an automated document structure nanny
(to use Mike's characterization), this is what style guides are for, and we
expect the writers reporting to us to adhere to those guides. Ever get an
item in your upcoming review year's list of objectives that says "adhere
to published style guide?" You have if you ever worked for me, and yes,
it did make a difference in your end-of-year review. We are supposed
to be professionals, and not kindergarteners who need to be lined up for
our milk and cookies in height-ascending order, yes?
> But, to be frank, the xml that this output uses is more of a dataset than a document. Still, though, the point still applies.
What tool did you use to create these?
> And now here-in lies, I believe, a core difference between "early adopters" and other users. Early adopters don't mind getting
> under the hood. In fact, they crave it. All others just want to get their work done. There's nothing wrong with either approach.
> ;-) The last time I really dug into authoring with XML it was still something gear mostly towards the "early adopter." I don't
> know if it's still that way.
It is, hence my "not ready for prime time" description.
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-