<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: And you didn&#8217;t think grammar was important</title>
	<atom:link href="http://blog.paulpehrson.com/2006/10/19/and-you-didnt-thing-grammar-was-important/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.paulpehrson.com/2006/10/19/and-you-didnt-thing-grammar-was-important/</link>
	<description>Paul Pehrson's technical writing blog</description>
	<pubDate>Sat, 22 Nov 2008 11:08:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: paul</title>
		<link>http://blog.paulpehrson.com/2006/10/19/and-you-didnt-thing-grammar-was-important/#comment-53102</link>
		<dc:creator>paul</dc:creator>
		<pubDate>Fri, 22 Feb 2008 03:21:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulpehrson.com/2006/10/19/and-you-didnt-thing-grammar-was-important/#comment-53102</guid>
		<description>Kristin,

Thanks for writing.  I agree with you... there are several problems that continue in Flare. I guess I do what you do, submit a bug report or contact support, and then figure out how to work around it. I've changed the way I lay out my Word doc, or I've made a list of steps I do post-processing, or whatever. There are some stability problems I experience that I'd love to see addressed; Flare tends to crash a lot for me when I'm using it.

That said, I have to say that I'm impressed with how MadCap as a company responds to the suggestions I've made. I'm one of their smaller customers. I have a single Flare license, and I only have Bronze support. However, when I posted a blog entry on persistent Flare problems, MadCap called me on the phone to discuss the problems I was experiencing. As you go back to that post, you can see how several of those problems have been resolved in subsequent releases. So, I find that very impressive. I have never been a customer of a software company that is so responsive to my needs. 

Have all of my concerns been addressed? Not yet. But I'm willing to work through the problems because (1) I truly believe in the power of the software to improve my workflow and output, and (2) I believe that my voice has been heard, and that my issues have been looked at, and will be addressed in some form at some future point. 

I don't know if this is entirely helpful to you, or not. I understand your troubles. I know how hard it is to work through the problems you encounter in your main authoring tool. I don't think this is a MadCap-specific problem, speaking of the industry as a whole. While I recognize that the problems you are experiencing are MadCap-specific, I am trying to point out that regardless of the tool you chose, you're going to have problems and you are going to need to find work arounds. I'm glad to be doing it with a product I believe in and with a company that I believe cares. 

Try getting that kind of response from Adobe. I've never been successful with it.&lt;div class="comment-remix-meta"&gt;&lt;a href="#" class="replyto" onclick="replyto('53102','paul'); return false;"&gt;Reply&lt;/a&gt;  - &lt;a href="#" class="quote" onclick="quote('53102','paul','Kristin,\r\n\r\nThanks for writing.  I agree with you... there are several problems that continue in Flare. I guess I do what you do, submit a bug report or contact support, and then figure out how to work around it. I\'ve changed the way I lay out my Word doc, or I\'ve made a list of steps I do post-processing, or whatever. There are some stability problems I experience that I\'d love to see addressed; Flare tends to crash a lot for me when I\'m using it.\r\n\r\nThat said, I have to say that I\'m impressed with how MadCap as a company responds to the suggestions I\'ve made. I\'m one of their smaller customers. I have a single Flare license, and I only have Bronze support. However, when I posted a blog entry on persistent Flare problems, MadCap called me on the phone to discuss the problems I was experiencing. As you go back to that post, you can see how several of those problems have been resolved in subsequent releases. So, I find that very impressive. I have never been a customer of a software company that is so responsive to my needs. \r\n\r\nHave all of my concerns been addressed? Not yet. But I\'m willing to work through the problems because (1) I truly believe in the power of the software to improve my workflow and output, and (2) I believe that my voice has been heard, and that my issues have been looked at, and will be addressed in some form at some future point. \r\n\r\nI don\'t know if this is entirely helpful to you, or not. I understand your troubles. I know how hard it is to work through the problems you encounter in your main authoring tool. I don\'t think this is a MadCap-specific problem, speaking of the industry as a whole. While I recognize that the problems you are experiencing are MadCap-specific, I am trying to point out that regardless of the tool you chose, you\'re going to have problems and you are going to need to find work arounds. I\'m glad to be doing it with a product I believe in and with a company that I believe cares. \r\n\r\nTry getting that kind of response from Adobe. I\'ve never been successful with it.'); return false;"&gt;Quote&lt;/a&gt;&lt;/div&gt;</description>
		<content:encoded><![CDATA[<p>Kristin,</p>
<p>Thanks for writing.  I agree with you&#8230; there are several problems that continue in Flare. I guess I do what you do, submit a bug report or contact support, and then figure out how to work around it. I&#8217;ve changed the way I lay out my Word doc, or I&#8217;ve made a list of steps I do post-processing, or whatever. There are some stability problems I experience that I&#8217;d love to see addressed; Flare tends to crash a lot for me when I&#8217;m using it.</p>
<p>That said, I have to say that I&#8217;m impressed with how MadCap as a company responds to the suggestions I&#8217;ve made. I&#8217;m one of their smaller customers. I have a single Flare license, and I only have Bronze support. However, when I posted a blog entry on persistent Flare problems, MadCap called me on the phone to discuss the problems I was experiencing. As you go back to that post, you can see how several of those problems have been resolved in subsequent releases. So, I find that very impressive. I have never been a customer of a software company that is so responsive to my needs. </p>
<p>Have all of my concerns been addressed? Not yet. But I&#8217;m willing to work through the problems because (1) I truly believe in the power of the software to improve my workflow and output, and (2) I believe that my voice has been heard, and that my issues have been looked at, and will be addressed in some form at some future point. </p>
<p>I don&#8217;t know if this is entirely helpful to you, or not. I understand your troubles. I know how hard it is to work through the problems you encounter in your main authoring tool. I don&#8217;t think this is a MadCap-specific problem, speaking of the industry as a whole. While I recognize that the problems you are experiencing are MadCap-specific, I am trying to point out that regardless of the tool you chose, you&#8217;re going to have problems and you are going to need to find work arounds. I&#8217;m glad to be doing it with a product I believe in and with a company that I believe cares. </p>
<p>Try getting that kind of response from Adobe. I&#8217;ve never been successful with it.
<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('53102','paul'); return false;">Reply</a>  - <a href="#" class="quote" onclick="quote('53102','paul','Kristin,\r\n\r\nThanks for writing.  I agree with you... there are several problems that continue in Flare. I guess I do what you do, submit a bug report or contact support, and then figure out how to work around it. I\'ve changed the way I lay out my Word doc, or I\'ve made a list of steps I do post-processing, or whatever. There are some stability problems I experience that I\'d love to see addressed; Flare tends to crash a lot for me when I\'m using it.\r\n\r\nThat said, I have to say that I\'m impressed with how MadCap as a company responds to the suggestions I\'ve made. I\'m one of their smaller customers. I have a single Flare license, and I only have Bronze support. However, when I posted a blog entry on persistent Flare problems, MadCap called me on the phone to discuss the problems I was experiencing. As you go back to that post, you can see how several of those problems have been resolved in subsequent releases. So, I find that very impressive. I have never been a customer of a software company that is so responsive to my needs. \r\n\r\nHave all of my concerns been addressed? Not yet. But I\'m willing to work through the problems because (1) I truly believe in the power of the software to improve my workflow and output, and (2) I believe that my voice has been heard, and that my issues have been looked at, and will be addressed in some form at some future point. \r\n\r\nI don\'t know if this is entirely helpful to you, or not. I understand your troubles. I know how hard it is to work through the problems you encounter in your main authoring tool. I don\'t think this is a MadCap-specific problem, speaking of the industry as a whole. While I recognize that the problems you are experiencing are MadCap-specific, I am trying to point out that regardless of the tool you chose, you\'re going to have problems and you are going to need to find work arounds. I\'m glad to be doing it with a product I believe in and with a company that I believe cares. \r\n\r\nTry getting that kind of response from Adobe. I\'ve never been successful with it.'); return false;">Quote</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristin Randle</title>
		<link>http://blog.paulpehrson.com/2006/10/19/and-you-didnt-thing-grammar-was-important/#comment-53096</link>
		<dc:creator>Kristin Randle</dc:creator>
		<pubDate>Fri, 22 Feb 2008 01:52:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.paulpehrson.com/2006/10/19/and-you-didnt-thing-grammar-was-important/#comment-53096</guid>
		<description>Paul,

Cool site. I stumbled across it searching for technical writing positions where Flare is used. 

After reading some of your blogs and information about using Flare, I am curious about something. I'm sure you're familiar with most of Flare's bugs and defects. Having used the application as much as it appears you have, how are you dealing with those issues?

The reason I inquire is that we, my company, are no doubt one of Flare's larger clients. We're constantly finding defects and bugs that we've either logged on their site or called them about. In most cases, we receive no solution. We've become adept at work-arounds, and yet, it's getting so we're tired of it. We've been dealing with some of the same bugs since version 1.0. I would have thought by now, they'd be fixed. 

Maybe I'm looking for a sympathetic ear, but have you found this to be the case as well? 

Thanks for your time and for this site. It's quite handy! 

Kristin&lt;div class="comment-remix-meta"&gt;&lt;a href="#" class="replyto" onclick="replyto('53096','Kristin Randle'); return false;"&gt;Reply&lt;/a&gt;  - &lt;a href="#" class="quote" onclick="quote('53096','Kristin Randle','Paul,\r\n\r\nCool site. I stumbled across it searching for technical writing positions where Flare is used. \r\n\r\nAfter reading some of your blogs and information about using Flare, I am curious about something. I\'m sure you\'re familiar with most of Flare\'s bugs and defects. Having used the application as much as it appears you have, how are you dealing with those issues?\r\n\r\nThe reason I inquire is that we, my company, are no doubt one of Flare\'s larger clients. We\'re constantly finding defects and bugs that we\'ve either logged on their site or called them about. In most cases, we receive no solution. We\'ve become adept at work-arounds, and yet, it\'s getting so we\'re tired of it. We\'ve been dealing with some of the same bugs since version 1.0. I would have thought by now, they\'d be fixed. \r\n\r\nMaybe I\'m looking for a sympathetic ear, but have you found this to be the case as well? \r\n\r\nThanks for your time and for this site. It\'s quite handy! \r\n\r\nKristin'); return false;"&gt;Quote&lt;/a&gt;&lt;/div&gt;</description>
		<content:encoded><![CDATA[<p>Paul,</p>
<p>Cool site. I stumbled across it searching for technical writing positions where Flare is used. </p>
<p>After reading some of your blogs and information about using Flare, I am curious about something. I&#8217;m sure you&#8217;re familiar with most of Flare&#8217;s bugs and defects. Having used the application as much as it appears you have, how are you dealing with those issues?</p>
<p>The reason I inquire is that we, my company, are no doubt one of Flare&#8217;s larger clients. We&#8217;re constantly finding defects and bugs that we&#8217;ve either logged on their site or called them about. In most cases, we receive no solution. We&#8217;ve become adept at work-arounds, and yet, it&#8217;s getting so we&#8217;re tired of it. We&#8217;ve been dealing with some of the same bugs since version 1.0. I would have thought by now, they&#8217;d be fixed. </p>
<p>Maybe I&#8217;m looking for a sympathetic ear, but have you found this to be the case as well? </p>
<p>Thanks for your time and for this site. It&#8217;s quite handy! </p>
<p>Kristin
<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('53096','Kristin Randle'); return false;">Reply</a>  - <a href="#" class="quote" onclick="quote('53096','Kristin Randle','Paul,\r\n\r\nCool site. I stumbled across it searching for technical writing positions where Flare is used. \r\n\r\nAfter reading some of your blogs and information about using Flare, I am curious about something. I\'m sure you\'re familiar with most of Flare\'s bugs and defects. Having used the application as much as it appears you have, how are you dealing with those issues?\r\n\r\nThe reason I inquire is that we, my company, are no doubt one of Flare\'s larger clients. We\'re constantly finding defects and bugs that we\'ve either logged on their site or called them about. In most cases, we receive no solution. We\'ve become adept at work-arounds, and yet, it\'s getting so we\'re tired of it. We\'ve been dealing with some of the same bugs since version 1.0. I would have thought by now, they\'d be fixed. \r\n\r\nMaybe I\'m looking for a sympathetic ear, but have you found this to be the case as well? \r\n\r\nThanks for your time and for this site. It\'s quite handy! \r\n\r\nKristin'); return false;">Quote</a></div>
]]></content:encoded>
	</item>
</channel>
</rss>
