Re: Defining root element in conversion table
Andy Lewis wrote: As you may remember, my problem is that when manually adding RE:RootElement to the first column of my conversion table and Parent to the second, the result is a NoName root element instead of the expected Parent element. Andy, Thank you for sending the simplified test files. I think I solved the mystery. There are two steps to creating a usable structured document from an unstructured one: 1. Applying a conversion table 2. Importing the desired element definitions In production, users typically perform these two steps in the listed order, using the Structure Current Document (or Structure Documents) command first, and then importing element definitions into the resulting new document (or documents). However, the steps can be performed in reverse. You can import element definitions into the unstructured document and then apply the conversion table. Doing so is convenient when testing a conversion table, because you can inspect the results, change the conversion table, and reapply it without needed to import element definitions each time you apply the conversion table. At least, it would be convenient, if it didn't affect the results. It seems that the RE: rule is only applied when the unstructured document has no element definitions. I stumbled on this fact by doing a Select All in your document, then copying and pasting the content into a new portrait document. When I structured the original document, the RE: rule was ignored. When I structured the new one, the RE: rule was applied. I then imported element definitions from the original file into the new one and structured that version. Sure enough, the RE: rule was ignored. Next, I created a new unstructured document of my own and a new conversion table. I confirmed that with this application also, the RE rule was only used when the unstructured document had no element definitions. --Lynne Lynne A. Price Text Structure Consulting, Inc. Specializing in structured FrameMaker consulting, application development, and training [EMAIL PROTECTED] http://www.txstruct.com voice/fax: (510) 583-1505 cell phone: (510) 421-2284 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Defining root element in conversion table
Andy Lewis wrote: >As you may remember, my problem is that when manually adding >RE:RootElement to the first column of my conversion table and Parent to >the second, the result is a NoName root element instead of the expected >Parent element. Andy, Thank you for sending the simplified test files. I think I solved the mystery. There are two steps to creating a usable structured document from an unstructured one: 1. Applying a conversion table 2. Importing the desired element definitions In production, users typically perform these two steps in the listed order, using the Structure Current Document (or Structure Documents) command first, and then importing element definitions into the resulting new document (or documents). However, the steps can be performed in reverse. You can import element definitions into the unstructured document and then apply the conversion table. Doing so is convenient when testing a conversion table, because you can inspect the results, change the conversion table, and reapply it without needed to import element definitions each time you apply the conversion table. At least, it would be convenient, if it didn't affect the results. It seems that the RE: rule is only applied when the unstructured document has no element definitions. I stumbled on this fact by doing a Select All in your document, then copying and pasting the content into a new portrait document. When I structured the original document, the RE: rule was ignored. When I structured the new one, the RE: rule was applied. I then imported element definitions from the original file into the new one and structured that version. Sure enough, the RE: rule was ignored. Next, I created a new unstructured document of my own and a new conversion table. I confirmed that with this application also, the RE rule was only used when the unstructured document had no element definitions. --Lynne Lynne A. Price Text Structure Consulting, Inc. Specializing in structured FrameMaker consulting, application development, and training lprice at txstruct.com http://www.txstruct.com voice/fax: (510) 583-1505 cell phone: (510) 421-2284
Defining root element in conversion table
At 07:26 AM 11/14/2006, Andy Lewis wrote: >I've tried manually adding RE: RootElement to the first column of my >table and Parent in the second, but no luck. Andy, What result are you getting? The row you describe works fine in my testing. --Lynne Lynne A. Price Text Structure Consulting, Inc. Specializing in structured FrameMaker consulting, application development, and training lprice at txstruct.comhttp://www.txstruct.com voice/fax: (510) 583-1505 cell phone: (510) 421-2284
Defining root element in conversion table
Hi All, Working in FM 7.2, I'm building a conversion table for adding structure to a document. I'm trying to specify the root element (Parent) in the table. I've tried manually adding RE: RootElement to the first column of my table and Parent in the second, but no luck. What am I missing? Many thanks, Andy Andy Lewis Senior Technical Writer Networking Business Unit RADVISION Tel: 972 (3) 767-9320 mailto:andy at radvision.com
