Note that there are some explanatory texts on larger screens.

plurals
  1. USalx9r
    primarykey
    data
    text
    plurals
    1. COQuestion #1 is answered. I think question #2 should probably be separated out as I think question #1 is obfuscating the heart of the matter of question #2. I'll have to spend some time in meta to figure out how to properly do that. Regardless, I appreciate your help.
      singulars
    2. COI added a picture of what I want the published output of 'test2.xml' to look like -- hopefully that makes my goal a bit more clear. Could you elaborate on "You can do that." The `ReusedTable` entity in 'test2.xml' is not part of the DocBook schema so produces validation errors. I assume that the schema could be extended to include this new entity (there are examples for how to do this), but how do I tell my tools to translate `ReusedTable` into the table I want when they encounter `ReusedTable`. I've searched unsuccessfully for an example of an xsl template that handles a schema extension.
      singulars
    3. CO@DevNull I tried your suggestion of putting the ReusedTable directly into the entity declaration and eventually got it to work. For some reason I was operating under the assumption that multiline entity declarations are not supported. Oxygen XML seems to support them just fine. So, putting the ReusedTable directly in the entity declaration seems to be the answer to my question #1.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload