Comments (3)
the problem with that is that I would be following a non-RFC document that receives updates and I would need to track.
The core of the issue is that RFCXML is a moving target and that the RFC editor's style guide is not published as an RFC.
closing as desired by unfeasible
from mmark.
update smartypants comment as that only works for html in ef81939
mmark warned about non-ascii when the ugly workaround <u>
was implemented in xml2rfc. This has since been removed as xml2rfc is 100% utf8 and ietf documents can now just use that encoding (and characters).
See ietf-tools/xml2rfc@ad2e035
and https://github.com/ietf-tools/xml2rfc/releases/tag/v3.16.0
As there is no new RFCXML rfc I don't know what the rfc-editor is clinging to 7991 and not using these features.
In short: I think this can be closes as WAI ?
from mmark.
update smartypants comment as that only works for html
Thanks, that explains why I was having trouble 😅
As there is no new RFCXML rfc I don't know what the rfc-editor is clinging to 7991 and not using these features.
I have confirmation from the RFC Editor that the authoritative document for RFCXML v3 is now https://authors.ietf.org/en/rfcxml-vocabulary (which notes this at its top, but I hadn't spotted it because I'd only ever linked into the middle of the page).
I think the issue here is not the RFCXML vocabulary, but the style guide. It's the latter that was being cited here, and I am completely unfamiliar with how that document is updated, or how mmark
users generally interact with it. Maybe the better way to reframe this issue would be as an idea to add a style linter flag?
from mmark.
Related Issues (20)
- mmark output not accepted by xml2rfc HOT 2
- Wrong rendering of inlined contact references to contacts HOT 7
- Enhancement: Using CDATA rather than entity escape codes in the sourcecode element HOT 5
- Use of anchor or id for referencing HOT 1
- fix releasing HOT 3
- bibliography.go should use bib.ietf.org URLs
- Incorrect GitHub Organization URL HOT 1
- Error referencing internet draft by version HOT 6
- Error referencing RFC drafts HOT 4
- Normative and Informative references are not wrapped in References section HOT 2
- Support more `rfc` attributes HOT 5
- `consensus` attribute applies to more than the IETF stream HOT 3
- Section citations hard-code `relative="#"` HOT 3
- Prebuilt binaries are missing HOT 2
- ref to BCP HOT 2
- Do not render `<area>` element from IRTF documents HOT 3
- Omit `day` attribute in `<date>` boilerplate element for RFCs HOT 3
- Provide release notes HOT 3
- Is it possible to specify metadata using YAML? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mmark.