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.

Sign up for GitHub

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

Jump to bottom

Schema Issue, RFC 7991, In Section 2.32, <name> #47

Closed
levkowetz opened this issue Oct 8, 2018 · 3 comments
Closed

Schema Issue, RFC 7991, In Section 2.32, <name> #47

levkowetz opened this issue Oct 8, 2018 · 3 comments

Comments

@levkowetz
Copy link
Contributor

In Section 2.32, <name>

So the <name> element can contain text or <tt>, and <tt> can contain
other markup like <sub> and <sup> etc., but why cannot <name> contain
<sup> etc. directly?

Proposal: Change the <name> element schema to permit all inline
elements that <tt> can contain, in addition to <tt>.

Implementation: Not changed in the current version of xml2rfc.
Implementing this would be a simple matter of changing
the v3 schema; no formatter changes would be needed.
@paulehoffman
Copy link
Contributor

Consensus was to implement.

paulehoffman added a commit that referenced this issue Oct 20, 2018
@paulehoffman
table/align: add note about caption; Issue #47
49aecca
@paulehoffman
Copy link
Contributor

Closed with PR #69

@reschke
Copy link
Contributor

reschke commented May 3, 2020

(duplicate of #32 )

@reschke reschke mentioned this issue May 3, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@reschke @paulehoffman @levkowetz