I am trying to catch up with all the suggestions and comments that have been passing through the list. I took little snippets from several different emails and added my comments and what I did to the DTD to try to conform. I also attached the template. This is a very rough draft and needs more refinement. For now this validates and can be used as a template with the new dtd attached.
~~Or <note type="warning">? Either way is fine with me. You may ~~want to check the Docbook DTD to see how they do it. One that might be ~~particularly useful in apache is <securitywarning> or something like that. I added <securitywarning> you can place any text or formating in it. Do we need any attributes for this? ~~The thing I like the most is that I added some basic support for ~~internationalization. One can switch language by adding <language> ~~to <directivesynopsis>. It defaults to English, but I've also added "sv" ~~so that the template be generated in Swedish. I added <language>. I don't really have any rules for language. And I am not really following how you are switching languages here. Are you pulling information from another file if the stylesheet sees the <language> tag it will find whatever xml file for that language you specify with an attribute and include that? I guess I really don't understand how the language conversion works. Can someone give me a list of attributes for this if that is how it is done? I also need to know where the language attribute will be used if anywhere other than <directivesynopsis>. ~~<section id="hereiam"><title>lala</title>... ~~should create the appropriate <a href="#hereiam">reference</a>. ~~ ~~Yes, sections can be nested. Main sections get <h2> and nested ones get ~~<h3> at the moment. Do I need to specify an "id" attribute? I never was too clear on id's, some dtd's I have seen it looks like they just assume id and others specify them. Lastly, do we want to stick with a DTD or should we be using a schema? I don't really have an opinion on this because I know dtd's better but schemas are more rubust. Converting to a schema at this point wouldn't take much effort. Thanks, Brad Miller [EMAIL PROTECTED] www.beldamar.com
httpd-doc-all.dtd
Description: Binary data
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="../style/manual.xsl"?>
<!--<modulesynopsis> is the root tag and must surround all other tags. Each tag listed below displays
either "required #" or some other description of it's rules. All required tags have a number which indicates there
sequence. The sequence is important and must be followed in order for the document to validate. Optional tags
that are placed between required tags can only be placed in that spot unless otherwise noted.-->
<modulesynopsis>
<name>required 1.</name>
<status>required 2.</status>
<identifier>optional</identifier>
<sourcefile>optional</sourcefile>
<compatibility>Optional</compatibility>
<description>required 3.</description>
<summary>
<p>Summary is optioanl, "p" is required and repeatable within summary.</p>
<example>
<title>titles can be placed in examples but are not required.</title>
example is optional and can include the <br/> tag.
</example>
</summary>
<seealso><a href="somefile.xml">seealso is optional and must contain an "a" tag. the "a" tag can have the
attribute "href"</a>
<directive>This tag is optional and must come after the "a" tag.</directive>
</seealso>
<!--<directivesynopsis> is required and can be repeated if necessary.-->
<directivesynopsis>
<name>required 1. can only include text</name>
<description>required 2. can only include text</description>
<syntax>required 3. can include as many <em>tags</em> as necessary.</syntax>
<default><i>default tag is optional and must have an italic or empasis tag but cannot have both</i></default>
<contextlist><context>required 4. contextlist can only have context tags included and can have as many
as needed</context>
<context>context tags can only have text in them</context></contextlist>
<override>required 5. can only include text</override>
<compatibility>optional and can only include text.</compatibility>
<usage>
<!-- <usage> is required and must contain at least one <p>. The tags <ol>, <ul>, <example>, <securitywarning>,
and <note> are allowed only after <p>. If any of the listed tags are placed before <p> the file will not
validate. The listed tags are only allowed in that order but are all optional. That means that you cannot
place a <note> before an <ol> unless <p> is placed before <note>-->
<p>usage is required 6. must contain at least one paragraph. Any tags are allowed within a paragraph.</p>
<!-- the <ol> and <ul> tags can be used here. These tags are optional and repeatable. -->
<ol>
<li>the "ol" tag is optional and must have at least one "li" tag.</li>
<li>"li" tags can include multiple <code>"code" can include "em" tags</code> see next "li" for example</li>
<li><code><em>varname</em>=<em>value</em></code></li>
</ol>
<p>paragraphs can be placed in "usage" wherever and as many times as needed.</p>
<example>
<title>titles can be placed in examples but are not required.</title>
example is optional and can include the <br/> tag.
</example>
<note>
<!-- <note> can contain <a>, <em>, <i>, <br>, <p>, <strong>, <title> and text. -->
</note>
<p><example>
<title>titles can be placed in examples but are not required.</title>
example is optional and can include the <br/> tag.
</example></p>
<securitywarning><!--Optional and can contain <a>, <em>, <i>, <br>, <p>, <strong>, <title> and text.--></securitywarning>
</usage>
</directivesynopsis>
</modulesynopsis>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
