-
Notifications
You must be signed in to change notification settings - Fork 55
Closed
Labels
bugSomething isn't workingSomething isn't workingtextIssues in text output and text writerIssues in text output and text writer
Description
Describe the issue
In the text output, there are two spaces after “a.k.a.” although there is only a single space in the xml:
From text output:
This recommendation is part of the basis for the review of user
privacy solutions for IEEE Std 802.11 (a.k.a. Wi-Fi) devices as part
of the RCM [rcm_privacy_csd] efforts.
The html and pdf outputs do not have this extra space.
This may be related to this closed issue: #115 (I don’t see “a.k.a.” listed though).
I looked at some recently published RFCs with “a.k.a.” (like RFCs 9653 and 9671), and they do not have this issue.
Files:
https://www.rfc-editor.org/v3test/draft-ietf-madinas-mac-address-randomization-15-TEST.xml
https://www.rfc-editor.org/v3test/draft-ietf-madinas-mac-address-randomization-15-TEST.txt
https://www.rfc-editor.org/v3test/draft-ietf-madinas-mac-address-randomization-15-TEST.html
https://www.rfc-editor.org/v3test/draft-ietf-madinas-mac-address-randomization-15-TEST.pdf
Code of Conduct
- I agree to follow the IETF's Code of Conduct
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingtextIssues in text output and text writerIssues in text output and text writer