X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;ds=sidebyside;f=man%2Fmdoc.5;h=440fc15a39793c8747007e4fb31ec825cfcd5c0a;hb=455905c41b6f3ad0a9b88c31ec06c9ea8a4d6a75;hp=bcf1268212e5031e32ac8a34326a70436c1b9171;hpb=b87c7e29df7d04e3199e224c8b8e9a41292cec1b;p=mono.git diff --git a/man/mdoc.5 b/man/mdoc.5 index bcf1268212e..440fc15a397 100644 --- a/man/mdoc.5 +++ b/man/mdoc.5 @@ -328,13 +328,26 @@ The \fIc\fR element can contain the following elements: \fIsee\fR, and \fItypeparamref\fR. .TP -.I TEXT +.I TEXT Display multiple lines of text in a code-like font (similar to the HTML
 element).
+.Sp
 .I LANGUAGE
 is the language this code block is for.  For example, if \fILANGUAGE\fR is
 \fBC#\fR, then \fITEXT\fR will get syntax highlighting for the C# language 
 within the Mono Documentation Browser.
+.Sp
+.I SOURCE
+is only interpreted by \fBmdoc-update\fR(1).  If the \fIsrc\fR attribute is
+present when \fBmdoc-update\fR(1) is run, then \fISOURCE\fR is a file 
+(relative to \fBmdoc-update\fR(1)'s \fB--out\fR directory) that
+should be inserted as the value for \fITEXT\fR.
+The contents of \fITEXT\fR will be ignored by \fBmdoc-update\fR(1)
+and replaced on every invocation.  \fISOURCE\fR can also contain an "anchor",
+e.g. \fIsrc="path/to/file.cs#RegionMarker"\fR.  If an anchor is present,
+\fIand\fR \fILANGUAGE\fR is \fIC#\fR, then \fI#region RegionMarker\fR will be
+searched for, and the contents between the \fI#region\fR and the following
+\fI#endregion\fR will be inserted as the value for \fITEXT\fR element.
 .TP
 .I XML_TEXT
 Indicates an example that should be displayed specially.  For example:
@@ -388,6 +401,31 @@ The \fIexception\fR element can contain the following elements:
 \fIsee\fR, and
 \fItypeparamref\fR.
 .TP
+.I XML_TEXT
+The \fI\fR element is an "escape hatch," for including (possibly XML)
+content that is not valid \fBmdoc\fR(5) content.  It's the moral equivalent of
+\fBperlpod\fR(1) \fI=begin format\fR blocks.
+
+\fITYPE\fR is the mime type of \fIXML_TEXT\fR.  \fBmdoc\fR(5) processors may
+skip \fIformat/>\fR blocks of they use a type that isn't supported.
+
+For example:
+
+.nf
+    
+      
+        
+      
Hello, world!
+
+.fi + +would cause the embedded HTML \fI\fR element to be inserted inline +into the resulting HTML document when \fBmdoc-export-html\fR(1) processes the +file. (Likewise, it may be skipped if processed by another program.) + +\fIformat/>\fR is intended to simplify importing documentation from existing +documentation sources. It should not be relied upon, if at all possible. +.TP .I XML Create a list or table of items. .I @@ -565,6 +603,8 @@ Describes the return value of a method: .fi The \fIreturns\fR element can contain the following elements: +\fIc\fR, +\fIformat\fR, \fIlist\fR, \fIpara\fR, \fIparamref\fR,