[EMAIL PROTECTED] wrote: > Here is another alternative. If it seems reasonable I can add it to > bugzilla. > > How about inserting some special inset (or comment) in those paragraphs > that don't have an equivalent in the new class? (The inset/comment would > not produce any output). > > That comment/inset would then server as a reminder/warning that the > paragraph layout wasn't properly converted.
And what should I do with it as a user? Am I required to delete 100 such insets after I changed documentclass if I am OK with the change? > As an extension, there could be a method that when converting to a new > document class looks in default paragraphs for such an inset. If the inset > exists, the paragraph is converted to the original layout. That would be a bad hack and lead to ugly code and almost certainly to bugs. I like Jean-Marc's solution much better. What also might be doable is the "inverse" of obsoletedby: If I have a special document class with special layouts (e.g. for problem sheets), I could declare that layout "subtask" of this class should be mapped to "enumerate" if I convert to a standard class. The advantage of that would be that the standard classes do not need to know all my special layouts. Georg
