Lisa, I am just wondering: what are the exact circumstances why you could not use conversion tables?
I have just finished a huge conversion project where manual work (except for the manual correction of details in the structured outcome) was simply NOT an option due to the sheer volume of the documentation. So I had to solve ALL problems that got in the way of automatic conversion. I wonder which problems might still exist that I did not encounter. I am preparing a series of blogs on this topic plus a presentation at tcworld in Wiesbaden this fall, so I have a keen interest in anything that seems impossible to automate in this domain. Cheers Jang JANG Communication Coaching - Copywriting - Consulting Amsterdam - Netherlands Tel. +31 20 755 8466 Cell +31 6 5478 1632 http://www.jang.nl > From: framers-bounces at lists.frameusers.com [mailto:framers-bounces at > lists.frameusers.com] On Behalf Of Lisa Freeman > Sent: Monday, July 02, 2012 1:24 PM > To: framers at lists.frameusers.com > Subject: Unstructured to Structured: Question about retaining paragraph > formats > > Hello All, > > FM10 - We are converting an unstructured Frame file to Structured. Due to > unfortunate circumstances, we are not able to use a conversion table (sigh). > > The issue is that during the hand tagging of this file, we have to wrap the > text in the element tags in para tags to match the schema. When we wrap the > text, we lose the paragraph's formatting properties. Everything turns to > "body" and we have to reapply the format. > > We are able to manipulate the EDD somewhat but can't stray from the > structure. We've looked at Read\Write rules but they don't appear to help in > this case. We've also looked at using the "TextFormatRules, > ElementPgfFormatTag" options but we have more than one paragraph style that > goes to an individual element. > > Does anyone have any other ideas? > > BTW, everything works great when a new document is created using the > template, EDD, etc. > > Thank you in advance! > > Sincerely, > Lisa Freeman > Publication Support Analyst > > E-mail: lfreeman at oneil.com<mailto:lfreeman at oneil.com>
