We are currently using conditional text settings in our in structured FrameMaker 6.0 documents.
Unfortunately, we have to migrate our documents to an XML environment and therefore, we have to convert our conditional text to filter attributes.
This means, we have to remove the conditional text from each individual text piece and wrap an element around it, which has the desired filter attribute.
I do not guarantee that this will work, because I have never done it.
I do not know about Frame 6, but in more recent versions conditions are replaced with processing instructions when structured files are saved in XML. Frame's structured applications, which you can use to save as XML, allow you to specify an XSL file to post-process the XML before Frame writes the file. You might be able to write an XSL transform that replaces the processing instructions with elements containing attributes.
All the previous suggestions are valid but I would contend that unless you have an enormous amount of conversion to do and you are confident that your conditional text is applied accurately, you might be better off just doing it manually. Native conditional text is antiquated and error-prone, such that a movement towards a much more precise method of conditionalization is normally bound to uncover errors, if studied manually. Or in other words, it is a great opportunity for some serious cleanup that you might otherwise miss during an automated process.
The following is just a guess, I've never done this myself:
If you are using FM conversion tables for the migration to XML, you could
1) Apply a specific paragraph or character format to the conditional text in the unstructured source document (Edit > Copy special to capture the format once, then Find & Change by pasting format to apply it).
2) Add a rule for these formats to the conversion table so that they are automatically wrapped into structure elements.
8
Replies
AdChoices