From 8685b5730458ff59cf22853300187c16eab89888 Mon Sep 17 00:00:00 2001 From: Kesara Rathnayake Date: Mon, 19 Feb 2024 14:15:03 +1300 Subject: [PATCH] chore: Run yestests with changes --- tests/valid/docfile.html | 7 ++++--- tests/valid/draft-miek-test.html | 4 ++++ tests/valid/draft-template.html | 4 ++++ tests/valid/draft-v3-features.text | 29 ++++++++++++++++++--------- tests/valid/draft-v3-features.v3.html | 18 +++++++++-------- tests/valid/manpage.txt | 15 +++++++++----- tests/valid/rfc7911.html | 4 ++++ 7 files changed, 55 insertions(+), 26 deletions(-) diff --git a/tests/valid/docfile.html b/tests/valid/docfile.html index 9d09ec7b..7c11c246 100644 --- a/tests/valid/docfile.html +++ b/tests/valid/docfile.html @@ -4225,11 +4225,12 @@

[BCP14]
+
Best Current Practice 14, <https://www.rfc-editor.org/bcp/bcp14.txt>.
At the time of writing, this BCP comprises the following: +
- Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, .
+ Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
- Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, .
-<https://www.rfc-editor.org/bcp/bcp14.txt> + Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.
[IDGUIDE]
diff --git a/tests/valid/draft-miek-test.html b/tests/valid/draft-miek-test.html index 9318cc12..8b7cf845 100644 --- a/tests/valid/draft-miek-test.html +++ b/tests/valid/draft-miek-test.html @@ -470,6 +470,10 @@ margin-bottom: 1.25em; } +.refSubseries { + margin-bottom: 1.25em; +} + .references .ascii { margin-bottom: 0.25em; } diff --git a/tests/valid/draft-template.html b/tests/valid/draft-template.html index 33099f8f..6ce69147 100644 --- a/tests/valid/draft-template.html +++ b/tests/valid/draft-template.html @@ -459,6 +459,10 @@ margin-bottom: 1.25em; } +.refSubseries { + margin-bottom: 1.25em; +} + .references .ascii { margin-bottom: 0.25em; } diff --git a/tests/valid/draft-v3-features.text b/tests/valid/draft-v3-features.text index 21a6b9cd..c6499401 100644 --- a/tests/valid/draft-v3-features.text +++ b/tests/valid/draft-v3-features.text @@ -1360,10 +1360,13 @@ Table of Contents _here_, November 2014. Due to a element, this should be listed as "[0REFTEST]". - [BCP45] Eggert, L. and S. Harris, "IETF Discussion List Charter", - BCP 45, RFC 9245, June 2022. + [BCP45] Best Current Practice 45, + . + At the time of writing, this BCP comprises the following: - + Eggert, L. and S. Harris, "IETF Discussion List Charter", + BCP 45, RFC 9245, DOI 10.17487/RFC9245, June 2022, + . [DUP] Reschke, J., "Reference Duplicate Test", July 2016. @@ -1385,23 +1388,29 @@ Table of Contents RFC 7996, DOI 10.17487/RFC7996, December 2016, . - [STD78] Schoenwaelder, J., "Simple Network Management Protocol + [STD78] Internet Standard 78, + . + At the time of writing, this STD comprises the following: + + Schoenwaelder, J., "Simple Network Management Protocol (SNMP) Context EngineID Discovery", STD 78, RFC 5343, - September 2008. + DOI 10.17487/RFC5343, September 2008, + . Harrington, D. and J. Schoenwaelder, "Transport Subsystem for the Simple Network Management Protocol (SNMP)", - STD 78, RFC 5590, June 2009. + STD 78, RFC 5590, DOI 10.17487/RFC5590, June 2009, + . Harrington, D. and W. Hardaker, "Transport Security Model for the Simple Network Management Protocol (SNMP)", - STD 78, RFC 5591, June 2009. + STD 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, + . Hardaker, W., "Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)", - STD 78, RFC 6353, July 2011. - - + STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, + . [STPETER] ᏚᎢᎵᎬᎢᎬᏒ Inc. (STPETER Inc.), "ᏚᎢᎵᎬᎢᎬᏒ's document". A document where the author element specifies just an diff --git a/tests/valid/draft-v3-features.v3.html b/tests/valid/draft-v3-features.v3.html index 806e0e73..9da8063f 100644 --- a/tests/valid/draft-v3-features.v3.html +++ b/tests/valid/draft-v3-features.v3.html @@ -13,7 +13,7 @@ This document tests features introduced in xml2rfc v3 vocabulary. " name="description"> - + @@ -4969,9 +4969,10 @@

[BCP45]
+
Best Current Practice 45, <https://www.rfc-editor.org/info/bcp45>.
At the time of writing, this BCP comprises the following: +
- Eggert, L. and S. Harris, "IETF Discussion List Charter", BCP 45, RFC 9245, .
-<https://www.rfc-editor.org/info/bcp45> + Eggert, L. and S. Harris, "IETF Discussion List Charter", BCP 45, RFC 9245, DOI 10.17487/RFC9245, , <https://www.rfc-editor.org/info/rfc9245>.
[DUP]
@@ -4998,15 +4999,16 @@

[STD78]
+
Internet Standard 78, <https://www.rfc-editor.org/info/std78>.
At the time of writing, this STD comprises the following: +
- Schoenwaelder, J., "Simple Network Management Protocol (SNMP) Context EngineID Discovery", STD 78, RFC 5343, .
+ Schoenwaelder, J., "Simple Network Management Protocol (SNMP) Context EngineID Discovery", STD 78, RFC 5343, DOI 10.17487/RFC5343, , <https://www.rfc-editor.org/info/rfc5343>.
- Harrington, D. and J. Schoenwaelder, "Transport Subsystem for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5590, .
+ Harrington, D. and J. Schoenwaelder, "Transport Subsystem for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5590, DOI 10.17487/RFC5590, , <https://www.rfc-editor.org/info/rfc5590>.
- Harrington, D. and W. Hardaker, "Transport Security Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5591, .
+ Harrington, D. and W. Hardaker, "Transport Security Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5591, DOI 10.17487/RFC5591, , <https://www.rfc-editor.org/info/rfc5591>.
- Hardaker, W., "Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 6353, .
-<https://www.rfc-editor.org/info/std78> + Hardaker, W., "Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 6353, DOI 10.17487/RFC6353, , <https://www.rfc-editor.org/info/rfc6353>.
[STPETER]
diff --git a/tests/valid/manpage.txt b/tests/valid/manpage.txt index b13846f8..0c6ad851 100644 --- a/tests/valid/manpage.txt +++ b/tests/valid/manpage.txt @@ -2642,13 +2642,18 @@ Table of Contents 4. References - [BCP14] Bradner, S., "Key words for use in RFCs to Indicate - Requirement Levels", BCP 14, RFC 2119, March 1997. + [BCP14] Best Current Practice 14, + . + At the time of writing, this BCP comprises the following: - Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC - 2119 Key Words", BCP 14, RFC 8174, May 2017. + Bradner, S., "Key words for use in RFCs to Indicate + Requirement Levels", BCP 14, RFC 2119, + DOI 10.17487/RFC2119, March 1997, + . - + Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC + 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, + May 2017, . [IDGUIDE] Housley, R., "Guidelines to Authors of Internet-Drafts", December 2010, diff --git a/tests/valid/rfc7911.html b/tests/valid/rfc7911.html index 82e679ea..6d173f12 100644 --- a/tests/valid/rfc7911.html +++ b/tests/valid/rfc7911.html @@ -463,6 +463,10 @@ margin-bottom: 1.25em; } +.refSubseries { + margin-bottom: 1.25em; +} + .references .ascii { margin-bottom: 0.25em; }