We are getting added space following the hyphen and slash characters in the name attribute (not line-break related). We are using &wj; as a workaround. Examples below:
In RFC 9244 (Figure 48):
Input:
<name>GET Request to Receive Asynchronous Notifications Filtered Using Uri-Query</name>
Output:
Figure 48: GET Request to Receive Asynchronous Notifications Filtered Using Uri- Query
In RFC 9486 (Figure 1):
Input:
<name>IPv6 Hop-by-Hop and Destination Option Format for Carrying IOAM Data-Fields</name>
Output:
Figure 1: IPv6 Hop-by-Hop and Destination Option Format for Carrying IOAM Data- Fields
In draft-ietf-alto-new-transport-22 (Figure 6):
Input:
<name>Example of an ALTO Server Supporting the ALTO Base Protocol, ALTO/SSE, and ALTO TIPS</name>
Output:
Figure 6: Example of an ALTO Server Supporting the ALTO Base Protocol, ALTO/ SSE, and ALTO TIPS
Describe the issue
We are getting added space following the hyphen and slash characters in the name attribute (not line-break related). We are using &wj; as a workaround. Examples below:
In RFC 9244 (Figure 48):
Input:
<name>GET Request to Receive Asynchronous Notifications Filtered Using Uri-Query</name>
Output:
Figure 48: GET Request to Receive Asynchronous Notifications Filtered Using Uri- Query
In RFC 9486 (Figure 1):
Input:
<name>IPv6 Hop-by-Hop and Destination Option Format for Carrying IOAM Data-Fields</name>
Output:
Figure 1: IPv6 Hop-by-Hop and Destination Option Format for Carrying IOAM Data- Fields
In draft-ietf-alto-new-transport-22 (Figure 6):
Input:
<name>Example of an ALTO Server Supporting the ALTO Base Protocol, ALTO/SSE, and ALTO TIPS</name>
Output:
Figure 6: Example of an ALTO Server Supporting the ALTO Base Protocol, ALTO/ SSE, and ALTO TIPS
Code of Conduct