|RFC2629 test cases||J. F. Reschke|
Test cases for RFC2629 formatting
A numbered list:
An ordered list using letters:
Example for numbered list with user-defined-format:
Next list should continue counting R's:
Same with character-based numbering:
A few requirements:
A few rules:
Explicit counter with name matching it's format string:
Same, without counter:
Simple list item.
This one has two paragraphs. This is the first one.
This one has two paragraphs. This is the second one.
Another simple list item.
This is default.
This is emph(asized).
This is strong.
This is verb(atim).
Here is a carriage return inside a spanx element.
The list of valid keywords are:
|strict||no||try to enforce the ID-nits conventions and DTD validity||a|
|iprnotified||no||include boilerplate from Section 10.4(d) of [RFC2026]||bb bb|
|compact||no||when producing a txt/nroff file, try to conserve vertical whitespace||ccc ccc ccc|
|subcompact||compact||if compact is "yes", then setting this to "no" will make things a little less compact||dddd dddd dddd dddd|
|needLines||n/a||an integer hint indicating how many contiguous lines are needed at this point in the output||eeeee eeeee eeeee eeeee eeeee|
|here come empty cells|
Remember, that as with everything else in XML, keywords and values are case-sensitive.
The table below should appear with no borders.
Table 1: a table with no borders
The table below should appear with borders just around the headers.
Table 1 shows a table with no borders.
The table above shows a table with no borders.
with preamble, no title...
+--+ | | +--+
+--+ | | +--+
with postamble and title...
Figure 1: another figure
The figure above has the title "another figure".
test test (leading ws)
test test (trailing ws)
test test (no ws)
We are in Section 5.
Section 5 is the parent section.
See first sentence of previous section.
See last entry in Section 1.3.
So far we have sections 1 ("Lists") through 5 ("References").
This is a subsection of References (Section 5).
This is a subsection of References. Here we are referring to RFC 2026, without emitting extra formatting.
See [RFC2026, RFC2396].
See also <http://greenbytes.de/tech/webdav>. Here's another one that is quite long: <http://greenbytes.de/tech/webdav/draft-reschke-rfc3744bis-issues.html#5.7_inherited-acl-set-protected>. Does it break properly?
See also greenbytes WebDAV resources.
This is the first sentence of the paragraph. This is the second sentence of the paragraph (with two leading blanks). Here's another sentence that was started on a separate line in the input file.
This is the second paragraph.
This line contains a few comments. [rfc.comment.1] This line contains a few comments. [comment1] This line contains a few comments. [comment2] This line contains a few comments. [rfc.comment.2] This line contains a few comments.
This should fit (69 characters plus three spaces of indentation in text output).
These are tests for extensions done in rfc2629.xslt. Do not expect them to work out-of-the-box in xml2rfc.
Internal References: a test reference to [RFC2396] External References: a test reference to <http://xml.resource.org> a test index entry inside a figure Styling: <spanx> inside artwork
Here's a quote:
This is a Quote.
Here's a block level quote:
Here's a quote.
The line above should be marked up similar to a subsection heading.
The figure below should use box drawing characters instead of "+", "-" and "|".
┌────────────────┐ │ This is a Box. │ └────────────────┘
Referring to this section by anchor name indirectly through the references: Section 10.5 of [TSTCS].
(default formatting): Section 10.5 of [TSTCS].
Default inside a figure: [TSTCS], Section 10.5
With a broken anchor: [TSTCS].
Just a forced
|[RFC2026]||Bradner, S., “The Internet Standards Process -- Revision 3”, BCP 9, RFC 2026, October 1996.|
|[RFC2396]||Berners-Lee, T., Fielding, R.T., and L. Masinter, “Uniform Resource Identifiers (URI): Generic Syntax”, RFC 2396, August 1998.|
This RFC will soon be updated, check <http://cvs.apache.org/viewcvs.cgi/*checkout*/ietf-uri/rev-2002/rfc2396bis.html> for the latest draft.
The issues list is at <http://cvs.apache.org/viewcvs.cgi/*checkout*/ietf-uri/rev-2002/issues.html>.
|[TSTCS]||Reschke, J. F., “Test cases for RFC2629 formatting”, October 2007.|