-
Notifications
You must be signed in to change notification settings - Fork 17
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
Asciidoc: attributes in functions rendered as a blank line #851
Comments
Attributes look fine in the tests (see test-files/golden-tests/metadata/attributes_1.html). It might be an issue with the version because MrDocs is moving very fast. Depending on how you're running it, you could create a script to update/reinstall MrDocs and run it every once in a while. In any case, I've included another test with the specific case: // issue #851
template <class T>
[[nodiscard]] int f(); ReferencefSynopsis
Declared in
<attributes-2.cpp>
Created with MrDocs |
I've updated to 375d913 and this seems to still happen. Can you please point me to the package.json with the Antora and asciidoctor versions you use in your test suite? |
There's no Antora and asciidoc in the test suite. You can see the fixtures in In this case, But I think in this case we have to investigate the relationship between the asciidoc it generates and Antora. Does |
Oh... Just had another look at it. The issue is Antora interprets that as an anchor. I'll fix that soon. |
Well I did post the generated asciidoc :) |
Gotcha. Thanks. |
#fix fix cppalliance#851
Yes. The word "rendered" is what was ambiguous. There are many rendering steps to be confused about. I thought you meant the attribute just wasn't in the adoc file. Not that it wasn't correctly escaped and being converted to an anchor. |
It looks like there is a rendering issue with attributes in the asciidoc generator. They seem to be added to the resulting asciidoc, but when rendered to HTML, they are replaced by blank lines.
For instance:
Generates the following asciidoc:
Which renders as:
The text was updated successfully, but these errors were encountered: