RE: RE: Why WYSIWYG for XML???

Subject: RE: RE: Why WYSIWYG for XML???
From: Mailing List <mlist -at- ca -dot- safenet-inc -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 18 May 2004 13:15:07 -0400


Gene Kim-Eng offered:

> As someone who continues to be somewhat nostalgic for
> the days when we used to spend our time working with
> product to generate content and send raw text to
> production people for formatting and page design,
> I would see a truly effective "roboformatter" as
> a benefit that would free me to spend more time
> finding, organizing and writing information. Beats
> me how anyone could see spending their time on that
> as "confining yourself to single-function cog-ness."
>
> At the risk of reigniting yet another "font fondler"
> exchange, this sounds more to me like the attitude
> I'd expect from someone who thinks their primary
> value as a writer is taking input from other people
> and making it "look good."

Oh, ok. But to me, on the other hand, it sounded more
like the "production people" you describe in your first
paragraph.

For those of us in one-writer shops or with just a few
writers on the team, we don't have "production people"
we've been using (gasp!) WYSIAWYG software like FrameMaker
for years. So we control both the input (by going and
getting it) *and* the look of the output. As Geoff
pointed out, there's always something that needs tweaking.
It may be just my failing that I've never designed the
perfect template that could suit me for the rest of my
days, but I've never gone more than two releases of a
doc set without running up against something that's broken,
or that no longer serves the updated needs.

Now that I do Help, as well, that's only multiplied.

It wasn't working to go from FM-based books, but once
we get our Help pages into the desired XML format,
we'll be effectively single-sourcing Help and QuickStart
Guides and one or two other output formats (Technotes,
Update Sheets, etc.).

I'll see about using Bluefish if there's no objection,
'cuz I've briefly tried it, and it seems to work the
way Bruce describes. But I'll also have to remain in
charge of the various outputs, as soon as I learn how
to do that. Chicken, meet the Egg. Egg, this is the
Chicken. One of you came before the other, I think...

Now, if you'll excuse me, I find that the old table
format is no longer sufficient, and I may need to turn
them on their sides to add new columns. YOW! That's ugly!
I may have to fondle a font or two to get this fixed...

/kevin
--
The following text added by my employer, outside my control:
The information contained in this electronic mail transmission may be
privileged and confidential, and therefore, protected from disclosure. If
you have received this communication in error, please notify us immediately
by replying to this message, and then delete it from your computer without
copying or disclosing it.



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

SEE THE ALL NEW ROBOHELP X5 IN ACTION: RoboHelp X5 is a giant leap forward
in Help authoring technology, featuring Word 2003 support, Content
Management, Multi-Author support, PDF and XML support and much more! http://www.macromedia.com/go/techwrldemo

>From a single set of Word documents, create online Help and printed
documentation with ComponentOne Doc-To-Help 7 Professional, a new yearly
subscription service offering free updates and upgrades, support, and more.
http://www.doctohelp.com

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit
http://www.raycomm.com/techwhirl/ for more resources and info.



Previous by Author: RE: Why WYSIWYG for XML???
Next by Author: E-mail source depends on the observer?
Previous by Thread: RE: RE: Why WYSIWYG for XML???
Next by Thread: RE: RE: RE: Why WYSIWYG for XML???


What this post helpful? Share it with friends and colleagues:


Sponsored Ads