Comments on: Six Persistent Flare Problems http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/ Paul Pehrson's technical writing blog Wed, 08 Oct 2008 05:19:20 +0000 http://wordpress.org/?v=2.6.2 By: paul http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-56006 paul Mon, 28 Apr 2008 14:10:57 +0000 http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-56006 Hi Chris, Yes, the munged output is a result of the Flare Demo. Basically MadCap doesn't want you downloading the demo version and using it to create all your content files without purchasing Flare. In fact, Flare warns you of this when you load it. Since you haven't registered your version, when Flare starts, it asks you if you want to run in trial mode, or if you want to purchase a copy. When you select trial mode, a pop-up warns you that all output will be munged. What you are calling "misspellings" is what Flare calls "munging." When you purchase a full copy of Flare, the files build as you would expect, without messing up the content. This allows you to create an unlimited number of topics so you can see how your particular project scales. The nice thing about munging the output is that when you purchase a copy of Flare, you can continue to use the topics you've already written, because the trial munging only happens to the output. The source files are not altered. Simpily enter your registration key, and you can continue working where you left off in Flare. Hope this helps. Have a great day. Thanks for reading.<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('56006','paul'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('56006','paul','Hi Chris,\r\n\r\nYes, the munged output is a result of the Flare Demo. Basically MadCap doesn\'t want you downloading the demo version and using it to create all your content files without purchasing Flare.\r\n\r\nIn fact, Flare warns you of this when you load it. Since you haven\'t registered your version, when Flare starts, it asks you if you want to run in trial mode, or if you want to purchase a copy. When you select trial mode, a pop-up warns you that all output will be munged. What you are calling \"misspellings\" is what Flare calls \"munging.\" \r\n\r\nWhen you purchase a full copy of Flare, the files build as you would expect, without messing up the content.\r\n\r\nThis allows you to create an unlimited number of topics so you can see how your particular project scales. The nice thing about munging the output is that when you purchase a copy of Flare, you can continue to use the topics you\'ve already written, because the trial munging only happens to the output. The source files are not altered. Simpily enter your registration key, and you can continue working where you left off in Flare.\r\n\r\nHope this helps. Have a great day.\r\n\r\nThanks for reading.'); return false;">Quote</a></div> Hi Chris,

Yes, the munged output is a result of the Flare Demo. Basically MadCap doesn’t want you downloading the demo version and using it to create all your content files without purchasing Flare.

In fact, Flare warns you of this when you load it. Since you haven’t registered your version, when Flare starts, it asks you if you want to run in trial mode, or if you want to purchase a copy. When you select trial mode, a pop-up warns you that all output will be munged. What you are calling “misspellings” is what Flare calls “munging.”

When you purchase a full copy of Flare, the files build as you would expect, without messing up the content.

This allows you to create an unlimited number of topics so you can see how your particular project scales. The nice thing about munging the output is that when you purchase a copy of Flare, you can continue to use the topics you’ve already written, because the trial munging only happens to the output. The source files are not altered. Simpily enter your registration key, and you can continue working where you left off in Flare.

Hope this helps. Have a great day.

Thanks for reading.

Reply - Quote
]]> By: Chris http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-56000 Chris Mon, 28 Apr 2008 07:12:51 +0000 http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-56000 Hi, Iam using Flare demo version. After generating any output file the words are all misspelled. implies the content in WYSWIG is not matching with the content of output file. Is this because m using demo.....plz help me out in this reagard. Thnx<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('56000','Chris'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('56000','Chris','Hi,\r\nIam using Flare demo version. After generating any output file the words are all misspelled. implies the content in WYSWIG is not matching with the content of output file. Is this because m using demo.....plz help me out in this reagard.\r\nThnx'); return false;">Quote</a></div> Hi,
Iam using Flare demo version. After generating any output file the words are all misspelled. implies the content in WYSWIG is not matching with the content of output file. Is this because m using demo…..plz help me out in this reagard.
Thnx
Reply - Quote
]]> By: paul http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-55364 paul Thu, 27 Mar 2008 21:46:33 +0000 http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-55364 Tana, Yes, the Linux box can obviously incorporate the builds, but there is no way for my Linux build box to kick off a new build. It can only grab whatever build I most recently made. If I made changes to the project and didn't build it, then those changes won't be included in the product build. (But if your application is a .NET application, then you won't be worried too much about this for your own project.) I've never heard of somebody using Eclipse as a HAT, so I'm not sure I can give you and advice there. Flare does, however, have a .NET help output for .NET applications. It is a pretty popular help output option. There are tons of ways you can integrate it directly into your application as well, so that is cool. I recommend that you go to <a href="http://madcapsoftware.com" rel="nofollow">MadCap's website</a> and download an evaluation copy of Flare and see what it can do for you. Also, you can visit the <a href="http://forums.madcapsoftware.com" rel="nofollow">MadCap Forums</a> for more information on the .NET output options and how you can integrate them into your application. Thanks for reading!!<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('55364','paul'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('55364','paul','Tana,\r\n\r\nYes, the Linux box can obviously incorporate the builds, but there is no way for my Linux build box to kick off a new build. It can only grab whatever build I most recently made. If I made changes to the project and didn\'t build it, then those changes won\'t be included in the product build. (But if your application is a .NET application, then you won\'t be worried too much about this for your own project.) \r\n\r\nI\'ve never heard of somebody using Eclipse as a HAT, so I\'m not sure I can give you and advice there. Flare does, however, have a .NET help output for .NET applications. It is a pretty popular help output option. There are tons of ways you can integrate it directly into your application as well, so that is cool. \r\n\r\nI recommend that you go to <a href=\"http:\/\/madcapsoftware.com\" rel=\"nofollow\">MadCap\'s website<\/a> and download an evaluation copy of Flare and see what it can do for you. \r\nAlso, you can visit the <a href=\"http:\/\/forums.madcapsoftware.com\" rel=\"nofollow\">MadCap Forums<\/a> for more information on the .NET output options and how you can integrate them into your application.\r\n\r\nThanks for reading!!'); return false;">Quote</a></div> Tana,

Yes, the Linux box can obviously incorporate the builds, but there is no way for my Linux build box to kick off a new build. It can only grab whatever build I most recently made. If I made changes to the project and didn’t build it, then those changes won’t be included in the product build. (But if your application is a .NET application, then you won’t be worried too much about this for your own project.)

I’ve never heard of somebody using Eclipse as a HAT, so I’m not sure I can give you and advice there. Flare does, however, have a .NET help output for .NET applications. It is a pretty popular help output option. There are tons of ways you can integrate it directly into your application as well, so that is cool.

I recommend that you go to MadCap’s website and download an evaluation copy of Flare and see what it can do for you.
Also, you can visit the MadCap Forums for more information on the .NET output options and how you can integrate them into your application.

Thanks for reading!!

Reply - Quote
]]> By: Tana http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-55363 Tana Thu, 27 Mar 2008 21:09:35 +0000 http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-55363 Paul, you mentioned in your Blog about the problems with Flare the issue of not being able to include your latest Help files with the nightly builds because the build machine is Linux... do you mean that the compiling of your help cannot be done on the linux box? Surely the output can be included in the builds, right? Know what i mean? Thanks, I am seeking a new HAT... so far it is between Eclipse and Flare. And I need to do some research on Flare's DotHelp, as my product is that platform, so if you have any insight on DotHelp, I would appreciate it. Tana<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('55363','Tana'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('55363','Tana','Paul, you mentioned in your Blog about the problems with Flare the issue of not being able to include your latest Help files with the nightly builds because the build machine is Linux... do you mean that the compiling of your help cannot be done on the linux box? Surely the output can be included in the builds, right? Know what i mean?\r\nThanks, I am seeking a new HAT... so far it is between Eclipse and Flare. And I need to do some research on Flare\'s DotHelp, as my product is that platform, so if you have any insight on DotHelp, I would appreciate it.\r\nTana'); return false;">Quote</a></div> Paul, you mentioned in your Blog about the problems with Flare the issue of not being able to include your latest Help files with the nightly builds because the build machine is Linux… do you mean that the compiling of your help cannot be done on the linux box? Surely the output can be included in the builds, right? Know what i mean?
Thanks, I am seeking a new HAT… so far it is between Eclipse and Flare. And I need to do some research on Flare’s DotHelp, as my product is that platform, so if you have any insight on DotHelp, I would appreciate it.
Tana
Reply - Quote
]]> By: David aka RamonS http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-49967 David aka RamonS Thu, 24 Jan 2008 00:58:29 +0000 http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-49967 Somewhere deep in the Flare forums I once came across a thread that indicated that MadCap sells "build licenses". I assume they are less expensive than the full license and I further assume that other than using the command line compile that license doesn't allow for doing much else. Way back when before Flare 1.0 came out I write to Mr. Hamilton and command line compile and source control integration were two of the core things that I though had to be in Flare 1.0. Well, the command line compile was there, but not the source control integration. Now it is there, but apparently fairly shaky and also fully Microsoft-centric. For a build server that may not come into play as one can pull the source out of source control via batch file and CLI. Speaking of which, I recommended multiple times to implement source control integration in Flare via CLI . A front end fires console commands via CLI and all is well. At one of my previous jobs we had a bunch of build scripts that pulled the source code from VSS, ran the compile, and packaged it all up using InnoSetup. That always worked, never gave a problem, and would have worked with any source control system that supports CLI. But no, MadCap had to use a proprietary, Microsoft-only API. I guess developer convenience won again over usability and flexibility. I really like MadCap's products and their approach in general, but they really block their way quite a bit by doing everything Microsoft-only. Number 5 is really dead-on.<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('49967','David aka RamonS'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('49967','David aka RamonS','Somewhere deep in the Flare forums I once came across a thread that indicated that MadCap sells \"build licenses\". I assume they are less expensive than the full license and I further assume that other than using the command line compile that license doesn\'t allow for doing much else.\r\nWay back when before Flare 1.0 came out I write to Mr. Hamilton and command line compile and source control integration were two of the core things that I though had to be in Flare 1.0. Well, the command line compile was there, but not the source control integration. Now it is there, but apparently fairly shaky and also fully Microsoft-centric. For a build server that may not come into play as one can pull the source out of source control via batch file and CLI. Speaking of which, I recommended multiple times to implement source control integration in Flare via CLI . A front end fires console commands via CLI and all is well. At one of my previous jobs we had a bunch of build scripts that pulled the source code from VSS, ran the compile, and packaged it all up using InnoSetup. That always worked, never gave a problem, and would have worked with any source control system that supports CLI. But no, MadCap had to use a proprietary, Microsoft-only API. I guess developer convenience won again over usability and flexibility.\r\nI really like MadCap\'s products and their approach in general, but they really block their way quite a bit by doing everything Microsoft-only. Number 5 is really dead-on.'); return false;">Quote</a></div> Somewhere deep in the Flare forums I once came across a thread that indicated that MadCap sells “build licenses”. I assume they are less expensive than the full license and I further assume that other than using the command line compile that license doesn’t allow for doing much else.
Way back when before Flare 1.0 came out I write to Mr. Hamilton and command line compile and source control integration were two of the core things that I though had to be in Flare 1.0. Well, the command line compile was there, but not the source control integration. Now it is there, but apparently fairly shaky and also fully Microsoft-centric. For a build server that may not come into play as one can pull the source out of source control via batch file and CLI. Speaking of which, I recommended multiple times to implement source control integration in Flare via CLI . A front end fires console commands via CLI and all is well. At one of my previous jobs we had a bunch of build scripts that pulled the source code from VSS, ran the compile, and packaged it all up using InnoSetup. That always worked, never gave a problem, and would have worked with any source control system that supports CLI. But no, MadCap had to use a proprietary, Microsoft-only API. I guess developer convenience won again over usability and flexibility.
I really like MadCap’s products and their approach in general, but they really block their way quite a bit by doing everything Microsoft-only. Number 5 is really dead-on.
Reply - Quote
]]> By: paul http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-43850 paul Mon, 19 Nov 2007 15:56:49 +0000 http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-43850 You don't even have the change the medium in your display before you publish; the medium is set in the target file (whether a Word target, a WebHelp target, or whatever). No matter what is shown on your screen, when you publish the target, the medium set in the target file will be used. (On the Advanced tab of your target, you can specifically set the Stylesheet Medium.) I <i>do</i> think the background color is a good idea, just so you remember what you are looking at. Did you just apply the background color the the body tag?<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('43850','paul'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('43850','paul','You don\'t even have the change the medium in your display before you publish; the medium is set in the target file (whether a Word target, a WebHelp target, or whatever). No matter what is shown on your screen, when you publish the target, the medium set in the target file will be used. (On the Advanced tab of your target, you can specifically set the Stylesheet Medium.)\r\n\r\nI <i>do<\/i> think the background color is a good idea, just so you remember what you are looking at. Did you just apply the background color the the body tag?'); return false;">Quote</a></div> You don’t even have the change the medium in your display before you publish; the medium is set in the target file (whether a Word target, a WebHelp target, or whatever). No matter what is shown on your screen, when you publish the target, the medium set in the target file will be used. (On the Advanced tab of your target, you can specifically set the Stylesheet Medium.)

I do think the background color is a good idea, just so you remember what you are looking at. Did you just apply the background color the the body tag?

Reply - Quote
]]> By: Jay Stephens http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-43822 Jay Stephens Mon, 19 Nov 2007 10:49:53 +0000 http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-43822 Great workaround Paul. I've also added a subtle a light green background colour to my new "BigOnScreen" medium's styles, so that I have a visual cue to remind me to change the medium before I publish.<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('43822','Jay Stephens'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('43822','Jay Stephens','Great workaround Paul.\r\nI\'ve also added a subtle a light green background colour to my new \"BigOnScreen\" medium\'s styles, so that I have a visual cue to remind me to change the medium before I publish.'); return false;">Quote</a></div> Great workaround Paul.
I’ve also added a subtle a light green background colour to my new “BigOnScreen” medium’s styles, so that I have a visual cue to remind me to change the medium before I publish.
Reply - Quote
]]> By: paul http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-43780 paul Mon, 19 Nov 2007 03:23:02 +0000 http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-43780 Hi, Jay Thanks for the comment. You aren't the first to complain about this. There isn't a setting anywhere that allows you to change the size of the text in the XML editor (unfortunately). However, what I have heard other people suggest is that you add an additional media type to your CSS style sheet, and when you are editing in the XML editor select that medium from the drop-down (top right of the XML editor). In fact, you could just go through the elements in your new media type, and change the font size. The other features would be inherited from the basic style sheet. Then, when you publish your targets, just make sure you have selected the default style medium, and nothing in your output should change. Its a bit more work, but you should be able to get the XML editor to show the text in a larger font. It might be worth it to submit a feature request to MadCap software. Their bug/feature page is: http://www.madcapsoftware.com/bugs/submit.aspx<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('43780','paul'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('43780','paul','Hi, Jay\r\n\r\nThanks for the comment.\r\n\r\nYou aren\'t the first to complain about this. There isn\'t a setting anywhere that allows you to change the size of the text in the XML editor (unfortunately). However, what I have heard other people suggest is that you add an additional media type to your CSS style sheet, and when you are editing in the XML editor select that medium from the drop-down (top right of the XML editor). In fact, you could just go through the elements in your new media type, and change the font size. The other features would be inherited from the basic style sheet.\r\n\r\nThen, when you publish your targets, just make sure you have selected the default style medium, and nothing in your output should change.\r\n\r\nIts a bit more work, but you should be able to get the XML editor to show the text in a larger font.\r\n\r\nIt might be worth it to submit a feature request to MadCap software. Their bug\/feature page is:\r\n\r\nhttp:\/\/www.madcapsoftware.com\/bugs\/submit.aspx'); return false;">Quote</a></div> Hi, Jay

Thanks for the comment.

You aren’t the first to complain about this. There isn’t a setting anywhere that allows you to change the size of the text in the XML editor (unfortunately). However, what I have heard other people suggest is that you add an additional media type to your CSS style sheet, and when you are editing in the XML editor select that medium from the drop-down (top right of the XML editor). In fact, you could just go through the elements in your new media type, and change the font size. The other features would be inherited from the basic style sheet.

Then, when you publish your targets, just make sure you have selected the default style medium, and nothing in your output should change.

Its a bit more work, but you should be able to get the XML editor to show the text in a larger font.

It might be worth it to submit a feature request to MadCap software. Their bug/feature page is:

http://www.madcapsoftware.com/bugs/submit.aspx

Reply - Quote
]]> By: Jay Stephens http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-43778 Jay Stephens Mon, 19 Nov 2007 02:51:08 +0000 http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-43778 Hey Paul, I've Googled & Forum'd this one to death, and can't find it anywhere in the interface.... is there a way to up the font size in the XML editor? I find working in is giving me eye strain, and it's currently my number one Flare gripe, to the point where I keep publishing to do every single proofread, which is slowing me down.<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('43778','Jay Stephens'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('43778','Jay Stephens','Hey Paul,\r\nI\'ve Googled &amp; Forum\'d this one to death, and can\'t find it anywhere in the interface.... is there a way to up the font size in the XML editor? I find working in is giving me eye strain, and it\'s currently my number one Flare gripe, to the point where I keep publishing to do every single proofread, which is slowing me down.'); return false;">Quote</a></div> Hey Paul,
I’ve Googled & Forum’d this one to death, and can’t find it anywhere in the interface…. is there a way to up the font size in the XML editor? I find working in is giving me eye strain, and it’s currently my number one Flare gripe, to the point where I keep publishing to do every single proofread, which is slowing me down.
Reply - Quote
]]> By: Michelle http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-37055 Michelle Wed, 18 Jul 2007 18:16:57 +0000 http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/#comment-37055 Paul: This is great, and I've experienced several of these quirks myself. I've hung on to v1.12 for a while due to the fact that I'm a broke independent contractor. (I will probably upgrade to v3 in a month or so.) As for .NET, I'm afraid it's here to stay. Several of the software products I document are based on a .Net framework. I believe it even comes installed on Windows Vista w/o the user needing know a thing about its existence. Upgrades are automatic through the dangerous windows Auto-Update. Since my clients require .Net, and Flare requires it, I haven't been able to upgrade to the wonderful MacBook I've had my eye on. I know they run Windows now, but I'm afraid .Net might be asking too much. Cheers!<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('37055','Michelle'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('37055','Michelle','Paul:\r\nThis is great, and I\'ve experienced several of these quirks myself. I\'ve hung on to v1.12 for a while due to the fact that I\'m a broke independent contractor. (I will probably upgrade to v3 in a month or so.)\r\nAs for .NET, I\'m afraid it\'s here to stay. Several of the software products I document are based on a .Net framework. I believe it even comes installed on Windows Vista w\/o the user needing know a thing about its existence. Upgrades are automatic through the dangerous windows Auto-Update. Since my clients require .Net, and Flare requires it, I haven\'t been able to upgrade to the wonderful MacBook I\'ve had my eye on. I know they run Windows now, but I\'m afraid .Net might be asking too much.\r\n\r\nCheers!'); return false;">Quote</a></div> Paul:
This is great, and I’ve experienced several of these quirks myself. I’ve hung on to v1.12 for a while due to the fact that I’m a broke independent contractor. (I will probably upgrade to v3 in a month or so.)
As for .NET, I’m afraid it’s here to stay. Several of the software products I document are based on a .Net framework. I believe it even comes installed on Windows Vista w/o the user needing know a thing about its existence. Upgrades are automatic through the dangerous windows Auto-Update. Since my clients require .Net, and Flare requires it, I haven’t been able to upgrade to the wonderful MacBook I’ve had my eye on. I know they run Windows now, but I’m afraid .Net might be asking too much.

Cheers!

Reply - Quote
]]>