Skip to content
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

Losing <tt and sorrounding whitespace from abstract #469

Open
1 task done
cabo opened this issue Nov 3, 2024 · 3 comments
Open
1 task done

Losing <tt and sorrounding whitespace from abstract #469

cabo opened this issue Nov 3, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@cabo
Copy link

cabo commented Nov 3, 2024

Describe the issue

https://bib.ietf.org/get-one/by-docid/?docid=RFC+9165&doctype=IETF&query=9165&query_format=docid_regex&page=1

Code of Conduct

@cabo cabo added the bug Something isn't working label Nov 3, 2024
@ajeanmahoney
Copy link
Collaborator

The API for RFC reference information is https://www.rfc-editor.org/rfc-index.xml, which does not contain text formatting such as <tt/>, so the abstract provided by bib.ietf.org won't have it either.

However, rfc-index.xml has the correct spaces around the terms:

The present document defines a number of control operators that were
not yet ready at the time RFC 8610 was completed: .plus, .cat, and
.det for the construction of constants; .abnf/.abnfb for including
ABNF (RFC 5234 and RFC 7405) in CDDL specifications; and .feature for
indicating the use of a non-basic feature in an instance.

So I don't know what happened there.

@kesara
Copy link
Member

kesara commented Nov 3, 2024

There's no spaces in the relaton source file.

So this is an issue in relaton-ietf gem.

@ajeanmahoney
Copy link
Collaborator

In our database and rfc-index.xml, this abstract (and also the abstracts of RFCs 9396 and 9495) initially had <tt/> formatting, which is why the spacing was incorrect.
The updated rfc-index.xml should be pulled into bib.ietf.org again to fix the spacing issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants