-
Notifications
You must be signed in to change notification settings - Fork 11
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
Link to tables and figures by name #308
Comments
So I honestly don't see anything terrible with <p>The relationships between the four kinds of image are illustrated in <a href="#image-relationship"></a>.</p>
<figure id="image-relationship">
<!-- Maintain a fragment named "figure41" to preserve incoming links to it -->
<object id="figure41" data="figures/image-relationships.svg" type="image/svg+xml">
</object>
<figcaption>
Relationships between source, reference, PNG, and display images
</figcaption>
</figure> instead of, I guess, <p>The relationships between the four kinds of image are illustrated in <a>Relationships between source, reference, PNG, and display images</a>.</p>
<figure id="image-relationship">
<!-- Maintain a fragment named "figure41" to preserve incoming links to it -->
<object id="figure41" data="figures/image-relationships.svg" type="image/svg+xml">
</object>
<figcaption>
Relationships between source, reference, PNG, and display images
</figcaption>
</figure> Either way, this was clearly not a blocker to going to Candidate Recommendation. Close? |
Agreed @ definitely not a blocker. I'll look into this. |
I just tried to add. Earlier, I mentioned that ReSpec added support. But now I'm not so sure. I think a similar feature was added but not the one I thought. I'll update once I know more. |
Removing the tag until we know what exactly we want to do here |
ReSpec added support for linking to tables and figures by name rather than id. This matches the way ReSpec links to sections.
Go through the spec and see if there are links to figures/tables which make more sense to link by name rather than id.
The text was updated successfully, but these errors were encountered: