-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
extraneous \% before Section #169
Comments
@arusso@amsl.com uploaded file |
@henrik@levkowetz.com changed priority from |
@arusso@amsl.com commented Bug in the nroff output: if the xref-created 'Section X' is at the beginning of a sentence, then there is only one space after the preceding period. (Should be 2 spaces after sentence-ending period.) Examples from attached test.nroff:
The nroff yields text with 1 space after 'them.' and 'collections.' when it should be 2 spaces. |
@arusso@amsl.com uploaded file |
@arusso@amsl.com uploaded file |
@arusso@amsl.com commented The extraneous % in the nroff sometimes yields a stray "-" when converted to text. For example: v2 nroff:
nroff-generated text:
corrected nroff (removed %):
|
@ietf@augustcellars.com changed owner from |
@henrik@levkowetz.com changed status from |
@henrik@levkowetz.com changed resolution from `` to |
@henrik@levkowetz.com commented Fixed in 531a96d: Patch from elwynd@dial.pipex.com: Don't emit '%' before 'Section' for xrefs in the nroff writer. Fixes issue #169. |
@henrik@levkowetz.com commented From 8bc0749: Tweaked known-good test masters to match Elwyn's fix, see issue #169. |
owner:ietf@augustcellars.com
resolution_fixed
type_defect
| by arusso@amsl.comThe nroff output has extraneous "%" before "Section" (generated from xref). Minor because it doesn't cause an issue when converting the nroff to text.
Example: see %Section 4.2
(Note: % correctly appears before anchors than contain a hyphen, e.g., %[IANA-PORT])
v2 nroff attached; generated from XML with #168.
Issue migrated from trac:169 at 2022-02-05 12:32:46 +0000
The text was updated successfully, but these errors were encountered: