🚀 go-pugleaf

Molly,

Look in the structure view to see where the error is (the red lines). My guess is your table has one or more Cell elements without a Para element inside it. Note that I am using generic element names; yours could be different.

The point is that in structured tables it is easy to delete cell-enclosed elements and have the table displayed as a table on screen. This can also happen when you straddle cells then unstraddle them later; the "new" cells are created without the inside content elements.

Van

Thank you. That tipped me off:

I'm inserting a Table element after the final Para element. The problem: I can't get in before the closing Section and Chapter tags. So: The doc "ends" before the Table element. ...

Any ideas on how to get the Table in between Para/Para and /Section /Chapter?

Molly,

Are you using the Structure View to position the insertion point? That's your best bet to get an element in the correct structural position.

Russ

Molly,

In addition to Russ's suggestion, I often select View > Element Boundaries or View > Element Boundaries (as Tags). These features are also helpful in placing the insertion point correctly, especially when working with an EDD of which one is unfamiliar.

Van

Thanks for the great help. Anyone else with ideas?

I work in the modes you both advise: with all of the tags, the elements, and the Structure in open view. - And by the way, the rest of the doc is valid.

I will post if I find the problem with the TableTitle. So frustrating!

Molly,

My previous attempt to respond seems to have been lost somewhere, so I will try again.

I am not familiar with the Scriptorium tutorial, but the error message indicates that the problem is within the TableTitle and not in the position of the table itself. I often require table titles to end with an element that inserts the table continuation variable. The element does not affect the appearance of one-page tables and requiring it means that the writer won't forget to include if a table happens to break over a page boundary. The template you are using may follow a similar convention.

This thread has mentioned the Structure View and Element Boundaries. Don't forget the Element Catalog. Validating a document helps you locate structure errors. By showing you the elements that are available at the current location, the Element Catalog suggests how they can be fixed. The Element Catalog will also let you know when a table is permitted at your current context.

--Lynne

Lynn was right!

Insert the TableContinuation element after the TableTitle element text. (Never mind that this is a single-page table.)

The document is now valid.

The company I work for sent 4 of us for training to convert our documents from unstructure to structure documents then xml. Unfortunately the training we received was very basic. IT DIDN'T HELP ANY OF US! Now I have been tasked to try to convert some documents to xml.

I have read everything I can on-line and have been successful in creating my own readwrite rules, edd and dtd. I was able to convert a document to structure. But I have some problems

My first problem is with the Table Continuation variable. My element structure is as follows

Element
  Tag ------- caption_tbl
  Container
    General Rule ----- ( | Cross-Ref)*
    Attribute List
      Attribute
        Name ----- Id
        UniqueID
        Optional
  TextFormatRules
      ElementPgFormatTag ---- caption_tbl

Element (System Variable): Table Continuation
  System variable format rule
    1. In all contexts.
          Use system variable: Table Continuation

When I validate the elements the -Continued is moving to the next line and applying Table format (Table 1-1) and caption_tbl element. I thought I read somewhere that drop was used, but I can find it again.

Do I need to add something in the readwrite rules?
Do I need to add something in the dtd?

Thanks in advance for all your help.