-
Notifications
You must be signed in to change notification settings - Fork 24
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
Hyperlink generation failure #30
Comments
cc @larseggert |
https://sandbox-htmlize.ietf.org/doc/html/rfc5741#section-3-2-2 has the same issue, because that document has no proper HTML available. So it won't be fixed in the future either. We could try and tweak the regexes, but given that there is no test suite I am afraid it will cause breakage elsewhere. |
I understand that the following may be a regex issue, so I'm adding it to #30. I've tried and failed to read CONTRIBUTING.md - it's a blank page in my browser and it didn't come with a git checkout so I gave up. Please feel free to update/move/delete/admonish as required. If there's no test suite, in my naïvety I imagine that it wouldn't be impossible for me to come up with something to test any changes to the regexes, even if all it did was compare the output from the new regexes with that from the old. A shell script employing wget and diff ought to do it. Observations? 8<-------------------------------------------------------------------------------------- RFC1112 has two appendices, Appendix I and Appendix II. First error: In the document, the first reference to one of these appendices is in In the HTML version at for example https://datatracker.ietf.org/doc/html/rfc1112 there is an HTML link in the section 4 reference: [quote] The link is incorrectly formed, as should be obvious. The second 'I' Second and third errors: There are no targets at the two appendices, thus clicking on the |
See section 3.2.3 of https://datatracker.ietf.org/doc/html/rfc5741 where there is a generated link for an unlinkable URL (as the URL contains an pseudocode parameter) but the linked text is only part of the usable URL (see where the
</a>
is placed).The HTML is
which appears onscreen as
"Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc<rfc-no>."
The text was updated successfully, but these errors were encountered: