RE: Any experience with Flare 4.0?

["Daniel Ng" <kjng -at- gprotechnologies -dot- com>]

*This message was transferred with a trial version of CommuniGate(r) Pro*
Here are some key points
- The Style Picker is a convenient shortcut (invaluable) Its not a new
feature just an emulation of a similar function you can do in Word.
- Rock solid print page design tools
- Superb image handling for single-sourcing -- Use width ranges for
different output mediums, DPI and pixels. 
- Stronger CSS support for things such as kerning, short-line elimination
and . 
- Global project linking - reuse a single stylesheet, topic or image
throughout all your projects consistently... A MASTER PROJECT..
- Strong single-sourcing tools available such as variables, snippets and
snippet conditions.

Daniel Ng
-----Original Message-----
From: magk -at- mindspring -dot- com [mailto:magk -at- mindspring -dot- com] 
Sent: Wednesday, October 01, 2008 9:39 PM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Any experience with Flare 4.0?

Hi,

We have Madcap Flare 3.1 and are thinking about upgrading to Flare 4.0. Has
anyone done this recently? I would like all feedback on any experiences that
you have had with using Flare, especially the 4.0 version.

Thanks so much!
Gina King

-----Original Message-----
>From: techwr-l-request -at- lists -dot- techwr-l -dot- com
>Sent: Sep 30, 2008 2:00 AM
>To: techwr-l -at- lists -dot- techwr-l -dot- com
>Subject: TECHWR-L Digest, Vol 35, Issue 28
>
>Send TECHWR-L mailing list submissions to
>	techwr-l -at- lists -dot- techwr-l -dot- com
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	http://lists.techwr-l.com/mailman/listinfo/techwr-l
>or, via email, send a message with subject or body 'help' to
>	techwr-l-request -at- lists -dot- techwr-l -dot- com
>
>You can reach the person managing the list at
>	techwr-l-owner -at- lists -dot- techwr-l -dot- com
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of TECHWR-L digest..."
>
>
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>ComponentOne Doc-To-Help gives you everything you need to author and 
>publish quality Help, Web, and print content. Perfect for technical 
>authors, developers, and policy writers. Download a FREE trial.
>http://www.componentone.com/DocToHelp/
>
>True single source, conditional content, PDF export, modular help.
>Help & Manual is the most powerful authoring tool for technical
>documentation. Boost your productivity! http://www.helpandmanual.com 
>
>---
>
>
>Today's Topics:
>
>   1. RE: Need examples of system documentation (Daniel Ng)
>   2. RE: Know Anything about Madcap Flare? (Daniel Ng)
>   3. RE: Need examples of system documentation (Daniel Ng)
>   4. Re: Writing a letter to an unknown part (Rob Hudson)
>   5. Re: Writing a letter to an unknown part (voxwoman)
>   6. RE: Documentation Legal Issues??? (Technical Writer)
>   7. RE: Documentation Legal Issues??? (Dan Goldstein)
>   8. RE: Documentation Legal Issues??? (Hemstreet, Deborah)
>   9. RE: Documentation Legal Issues??? (Combs, Richard)
>  10. Re: Documentation Legal Issues??? (Peter Neilson)
>  11. RE: Documentation Legal Issues??? (Dan Goldstein)
>  12. RE: Writing a letter to an unknown part (Tim Lewis)
>  13. Re: Documentation Legal Issues??? (Gene Kim-Eng)
>  14. RE: Documentation Legal Issues??? (Combs, Richard)
>  15. Can you help me with this macro? (Word 2003) (Hemstreet, Deborah)
>  16. RE: Can you help me with this macro? (Word 2003)
>      (Jessica Weissman)
>  17. Re: Can you help me with this macro? (Word 2003) (Chris Morton)
>  18. RE: Can you help me with this macro? (Word 2003)
>      (Hemstreet, Deborah)
>  19. Any experts with Audacity? (Tissa Salter)
>  20. Re: Can you help me with this macro? (Word 2003) (Jonathan West)
>  21. Re: Documentation Legal Issues??? (Janet Swisher)
>  22. Macro Solution for Only Label and Number - Thank you
>      (Hemstreet, Deborah)
>  23. RE: Documentation Legal Issues??? (Gause_Brian -at- emc -dot- com)
>  24. RE: Documentation Legal Issues??? (Dan Goldstein)
>  25. Re: Can you help me with this macro? (Word 2003) (Chris Morton)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Mon, 29 Sep 2008 14:14:26 +0800
>From: "Daniel Ng" <kjng -at- gprotechnologies -dot- com>
>Subject: RE: Need examples of system documentation
>To: "'Janice Gelb'" <Janice -dot- Gelb -at- Sun -dot- COM>,
>	<techwr-l -at- lists -dot- techwr-l -dot- com>
>Message-ID: <941DF257214D4EE893DA3A452F141000 -at- gprotechnologies -dot- com>
>Content-Type: text/plain;	charset="us-ascii"
>
>*This message was transferred with a trial version of CommuniGate(r) Pro*
>I've got just the book for you about this. I keep a copy of this
>
>The Practice of System and Network Administration: Thomas A. Limoncelli,
>Christina J. Hogan: Books.
>http://www.amazon.com/Practice-System-Network-Administration/dp/0201702711
>
>Easy to understand, and filled with system administration best practices,
>from terribly experienced people...the people who administer the thousands
>of PCs in the Google server megafarms. Its not platform specific so there
>are portions that apply to you regardless if its unix, or Win Server
>environs.
>
>>From time managamenent, stress management, hiring people, to handling
>migration projects, using bug tracking systems, to using wikis, providing
>training and support, communication, and documenting IT policies/disaster
>recovery plans...good case studies and anecdotes...recommended for anyone
>writing system admin guides - base it on a good resource like
>this...Practical and tested..
>
> 
>
>-----Original Message-----
>From: Janice Gelb [mailto:Janice -dot- Gelb -at- Sun -dot- COM] 
>Sent: Sunday, September 28, 2008 6:12 PM
>To: techwr-l -at- lists -dot- techwr-l -dot- com
>Subject: Re: Need examples of system documentation
>
>deltaskye wrote:
>> I am returning to IT system tech writing after an absence of four years.
>My client wants me to document a system that is already in place; the
>engineer who designed it did not write anything down! 
>> 
>> I will be working with a new engineer to try to document the system (not
>for end-users, for the company's internal/engineering use). The engineer
>will be the technical SME and I will be the scribe and desktop publisher.
>The system is used by staff to register new customers for a service,
>document customer service calls, and transmit each day's activities to
>another system.
>> 
>> The engineer has asked me to provide him some examples of what the
>documentation might look like. I have all kinds of stuff generated when
>other customers followed an organized SDLC as they were designing a system.
>I'm looking for ideas on how to frame the documentation as the engineer and
>I try to document a system that someone else designed (and who is no longer
>available).
>> 
>> I don't know if the following is helpful, but here are some of the topics
>the engineer has suggested:
>> 
>> External data interfaces
>> Oracle database management system
>> BEA configuration
>> System backup/restore
>> 
>
>Funny you should ask... I've been combing the web lately for system
>administration documentation for a paper I'm giving at the Usenix LISA
>conference (called "WTFM: Documentation and the System Administrator").
>It's the most nervous I've ever been about presenting at a conference
>because my audience won't be tech writers and I haven't actually worked in
a
>sys admin environment.
>(If anyone has examples of bad internal sys admin docs.
>please let me know - I promise to remove all company identification :-> )
>
>But enough about me. Try searching for:
>
>system administrator internal documentation documentation system
>documentation server
>
>I've also found that http://techrepublic.com is a great source of
>information. I'm not sure how useful it will be, but they link to a set of
>templates for some aspects of system administration docs at
>http://articles.techrepublic.com.com/5100-10878_11-5027838.html?tag=rbxccnb
t
>r1
>
>Best of luck!
>
>-- Janice
>
>***********************************************************
>Janice Gelb          | The only connection Sun has with
>janice -dot- gelb -at- sun -dot- com  | this message is the return address
>
>
>
>
>
>------------------------------
>
>Message: 2
>Date: Mon, 29 Sep 2008 14:16:59 +0800
>From: "Daniel Ng" <kjng -at- gprotechnologies -dot- com>
>Subject: RE: Know Anything about Madcap Flare?
>To: <beelia -at- pacbell -dot- net>,	"'Chris Vickery'"
>	<cvickery -at- arenasolutions -dot- com>
>Cc: "'Norman, Mary'" <Mary -dot- Norman -at- xerox -dot- com>,
>	techwr-l -at- lists -dot- techwr-l -dot- com
>Message-ID: <F24B6E086B6B4578B45B5F96E6C8B081 -at- gprotechnologies -dot- com>
>Content-Type: text/plain;	charset="us-ascii"
>
>*This message was transferred with a trial version of CommuniGate(r) Pro*
>Get in touch with sales -at- madcapsoftware -dot- com or drop mail to 
>
>The team at madcapsoftware.com (mhamilton -at- madcapsoftware -dot- com) they'll be
>sure to sort you out with a pretty quick response or a list of what you
>need. All the best.
>
>
> 
>
>-----Original Message-----
>From: beelia [mailto:beelia -at- gmail -dot- com] 
>Sent: Monday, September 29, 2008 8:38 AM
>To: Chris Vickery
>Cc: Norman, Mary; techwr-l -at- lists -dot- techwr-l -dot- com
>Subject: Re: Know Anything about Madcap Flare?
>
>XML is the primary requirement, which is extended by tools like Trados,
>which my company uses.
>
>I asked the question about translation houses because I have finally
>convinced my managers that they need Lingo to support my Flare help system,
>but now I have to convince staff in the localization unit, who are used to
>DITA OT (which uses documents as input and has produced only very
>rudimentary help). It would help to have a list of translation houses that
>support Lingo because then I could tell them they could outsource the task
>if they don't want to learn Lingo.
>
>I read the entire manual this weekend, though, and it seems to me that
>anyone who is used to translation memory software wouldn't have a problem
>with it. Plus it has an API that supports third-party applications, like
>across.net, which I'm pretty sure our localization unit uses.
>
>I have a feeling it will work out OK, but it's a very time-consuming
>process.
>
>Bee
>On Fri, Sep 26, 2008 at 9:33 AM, Chris Vickery
><cvickery -at- arenasolutions -dot- com>wrote:
>
>> Hmm. I guess I was basing my assumption on the translation houses I've 
>> dealt with, who've all been delighted we author in XML. Apologies for 
>> any confusion.
>>
>> c
>>
>> -----Original Message-----
>> From: Lech Rzedzicki [mailto:xchaotic -at- gmail -dot- com]
>> Sent: Friday, September 26, 2008 5:48 AM
>> To: techwr-l -at- lists -dot- techwr-l -dot- com
>> Cc: beelia -at- pacbell -dot- net; Norman, Mary; Chris Vickery
>> Subject: Re: Know Anything about Madcap Flare?
>>
>>  On Thu, Sep 25, 2008 at 6:05 PM, Chris Vickery 
>> <cvickery -at- arenasolutions -dot- com> wrote:
>> > Flare uses XML, so shouldn't any translation house be able to use it?
>>
>> While in this case, you might not be far from truth, this is a very 
>> wrong assumption.
>> XML is merely a markup language in which you can express a variety of 
>> data models: DITA, Docbook, XHTML just to name a few popular in 
>> authoring.
>> Any given tool supports a flavor of XML such as DITA, if it supports 
>> generic XML, the support itself is equally generic, in case of MadCap 
>> Products, there's even a dedicated app to support the needs of 
>> translation and localization, called Lingo[1]
>>
>> But that doesn't mean than any translation house supports any tools 
>> you throw at them, most translators are outsourced, overworked and 
>> underpaid and M$ Word is usually the top of their tool proficiency.
>>
>>
>> [1] http://www.madcapsoftware.com/products/lingo/
>>
>>
>
>
>
>
>------------------------------
>
>Message: 3
>Date: Mon, 29 Sep 2008 14:21:09 +0800
>From: "Daniel Ng" <kjng -at- gprotechnologies -dot- com>
>Subject: RE: Need examples of system documentation
>To: "'Janice Gelb'" <Janice -dot- Gelb -at- Sun -dot- COM>,
>	<techwr-l -at- lists -dot- techwr-l -dot- com>
>Message-ID: <9435A6BBB3A140C4A9D912D340645777 -at- gprotechnologies -dot- com>
>Content-Type: text/plain;	charset="us-ascii"
>
>*This message was transferred with a trial version of CommuniGate(r) Pro*
>The book has been updated ..get the newer 2nd edition (updated 2007)
>
>http://www.amazon.com/Practice-System-Network-Administration-2nd/dp/0321492
6
>68/ref=sr_1_1?ie=UTF8&s=books&qid=1222668987&sr=1-1
>This is the one..The new one is more contemporary with updates for hiring,
>and about using wikis.. 
>
>-----Original Message-----
>From: Janice Gelb [mailto:Janice -dot- Gelb -at- Sun -dot- COM] 
>Sent: Sunday, September 28, 2008 6:12 PM
>To: techwr-l -at- lists -dot- techwr-l -dot- com
>Subject: Re: Need examples of system documentation
>
>deltaskye wrote:
>> I am returning to IT system tech writing after an absence of four years.
>My client wants me to document a system that is already in place; the
>engineer who designed it did not write anything down! 
>> 
>> I will be working with a new engineer to try to document the system (not
>for end-users, for the company's internal/engineering use). The engineer
>will be the technical SME and I will be the scribe and desktop publisher.
>The system is used by staff to register new customers for a service,
>document customer service calls, and transmit each day's activities to
>another system.
>> 
>> The engineer has asked me to provide him some examples of what the
>documentation might look like. I have all kinds of stuff generated when
>other customers followed an organized SDLC as they were designing a system.
>I'm looking for ideas on how to frame the documentation as the engineer and
>I try to document a system that someone else designed (and who is no longer
>available).
>> 
>> I don't know if the following is helpful, but here are some of the topics
>the engineer has suggested:
>> 
>> External data interfaces
>> Oracle database management system
>> BEA configuration
>> System backup/restore
>> 
>
>Funny you should ask... I've been combing the web lately for system
>administration documentation for a paper I'm giving at the Usenix LISA
>conference (called "WTFM: Documentation and the System Administrator").
>It's the most nervous I've ever been about presenting at a conference
>because my audience won't be tech writers and I haven't actually worked in
a
>sys admin environment.
>(If anyone has examples of bad internal sys admin docs.
>please let me know - I promise to remove all company identification :-> )
>
>But enough about me. Try searching for:
>
>system administrator internal documentation documentation system
>documentation server
>
>I've also found that http://techrepublic.com is a great source of
>information. I'm not sure how useful it will be, but they link to a set of
>templates for some aspects of system administration docs at
>http://articles.techrepublic.com.com/5100-10878_11-5027838.html?tag=rbxccnb
t
>r1
>
>Best of luck!
>
>-- Janice
>
>***********************************************************
>Janice Gelb          | The only connection Sun has with
>janice -dot- gelb -at- sun -dot- com  | this message is the return address
>
>
>
>
>
>------------------------------
>
>Message: 4
>Date: Mon, 29 Sep 2008 08:46:11 -0400
>From: "Rob Hudson" <caveatrob -at- gmail -dot- com>
>Subject: Re: Writing a letter to an unknown part
>To: Lauren <lauren -at- writeco -dot- net>
>Cc: techwr-l List <techwr-l -at- lists -dot- techwr-l -dot- com>
>Message-ID:
>	<dac8acf60809290546r274dfbf3j8dd2e8ccce89e3b3 -at- mail -dot- gmail -dot- com>
>Content-Type: text/plain; charset=ISO-8859-1
>
>Somehow my students have found a template that indicates that first
>and last name should be used, when possible:
>
>"Dear Mr. Rob Hudson"
>
>This just sounds weird.
>
>
>------------------------------
>
>Message: 5
>Date: Mon, 29 Sep 2008 08:51:54 -0400
>From: voxwoman <voxwoman -at- gmail -dot- com>
>Subject: Re: Writing a letter to an unknown part
>To: "Rob Hudson" <caveatrob -at- gmail -dot- com>
>Cc: techwr-l List <techwr-l -at- lists -dot- techwr-l -dot- com>
>Message-ID:
>	<310338340809290551m6d210f29jcdd38cb680354657 -at- mail -dot- gmail -dot- com>
>Content-Type: text/plain; charset=ISO-8859-1
>
>"Dear Mr. Robert Hudson" sounds less weird. I was taught to use the full
>name, not nicknames in a formal situation like that.
>
>the other way would be to have in the recipient's address block
>
>Mr. Robert Hudson
>1234 Anystreet
>Anytown, State 123455
>
>Dear Rob,
>
>- this is, of course, if I knew you and your preferred form of address.
>
>-Wendy
>
>On Mon, Sep 29, 2008 at 8:46 AM, Rob Hudson <caveatrob -at- gmail -dot- com> wrote:
>
>> Somehow my students have found a template that indicates that first
>> and last name should be used, when possible:
>>
>> "Dear Mr. Rob Hudson"
>>
>> This just sounds weird.
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>> ComponentOne Doc-To-Help gives you everything you need to author and
>> publish quality Help, Web, and print content. Perfect for technical
>> authors, developers, and policy writers. Download a FREE trial.
>> http://www.componentone.com/DocToHelp/
>>
>> True single source, conditional content, PDF export, modular help.
>> Help & Manual is the most powerful authoring tool for technical
>> documentation. Boost your productivity! http://www.helpandmanual.com
>>
>> ---
>> You are currently subscribed to TECHWR-L as voxwoman -at- gmail -dot- com -dot- 
>>
>> To unsubscribe send a blank email to
>> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
>> or visit
>> http://lists.techwr-l.com/mailman/options/techwr-l/voxwoman%40gmail.com
>>
>>
>> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
>>
>> Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
>> http://www.techwr-l.com/ for more resources and info.
>>
>>
>
>
>------------------------------
>
>Message: 6
>Date: Mon, 29 Sep 2008 09:40:00 -0400
>From: Technical Writer <tekwrytr -at- hotmail -dot- com>
>Subject: RE: Documentation Legal Issues???
>To: <techwr-l -at- lists -dot- techwr-l -dot- com>
>Message-ID: <BAY101-W1848AF25AC09AD6BD4155ECF400 -at- phx -dot- gbl>
>Content-Type: text/plain; charset="Windows-1252"
>
>
>Other than implied warranty of fitness, and similar "generic good will"
considerations, is anyone aware of specific legislation that mandates
accuracy in documentation under penalty of law? For example, a mandate that
would require a software product manual or other similar document to be
"absolutely perfect"--meaning, if there was an error (not threatening to the
life, limb, or well-being of the user), is there some law that would require
a company to essentially recall and replace the entire manual?
> 
>Despite having worked in the field as an independent contractor for a
number of years, and taken various business classes at the local university
on legal and regulatory issues, I have never heard of such. If anyone has, I
would really appreciate it.
> 
>The issue is not the software or product itself, but rather the
documentation for that product. The way it was stated to me(by a technical
writer for a software company), was that every manual, and presumably every
piece of documentation generated, was a "legally binding contract," and as
such, had zero tolerance for errors of any type.
> 
>This is not a rhetorical question, or a lead-in to a debate; I have
honestly never seen, and never seen reference to, any such notion before,
except in broad, general terms that usually involve "credibility" and
"customer good-will." 
> 
>The issue of developers being legally accountable for their code has been
mentioned briefly on other forums, with the vague statement that someday,
somewhere, that might happen. The statement regarding documentation was made
as if some law or regulation is already in effect that dictates what a
company must do if and when an error is discovered, and what the scope of
their liability is; rather important pieces of information for a technical
writer documenting last week's version of the (now revised) software that
ships this afternoon.
> 
>If some "legally binding contract" legislation exists, it obviously affects
everyone in the documentation field. It would not take much imagination to
conjure up a situation in which TW Smith is sued by Company Jones for some
error. That, in turn, would imply that the fine print in an employment
contract might contain such a provision or condition, and that quickie temp
job to rush a product manual could result in a lawsuit down the road that
could bankrupt (in a best case scenario) the writer who worked one week on a
year-long project.
> 
>Any information you might have on the legal issues involved in the
production of documentation (again, not the product--the product
documentation) would be sincerely appreciated.
>Thanks,
>tekwrytr
> 
>http://www.tekwrytrs.com
> 
>_________________________________________________________________
>See how Windows Mobile brings your life together?at home, work, or on the
go.
>http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/
>
>------------------------------
>
>Message: 7
>Date: Mon, 29 Sep 2008 09:54:32 -0400
>From: "Dan Goldstein" <DGoldstein -at- riverainmedical -dot- com>
>Subject: RE: Documentation Legal Issues???
>To: <techwr-l -at- lists -dot- techwr-l -dot- com>
>Message-ID:
>	<0ADA9A22B5BC2147B360A22FD2BAD25C013794B1 -at- RMGBEX01 -dot- rmg -dot- local>
>Content-Type: text/plain;	charset="us-ascii"
>
>Maybe the technical writer was pulling your leg.
>
>> -----Original Message-----
>> From: Technical Writer
>> Sent: Monday, September 29, 2008 9:40 AM
>> To: techwr-l -at- lists -dot- techwr-l -dot- com
>> Subject: RE: Documentation Legal Issues???
>> 
>> ... The way it was stated to 
>> me (by a technical writer for a software company), was that 
>> every manual, and presumably every piece of documentation 
>> generated, was a "legally binding contract," and as such, had 
>> zero tolerance for errors of any type...
>>  
>
>This message contains confidential information intended only for the use of
the addressee(s). If you are not the addressee, or the person responsible
for delivering it to the addressee, you are hereby notified that reading,
disseminating, distributing, copying, electronic storing or the taking of
any action in reliance on the contents of this message is strictly
prohibited.  If you have received this message by mistake, please notify us,
by replying to the sender, and delete the original message immediately
thereafter.  Thank you.
>
>
>
>------------------------------
>
>Message: 8
>Date: Mon, 29 Sep 2008 10:24:16 -0400
>From: "Hemstreet, Deborah" <DHemstreet -at- kaydon -dot- com>
>Subject: RE: Documentation Legal Issues???
>To: <techwr-l -at- lists -dot- techwr-l -dot- com>
>Message-ID:
>
<D5026CC91D16464EAEF063B3BCEE30C001F4F6C9 -at- bear-plt01-ex1 -dot- kaydonint -dot- com>
>	
>
> 
>>From what I have seen, what you were told is "technically" and
>"theoretically" correct.
>
>The issue would be, when does it become in the interest of the end-user
>to take such a document to court and sue the company. I believe this is
>why many manuals have statements such as "The content of this manual is
>substantially correct. Graphical representations or instructions may
>differ slightly from the actual product."
>
>In the US, this kind of stuff is critical. Overseas, people tend to
>laugh at how sue-happy Americans are - but the problem is, if someone
>can make money out of an error in a manual, someone, somewhere will.
>
>Of even more critical interest is the issue of medical devices. Here,
>pardon my language, I don't know what else to call it, "butt-covering"
>is essential for any instructions about the medical device where an
>inadvertent error could result in harm to a patient - even if it is the
>physician's error! At one company where I worked, my ability to show
>that certain safety issues and how they related to certain aspects of
>the hardware and software saved the company from a lawsuit from a doctor
>who was looking for an excuse for his error. He was being sued and
>wanted to find someone to blame. Sadly, there are many such cases out
>there.
>
>Smaller companies and start-ups do not worry about these issues so much
>(though they should). Many larger companies insist on manuals going
>through a legal review, for just this reason, to make sure that all the
>appropriate disclaimers appear somewhere.
>
>I am sure there are people who would disagree - and in theory - I do as
>well. But at the end of the day - if there is the remotest chance that
>an unhappy customer could sue your company (and benefit in so doing),
>because of a silly error in the manual - either make sure you have no
>errors (next to impossible with development the way it often is), or
>make sure you have the appropriate disclaimers in the front matter.
>
>Hope these thoughts lend to fruitful discussion.
>
>Deborah
>
>
>
>------------------------------
>
>Message: 9
>Date: Mon, 29 Sep 2008 08:32:38 -0600
>From: "Combs, Richard" <richard -dot- combs -at- Polycom -dot- com>
>Subject: RE: Documentation Legal Issues???
>To: "Technical Writer" <tekwrytr -at- hotmail -dot- com>,
>	<techwr-l -at- lists -dot- techwr-l -dot- com>
>Message-ID:
>
<AABEB232F95338499DF8F513EE2B2C78A6A131 -at- WSTEXCH00 -dot- westminster -dot- polycom -dot- com>
>	
>Content-Type: text/plain;	charset="us-ascii"
>
>Technical Writer wrote:
> 
>> The issue is not the software or product itself, but rather the
>> documentation for that product. The way it was stated to me(by a
>technical
>> writer for a software company), was that every manual, and presumably
>every
>> piece of documentation generated, was a "legally binding contract,"
>and as
>> such, had zero tolerance for errors of any type.
>
>Did this writer also warn you about the Postal Service's plan to collect
>postage for emails? This is twaddle. 
>
>Just for starters, there is no such thing as a "legally binding
>contract" that all parties to the contract didn't willingly agree to
>with a full understanding of what they were agreeing to. 
>
>Then take a deep breath, calm your mind, and ask yourself if it's really
>believable that the law would single out documentation, of all things,
>to be held to the absurd standard of "absolutely perfect" with "zero
>tolerance for errors of any type." What else, besides surgery and
>childbirth (thanks, Sen. Edwards), does the law hold to that standard?
>
>And if some jurisdiction were stupid enough to enact such a law (I'm
>thinking that the bureaucrats in Brussels are capable of astonishingly
>stupid things), what would be the unintended consequence? Documentation
>would get very slim very quickly. The easiest way to minimize the
>possibility of documentation error is to reduce the volume of
>documentation. 
>
>"PerfectWord lets you produce letters, memos, and other documents. Use
>the keyboard to enter text. Use the menus, mouse, and keyboard to
>explore the many features of PerfectWord. Good luck."
>
>Richard
>
>
>Richard G. Combs
>Senior Technical Writer
>Polycom, Inc.
>richardDOTcombs AT polycomDOTcom
>303-223-5111
>------
>rgcombs AT gmailDOTcom
>303-777-0436
>------
>
>
>
>
>
>
>
>------------------------------
>
>Message: 10
>Date: Mon, 29 Sep 2008 10:39:26 -0400
>From: Peter Neilson <neilson -at- windstream -dot- net>
>Subject: Re: Documentation Legal Issues???
>To: Technical Writer <tekwrytr -at- hotmail -dot- com>
>Cc: techwr-l -at- lists -dot- techwr-l -dot- com
>Message-ID: <48E0E89E -dot- 5000100 -at- windstream -dot- net>
>Content-Type: text/plain; charset=windows-1252; format=flowed
>
>Technical Writer wrote:
>(about writer liability for supposed errors in documentation that the 
>writer somehow touched)
>
>There is a move afoot in regulation of livestock farming to make the 
>livestock farmer liable, in the name of "food safety", for any illness 
>contracted by consumers of meat from the farmer's animals. The game is 
>to implement "farm to fork" traceability. (The slogan appears to be 
>chosen for its cute alliteration.) Traceability--documentation--is 
>substituted for the USDA slaughterhouse inspection previously used. As 
>far as I have been able to tell, the underlying purpose is to move the 
>liability for tainted meat from meatpackers (where the troubles usually 
>arise) back to the farmer.
>
>A similar effort in the documentation business would likely take the 
>form of required certification or registration that has no actual 
>bearing on the quality of writing, but is put forth as a feel-good 
>"solution" to a perceived problem. You'll know it's happening for real 
>if you hear of non-certified writers being mentioned in a news story 
>about the crash of an airplane, of a railway train, or of a banking 
>system. You'll know you've bumped into it personally when you are asked 
>for (or suddenly receive in the mail) your Writer Certification Number 
>or WCN microchip.
>
>See nonais.org for the situation in farming.
>
>Comment number 9 at http://nonais.org/2008/09/01/bulletin-board-200809/ 
>is interesting. Piles of mandated record keeping ("documentation") none 
>of which improves food safety but all with legal liability for the 
>farmer-writer.
>
>
>------------------------------
>
>Message: 11
>Date: Mon, 29 Sep 2008 10:46:12 -0400
>From: "Dan Goldstein" <DGoldstein -at- riverainmedical -dot- com>
>Subject: RE: Documentation Legal Issues???
>To: <techwr-l -at- lists -dot- techwr-l -dot- com>
>Message-ID:
>	<0ADA9A22B5BC2147B360A22FD2BAD25C013794DA -at- RMGBEX01 -dot- rmg -dot- local>
>Content-Type: text/plain;	charset="us-ascii"
>
>Can I get the microchip with an intramuscular caffeine pump?
>
>> -----Original Message-----
>> From: Peter Neilson
>> Sent: Monday, September 29, 2008 10:39 AM
>> To: Technical Writer
>> Cc: techwr-l -at- lists -dot- techwr-l -dot- com
>> Subject: Re: Documentation Legal Issues???
>> 
>> ... You'll know you've bumped into it personally when you 
>> are asked for (or suddenly receive in the mail) your Writer 
>> Certification Number or WCN microchip...
>> 
>
>This message contains confidential information intended only for the use of
the addressee(s). If you are not the addressee, or the person responsible
for delivering it to the addressee, you are hereby notified that reading,
disseminating, distributing, copying, electronic storing or the taking of
any action in reliance on the contents of this message is strictly
prohibited.  If you have received this message by mistake, please notify us,
by replying to the sender, and delete the original message immediately
thereafter.  Thank you.
>
>
>
>------------------------------
>
>Message: 12
>Date: Mon, 29 Sep 2008 09:50:53 -0500
>From: "Tim Lewis" <ltc -dot- writer -at- comcast -dot- net>
>Subject: RE: Writing a letter to an unknown part
>To: <techwr-l -at- lists -dot- techwr-l -dot- com>
>Message-ID: <000001c92242$c5fba8c0$51f2fa40$ -at- writer@comcast.net>
>Content-Type: text/plain;	charset="us-ascii"
>
>Long ago, I took a college-level letter writing class where I learned how
to
>write effective complaint letters. The letter generally contains 3
>paragraphs. 
>Paragraph 1: Background information such as date of purchase and where.
>Paragraph 2: Nature of the problem.
>Paragraph 3: Your request.
>
>Oh yes, the salutation is "Ladies and Gentlemen:" when you do not know who
>you are writing to. I have used this format for years and have gotten
>favorable responses from most that I have sent. Here is an example of one.
>
>Ladies and Gentlemen:
>
>I purchased your model XYX Product Name last year and gave it to my wife
for
>Christmas. We have used it only about times, it did a good job of cleaning.
>[include proof of purchase.]
>
>Unfortunately, when we went to use it yesterday, it would not run. I tried
>it on different outlets and rocked the power switch several times. It acts
>like it is not getting power. The store where I bought it will not take it
>back because too much time has lapsed. [Explain in sufficient detail what
>problems you are experiencing.] 
>
>I am asking that you waive the shipping and handling fee and repair or
>replace the XYX Product Name at your expense.
>
>Sincerely,
>
>Your name and contact information.
>
>Tim Lewis
>Lewis Technical Communications, Inc.
>ltc -dot- writer -at- comcast -dot- net
>www.lewiscomms.com
>
>> > -----Original Message-----
>> > From: techwr-l-bounces+lauren=writeco -dot- net -at- lists -dot- techwr-l -dot- com
>> > [mailto:techwr-l-bounces+lauren=writeco -dot- net -at- lists -dot- techwr-l -dot- com
>> > ] On Behalf Of Rob Hudson
>> > Sent: Sunday, September 28, 2008 3:59 PM
>> > To: techwr-l List
>> > Subject: Writing a letter to an unknown part
>> >
>> > Hello Everyone,
>> >
>> > When you're writing a letter of complaint or inquiry, and you don't
>> > know the name of the contact person, what is the preferred
>> salutation?
>> > Is it "to whom it may concern," "sir or madam," representative,' or
>> > "<<job title>>"?
>> >
>> > Thanks,
>> >
>> > Rob
>
>
>
>------------------------------
>
>Message: 13
>Date: Mon, 29 Sep 2008 08:06:58 -0700
>From: "Gene Kim-Eng" <techwr -at- genek -dot- com>
>Subject: Re: Documentation Legal Issues???
>To: <techwr-l -at- lists -dot- techwr-l -dot- com>
>Message-ID: <CC579B64FA1E49B2B3FF0635136CA91F -at- genekoptx2>
>Content-Type: text/plain; format=flowed; charset="iso-8859-1";
>	reply-type=original
>
>As long as you remember to include the usual blurbs about 
>information being accurate at time of publication, products
>(which would include documents) being subject to change 
>without notice, no liability for consequential damages, etc., 
>etc., yes. This is why you see all these blurbs somewhere 
>on just about everything you buy (usually either the manual 
>or the warranty statement). 
>
>In the absence of such disclaimers, a customer could argue
>that erroneous information formed a substantial part of the
>decision to buy, that the product was unsuitable for its 
>intended/advertised purpose, was falsely represented, and 
>its use led to the dreaded "consequential damage."   
>
>Look up "implied warranty."
>
>However, the consequences of failing to protect against
>"implied warranty" liability would be demands for and/or
>action to obtain refunds and/or damages, not to mandate 
>document recalls and updates (though if a manufacturer
>were to lose such a suit due to the absence of disclaimers,
>you can see why they'd want to do them).
>
>In government-regulated industries, the ultimate decision-
>making power with regard to mandatory recalls and product
>updates rests with the regulators, and all others are made
>by the manufacturers based on their assessment of their
>exposure to liability.
>
>Gene Kim-Eng
>
>
>
>----- Original Message ----- 
>From: "Combs, Richard" <richard -dot- combs -at- Polycom -dot- com>
>> Just for starters, there is no such thing as a "legally binding
>> contract" that all parties to the contract didn't willingly agree to
>> with a full understanding of what they were agreeing to. 
>.
>
>
>------------------------------
>
>Message: 14
>Date: Mon, 29 Sep 2008 09:12:00 -0600
>From: "Combs, Richard" <richard -dot- combs -at- Polycom -dot- com>
>Subject: RE: Documentation Legal Issues???
>To: "Dan Goldstein" <DGoldstein -at- riverainmedical -dot- com>,
>	<techwr-l -at- lists -dot- techwr-l -dot- com>
>Message-ID:
>
<AABEB232F95338499DF8F513EE2B2C78A6A132 -at- WSTEXCH00 -dot- westminster -dot- polycom -dot- com>
>	
>Content-Type: text/plain;	charset="us-ascii"
>
>Dan Goldstein wrote:
> 
>> Can I get the microchip with an intramuscular caffeine pump?
>
>No, no -- not IM, IV! It needs to go directly into a vein so that the
>circulatory system can get it to the brain expeditiously. 
>
>Richard
>
>
>Richard G. Combs
>Senior Technical Writer
>Polycom, Inc.
>richardDOTcombs AT polycomDOTcom
>303-223-5111
>------
>rgcombs AT gmailDOTcom
>303-777-0436
>------
>
>
>
>
>
>
>
>
>------------------------------
>
>Message: 15
>Date: Mon, 29 Sep 2008 11:37:54 -0400
>From: "Hemstreet, Deborah" <DHemstreet -at- kaydon -dot- com>
>Subject: Can you help me with this macro? (Word 2003)
>To: <techwr-l -at- lists -dot- techwr-l -dot- com>
>Message-ID:
>
<D5026CC91D16464EAEF063B3BCEE30C00360F7ED -at- bear-plt01-ex1 -dot- kaydonint -dot- com>
>	
>
>Hi All,
>
>Below my question is a macro I've recorded. My question: I want this
>macro to merely open the Cross Reference dialog box, with it pre-set to
>insert a Figure with the Only Label and Number option selected. The user
>would then select the figure number, insert the ref and close the dialog
>box.
> 
>Is there a way to modify this macro for the above desired action? My
>attempts have failed.
>
>Thanks in advance, 
> 
>Deborah
> 
> 
>Sub temp()
>    Selection.InsertCrossReference ReferenceType:="Figure",
>ReferenceKind:= _
>        wdOnlyLabelAndNumber, ReferenceItem:="1",
>InsertAsHyperlink:=True, _
>        IncludePosition:=False, SeparateNumbers:=False,
>SeparatorString:=" "
>End Sub
>
>
>
>
>------------------------------
>
>Message: 16
>Date: Mon, 29 Sep 2008 11:47:08 -0400
>From: "Jessica Weissman" <Jessica -dot- Weissman -at- hillcrestlabs -dot- com>
>Subject: RE: Can you help me with this macro? (Word 2003)
>To: "Hemstreet, Deborah" <DHemstreet -at- kaydon -dot- com>,
>	<techwr-l -at- lists -dot- techwr-l -dot- com>
>Message-ID:
>	<36E4692623C5974BA6661C0B18EE8EDF01015F05 -at- MAILSERV -dot- hcrest -dot- com>
>Content-Type: text/plain;	charset="us-ascii"
>
>If you find a way to default the CR dialog to that setting please let me
>know.  Nothing I've tried over the years has worked.
>
>-  Jessica
>
>
>
>------------------------------
>
>Message: 17
>Date: Mon, 29 Sep 2008 08:47:17 -0700
>From: "Chris Morton" <salt -dot- morton -at- gmail -dot- com>
>Subject: Re: Can you help me with this macro? (Word 2003)
>To: "Hemstreet, Deborah" <DHemstreet -at- kaydon -dot- com>,
>	techwr-l -at- lists -dot- techwr-l -dot- com
>Message-ID:
>	<746d910c0809290847s25b584f9p170b3bd96a2a1b67 -at- mail -dot- gmail -dot- com>
>Content-Type: text/plain; charset=ISO-8859-1
>
>Try posting at Woody's Lounge if you don't get the answer you're looking
for
>here. Woody Leonard has written many a book about Word, appears at M$
>seminars, and is noted Word guru.
>
>The link is: http://askwoody.com/askforhelp.php
>
>> Chris *(who doesn't work for Woody or M$, but knows of this excellent
>online resource for all Word wonks)*
>
>On Mon, Sep 29, 2008 at 8:37 AM, Hemstreet, Deborah
><DHemstreet -at- kaydon -dot- com>wrote:
>
>> Hi All,
>>
>> Below my question is a macro I've recorded. My question: I want this
>> macro to merely open the Cross Reference dialog box, with it pre-set to
>> insert a Figure with the Only Label and Number option selected. The user
>> would then select the figure number, insert the ref and close the dialog
>> box.
>>
>> Is there a way to modify this macro for the above desired action? My
>> attempts have failed.
>>
>> Thanks in advance,
>>
>> Deborah
>>
>>
>> Sub temp()
>>    Selection.InsertCrossReference ReferenceType:="Figure",
>> ReferenceKind:= _
>>        wdOnlyLabelAndNumber, ReferenceItem:="1",
>> InsertAsHyperlink:=True, _
>>        IncludePosition:=False, SeparateNumbers:=False,
>> SeparatorString:=" "
>> End Sub
>>
>>
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>> ComponentOne Doc-To-Help gives you everything you need to author and
>> publish quality Help, Web, and print content. Perfect for technical
>> authors, developers, and policy writers. Download a FREE trial.
>> http://www.componentone.com/DocToHelp/
>>
>> True single source, conditional content, PDF export, modular help.
>> Help & Manual is the most powerful authoring tool for technical
>> documentation. Boost your productivity! http://www.helpandmanual.com
>>
>> ---
>> You are currently subscribed to TECHWR-L as salt -dot- morton -at- gmail -dot- com -dot- 
>>
>> To unsubscribe send a blank email to
>> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
>> or visit
>>
http://lists.techwr-l.com/mailman/options/techwr-l/salt.morton%40gmail.com
>>
>>
>> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
>>
>> Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
>> http://www.techwr-l.com/ for more resources and info.
>>
>>
>
>
>------------------------------
>
>Message: 18
>Date: Mon, 29 Sep 2008 12:10:18 -0400
>From: "Hemstreet, Deborah" <DHemstreet -at- kaydon -dot- com>
>Subject: RE: Can you help me with this macro? (Word 2003)
>To: <chrismorton11 -at- gmail -dot- com>,	<techwr-l -at- lists -dot- techwr-l -dot- com>
>Message-ID:
>
<D5026CC91D16464EAEF063B3BCEE30C00360F7EE -at- bear-plt01-ex1 -dot- kaydonint -dot- com>
>	
>Content-Type: text/plain;	charset="us-ascii"
>
>Thanks for the tip - looks like this is one sweetie the people at work
>won't get...
> 
>The answer I found is:
> 
>"That particular dialog is known to be very buggy when you try to
>control it from VBA. Expect problems. (see
>http://support.microsoft.com/default.aspx?scid=kb;en-us;209668 for one
>such bug.) SendKeys is likely to be your only reliable option.
>(Don't mean to be a Gloomy Gus here, but I wasted a lot of time trying
>to customize that dialog myself some time ago.)
>Andrew Savikas"
> 
>Thanks for saving me a LOT of time!
>
>Deborah
>
>
>  _____  
>
>	From: Chris Morton [mailto:salt -dot- morton -at- gmail -dot- com] 
>	Sent: Monday, September 29, 2008 11:47 AM
>	To: Hemstreet, Deborah; techwr-l -at- lists -dot- techwr-l -dot- com
>	Subject: Re: Can you help me with this macro? (Word 2003)
>	
>	
>	Try posting at Woody's Lounge if you don't get the answer you're
>looking for here. Woody Leonard has written many a book about Word,
>appears at M$ seminars, and is noted Word guru.
>	 
>	The link is: http://askwoody.com/askforhelp.php
>	 
>	> Chris (who doesn't work for Woody or M$, but knows of this
>excellent online resource for all Word wonks)
>	
>	
>	On Mon, Sep 29, 2008 at 8:37 AM, Hemstreet, Deborah
><DHemstreet -at- kaydon -dot- com> wrote:
>	
>
>		Hi All,
>		
>		Below my question is a macro I've recorded. My question:
>I want this
>		macro to merely open the Cross Reference dialog box,
>with it pre-set to
>		insert a Figure with the Only Label and Number option
>selected. The user
>		would then select the figure number, insert the ref and
>close the dialog
>		box.
>		
>		Is there a way to modify this macro for the above
>desired action? My
>		attempts have failed.
>		
>		Thanks in advance,
>		
>		Deborah
>		
>		
>		Sub temp()
>		   Selection.InsertCrossReference
>ReferenceType:="Figure",
>		ReferenceKind:= _
>		       wdOnlyLabelAndNumber, ReferenceItem:="1",
>		InsertAsHyperlink:=True, _
>		       IncludePosition:=False, SeparateNumbers:=False,
>		SeparatorString:=" "
>		End Sub
>		
>		
>	
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>		
>		ComponentOne Doc-To-Help gives you everything you need
>to author and
>		publish quality Help, Web, and print content. Perfect
>for technical
>		authors, developers, and policy writers. Download a FREE
>trial.
>		http://www.componentone.com/DocToHelp/
>		
>		True single source, conditional content, PDF export,
>modular help.
>		Help & Manual is the most powerful authoring tool for
>technical
>		documentation. Boost your productivity!
>http://www.helpandmanual.com <http://www.helpandmanual.com/> 
>		
>		---
>		You are currently subscribed to TECHWR-L as
>salt -dot- morton -at- gmail -dot- com -dot- 
>		
>		To unsubscribe send a blank email to
>		techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
>		or visit
>http://lists.techwr-l.com/mailman/options/techwr-l/salt.morton%40gmail.c
>om
>		
>		
>		To subscribe, send a blank email to
>techwr-l-join -at- lists -dot- techwr-l -dot- com
>		
>		Send administrative questions to admin -at- techwr-l -dot- com -dot- 
>Visit
>		http://www.techwr-l.com/ for more resources and info.
>		
>		
>
>
>
>
>------------------------------
>
>Message: 19
>Date: Mon, 29 Sep 2008 19:40:07 +0300
>From: "Tissa Salter" <tissa55 -at- gmail -dot- com>
>Subject: Any experts with Audacity?
>To: techwr-l -at- lists -dot- techwr-l -dot- com
>Message-ID:
>	<69fb49fd0809290940j7913de26n55fb0c5b3e0d716f -at- mail -dot- gmail -dot- com>
>Content-Type: text/plain; charset=ISO-8859-1
>
>If anyone on this list considers themselves a master with Audacity and
>podcasting in general, would you please contact me off list if you would be
>so kind as to answer a few questions?  I am trying to produce a
professional
>podcast and I have a few questions -
>
>Thank you,
>t.
>
>-- 
>______________________________________
>Tissa Salter
>English Faculty - Texas A&M University at Qatar
>Local Doha Mobile:  974-572-2976
>Local Doha Office:  974-423-0224
>US line ringing in Doha home (+9 hours from CST):  979-216-1223
>Texas Mobile ( voicemail checked weekly):  979-218-3462
>US Forwarding address:
>Liticia J. Salter
>c/o TAMUQ Support Office
>PO Box B-6
>College Station, TX  77844
>.............................................
>"... not a melting pot but a beautiful mosaic. Different people, different
>beliefs, different yearnings, different hopes, different dreams."- Jimmy
>Carter
>.............................................
>Great Music on the web: www.radioio.com
>
>
>------------------------------
>
>Message: 20
>Date: Mon, 29 Sep 2008 17:58:26 +0100
>From: "Jonathan West" <jwest -at- mvps -dot- org>
>Subject: Re: Can you help me with this macro? (Word 2003)
>To: "Hemstreet, Deborah" <DHemstreet -at- kaydon -dot- com>
>Cc: techwr-l -at- lists -dot- techwr-l -dot- com
>Message-ID:
>	<1b2bd87b0809290958n5a01b8c1tccc17bd981e4216f -at- mail -dot- gmail -dot- com>
>Content-Type: text/plain; charset=ISO-8859-1
>
>2008/9/29 Hemstreet, Deborah <DHemstreet -at- kaydon -dot- com>:
>> Hi All,
>>
>> Below my question is a macro I've recorded. My question: I want this
>> macro to merely open the Cross Reference dialog box, with it pre-set to
>> insert a Figure with the Only Label and Number option selected. The user
>> would then select the figure number, insert the ref and close the dialog
>> box.
>>
>> Is there a way to modify this macro for the above desired action? My
>> attempts have failed.
>>
>
>Not easy, as the dialog doesn't respond as it should to setting the
>dialog box arguments, so you have to use SendKeys which can be rather
>flaky. But this does seem to work.
>
>With Dialogs(wdDialogInsertCrossReference)
>  SendKeys "ff{TAB}{DOWN}{DOWN}~%w": .Show
>End With
>
>The "ff" sets the reference kind to Figure. The "{TAB}" moves the
>focus across to the "Insert reference to" box. "{DOWN}{DOWN}" opens
>the dropdown and moves down one item. "~" selects and closes the
>dropdown. "%w" moves the focus to the "For which heading" dialog.
>
>It works for me. YMMV.
>
>Regards
>Jonathan West
>
>
>------------------------------
>
>Message: 21
>Date: Mon, 29 Sep 2008 13:02:40 -0500
>From: "Janet Swisher" <jmswisher -at- gmail -dot- com>
>Subject: Re: Documentation Legal Issues???
>To: "Technical Writer" <tekwrytr -at- hotmail -dot- com>
>Cc: techwr-l -at- lists -dot- techwr-l -dot- com
>Message-ID:
>	<38c5f0150809291102i4041f8d9nf1e9ccdbae96b6b6 -at- mail -dot- gmail -dot- com>
>Content-Type: text/plain; charset=ISO-8859-1
>
>On Mon, Sep 29, 2008 at 8:40 AM, Technical Writer <tekwrytr -at- hotmail -dot- com>
wrote:
>>
>> Other than implied warranty of fitness, and similar "generic good will"
considerations, is anyone aware of specific legislation that mandates
accuracy in documentation under penalty of law? For example, a mandate that
would require a software product manual or other similar document to be
"absolutely perfect"--meaning, if there was an error (not threatening to the
life, limb, or well-being of the user), is there some law that would require
a company to essentially recall and replace the entire manual?
>>
>> Despite having worked in the field as an independent contractor for a
number of years, and taken various business classes at the local university
on legal and regulatory issues, I have never heard of such. If anyone has, I
would really appreciate it.
>>
>> The issue is not the software or product itself, but rather the
documentation for that product. The way it was stated to me(by a technical
writer for a software company), was that every manual, and presumably every
piece of documentation generated, was a "legally binding contract," and as
such, had zero tolerance for errors of any type.
>>
>
>A company I worked for put in their contracts that the software was
>warranted to work "as documented". This did not lead to them requiring
>that the documentation be perfect. Rather, it led to omitting things
>from the documentation if there was any possibility that the software
>might now work that way (e.g., last-minute features), while still
>producing plausibly complete docs. I think they also took the view
>that a discrepancy between the docs and the software would simply be
>considered a software defect, to be remedied under the maintenance
>section of the contract. The software in question was potentially
>business-critical but not life-critical.
>
>That clause of the contracts was never tested while I was there.
>
>
>
>-- 
>Visit my blog at: http://www.janetswisher.com
>
>
>------------------------------
>
>Message: 22
>Date: Mon, 29 Sep 2008 14:59:50 -0400
>From: "Hemstreet, Deborah" <DHemstreet -at- kaydon -dot- com>
>Subject: Macro Solution for Only Label and Number - Thank you
>To: "Jonathan West" <jwest -at- mvps -dot- org>
>Cc: techwr-l -at- lists -dot- techwr-l -dot- com
>Message-ID:
>
<D5026CC91D16464EAEF063B3BCEE30C00360F7F2 -at- bear-plt01-ex1 -dot- kaydonint -dot- com>
>	
>
>Major thanks to Jonathan West for his solution.
>
>I now have two nifty macros for helping employees quickly cross-ref
>figures and tables - here they are, tested and working in MS Word 2003 -
>for anyone who would like. I have a toolbar and have mapped these to a
>toolbar (and a short-cut key on my own add-in template).
>
>Many thanks!
>Deborah
>
>
>Sub CrossRefFigure()
>'
>' Written 9/29/2008 by Deborah Hemstreet with help of Jonathan West
>'
>With Dialogs(wdDialogInsertCrossReference)
>  SendKeys "ff{TAB}{DOWN}{DOWN}~%w": .Show
>End With
>End Sub
>-------------------------------------------------------------------
>Sub CrossRefTable()
>'
>' Written 9/29/2008 by Deborah Hemstreet with help of Jonathan West
>'
>    
>    With Dialogs(wdDialogInsertCrossReference)
>        SendKeys "tt{TAB}{DOWN}{DOWN}~%w": .Show
>    End With
>End Sub
>
>
>
>-----Original Message-----
>From: jonathanwest22 -at- googlemail -dot- com
>[mailto:jonathanwest22 -at- googlemail -dot- com] On Behalf Of Jonathan West
>Sent: Monday, September 29, 2008 12:58 PM
>To: Hemstreet, Deborah
>Cc: techwr-l -at- lists -dot- techwr-l -dot- com
>Subject: Re: Can you help me with this macro? (Word 2003)
>
>2008/9/29 Hemstreet, Deborah <DHemstreet -at- kaydon -dot- com>:
>> Hi All,
>>
>> Below my question is a macro I've recorded. My question: I want this
>> macro to merely open the Cross Reference dialog box, with it pre-set
>to
>> insert a Figure with the Only Label and Number option selected. The
>user
>> would then select the figure number, insert the ref and close the
>dialog
>> box.
>>
>> Is there a way to modify this macro for the above desired action? My
>> attempts have failed.
>>
>
>Not easy, as the dialog doesn't respond as it should to setting the
>dialog box arguments, so you have to use SendKeys which can be rather
>flaky. But this does seem to work.
>
>With Dialogs(wdDialogInsertCrossReference)
>  SendKeys "ff{TAB}{DOWN}{DOWN}~%w": .Show
>End With
>
>The "ff" sets the reference kind to Figure. The "{TAB}" moves the
>focus across to the "Insert reference to" box. "{DOWN}{DOWN}" opens
>the dropdown and moves down one item. "~" selects and closes the
>dropdown. "%w" moves the focus to the "For which heading" dialog.
>
>It works for me. YMMV.
>
>Regards
>Jonathan West
>
>
>
>
>
>------------------------------
>
>Message: 23
>Date: Mon, 29 Sep 2008 15:28:57 -0400
>From: Gause_Brian -at- emc -dot- com
>Subject: RE: Documentation Legal Issues???
>To: <tekwrytr -at- hotmail -dot- com>
>Cc: techwr-l -at- lists -dot- techwr-l -dot- com
>Message-ID:
>	<FEA8D40A7473E64A95AFE058FC897C3805C6116D -at- CORPUSMX20B -dot- corp -dot- emc -dot- com>
>Content-Type: text/plain;	charset="us-ascii"
>
> 
>Zero tolerance for errors of any type??
>
>Hahahaha
>
>Every manual has errors. Every single one.
>
>There is no law saying your manuals have to be perfect. But just to be
>safe, your copyright page should say something like this "The
>information in this publication is provided AS-IS."
>
>That will solve the crisis.
>
>Brian Gause
>
>Technical Writer
>
>
>-----Original Message-----
>From: techwr-l-bounces+gause_brian=emc -dot- com -at- lists -dot- techwr-l -dot- com
>[mailto:techwr-l-bounces+gause_brian=emc -dot- com -at- lists -dot- techwr-l -dot- com] On
>Behalf Of Janet Swisher
>Sent: Monday, September 29, 2008 11:03 AM
>To: Technical Writer
>Cc: techwr-l -at- lists -dot- techwr-l -dot- com
>Subject: Re: Documentation Legal Issues???
>
>On Mon, Sep 29, 2008 at 8:40 AM, Technical Writer <tekwrytr -at- hotmail -dot- com>
>wrote:
>>
>> Other than implied warranty of fitness, and similar "generic good
>will" considerations, is anyone aware of specific legislation that
>mandates accuracy in documentation under penalty of law? For example, a
>mandate that would require a software product manual or other similar
>document to be "absolutely perfect"--meaning, if there was an error (not
>threatening to the life, limb, or well-being of the user), is there some
>law that would require a company to essentially recall and replace the
>entire manual?
>>
>> Despite having worked in the field as an independent contractor for a
>number of years, and taken various business classes at the local
>university on legal and regulatory issues, I have never heard of such.
>If anyone has, I would really appreciate it.
>>
>> The issue is not the software or product itself, but rather the
>documentation for that product. The way it was stated to me(by a
>technical writer for a software company), was that every manual, and
>presumably every piece of documentation generated, was a "legally
>binding contract," and as such, had zero tolerance for errors of any
>type.
>>
>
>A company I worked for put in their contracts that the software was
>warranted to work "as documented". This did not lead to them requiring
>that the documentation be perfect. Rather, it led to omitting things
>from the documentation if there was any possibility that the software
>might now work that way (e.g., last-minute features), while still
>producing plausibly complete docs. I think they also took the view
>that a discrepancy between the docs and the software would simply be
>considered a software defect, to be remedied under the maintenance
>section of the contract. The software in question was potentially
>business-critical but not life-critical.
>
>That clause of the contracts was never tested while I was there.
>
>
>
>-- 
>Visit my blog at: http://www.janetswisher.com
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>ComponentOne Doc-To-Help gives you everything you need to author and 
>publish quality Help, Web, and print content. Perfect for technical 
>authors, developers, and policy writers. Download a FREE trial.
>http://www.componentone.com/DocToHelp/
>
>True single source, conditional content, PDF export, modular help.
>Help & Manual is the most powerful authoring tool for technical
>documentation. Boost your productivity! http://www.helpandmanual.com
>
>---
>You are currently subscribed to TECHWR-L as gause_brian -at- emc -dot- com -dot- 
>
>To unsubscribe send a blank email to 
>techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
>or visit
>http://lists.techwr-l.com/mailman/options/techwr-l/gause_brian%40emc.com
>
>
>To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
>
>Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
>http://www.techwr-l.com/ for more resources and info.
>
>
>
>
>------------------------------
>
>Message: 24
>Date: Mon, 29 Sep 2008 15:39:34 -0400
>From: "Dan Goldstein" <DGoldstein -at- riverainmedical -dot- com>
>Subject: RE: Documentation Legal Issues???
>To: <techwr-l -at- lists -dot- techwr-l -dot- com>
>Message-ID:
>	<0ADA9A22B5BC2147B360A22FD2BAD25C01379560 -at- RMGBEX01 -dot- rmg -dot- local>
>Content-Type: text/plain;	charset="us-ascii"
>
>No. To be safe, ask your company lawyer for the correct text.
>
>> -----Original Message-----
>> From: Gause_Brian
>> Sent: Monday, September 29, 2008 3:29 PM
>> To: techwr-l -at- lists -dot- techwr-l -dot- com
>> Subject: RE: Documentation Legal Issues???
>> 
>> ...There is no law saying your manuals have to be perfect. But 
>> just to be safe, your copyright page should say something 
>> like this "The information in this publication is provided AS-IS"...
>> 
>
>This message contains confidential information intended only for the use of
the addressee(s). If you are not the addressee, or the person responsible
for delivering it to the addressee, you are hereby notified that reading,
disseminating, distributing, copying, electronic storing or the taking of
any action in reliance on the contents of this message is strictly
prohibited.  If you have received this message by mistake, please notify us,
by replying to the sender, and delete the original message immediately
thereafter.  Thank you.
>
>
>
>------------------------------
>
>Message: 25
>Date: Mon, 29 Sep 2008 15:33:56 -0700
>From: "Chris Morton" <salt -dot- morton -at- gmail -dot- com>
>Subject: Re: Can you help me with this macro? (Word 2003)
>To: techwr-l -at- lists -dot- techwr-l -dot- com
>Message-ID:
>	<746d910c0809291533l9c3c6a7of0c90cf648b2044e -at- mail -dot- gmail -dot- com>
>Content-Type: text/plain; charset=ISO-8859-1
>
>I did find the link to M$'s free version of *SendKeysTo*, called*
ScriptIt*:
>
>http://technet.microsoft.com/en-us/library/cc723493.aspx
>
>No VBA involved!
>
>> Chris
>
>On 9/29/08, Jonathan West <jwest -at- mvps -dot- org> wrote:
>>
>> 2008/9/29 Hemstreet, Deborah <DHemstreet -at- kaydon -dot- com>:
>> > Hi All,
>> >
>> > Below my question is a macro I've recorded. My question: I want this
>> > macro to merely open the Cross Reference dialog box, with it pre-set to
>> > insert a Figure with the Only Label and Number option selected. The
user
>> > would then select the figure number, insert the ref and close the
dialog
>> > box.
>> >
>> > Is there a way to modify this macro for the above desired action? My
>> > attempts have failed.
>> >
>>
>> Not easy, as the dialog doesn't respond as it should to setting the
>> dialog box arguments, so you have to use SendKeys which can be rather
>> flaky. But this does seem to work.
>>
>> With Dialogs(wdDialogInsertCrossReference)
>> SendKeys "ff{TAB}{DOWN}{DOWN}~%w": .Show
>> End With
>>
>> The "ff" sets the reference kind to Figure. The "{TAB}" moves the
>> focus across to the "Insert reference to" box. "{DOWN}{DOWN}" opens
>> the dropdown and moves down one item. "~" selects and closes the
>> dropdown. "%w" moves the focus to the "For which heading" dialog.
>>
>> It works for me. YMMV.
>>
>> Regards
>> Jonathan West
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>> ComponentOne Doc-To-Help gives you everything you need to author and
>> publish quality Help, Web, and print content. Perfect for technical
>> authors, developers, and policy writers. Download a FREE trial.
>> http://www.componentone.com/DocToHelp/
>>
>> True single source, conditional content, PDF export, modular help.
>> Help & Manual is the most powerful authoring tool for technical
>> documentation. Boost your productivity! http://www.helpandmanual.com
>>
>> ---
>> You are currently subscribed to TECHWR-L as salt -dot- morton -at- gmail -dot- com -dot- 
>>
>> To unsubscribe send a blank email to
>> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
>> or visit
>>
http://lists.techwr-l.com/mailman/options/techwr-l/salt.morton%40gmail.com
>>
>>
>> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
>>
>> Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
>> http://www.techwr-l.com/ for more resources and info.
>>
>>
>
>
>------------------------------
>
>_______________________________________________
>You are currently subscribed to 
>TECHWR-L.
>To unsubscribe send a blank email to 
>http://lists.techwr-l.com/mailman/listinfo/techwr-l
>Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit 
>http://www.techwr-l.com/ for more resources and info.
>
>End of TECHWR-L Digest, Vol 35, Issue 28
>****************************************





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

ComponentOne Doc-To-Help gives you everything you need to author and 
publish quality Help, Web, and print content. Perfect for technical 
authors, developers, and policy writers. Download a FREE trial.
http://www.componentone.com/DocToHelp/

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to 
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/ for more resources and info.