ÿþ<html xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:du="http://www.docsoft.com/xslt/date-utils"> <head> <META http-equiv="Content-Type" content="text/html; charset=UTF-16"> <title>W2XML 2.5 Help Documentation v2.5</title> <meta name="description" content="DocSoft Inc. - XML search, IETMs, and consulting."> <meta name="keywords" content="xml, search, engine, IETM, extend, bdynamics, XSL."><!-- This file automatically generated by DocSoft's Eclipse Autopublisher --> <link rel="stylesheet" type="text/css" href="helpstyle.css" title="styles"><script type="text/javascript" language="JavaScript1.2" src="sw2.js"></script><style> p { padding-bottom: 0; } .strong {text-weight:bold;} </style> </head> <body topmargin="0" leftmargin="0" marginheight="0" marginwidth="0" bgcolor="#ffffff"> <div id="mainPart"> <div align="center"><br><img src="../images/w2xv25Logo.jpg" alt="W2XML v2.5 Help Documentation" border="0"><br><br><b>W2XML v2.5 Help Documentation</b><br><br></div> <center>You may download the PDF version of this document <a class="link" id="_id1005" href="w2xHelp.pdf" target="_top">here</a>.</center> <center>Load <a class="link" id="_id1007" href="w2xfset.htm" target="_top">frameset</a>.</center> <div align="left" style="docData"><b>Software Name: </b><softwareName id="_id1009" xmlns:xi="http://www.w3.org/2001/XInclude">W2XML</softwareName><br><b>Software Description: </b><softwareDesc id="_id1010" xmlns:xi="http://www.w3.org/2001/XInclude">Converts *.doc, *.rtf, *.htm, *.asp, *.jsp to XML.</softwareDesc><br><b>Software Version Number: </b><versionNo id="_id1011" xmlns:xi="http://www.w3.org/2001/XInclude">2.5</versionNo><br><b>Version Release Date: </b><versionReleaseDate id="_id1013" xmlns:xi="http://www.w3.org/2001/XInclude">June 1, 2005</versionReleaseDate><br><b>Original Release Date: </b><releaseDate id="_id1012" xmlns:xi="http://www.w3.org/2001/XInclude">January 17, 2003</releaseDate><br><b>Software Author: </b><docAuthor id="_id1014" xmlns:xi="http://www.w3.org/2001/XInclude">DocSoft, Inc.</docAuthor><br><b>Author Website: </b><authorURL id="_id1015" xmlns:xi="http://www.w3.org/2001/XInclude">http://wwww.docsoft.com/</authorURL><br><b>Author Phone: </b><authorPhone id="_id1016" xmlns:xi="http://www.w3.org/2001/XInclude">1.877.430.3502 or 1.405.236.2466</authorPhone><br><b>Documentation Version Number: </b><docVer id="_id1017" xmlns:xi="http://www.w3.org/2001/XInclude">2.5.0</docVer><br><b>Last Updated: </b>Wednesday, June 08, 2005 5:20:36 PM<br><b>Support Site: </b><a href="http://www.docsoft.com/productq.aspx">http://www.docsoft.com/productq.aspx</a><br><b>Source Filename: </b><filename id="_id1020" xmlns:xi="http://www.w3.org/2001/XInclude">w2xHelp</filename>.xml<br></div><tocdoc id="_id1021" xmlns:xi="http://www.w3.org/2001/XInclude"></tocdoc><a name="_id1022"></a><a name="_id1024"></a><h3>Introduction</h3> <p id="_id1025" xmlns:xi="http://www.w3.org/2001/XInclude">W2XML will convert *.doc, *.rtf, *.asp, *.htm, *.html and *.jsp to well-formed XML. The software can also apply eXtensible Style Language Transformations (XSLTs) to the standard output so that you can match virtually any Schema's tag set.</p> <p id="_id1026" xmlns:xi="http://www.w3.org/2001/XInclude">Customers who use W2XML to convert Word to XML must understand the relatively complex concepts behind conversion from an unstructured format to a structured format. For this reason, DocSoft recommends that customers who are new to structured content or do not have the expertise to develop sometimes complex XSLTs, contract with <a class="link" id="_id1027" href="http://www.docsoft.com/consulting.htm">DocSoft's consulting services</a> to develop XSLTs to convert the standard output to a Schema or tag set for their specific needs.</p><a name="_id1028"></a><h5>Features Available in Version 2.5</h5> <ul><a name="_id1030"></a><li style="margin-bottom:4px;">Use W2XML to convert embedded <a class="link" id="_id2000" href="#EquationObjects">Equation Objects</a> to <a class="link" id="_id1031" href="http://www.w3.org/Math/">MathML</a></li><a name="_id1032"></a><li style="margin-bottom:4px;">New "<a class="link" id="_id2001" href="#Removerevisioninformation">Remove revision information</a>" option allows users to ignore revision information when publishing Word documents to xml</li><a name="_id1033"></a><li style="margin-bottom:4px;">New "<a class="link" id="_id2002" href="#RemoveSmartTags">Remove SmartTags</a>" option allows users to ignore SmartTags when publishing Word documents to xml</li> </ul><a name="_id1034"></a><h5>Features Available in Version 2.4</h5> <ul><a name="_id1036"></a><li style="margin-bottom:4px;">Use W2XML to <a class="link" id="_id2003" href="#preservepage">preserve page numbering</a> from original Word documents to xml</li> </ul><a name="_id1037"></a><h5>New parameters available to XSLT processor in Version 2.4</h5> <ul><a name="_id1039"></a><li style="margin-bottom:4px;">New element function <a class="link" id="_id2004" href="#w2x-cdata">w2x:cdata</a>, available attributes "xml | html | text"</li> </ul><a name="_id1040"></a><h5>Features Available in Version 2.3</h5> <ul><a name="_id1042"></a><li style="margin-bottom:4px;">Use <a class="link" id="_id1043" href="http://www.exslt.org/">EXSLT</a> library for transformation</li><a name="_id1045"></a><li style="margin-bottom:4px;">Use <a class="link" id="_id2005" href="#multiout">multiple output</a> transformation</li> </ul><a name="_id1046"></a><h5>Parameters available to XSLT processor in Version 2.3</h5> <ul><a name="_id1048"></a><li style="margin-bottom:4px;">Extended object functions in namespace "urn:schemas-docsoft-com:word-to-xml:extensions", such as <a class="link" id="_id2006" href="#hopts">GetOptionValue(Name)</a></li><a name="_id1049"></a><li style="margin-bottom:4px;"><a class="link" id="_id2007" href="#hopts">OutputExtension</a> - Specify any extension for exporting (versus only XML)</li><a name="_id1050"></a><li style="margin-bottom:4px;"><a class="link" id="_id2008" href="#hopts">CustomOptions</a> - Accessed in XSLT via GetOptionValue()</li> </ul><a name="_id1051"></a><h5>Features Added in Version 2.2</h5> <ul><a name="_id1053"></a><li style="margin-bottom:4px;"><a class="link" id="_id2009" href="#Groupfieldcontent">Group field content</a></li><a name="_id1054"></a><li style="margin-bottom:4px;"><a class="link" id="_id2010" href="#Removespacebeforepunctuation">Remove space before punctuation</a></li><a name="_id1055"></a><li style="margin-bottom:4px;"><a class="link" id="_id2011" href="#hopts">User Mode</a></li> </ul><a name="_id1056"></a><h5>Features Added in Version 2.1</h5> <ul><a name="_id1058"></a><li style="margin-bottom:4px;"><a class="link" id="_id2012" href="#Removeextraneousanchorbookmark">Remove extraneous anchor and bookmark tags</a></li><a name="_id1059"></a><li style="margin-bottom:4px;"><a class="link" id="_id2013" href="#PlaceWordimagesintosinglesubfolder">Export Images from Word® into single subfolder</a></li><a name="_id1060"></a><li style="margin-bottom:4px;"><a class="link" id="_id2014" href="#PostPublishing">Post Publishing</a></li> </ul><new_page id="_id1061" xmlns:xi="http://www.w3.org/2001/XInclude"></new_page><a name="_id1062"></a><a name="_id1064"></a><h3>System Requirements</h3> <p id="_id1065" xmlns:xi="http://www.w3.org/2001/XInclude">Please review the following requirements to ensure optimum application performance and operability:</p> <ul><a name="_id1067"></a><li style="margin-bottom:4px;">Windows Platform w/.NET® Framework 1.1;</li><a name="_id1068"></a><li style="margin-bottom:4px;">512 RAM;</li><a name="_id1069"></a><li style="margin-bottom:4px;">700K of hard disk space (additional 300K for the Universal Application Console);</li><a name="_id1070"></a><li style="margin-bottom:4px;">MSWord® 2000 (or greater) installed on host system;</li><a name="_id1071"></a><li style="margin-bottom:4px;">Mouse or suitable pointing device;</li><a name="_id1072"></a><li style="margin-bottom:4px;">Some knowledge of XSL is mandatory to create custom output.</li> </ul><a name="_id1073"></a><br><br><center> <table width="475" border="0" cellspacing="2" cellpadding="3" bgcolor="#CCFFFF"> <tr> <td valign="top"><b>NOTE: </b></td> <td><div><p id="_id1076" xmlns:xi="http://www.w3.org/2001/XInclude">Customers who use W2XML to convert Word to XML must understand the relatively complex concepts behind conversion from an unstructured format to a structured format. For this reason, DocSoft recommends that customers who are new to structured content or do not have the expertise to develop sometimes complex XSLTs, contract with <a class="link" id="_id1077" href="http://www.docsoft.com/consulting.htm">DocSoft's consulting services</a> to develop XSLTs to convert the standard output to a Schema or tag set for their specific needs.</p> </div></td> </tr> </table> </center><br><br><new_page id="_id1078" xmlns:xi="http://www.w3.org/2001/XInclude"></new_page><a name="_id1079"></a><br><br><center> <table width="475" border="0" cellspacing="2" cellpadding="3" bgcolor="#CCFFFF"> <tr> <td valign="top"><b>NOTE: </b></td> <td><div><p id="_id1082" xmlns:xi="http://www.w3.org/2001/XInclude">Some of the information in this help file is dynamically included from the source <a class="link" id="_id1083" href="http://www.docsoft.com/help/uacFset.htm" target="_top">UAC documentation</a> XML using <a class="link" id="_id1084" href="http://www.docsoft.com/eclipse.htm">Eclipse Autopublisher</a>. Therefore, some of the graphics used may have slight differences in terms of files and plug-ins used. This does not affect any procedural information.</p> </div></td> </tr> </table> </center><br><br><a name="prod4"></a><a name=""></a><h3>UAC Product Description</h3> <p xmlns:xi="http://www.w3.org/2001/XInclude">The Graphical User Interface (GUI) is simple and easy to learn. There are four main areas in the interface (see accompanying Figure 1):</p> <ol><a name=""></a><li style="margin-bottom:4px;">Menu Bar</li><a name=""></a><li style="margin-bottom:4px;">Toolbar</li><a name=""></a><li style="margin-bottom:4px;">Workspace List Window</li><a name=""></a><li style="margin-bottom:4px;">Options Window</li> </ol><a name="uac1"></a><div align="center"><br><img src="uacImgs/uac1.gif" border="0"><br><br><b>Figure 1 - Interface Description</b><br><br></div><new_page id="_id1086" xmlns:xi="http://www.w3.org/2001/XInclude"></new_page><a name="prod5"></a><a name=""></a><h3>UAC Menu Bar Description</h3> <p xmlns:xi="http://www.w3.org/2001/XInclude">When the GUI is first launched, the Menu Bar contains only three top-level menu options (as shown in Figure 2):</p> <ol><a name=""></a><li style="margin-bottom:4px;">File</li><a name=""></a><li style="margin-bottom:4px;">Workspace</li><a name=""></a><li style="margin-bottom:4px;">Help</li> </ol> <p xmlns:xi="http://www.w3.org/2001/XInclude">As soon as you load an application plug-in, the third top-level menu item inherits an application-specific menu item, usually named something similar to the loaded application. The UAC inherently comes packaged with a search-and-replace application called "Replace", which once loaded, applies menu items specific to the Replace application, as shown in Figure 3. Also notice the Options Window has also loaded application specific information as well.</p><a name="uac2"></a><div align="center"><br><img src="uacImgs/uac2.gif" border="0"><br><br><b>Figure 2 - Standard Menu Bar List Items</b><br><br></div><continued xmlns:xi="http://www.w3.org/2001/XInclude"></continued><a name="uac3"></a><div align="center"><br><img src="uacImgs/uac3.gif" border="0"><br><br><b>Figure 3 - Dynamic Menu Bar Loaded As Third Menu Item</b><br><br></div><continued xmlns:xi="http://www.w3.org/2001/XInclude"></continued><a name="uac001"></a><h5>File Menu</h5> <p xmlns:xi="http://www.w3.org/2001/XInclude">The <b>File Menu</b> is used to Create, Open, Save, and Save as Workspaces. You may also exit out of the UAC by choosing the "Exit" menu item.</p><a name="uac4"></a><div align="center"><br><img src="uacImgs/uac4.gif" border="0"><br><br><b>Figure 4 - File Menu</b><br><br></div><a name="uac002"></a><h5>Workspace Menu</h5> <p xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Workspace Menu</b> is used for actions specifically oriented around Workspace information, such as adding or removing files from a workspace, and/or changing the application plug-in for use within the Workspace.</p><a name="uac5"></a><div align="center"><br><img src="uacImgs/uac5.gif" border="0"><br><br><b>Figure 5 - Workspace Menu</b><br><br></div><continued xmlns:xi="http://www.w3.org/2001/XInclude"></continued><p xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Workspace Menu</b> is also used to load an installed application plug-in, using the <b>Change Plug-in...</b> menu item. This launches the <b>Select Plug-in</b> dialog (Figure 7).</p><a name="uac5b"></a><div align="center"><br><img src="uacImgs/uac5b.gif" border="0"><br><br><b>Figure 6 - UAC Drop Pad</b><br><br></div><continued xmlns:xi="http://www.w3.org/2001/XInclude"></continued><p xmlns:xi="http://www.w3.org/2001/XInclude">One of the features in the UAC is the <b>Drop Pad</b> (Figure 6). It is a shortcut that always stays on top, and appears at the lower, right-hand corner of the screen (it can be placed anywhere on the screen). The <b>Drop Pad</b> provides a quick method of adding files to the UAC. Simply drag-and-drop the files you want to add to the current UAC workspace to the <b>Drop Pad</b>.</p><a name="uac5a"></a><div align="center"><br><img src="uacImgs/uac5a.gif" border="0"><br><br><b>Figure 7 - Select Plug-in Dialog</b><br><br></div><a name="uac003"></a><h5>Dynamic Application Menu</h5> <p xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Dynamic Application Menu</b> is a menu item that is dynamically generated each time an application plug-in is loaded. It loads application-specific menu items depending on what application plug-in is currently loaded. The example in Figure 8 shows that the standard "Replace" application plug-in has been loaded and thereby shows menu items specific to the "Replace" application.</p> <p xmlns:xi="http://www.w3.org/2001/XInclude">The one standard menu item that will appear here is the <b>Options...</b> item. Choosing this option on any application plug-in will launch the "Options" dialog box, in which you can modify current associated options within the current workspace.</p><a name="uac6"></a><div align="center"><br><img src="uacImgs/uac6.gif" border="0"><br><br><b>Figure 8 - Dynamic Application Menu - Replace Application Example</b><br><br></div><continued xmlns:xi="http://www.w3.org/2001/XInclude"></continued><a name="uac004"></a><h5>Help Menu</h5> <p xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Help Menu</b> contains items relating to application help, both for the UAC and the installed application plug-ins. The <b>Plug-in Info...</b> item opens the <b>Plug-in Info</b> dialog (Figure 10), which displays information specific to the currently-loaded plug-in, such as <b>Plug-in Name</b>, <b>Version</b> and <b>Valid Files</b>, or files that the plug-in can effect or modify.</p><a name="uac7"></a><div align="center"><br><img src="uacImgs/uac7.gif" border="0"><br><br><b>Figure 9 - Help Menu</b><br><br></div><a name="uac8"></a><div align="center"><br><img src="uacImgs/uac8.gif" border="0"><br><br><b>Figure 10 - Plug-in Info Dialog</b><br><br></div><new_page id="_id1088" xmlns:xi="http://www.w3.org/2001/XInclude"></new_page><a name="prod6"></a><a name=""></a><h3>UAC Toolbar Description</h3> <p xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Toolbar</b> provides a quick, graphical interface to most of the functionality provided by the UAC. The following information describes each button's purpose.</p><a name="uac005"></a><h5>New Workspace Button</h5><a name="uac8a"></a><div align="center"><br><img src="uacImgs/uacToolbar1.gif" border="0"><br><br><b>Figure 11 - New Workspace Button</b><br><br></div> <p xmlns:xi="http://www.w3.org/2001/XInclude">The <b>New Workspace</b> button is used to create a new workspace.</p><a name="uac006"></a><h5>Open Workspace Button</h5><a name="uac8b"></a><div align="center"><br><img src="uacImgs/uacToolbar2.gif" border="0"><br><br><b>Figure 12 - Open Workspace Button</b><br><br></div> <p xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Open Workspace</b> button is used to open a previously-created workspace.</p><a name="uac007"></a><h5>Save Workspace Button</h5><a name="uac8c"></a><div align="center"><br><img src="uacImgs/uacToolbar3.gif" border="0"><br><br><b>Figure 13 - Save Workspace Button</b><br><br></div> <p xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Save Workspace</b> button is used to save a new or modified workspace.</p><a name="uac008"></a><h5>Add Files Button</h5><a name="uac8d"></a><div align="center"><br><img src="uacImgs/uacToolbar4.gif" border="0"><br><br><b>Figure 14 - Add Files Button</b><br><br></div> <p xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Add Files</b> button launches the <b>Open</b> dialog, which is used to browse and load files for use within the UAC.</p><a name="uac009"></a><h5>Remove Files Button</h5><a name="uac8e"></a><div align="center"><br><img src="uacImgs/uacToolbar5.gif" border="0"><br><br><b>Figure 15 - Remove Files Button</b><br><br></div> <p xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Remove Files</b> button removes selected files from the <b>Workspace List Window</b>.</p><a name="uac010"></a><h5>Process All Files Button</h5><a name="uac8f"></a><div align="center"><br><img src="uacImgs/uacToolbar6.gif" border="0"><br><br><b>Figure 16 - Process All Files Button</b><br><br></div> <p xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Process All Files</b> button initiates the run sequence using the parameters as defined in the application plug-in options on the files in the <b>Workspace List Window</b>.</p><new_page id="_id1090" xmlns:xi="http://www.w3.org/2001/XInclude"></new_page><a name="prod7"></a><a name=""></a><h3>UAC Workspace List Window Description</h3> <p xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Workspace List Window</b> displays the currently selected files the UAC will effect. It shows the <b>File</b> name, file <b>Size</b>, <b>Location</b> of each file, and the date/time the file was last <b>Modified</b>.</p> <p xmlns:xi="http://www.w3.org/2001/XInclude">You can add files to this window by using <b>Workspace &gt; Add Files...</b> to launch the <b>Open</b> dialog, or copy- or cut-and-paste files into the window, or simply drag-and-drop files into the window.</p> <p xmlns:xi="http://www.w3.org/2001/XInclude">If file types dragged into the window do not match the proper type for the loaded plug-in, the non-compatible file will be listed in red text (see Figure 18). Keeping these non-compatible files can be useful within a workspace in case you have multiple plug-ins you want to use on a single group of files, allowing you to create a single workspace of files to be effected through multiple plug-ins.</p><a name="uac9"></a><div align="center"><br><img src="uacImgs/uac9.gif" border="0"><br><br><b>Figure 17 - Workspace List Window</b><br><br></div><a name="uac10"></a><div align="center"><br><img src="uacImgs/uac10.gif" border="0"><br><br><b>Figure 18 - Workspace List Window with Non-Compatible Files</b><br><br></div><new_page id="_id1092" xmlns:xi="http://www.w3.org/2001/XInclude"></new_page><a name="uac506"></a><a name=""></a><h3>Installation</h3> <p xmlns:xi="http://www.w3.org/2001/XInclude">The UAC can be installed from CD or via an Electronic Software Distribution (ESD) file downloaded from the DocSoft website. You will need a valid key code to install the full version. After purchase, you will have seven (7) days to activate the software electronically. If you do not activate the software within seven (7) days, the software will not operate until it is properly activated.</p><a name="uac507"></a><a name=""></a><h3>Installation Procedure</h3> <p xmlns:xi="http://www.w3.org/2001/XInclude">The Universal Application Console is easy to install, and can be installed with just a few clicks. Use the following procedure to install the UAC.</p><a name=""></a><br><br><center> <table width="475" border="0" cellspacing="2" cellpadding="3" bgcolor="#CCFFFF"> <tr> <td valign="top"><b>NOTE: </b></td> <td><div><p xmlns:xi="http://www.w3.org/2001/XInclude">The installer file requires Windows Installer version 2 or greater. A compatible Windows Installer version is installed as part of the .NET Framework installation. If you received the executable via CD-ROM, a compatible Windows Installer version is located on the CD-ROM in the "Support Installs" directory.</p> <p xmlns:xi="http://www.w3.org/2001/XInclude">If you continue to have problems launching the UAC installer executable, visit <a class="link" href="http://www.microsoft.com/">http://www.microsoft.com/</a> to download the latest installer version.</p> </div></td> </tr> </table> </center><br><br><continued xmlns:xi="http://www.w3.org/2001/XInclude"></continued><ol><a name=""></a><li style="margin-bottom:4px;">Double-click the UACSetup.msi installer file. This will launch the installer wizard as shown in the following figure. Click "<b>Next &gt;</b>" to continue.</li><a name=""></a><div align="center"><br><img src="uacImgs/inst1.gif" border="0"><br><br><b>Figure 19 - Universal Application Console Installer Wizard</b><br><br></div><a name=""></a><li style="margin-bottom:4px;">Read the license agreement. If you agree to the license agreement, click "I agree" and press the "<b>Next &gt;</b>" button to continue.</li><a name=""></a><div align="center"><br><img src="uacImgs/inst2.gif" border="0"><br><br><b>Figure 20 - UAC License Agreement</b><br><br></div><a name=""></a><li style="margin-bottom:4px;">Select the folder in which to install the UAC files. Default is to "<b>C:\Program Files\DocSoft Universal Application Console\</b>". You may press the "<b>Browse...</b>" button to select a different folder. Press the "<b>Disk Cost...</b>" to see how much space will be needed to install the UAC. Select the "<b>Everyone</b>" radio button to install the UAC for everyone that will use the client computer, or "<b>Just me</b>" radio button to only allow the currently-logged-in user to use software. Press "<b>Next &gt;</b>" to continue.</li><a name=""></a><div align="center"><br><img src="uacImgs/inst3.gif" border="0"><br><br><b>Figure 21 - Select Installation Folder</b><br><br></div><a name=""></a><li style="margin-bottom:4px;">This screen allows the user to go back and change installation configuration before installing. If configuration is correct, press "<b>Next &gt;</b>" to continue. If changes need to be made, press "<b>&lt; Back</b>" to modify before continuing.</li><a name=""></a><div align="center"><br><img src="uacImgs/inst4.gif" border="0"><br><br><b>Figure 22 - Confirm Installation</b><br><br></div><a name=""></a><li style="margin-bottom:4px;">Upon successfully entering installation path information, the <b>Installing Universal Application Console</b> screen appears. A progress bar details the progress of the installation.</li><a name=""></a><div align="center"><br><img src="uacImgs/inst5.gif" border="0"><br><br><b>Figure 23 - Installing Universal Application Console</b><br><br></div><a name=""></a><li style="margin-bottom:4px;">Once installation is successful, the "<b>Installation Complete</b>" screen appears. Press "<b>Close</b>" to complete installation.</li><a name=""></a><div align="center"><br><img src="uacImgs/inst6.gif" border="0"><br><br><b>Figure 24 - Installation Complete</b><br><br></div> </ol><new_page id="_id1095" xmlns:xi="http://www.w3.org/2001/XInclude"></new_page><a name="uac516"></a><a name=""></a><h3>Creating a New Workspace</h3> <p xmlns:xi="http://www.w3.org/2001/XInclude">The UAC uses workspaces to save information for which files to effect, and which plug-in(s) and associated options to use within a workspace. You may create a workspace that does not contain any specific files, but rather only plug-in and options, so that you may add different files each time you need to effect different files over a period of time.</p> <p xmlns:xi="http://www.w3.org/2001/XInclude">The UAC also provides a method of using command line instructions to automatically schedule files to effect, or to run a series of workspaces in chronological order. Please see <b>Using Command Line Instructions</b> for detailed information.</p> <p xmlns:xi="http://www.w3.org/2001/XInclude">To create a new workspace, choose <b>File &gt; New Workspace</b> from the Menu Bar (as shown in Figure 25), or press <b>Ctrl+N</b>.</p><a name="uac15a"></a><div align="center"><br><img src="uacImgs/uac15a.gif" border="0"><br><br><b>Figure 25 - Creating New Workspace from File Menu</b><br><br></div><new_page id="_id1097" xmlns:xi="http://www.w3.org/2001/XInclude"></new_page><a name="uac517"></a><a name=""></a><h3>Adding Files to a Workspace</h3> <p xmlns:xi="http://www.w3.org/2001/XInclude">The UAC provides 4 ways of adding files to a workspace. The following defines and described each method.</p> <ol><a name=""></a><li style="margin-bottom:4px;"><b>Workspace Menu</b> - Go to <b>Workspace Menu &gt; Add Files...</b>, which will launch the <b>Open</b> dialog in which you can browse and select files to add to the workspace.</li><a name=""></a><li style="margin-bottom:4px;"><b>Drop Pad</b> - Go to <b>Workspace Menu &gt; Drop Pad</b> or use the <b>Ctrl+D</b> shortcut to toggle. The <b>Drop Pad</b> will be located at the bottom-right corner of the screen and always stay on top. You can drag-and-drop files to the <b>Drop Pad</b> to add to the current workspace.</li><a name=""></a><li style="margin-bottom:4px;"><b>Drag-and-Drop</b> - You may drag-and-drop files directly to the workspace window.</li><a name=""></a><li style="margin-bottom:4px;"><b>Copy-and-Paste</b> - You may copy-and-paste files to the workspace window. You may paste using <b>Ctrl+V</b> shortcut or paste via the <b>Workspace Menu</b> (<b>Workspace Menu &gt; Paste From Clipboard</b>).</li> </ol><new_page id="_id1099" xmlns:xi="http://www.w3.org/2001/XInclude"></new_page><a name="uac518"></a><a name=""></a><h3>Saving a Workspace</h3> <p xmlns:xi="http://www.w3.org/2001/XInclude">After you have created and/or modified a workspace, you will probably want to save the workspace for later use. When you save a workspace, the UAC saves the workspace as a *.uac file (as shown in Figure 26).</p> <p xmlns:xi="http://www.w3.org/2001/XInclude">To save a newly created or modified workspace, simply press <b>Ctrl+S</b> or choose <b>File &gt; Save Workspace</b> or <b>File &gt; Save Workspace As...</b> menu items.</p><a name="uac17"></a><div align="center"><br><img src="uacImgs/uac17.gif" border="0"><br><br><b>Figure 26 - Saving a Workspace</b><br><br></div><new_page id="_id1101" xmlns:xi="http://www.w3.org/2001/XInclude"></new_page><a name="uac519"></a><a name=""></a><h3>Opening a Workspace</h3> <p xmlns:xi="http://www.w3.org/2001/XInclude">To open a previously-created workspace, use the <b>File &gt; Open Workspace</b> menu item (see Figure 27), or <b>Ctrl+O</b> shortcut.</p><a name="uac16"></a><div align="center"><br><img src="uacImgs/uac16.gif" border="0"><br><br><b>Figure 27 - Accessing Replace Application Plug-in Help</b><br><br></div><new_page id="_id1103" xmlns:xi="http://www.w3.org/2001/XInclude"></new_page><a name="uac520"></a><a name=""></a><h3>Removing Files from a Workspace</h3><a name=""></a><br><br><center> <table width="475" border="0" cellspacing="2" cellpadding="3" bgcolor="#CCFFFF"> <tr> <td valign="top"><b>NOTE: </b></td> <td><div><p xmlns:xi="http://www.w3.org/2001/XInclude">It is not necessary to remove files from a workspace when a new application plug-in is loaded to a current workspace. The application plug-in will only affect files compatible with the currently-loaded plug-in. Non-compatible files will not be modified.</p> </div></td> </tr> </table> </center><br><br><p xmlns:xi="http://www.w3.org/2001/XInclude">To remove files from a workspace, highlight the file(s) you want to remove from the workspace, and press the <b>Remove Files</b> button (see <a class="link" href="#uac009">Figure 15</a>), or from the Menu Bar, go to <b>Workspace Menu &gt; Remove Files</b>. You may also press the <b>Del</b> key to remove selected files from Workspace.</p> <p xmlns:xi="http://www.w3.org/2001/XInclude">To remove ALL files from the workspace, go to <b>Workspace Menu &gt; Remove All Files</b>.</p><new_page id="_id1105" xmlns:xi="http://www.w3.org/2001/XInclude"></new_page><a name="uac520a"></a><a name=""></a><h3>Executing Workspaces From Context Menu</h3> <p xmlns:xi="http://www.w3.org/2001/XInclude">You may execute a saved workspace directly without opening the UAC by right-clicking on a workspace file (*.uac) and choosing "<b>Execute</b>" from the context menu (as shown in Figure 28). This will run the workspace in the background without opening the UAC interface. This is especially useful when you want to run specific workspaces from a scheduler, such as Microsoft's Scheduled Tasks.</p><a name="uac16a"></a><div align="center"><br><img src="uacImgs/uac16a.gif" border="0"><br><br><b>Figure 28 - Executing a Workspace From the Context Menu</b><br><br></div> <p xmlns:xi="http://www.w3.org/2001/XInclude">After a workspace has been executed, a log file will be created in the same directory in which the *.uac workspace file resides. You can view this log file to see the results of the executed workspace (see Figure 29).</p><a name="uac16b"></a><div align="center"><br><img src="uacImgs/uac16b.gif" border="0"><br><br><b>Figure 29 - Workspace Log Created After Execting a Workspace File</b><br><br></div><new_page id="_id1107" xmlns:xi="http://www.w3.org/2001/XInclude"></new_page><a name="uac521"></a><a name=""></a><h3>Using Command Line to Run UAC</h3> <p xmlns:xi="http://www.w3.org/2001/XInclude">The UAC provides a method of using command line parameters to run workspaces. This is especially helpful if you need to schedule the operation of workspaces for a particular time of the day or week using Scheduler.</p> <p xmlns:xi="http://www.w3.org/2001/XInclude">Use the following command line parameters to run the UAC via the <b>Run</b> command line:</p> <p xmlns:xi="http://www.w3.org/2001/XInclude"><b>UniversalConsole.exe [workspace_file] [options]</b></p> <table pwidth="300" width="350" align="center" border="1" id="uac522" xmlns:xi="http://www.w3.org/2001/XInclude"><tr><td align="center"><b>Parameter</b></td> <td align="center"><b>Description</b></td> </tr> <tr><td align="left"><b>-r</b></td> <td>Run application without UI</td> </tr> <tr><td align="left"><b>-l [log_file]</b></td> <td>Create log file</td> </tr> <tr><td align="left"><b>-p plug-in_id</b></td> <td>Select Plug-in</td> </tr> <tr><td align="left"><b>-a [file [filename ...]]</b></td> <td>Add files</td> </tr> </table><new_page id="_id1109" xmlns:xi="http://www.w3.org/2001/XInclude"></new_page><a name="_id1110"></a><a name="_id1112"></a><h3>Loading the W2XML Application Plug-in</h3><a name="_id1113"></a><br><br><center> <table width="475" border="0" cellspacing="2" cellpadding="3" bgcolor="#CCFFFF"> <tr> <td valign="top"><b>NOTE: </b></td> <td><div><p id="_id1116" xmlns:xi="http://www.w3.org/2001/XInclude">Operation of the Universal Application Console is covered under the UAC documentation. Please refer to the <a class="link" id="_id1117" href="http://www.docsoft.com/help/uacFset.htm" target="_top">UAC documentation</a> for UAC-specific help.</p> </div></td> </tr> </table> </center><br><br><p id="_id1118" xmlns:xi="http://www.w3.org/2001/XInclude">Loading the W2XML application plug-in is simple. Perform these three easy steps to properly load the application.</p> <ol><a name="_id1120"></a><li style="margin-bottom:4px;">Go to <b>Workspace &gt; Change Plug-in...</b> (Figure 30) to launch the <b>Select Plug-in</b> dialog (Figure 31).</li><a name="rep1"></a><div align="center"><br><img src="uacImgs/rep1.gif" border="0"><br><br><b>Figure 30 - Change Plug-in</b><br><br></div><a name="_id1126"></a><li style="margin-bottom:4px;">A list of all of your installed application plug-ins is shown. Highlight the <b>W2XML v2.5</b> application plug-in, then press <b>OK</b>.</li><a name="w2x1"></a><div align="center"><br><img src="uacImgs/w2x1.gif" border="0"><br><br><b>Figure 31 - Select Plug-in Dialog</b><br><br></div><a name="_id1130"></a><li style="margin-bottom:4px;">The <b>W2XML v2.5</b> application plug-in is now loaded. Notice there is now a <b>W2XML</b> menu on the UAC menu bar, and the name of the application plug-in is shown on the UAC title bar and the <b>Options Window</b> reflects current W2XML options configuration (Figure 32).</li><a name="w2x2"></a><div align="center"><br><img src="uacImgs/w2x2.gif" border="0"><br><br><b>Figure 32 - W2XML Application Plug-in Loaded</b><br><br></div> </ol><new_page id="_id1136" xmlns:xi="http://www.w3.org/2001/XInclude"></new_page><a name="_id1137"></a><a name="_id1138"></a><h3>How W2XML Works</h3> <p id="_id1139" xmlns:xi="http://www.w3.org/2001/XInclude">W2XML uses Microsoft's .NET® framework and <a class="link" id="_id1140" href="http://tidy.sourceforge.net/">Tidy</a> Open Source technology, along with some of DocSoft's own conversion technology to output pure, structured XML from MSWord®, RTF, ASP*, and JSP* files.</p> <p id="_id1141" xmlns:xi="http://www.w3.org/2001/XInclude">W2XML first opens each *.doc and *.rtf document in Word, saves as HTML, then uses Tidy technology to save as raw XHTML. Then the W2XML application applies special technology to clean up the raw exported data and apply custom configuration options and XSLTs to the XML to provide you with XML your organization can use to add life to your legacy information.</p> <p id="_id1142" xmlns:xi="http://www.w3.org/2001/XInclude">This version of W2XML also exports named styles from Word and uses them as attributes within the exported document's elements. Because of this technology, you can use MSWord to author all of your documentation, by applying custom, named styles from a custom template, then using a custom XSLT to transform the exported XML to a complete, custom XML document that conforms to any Schema or DTD you desire. See <a class="link" href="#w2xml011">Using Named Styles in Word for Custom XML Attributes</a> for complete details.</p><a name="_id1144"></a><br><br><center> <table width="475" border="0" cellspacing="2" cellpadding="3" bgcolor="#CCFFFF"> <tr> <td valign="top"><b>NOTE: </b></td> <td><div><p id="_id1147" xmlns:xi="http://www.w3.org/2001/XInclude">Customers who use W2XML to convert Word to XML must understand the relatively complex concepts behind conversion from an unstructured format to a structured format. For this reason, DocSoft recommends that customers who are new to structured content or do not have the expertise to develop sometimes complex XSLTs, contract with <a class="link" id="_id1148" href="http://www.docsoft.com/consulting.htm">DocSoft's consulting services</a> to develop XSLTs to convert the standard output to a Schema or tag set for their specific needs.</p> </div></td> </tr> </table> </center><br><br><a name="_id1149"></a><a name="_id1150"></a><h3>W2XML Options</h3> <p id="_id1151" xmlns:xi="http://www.w3.org/2001/XInclude">The W2XML Options Window contains four links that are used to modify the output configuration:</p> <ol><a name="_id1153"></a><li style="margin-bottom:4px;">Mode Link</li><a name="_id1154"></a><li style="margin-bottom:4px;">Output Folder Link</li><a name="_id1155"></a><li style="margin-bottom:4px;">Open Output Folder</li><a name="_id1156"></a><li style="margin-bottom:4px;">Options Link</li> </ol> <p id="_id1157" xmlns:xi="http://www.w3.org/2001/XInclude">Explanations for each of the links are included below:</p><a name="_id1158"></a><h5>Mode Link</h5> <p id="_id1159" xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Mode Link</b>, when clicked, opens a menu dialog allowing the user to choose from a list of preset output configurations or to choose a <b>Custom</b> mode (see Figure 33). The menu consists of four preset configurations and the custom option (which is default). When one of the four preset configurations is chosen, the link changes to reflect which configuration is current (see Figure 34).</p><a name="w2x3"></a><div align="center"><br><img src="uacImgs/w2x3.gif" border="0"><br><br><b>Figure 33 - Preset Configuration Menu from Options Window</b><br><br></div><a name="w2x4"></a><div align="center"><br><img src="uacImgs/w2x4.gif" border="0"><br><br><b>Figure 34 - Mode Link Shows Current Configuration Mode</b><br><br></div> <p id="_id1166" xmlns:xi="http://www.w3.org/2001/XInclude">When the <b>Custom</b> mode is chosen from the menu dialog (Figure 35), the <b>Options</b> dialog is launched. The <b>Options</b> dialog's interface provides a means to fully customize the configuration. (The <b>Options</b> dialog will be covered in depth in "<a class="link" href="#w2xml008">Configuring W2XML Options</a>.")</p><a name="w2x5"></a><div align="center"><br><img src="uacImgs/w2x5.gif" border="0"><br><br><b>Figure 35 - Choosing Custom Mode from Menu Dialog</b><br><br></div><a name="w2x6"></a><div align="center"><br><img src="uacImgs/w2x6.gif" border="0"><br><br><b>Figure 36 - Options Dialog</b><br><br></div> <p id="_id1175" xmlns:xi="http://www.w3.org/2001/XInclude">The preset configuration output options are defined in the following list. The fewer tags you select, the smaller the XML. In some instances you will choose to use many tags for maximum information; other times, you will require less information and, consequently, fewer tags. It is recommended to test the output to see what preset configuration is best for your needs or to create a custom configuration.</p> <ul><a name="_id1177"></a><li style="margin-bottom:4px;"><b>All Information</b> - Exports all data from the source document, including all the MS Office® tags, styles information, and other information that otherwise might not be useful for XML. </li><a name="_id1179"></a><li style="margin-bottom:4px;"><b>All Information Except Styles</b> - Exports all source information except styles data.</li><a name="_id1181"></a><li style="margin-bottom:4px;"><b>Minimum Tags with Document Properties</b> - Exports all source information (except styles data), with minimum MS Office® tags including the document properties Office tags (such as author, lastauthor, revision, company, etc.).</li><a name="_id1183"></a><li style="margin-bottom:4px;"><b>Minimum Tags</b> - Outputs only tags specifically used to markup textual information in the source document. Styles, MS Office® document property tags and other tags are eliminated.</li> </ul><a name="_id1185"></a><h5>Output Folder Link</h5> <p id="_id1186" xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Output Folder Link</b> launches the <b>Browse For Folder</b> dialog, which you can use to navigate to a folder or create a new folder for output. (See Figure 37).</p><a name="w2x7"></a><div align="center"><br><img src="uacImgs/w2x7.gif" border="0"><br><br><b>Figure 37 - Browse For Folder Dialog</b><br><br></div><a name="_id1191"></a><h5>Open Output Folder</h5> <p id="_id1192" xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Open Output Folder</b> link opens the folder you specified in the <b>Browse For Folder</b> dialog, which you can launch using the <b>Output Folder Link</b>. (See Figure 38).</p><a name="w2x7a"></a><div align="center"><br><img src="uacImgs/w2x7a.gif" border="0"><br><br><b>Figure 38 - Launching the W2XML Output folder</b><br><br></div><a name="_id1198"></a><h5>Options Link</h5> <p id="_id1199" xmlns:xi="http://www.w3.org/2001/XInclude">Pressing the <b>Options Link</b> will launch the <b>Options</b> dialog (see Figure 39). You can also access this dialog by choosing <b>W2XML &gt; Options...</b> from the menu bar (Figure 39).</p><a name="w2x8"></a><div align="center"><br><img src="uacImgs/w2x8.gif" border="0"><br><br><b>Figure 39 - Launching the W2XML Options Dialog from the Options Window Link</b><br><br></div><a name="w2x9"></a><div align="center"><br><img src="uacImgs/w2x9.gif" border="0"><br><br><b>Figure 40 - Launching the W2XML Options Dialog from the W2XML Menu</b><br><br></div><new_page id="_id1207" xmlns:xi="http://www.w3.org/2001/XInclude"></new_page><a name="_id1208"></a><a name="_id1209"></a><h3>Configuring W2XML Options</h3> <p id="_id1210" xmlns:xi="http://www.w3.org/2001/XInclude">The <b>W2XML Options Dialog</b> (see accompanying Figure 41) provides access to all of the options needed to perform XML conversion. It consists of three main areas used for configuring options:</p> <ol><a name="_id1214"></a><li style="margin-bottom:4px;">Output Folder</li><a name="_id1215"></a><li style="margin-bottom:4px;">Export Settings</li><a name="_id1216"></a><li style="margin-bottom:4px;">Apply Custom XSLT</li> </ol><a name="w2x10"></a><div align="center"><br><img src="uacImgs/w2x10.gif" border="0"><br><br><b>Figure 41 - W2XML Options Dialog</b><br><br></div> <p id="_id1218" xmlns:xi="http://www.w3.org/2001/XInclude">The following sections describe each of the above option items.</p><a name="_id1219"></a><h5>Output Folder</h5> <p id="_id1220" xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Output Folder</b> option can be used to choose a specific folder for output or to create a new folder for output. The <b>Output Folder</b> text field shows the currently-selected path in which the XML files will be exported. To change the path, click the <b>Browse...</b> button to launch the <b>Browse For Folder</b> dialog (as shown in <a class="link" href="#w2x7">Figure 37</a>).</p><a name="_id1227"></a><h5>Export Settings</h5> <p id="_id1228" xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Export Settings</b> option contains four preset configuration options and a custom option. The custom option can be saved for future use by saving the workspace with the custom settings selected. Choosing one of the preset configurations, selects predetermined settings in the configuration list. </p> <p id="_id1230" xmlns:xi="http://www.w3.org/2001/XInclude">Each configuration item checkbox is listed and exlained below:</p> <ul><a name="_id1232"></a><li style="margin-bottom:4px;"><b>Add possible list attributes</b> - Sometimes Word confuses actual lists with paragraphs and inherently uses a paragraph (<a name="_id1234"></a><font color="red" face="courier new" size="-1">&lt;p&gt;</font>) tag instead of a list item (<a name="_id1235"></a><font color="red" face="courier new" size="-1">&lt;li&gt;</font>) tag. Checking this option will add <b>w2x:list</b> attributes to the <a name="_id1237"></a><font color="red" face="courier new" size="-1">&lt;p&gt;</font> tag so that you can capture these as lists. The resultant output would look something like <a name="_id1238"></a><font color="red" face="courier new" size="-1">&lt;p w2x:list-item-class="1" w2x:list-item-level="1"&gt;</font>.<br id="_id1239" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1240" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1241"></a><li style="margin-bottom:4px;"><b>Clean HTML header</b> - Checking this option removes meta tags and other data from the <a name="_id1243"></a><font color="red" face="courier new" size="-1">&lt;head&gt;</font> tags. The information contained in the meta tags is data like <a name="_id1244"></a><font color="red" face="courier new" size="-1">&lt;meta name="ProgId" content="Word.Document" /&gt;</font><a name="_id1245"></a><font color="red" face="courier new" size="-1">&lt;meta name="Generator" content="Microsoft Word 10" &gt;</font> and <a name="_id1246"></a><font color="red" face="courier new" size="-1">&lt;meta name="Originator" content="Microsoft Word 10" /&gt;</font> and may or may not be useful to your specific project. You can always choose to export the data using a custom XSLT of your own (<b>Apply Custom XSLT</b>) to ignore or manipulate your data as needed.<br id="_id1248" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1249" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1250"></a><li style="margin-bottom:4px;"><b>Convert Equation objects to MathML</b> - Allows W2XML to process an embedded Equation object to the MathML equivalent, enabling you to post process the MathML as needed.<br id="_id1252" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1253" xmlns:xi="http://www.w3.org/2001/XInclude"><a name="_id2015"></a><br><br><center> <table width="475" border="0" cellspacing="2" cellpadding="3" bgcolor="#CCFFFF"> <tr> <td valign="top"><b>NOTE: </b></td> <td><div>Choosing the 'Remove XML data islands' or 'Remove IE hide/show tags' options may cause the 'Convert Equation objects to MathML' option to not function properly. Please ensure these options are not selected when using this option.</div></td> </tr> </table> </center><br><br></li><a name="_id1254"></a><li style="margin-bottom:4px;"><a class="link" name="Groupfieldcontent" id="Groupfieldcontent"></a><b>Group field content</b> - Allows grouping of Word's field content (index entry, reference, input form field) using specific XML tags. It uses w2x:field tag to border content: <a name="_id1256"></a><font color="red" face="courier new" size="-1">&lt;p class="msonormal"&gt;Sample of &lt;w2x:field code="FILENAME"&gt;Document5.doc&lt;/w2x:field&gt;&lt;/p&gt; (file name field)</font><br id="_id1257" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1258" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1259"></a><li style="margin-bottom:4px;"><b>Insert page markers</b> - Inserts anchor tags with prefix "_PgM" when a new page is encountered in the Word document.<br id="_id1261" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1262" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1263"></a><li style="margin-bottom:4px;"><b>Make CLASS attribute value in lower case</b> - Choose this option if you want to use named styles from Word that may contain capital letters and use as lower case XML elements (i.e. <a name="_id1265"></a><font color="red" face="courier new" size="-1">&lt;p class="Para"&gt; to &lt;p class="para"&gt;</font>).<br id="_id1266" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1267" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1268"></a><li style="margin-bottom:4px;"><a class="link" name="PlaceWordimagesintosinglesubfolder" id="PlaceWordimagesintosinglesubfolder"></a><b>Place Word images into single subfolder</b> - Checking this option will allow images from different documents to be placed into one folder. This folder will be named "images" and will be created as a subfolder of the output folder.<br id="_id1270" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1271" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1272"></a><li style="margin-bottom:4px;"><b>Post process of 'cdata' attributes</b> - Checking this option will allow W2XML to process elements that have the CDATA attribute in &lt;![CDATA[text here]]&gt; Tags. This would allow you to add preformatted code such as 'code' examples into your output XML without errors.<br id="_id1274" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1275" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1276"></a><li style="margin-bottom:4px;"><a class="link" name="PostPublishing" id="PostPublishing"></a><b>Post Publishing</b> - Checking this option will allow post publishing instructions to be specified in the resulting XML file. A custom XSLT can then be used to implement these post publishing instructions. Post publishing sample: <br id="_id1278" xmlns:xi="http://www.w3.org/2001/XInclude"><a name="_id1279"></a><font color="red" face="courier new" size="-1">&lt;?w2x-publish extension=".fo" xslt="genfo.xsl" output="C:\GeneratedFO\"?&gt;</font><br id="_id1280" xmlns:xi="http://www.w3.org/2001/XInclude"><a name="_id1281"></a><font color="red" face="courier new" size="-1">&lt;?w2x-publish extension=".htm" xslt="genhtm.xsl" output="C:\GeneratedHTML\"?&gt;</font><br id="_id1282" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1283" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1284"></a><li style="margin-bottom:4px;"><b>Remove Auto-Numeration</b> - Checking this option removes numbers added by Word used in various types of numeration, such as numbered lists and topics. It will replace items similar to <a name="_id1286"></a><font color="red" face="courier new" size="-1">&lt;span w2x:class="w2x_style_10012" w2x:list-number="yes"&gt;1. &lt;/span&gt;list item 1&lt;/p&gt;</font> with <a name="_id1287"></a><font color="red" face="courier new" size="-1">&lt;p w2x:list-item-class="2" w2x:list-item-level="1"&gt;list item 1&lt;/p&gt;</font><br id="_id1288" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1289" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1290"></a><li style="margin-bottom:4px;"><a class="link" name="Removeextraneousanchorbookmark" id="Removeextraneousanchorbookmark"></a><b>Remove extraneous anchor and bookmark tags</b> - Removes anchor tags and office SPAN bookmarks that are not referenced inside the document. This option removes only bookmarks with id's that start with "_Ref" or "_Toc".<br id="_id1292" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1293" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1294"></a><li style="margin-bottom:4px;"><b>Remove generated HTM file</b> - (<b>For *.doc and *.rtf files only</b>) - As part of the conversion process, W2XML transforms *.doc and *.rtf documents to HTML for easier manipulation. This intermediate HTML file can be saved as an additional output from W2XML.<br id="_id1297" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1298" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1299"></a><li style="margin-bottom:4px;"><b>Remove IE hide/show tags</b> - As part of the conversion process, some constructs are exported using standard syntax for Internet Explorer use, such as <a name="_id1301"></a><font color="red" face="courier new" size="-1">&lt;!--[if ...]&gt;...&lt;![endif]--&gt;</font> and <a name="_id1302"></a><font color="red" face="courier new" size="-1">&lt;![if ...]&gt; ... &lt;![endif]&gt;</font>. Unchecking this option will perform the following substitutions:<br id="_id1303" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1304" xmlns:xi="http://www.w3.org/2001/XInclude"><ul><a name="_id1306"></a><li>Construct "<a name="_id1307"></a><font color="red" face="courier new" size="-1">&lt;!--[if ...]&gt;...&lt;![endif]--&gt;</font>" will be substituted with "<a name="_id1308"></a><font color="red" face="courier new" size="-1">&lt;w2x:hide&gt; ... &lt;/w2x:hide&gt;</font>"</li><a name="_id1309"></a><li>Construct "<a name="_id1310"></a><font color="red" face="courier new" size="-1">&lt;![if ...]&gt; ... &lt;![endif]&gt;</font>" will be substituted with "<a name="_id1311"></a><font color="red" face="courier new" size="-1">&lt;w2x:show&gt; ... &lt;/w2x:show&gt;</font>"</li><a name="_id1312"></a><li>Construct "<a name="_id1313"></a><font color="red" face="courier new" size="-1">&lt;% ... %&gt;</font>" will be substituted with "<a name="_id1314"></a><font color="red" face="courier new" size="-1">&lt;w2x:script&gt; ... &lt;/w2x:script&gt;</font>"</li> </ul><br id="_id1315" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1316" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1317"></a><li style="margin-bottom:4px;"><b>Remove Office tags (o:*) except document properties</b> - Checking this option will remove MS Office-specific tags, such as <a name="_id1319"></a><font color="red" face="courier new" size="-1">&lt;o:smarttagtype&gt;</font> and <a name="_id1320"></a><font color="red" face="courier new" size="-1">&lt;o:p&gt;</font> tags.<br id="_id1321" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1322" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1323"></a><li style="margin-bottom:4px;"><a class="link" name="Removerevisioninformation" id="Removerevisioninformation"></a><b>Remove revision information</b> - Checking this option will disregard change information, when publishing to xml, and only place current text in output.<br id="_id1325" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1326" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1327"></a><li style="margin-bottom:4px;"><b>Remove script elements and attributes</b> - Removes script elements and attributes that otherwise are reserved for use in web browsers.<br id="_id1329" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1330" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1331"></a><li style="margin-bottom:4px;"><a class="link" name="RemoveSmartTags" id="RemoveSmartTags"></a><b>Remove SmartTags</b> - Checking this option will remove MS Office SmartTags while leaving the data intact, tags such as <a name="_id1333"></a><font color="red" face="courier new" size="-1">&lt;st2:personname&gt;</font> and <a name="_id1334"></a><font color="red" face="courier new" size="-1">&lt;st2:place&gt;</font> tags.<br id="_id1335" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1336" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1337"></a><li style="margin-bottom:4px;"><a class="link" name="Removespacebeforepunctuation" id="Removespacebeforepunctuation"></a><b>Remove space before punctuation</b> - Removes 'extra' spaces before punctuation sometimes left behind by TIDY after document processing.<br id="_id1339" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1340" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1341"></a><li style="margin-bottom:4px;"><b>Remove SPAN tags</b> - Removes sometimes un-needed SPAN tags often used with formatting. Since XML can separate content from formatting, using this option may be beneficial to your project.<br id="_id1343" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1344" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1345"></a><li style="margin-bottom:4px;"><b>Remove styles elements and attributes</b> - This option removes the inline styles information from the exported XML. Can be used in conjunction with the <b>Save CSS file</b> option to remove styles information from the exported XML into an external *.css file.<br id="_id1348" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1349" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1350"></a><li style="margin-bottom:4px;"><b>Remove VML tags (v:*)</b> - Removes extra Office-specific VML (Microsoft's Vector Markup Language) tags, such as <a name="_id1352"></a><font color="red" face="courier new" size="-1">&lt;v:shapes&gt;</font>.<br id="_id1353" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1354" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1355"></a><li style="margin-bottom:4px;"><b>Remove XML data islands</b> - Microsoft stores some information into what is termed "XML Data Islands". Choosing this option will remove these usually Word-specific items from the exported XML.<br id="_id1357" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1358" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1359"></a><li style="margin-bottom:4px;"><b>Replace NBSP to regular space</b> - There may be some instances in which non-breaking spaces (<a name="_id1361"></a><font color="red" face="courier new" size="-1">&amp;nbsp;</font>) are used and you may want to be remove since non-breaking spaces are usually associated with format and not content. If you intend to keep your XML clean of formatting, use this option to replace the <a name="_id1362"></a><font color="red" face="courier new" size="-1">&amp;nbsp;</font> character entity with a regular space.<br id="_id1363" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1364" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1365"></a><li style="margin-bottom:4px;"><b>Save CSS file</b> - Exports any styles information into an external *.css file. The exported *.css file will have the same name as the exported *.xml file.<br id="_id1367" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1368" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1369"></a><li style="margin-bottom:4px;"><b>Save raw XML file</b> - Exports a separate, "raw" XML file that contains all of the original exported data before applying any of the configuration options. The exported raw *.xml file will have the same name as the regular exported *.xml file, but has an extension of "*.raw.xml".<br id="_id1371" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1372" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1373"></a><li style="margin-bottom:4px;"><b>Separate header tags and content by DIV</b> - Choosing this option adds DIV tags that separate out headers within the original Word document. This adds more structure to the exported XML file.<br id="_id1375" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1376" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1377"></a><li style="margin-bottom:4px;"><b>Use <a class="link" id="_id1379" href="http://www.exslt.org/">EXSLT</a> library for transformation</b> - Choosing this option adds <a class="link" id="_id1380" href="http://www.exslt.org/">EXSLT</a> functionality to your applied Custom XSLT.<br id="_id1381" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1382" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1383"></a><li style="margin-bottom:4px;"><b>Use multiple output transformation</b> - Used in conjunction with the <a class="link" id="_id1385" href="http://www.exslt.org/">EXSLT</a> library option to output multiple files from one custom XSLT; Uses <a class="link" id="_id1386" href="http://www.exslt.org/exsl/elements/document/index.html">EXSLT:DOCUMENT</a> function: see the <a class="link" id="_id1387" href="http://msdn.microsoft.com/library/en-us/dnexxml/html/xml06162003.asp">"Producing Multiple Outputs from an XSL Transformation"</a> article at MSDN for more details. <br id="_id1388" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1389" xmlns:xi="http://www.w3.org/2001/XInclude"></li> </ul><a name="hopts"></a><h5>Hidden Options</h5> <ul><a name="_id1392"></a><li style="margin-bottom:4px;"><b>User Mode</b> - You may enable this option by editing a workspace file with your text editor. Setting the "usermode" tag to "true" (<usermode id="_id1394" xmlns:xi="http://www.w3.org/2001/XInclude">true</usermode>) will disable the Options Dialog link and disallow potential end-users from modifying the options Settings. This capability is provided so that W2XML can be distributed throughout an organization without the hassles of settings options or inadvertent mistakes by accidental modification of the Workspace Options.<br id="_id1395" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1396" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1397"></a><li style="margin-bottom:4px;"><b>OutputExtension</b> - Set this option to set the output extension to a value other than the default ".xml"<br id="_id1399" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1400" xmlns:xi="http://www.w3.org/2001/XInclude"></li><a name="_id1401"></a><li style="margin-bottom:4px;"><b><i id="_id1403" xmlns:xi="http://www.w3.org/2001/XInclude">CustomOptions</i></b> - Introduced in v.2.3 of W2XML, the ability to set custom options in your XSLT and read them using w2x:GetOptionValue.<br id="_id1404" xmlns:xi="http://www.w3.org/2001/XInclude"> GetOptionValue parameter sample:<br id="_id1405" xmlns:xi="http://www.w3.org/2001/XInclude"><a name="_id1406"></a><font color="red" face="courier new" size="-1">&lt;xsl:value-of select="w2x:GetOptionValue('CustomOptions')"/&gt;</font><br id="_id1407" xmlns:xi="http://www.w3.org/2001/XInclude"><br id="_id1408" xmlns:xi="http://www.w3.org/2001/XInclude"></li> </ul><a name="_id1409"></a><h5>Apply Custom XSLT</h5><a name="_id1410"></a><br><br><center> <table width="475" border="0" cellspacing="2" cellpadding="3" bgcolor="#CCFFFF"> <tr> <td valign="top"><b>NOTE: </b></td> <td><div><p id="_id1413" xmlns:xi="http://www.w3.org/2001/XInclude">The Docbook XSLT that is provided with the installation program gives the end-user a starting point in exporting Docbook-compliant XML. Since there is no way to determine the exact layout of everyone's Word documents, you may need to tweak this XSLT to meet your specific Docbook requirements.</p> </div></td> </tr> </table> </center><br><br><a name="_id1414"></a><br><br><center> <table width="475" border="0" cellspacing="2" cellpadding="3" bgcolor="#CCFFFF"> <tr> <td valign="top"><b>NOTE: </b></td> <td><div><p id="_id1417" xmlns:xi="http://www.w3.org/2001/XInclude">Customers who use W2XML to convert Word to XML must understand the relatively complex concepts behind conversion from an unstructured format to a structured format. For this reason, DocSoft recommends that customers who are new to structured content or do not have the expertise to develop sometimes complex XSLTs, contract with <a class="link" id="_id1418" href="http://www.docsoft.com/consulting.htm">DocSoft's consulting services</a> to develop XSLTs to convert the standard output to a Schema or tag set for their specific needs.</p> </div></td> </tr> </table> </center><br><br><p id="_id1419" xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Apply Custom XSLT</b> checkbox, when checked, provides the ability to create and use custom XSLTs to further customize the exported output. You may press the <b>Browse...</b> button to choose a custom XSLT that you have created, or press the <b>Set Docbook XSLT</b> button to auto-select an XSLT that will transform the standard XHTML output to <a class="link" id="_id1423" href="http://www.docbook.org/">Docbook</a>-compliant XML (which is included as part of the installation package).</p> <p id="_id1424" xmlns:xi="http://www.w3.org/2001/XInclude">The <b>Check XSLT</b> will check the selected XSLT to ensure it is a valid XSLT in terms of structure and error.</p> <p id="_id1426" xmlns:xi="http://www.w3.org/2001/XInclude">Remember, since W2XML exports named styles from Word as attributes, you can use them to fully customize the exported XML. For more information on using named styles as attributes, see <a class="link" href="#w2xml011">Using Named Styles in Word for Custom XML</a>.</p><a name="_id1428"></a><a name="_id1429"></a><h3>Creating XSLTs for Custom XML Output</h3><a name="_id1430"></a><br><br><center> <table width="475" border="0" cellspacing="2" cellpadding="3" bgcolor="#CCFFFF"> <tr> <td valign="top"><b>NOTE: </b></td> <td><div><p id="_id1433" xmlns:xi="http://www.w3.org/2001/XInclude">Customers who use W2XML to convert Word to XML must understand the relatively complex concepts behind conversion from an unstructured format to a structured format. For this reason, DocSoft recommends that customers who are new to structured content, or do not have the expertise to develop sometimes complex XSLTs, contract with <a class="link" id="_id1434" href="http://www.docsoft.com/consulting.htm">DocSoft's consulting services</a> to develop XSLTs to convert the standard output to a Schema or tag set for your specific needs.</p> </div></td> </tr> </table> </center><br><br><p id="_id1435" xmlns:xi="http://www.w3.org/2001/XInclude">To fully take advantage of W2XML's capabilities, one of the prerequisites is a good understanding of XML and XSL. If you don't have a good understanding, or do not have access to someone within your organization who does, then you may want to inquire with DocSoft or some other consulting agency that can build the XSLT you need to take advantage of the rich capabilities W2XML offers. The following information is provided to give a high-level understanding of the standard output so that one can build a custom XSLT to create a completely custom output.</p> <p id="_id1436" xmlns:xi="http://www.w3.org/2001/XInclude">W2XML's standard output is XHTML (which is well-formed XML using HTML tags). If you retain the raw xml file (an option in the options list), you will see that there is a lot of information that is exported from the Word document. So much so, that you could write an XSLT to convert it back to a properly formatted Word document. The first thing to do when starting the development of an XSLT is to determine which options to select to give you the output that you want to start with. Familiarizing yourself with the standard output and options is one of the most important things to do.</p> <p id="_id1437" xmlns:xi="http://www.w3.org/2001/XInclude">W2XML also wraps div tags around each section (such as <a name="_id1438"></a><font color="red" face="courier new" size="-1">&lt;div class="section1"&gt;</font>) that will enable you to identify sections throughout your XML document for proper nesting and hierarchy.</p> <p id=