TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Use of XLST to clean up MadCap HTML; RE: Unadulterated Flare HTML/XML output
Subject:Use of XLST to clean up MadCap HTML; RE: Unadulterated Flare HTML/XML output From:"Porrello, Leonard" <lporrello -at- illumina -dot- com> To:'Mark Giffin' <mgiffin -at- earthlink -dot- net> Date:Mon, 8 Aug 2011 21:26:52 +0000
As far as I can tell, you can use XSLT only to convert/transform XML files, so I am not sure how it would work for Flare or Flare output. Help? Anyone?
-----Original Message-----
From: Porrello, Leonard
Sent: Monday, August 08, 2011 9:10 AM
To: 'Mark Giffin'
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: Unadulterated Flare HTML/XML output
Thanks for the tip, Mark. We want to use Flare to single-source end user docs as well as content for an online "portal." In the end user docs MadCap tags are not a problem, but the content in the portal cannot have MadCap tags.
I'd not heard of XSLT before you sent your note, so I hope you forgive the naiveté of my question. Would you do the "identity transform" on normal generated WebHelp output?
-----Original Message-----
From: Mark Giffin [mailto:mgiffin -at- earthlink -dot- net]
Sent: Saturday, August 06, 2011 8:23 PM
To: Porrello, Leonard
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Unadulterated Flare HTML/XML output
Leonard,
I see what you mean, but I guess I wouldn't call those proprietary,
because they use a standard XML namespace:
xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd";. Of
course, MadCap does not provide the full schema if you wanted to
validate their files in a real XML editor (I've tried to get the schema
over the last couple years), so maybe they are proprietary. If you want
to see real proprietary HTML, go back to the old RoboHelp days.
Anyway, you could use XSLT to remove the MadCap stuff. I don't think it
would be real complicated if you knew XSLT. I would use an "identity
transform" to copy the entire contents of the file, plus a few templates
to snuff out the MadCap bits.
On 8/5/2011 12:25 PM, Porrello, Leonard wrote:
> There's the header info:
>
> <?xml version="1.0" encoding="utf-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
> <html xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd"; MadCap:lastBlockDepth="7" MadCap:lastHeight="211" MadCap:lastWidth="808" MadCap:disableMasterStylesheet="true" MadCap:tocPath="" MadCap:medium="OLH" MadCap:InPreviewMode="false" MadCap:PreloadImages="false" MadCap:RuntimeFileType="Topic" MadCap:TargetType="WebHelp" lang="en-us" xml:lang="en-us" MadCap:PathToHelpSystem="../../../../" MadCap:HelpSystemFileName="Default.xml" MadCap:SearchType="Stem">
>
> And then there is inline stuff:
>
> <td class="AutoNumber_p_Bullet1" MadCap:autonum="<span style="color: #b7b7b7;" class="mcFormatColor">*</span>" valign="top"><b>Coordinates</b> based on start and stop bp range for chromosomes</td>
>
> <p class="TblTitle" MadCap:conditions="" MadCap:autonum="Table 47  " MadCap:xrefTargetName="Table_47_  Manage_Targets_Tab_Options"><a MadCap:generatedBookmark="ListOf" name="Table_47_  Manage_Targets_Tab_Options"></a><span class="autonumber"><span class="KeyColorBold">Table 47  </span></span>Manage Targets Tab Options</p>
>
> <script type="text/javascript" src="../../../SkinSupport/MadCapBodyEnd.js">
>
> -----Original Message-----
> From: techwr-l-bounces+lporrello=illumina -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+lporrello=illumina -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of Robert Lauriston
> Sent: Thursday, August 04, 2011 3:35 PM
> To: techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: Re: Unadulterated Flare HTML/XML output
>
> Such as what? Looking at the HTML files in the Content directory of my
> Flare 7.1 WebHelp output, I don't see any proprietary tags.
>
> On Thu, Aug 4, 2011 at 2:07 PM, Porrello, Leonard
> <lporrello -at- illumina -dot- com> wrote:
>> Does anyone know how to get HTML or XML files out of Flare that are free from proprietary Flare tags?
>
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
