James Addison

Hi @Johnnynator - thanks for the bugreport. Let's check if I understand your request correctly: * Docutils 0.21+ allows some image files in source `rST` projects to be annotated as...

> > Could I also ask what behaviour docutils provides if-and-when writing such embedded-annotated images to a purely text-based output format? > The loading attribute is only used for their...

First of all, thanks for the screenshot: when you mentioned that the error message appeared in the output in your previous messages, I misinterpreted that as being the Sphinx build...

A small concern I had about adding support for embedded SVGs is that there is no implicit namespace for each SVG file embedded within an HTML document. This can cause...

@goerz can you confirm that the absence of the messaging logic that we discussed in the original pull-request from your follow-up changeset _was not_ an attempt to check whether it's...

> Are you asking whether I deliberately not implemented the warning messages as a form of pentesting? Definitely not. I can confirm that I wasn't trying to poke holes in...

Yep, it does raise the complexity and that is unfortunate. However, if we discover ambiguous entries within an `objects.inv` file, then I think it's important to report the specific source...

> > I think it's important to report the specific source > > Yes and reporting the inventory key `inv_name` is sufficient for this, I don't think `intersphinx_mapping[inv_name][1][0]` is even...

A thought: perhaps the warnings could/should be detected during the inventory loading process instead of at resolution-time?

Ok; I've no further changes planned on this branch and will await further review. The changeset has been expanded to emit warnings when ambiguous references are discovered during loading of...