Relax NG and XInclude?

[Su-Laine Yeo]

Good news: XInclude is supported in XMetaL 6.0. The Help menu has a couple of DocBook samples that include XIncludes. If you want to add XInclude-related menu items to your own XMetaL customization, you can poke around the XMetaL Author folder in Program Files to see how the menu items are hooked up for the DocBook customization.

Reply

[dcramer]

Good news indeed. I'll give it a spin.

Thanks for the update!

David

Reply

[rekk1986]

Hi,

Can anyone tell me if XMetaL plans to incorporate Relax NG and XInclude standards in future releases?

http://en.wikipedia.org/wiki/XInclude

http://en.wikipedia.org/wiki/RELAX_NG

If XMetaL included these standards we could start using it again. As it stands today, we are forced to use another authoring tool.

Thanks,

Dave

I don't know when but if that happen , we will have many choice to add code into this

Reply

[dcramer]

I've finally had a chance to check out the xinclude examples. They look nice. One question: is it possible to have the xincluded content appear in the structure view as well (with the structure view css applied)?

Thanks,
David

Reply

[Derek Read]

For the DocBook sample you should just need to modify the CSS files being used for structure view to display all elements. We shipped a version of the CSS that hides pretty much everything. The file being used is this one:

AuthorRulesDocBook5.0xidocbookxi_structure.css

The simplest way to demo what you want is to modify the following to remove the display:none setting, or change it to display:block.

* {
  white-space: nowrap;
  text-align: left;
  margin-left: 20px;
  margin-top: 14px;
  display: none;
}

The APIs for showing and hiding XIncluded content in TagsOn and Normal view directly (and always) affect Structure view as well. Perhaps that is what you are asking about?

Reply

[dcramer]

Ok, got it to work. I had replaced the default structure css with my css that shows the document structure, but hadn't added a rule to handle the xi:include element, which apparently XMetaL considers to be a parent node to the xincluded content:

xi|include{
display: inline;
}

I think the DocBook samples would be more impressive with a good structure view css. Here's what I use, in case you want to use it:

@sq-plus-minus;

@sq-structure-view-icons;

$COMMENT {
display: none;
}

* {
white-space: nowrap;
text-align: left;
font-family: "Arial";
font-size: 10pt;
font-style: normal;
font-weight: bold;
color: black;
margin-left: 20px;
display: none;
}

/* top-level elements */
$DOCUMENT > * {
margin-left: 0px;
}

xi|include{
display: inline;
}

title, title *, glossterm, glossterm *, question * {
display: inline;
}

book, part, chapter, article, section, simplesect, glossary, preface, reference, appendix, procedure, glossentry, glossdiv, glossentry, qandaset, qandaentry, question {
display: block;
}

procedure>title, procedure>title *{
  color: green;
}

chapter>title, part>title, appendix>title
{
color:#00589E;
}

chapter>title *, part>title *, appendix>title *
{
color:#00589E;
display: inline;

}

simplesect>title *, section>title * {
display: inline;
}

Interesting, I just noticed that the comment rule isn't working in structure view:

$COMMENT {
  display: none;
}

David

Reply

[Author]

Posts