🚀 go-pugleaf

OK, yes you are right. Thanx. I do not need those in the read/write rules, just in the EDD and the Conversion Table. Still, it would be very convinient if there was a rule that I could write similar to this:

element "para"
{
  is fm element "Para";
  attribute "pgfformat"
  {
     is fm property paragraph format; <---

}
}

The reason is so I do not have to add new paragrph formats to the EDD and I dont need coversion table rules such as:
P:GB2_Title para[pgfformat=&#8221;GB2_Title&#8221;]

I seems like extra work and extra maintenance when I could just have one rule that reads and writes the paragraph and character formats so the EDD and coversion table can be used for all documents no matter what the paragraph formats are. For instance, using the example of the "tgroupstyle" attribute again, I can add or remove table formats freely without needed to make any changes to the EDD or write extra rules in the conversion table, as long as the correct template is applied.
In other words, it just doesnt scale well, especially when you are applying roundtrip Frame -> XML -> Frame for houndreds of documents from several different companies all using different paragraph and character formats.

-Scott