-
Notifications
You must be signed in to change notification settings - Fork 12
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
link fest #244
Comments
There are a few tooling changes that might be worth pursuing here, but I don't intend to make any changes in response to this issue. |
For reference: ietf-tools/datatracker#5071 and ietf-tools/xml2rfc#963 and cabo/kramdown-rfc#185 |
I believe the tooling used still creates a large number of useless and distracting links in the document. I've created an agenda item to this weeks IESG's Informal meeting to discuss this. |
Was there any outcome of the IESG discussion? (The tooling does what it is told to do. Auto-creating links obviously needs to be applied sparingly... |
Oh, that change actually happened: In xml2rfc 3.17.0. |
Steps have been taken. The index remains problematic, but that's (again) on xml2rfc. |
Comment by @paulwouters
It seems some automated tooling was used to creating links within the document, eg for "key configuration": 7 times in Section 3, pointing to a few lines below in section 3.1, and even one time within section 3.1 itself pointing recursively back to itself, and 3 more times in section 3.2, and then I stopped counting.
The same for things like "client", Oblivious Gateway Resource", etc etc culminating in Section 5 that's more blue than black, making the blue links, uhm, oblivious :P
The text was updated successfully, but these errors were encountered: