xml2rfc 2.4.1 v2 puts two spaces after "i.e." #115
Description
resolution_fixed type_defect | by jonathan@vidyo.com
I have an I-D whose source text includes the XML source
<t>Note: To avoid confusion, an RTCP packet is an individual item,
such as a Sender Report (SR), Receiver Report (RR), Source
Description (SDES), Goodbye (BYE), Application Defined (APP), <xref
target="RFC4585">Feedback</xref> or <xref target="RFC3611">Extended
Report (XR)</xref> packet. A compound packet is the combination of two
or more such RTCP packets where the first packet must be an SR or an
RR packet, and which contains a SDES packet containing an CNAME item.
Thus the above results in compound RTCP packets that contain multiple
SR or RR packets from different sources as well as any of the other
packet types. There are no restrictions on the order the packets may
occur within the compound packet, except the regular compound rule,
i.e. starting with an SR or RR.</t>
(I've also attached the full document below. This is the same document as attached to Ticket 114, except with a workaround for the problem in Ticket 114.)
The xml2rfc 2.4.1 output of the last line of the paragraph is:
the regular compound rule, i.e. starting with an SR or RR.
Notice that there are two spaces after "i.e.", which isn't correct.
xml2rfc-1.36 handled this correctly.
Issue migrated from trac:115 at 2022-02-05 12:29:10 +0000