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

Put reference in its own element (bibliography) #4548

Open
nvitucci opened this issue Feb 9, 2024 · 4 comments
Open

Put reference in its own element (bibliography) #4548

nvitucci opened this issue Feb 9, 2024 · 4 comments
Labels
area/html-next Issues related to the next generation HTML converter

Comments

@nvitucci
Copy link

nvitucci commented Feb 9, 2024

I think this is an Asciidoctor request rather than a language one, but I'm happy to ask this in the language repository instead.

At the moment, when converted to HTML, the reference to an entry is rendered as part of the text within the <p> element. From the examples in the docs, the References section is converted as follows:

<div class="ulist bibliography">
  <ul class="bibliography">
    <li>
      <p><a id="pp"></a>[pp] Andy Hunt &amp; Dave Thomas. The Pragmatic Programmer: From Journeyman to Master. Addison-Wesley. 1999.</p>
    </li>
  </ul>
</div>

Can we have the reference in its own element instead? For example, if [pp] were converted to <span>[pp]</span> or something similar, it could easily be styled with CSS. I believe it could even just be text for the currently empty <a> element, unless you have excluded this for another reason.

@mojavelinux
Copy link
Member

Actually, this would be a change to consider for the next gen HTML converter. We aren't making any more substantial structural changes to the existing HTML converter as that would severely impact backwards compatibility. But that's why we are rethinking the whole thing. So I'm going to classify this issue as part of the next gen effort.

@mojavelinux mojavelinux added this to To do in Create Modern HTML Converter via automation Feb 9, 2024
@mojavelinux mojavelinux added the area/html-next Issues related to the next generation HTML converter label Feb 9, 2024
@mojavelinux
Copy link
Member

I don't think this would be a language issue (so this is the right place). This is really about how the information from the semantic element is organized in the converted output. At the moment, that is up to the AsciiDoc processor. In the future, there may be an HTML converter specification, but we think that will come out of the next gen converter, not the current one (which is intentionally backwards compatible with the HTML that has been produced from AsciiDoc for almost two decades).

@nvitucci
Copy link
Author

nvitucci commented Feb 9, 2024

Thank you for the clarification. Feel free to close it then.

@mojavelinux
Copy link
Member

mojavelinux commented Feb 9, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/html-next Issues related to the next generation HTML converter
Development

No branches or pull requests

2 participants