Re: documentation best practices

2011-12-06 Thread Neeraj Jain
: Jeff Coatsworth jeff.coatswo...@jonassoftware.com To: framers@lists.frameusers.com framers@lists.frameusers.com Sent: Tuesday, 6 December 2011 3:51 AM Subject: RE: documentation best practices It's called marketing ;) From: framers-boun...@lists.frameusers.com

Re: documentation best practices

2011-12-06 Thread Neeraj Jain
) syed.hos...@aeris.net To: Writer generic...@yahoo.ca; Jeff Coatsworth jeff.coatswo...@jonassoftware.com; framers@lists.frameusers.com framers@lists.frameusers.com Sent: Tuesday, 6 December 2011 5:45 AM Subject: RE: documentation best practices Not necessarily, but usually, I suspect. J   In our

RE: Documentation Best Practices

2011-12-06 Thread Galanter, Lea
Don't know if anyone has mentioned this, but the reason why you're not supposed to mention what will be in future versions is for legal reasons. You should not make forward-looking statements because the company could be held legally responsible for them. And since none of us can guarantee what

Re: documentation best practices

2011-12-06 Thread Grant Hogarth
@lists.frameusers.com framers@lists.frameusers.com *Sent:* Monday, December 5, 2011 5:21:46 PM *Subject:* RE: documentation best practices It's called marketing ;) *From:* framers-boun

Re: Documentation Best Practices

2011-12-06 Thread Writer
Nicely put. Nadine From: Galanter, Lea lea.galan...@fticonsulting.com To: framers@lists.frameusers.com Sent: Tuesday, December 6, 2011 1:30:28 PM Subject: RE: Documentation Best Practices Don't know if anyone has mentioned this, but the reason why you're

Re: documentation best practices

2011-12-06 Thread Steve Rickaby
At 02:56 -0800 5/12/11, hessiansx4 wrote: I could use some insight into a situation I haven't encountered before today: how does one best respond to a request (read: order) to include something in their product's documentation about a functionality that will not be released with the upcoming

RE: documentation best practices

2011-12-05 Thread Lea Rush
As someone who both develops and documents software, I can only answer with a hearty “Hear hear!”. I think you’re exactly right, and I hope you can get them to see the light. Good luck, Lea _ Lea Rush Software and Documentation Specialist Astoria-Pacific

RE: documentation best practices

2011-12-05 Thread Owen, Clint
If they insist, I would make sure that it is well-marked as a future enhancement, perhaps is a separate section of the documentation. I just had a situation where a major aircraft maker (the one that does not start with a B) gave all sorts of very specific information about a software tool to

RE: documentation best practices

2011-12-05 Thread Jeff Coatsworth
It's called marketing ;) From: framers-boun...@lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of hessiansx4 Sent: Monday, December 05, 2011 5:56 AM To: framers@lists.frameusers.com Subject: documentation best practices I could use

Re: documentation best practices

2011-12-05 Thread Writer
Subject: RE: documentation best practices It's called marketing ;) From: framers-boun...@lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of hessiansx4 Sent: Monday, December 05, 2011 5:56 AM To: framers@lists.frameusers.com Subject