Intersphinx :any: references to link targets with capital letters fails

[bjones1]

Unzip Sphinx_projects.zip, then:

cd two
make html
cd ../one
make html

This illustrates the following problems:

From one/index.rst

From two/index.rst

Bugs observed

1. The :any: tag fails to find Intersphinx tags that contain capital letters.
2. The :any: tag produces an odd visual style for Intersphinx links; I would expect them to render identically to any other link (such as the standard style produced by using :ref:.)

Inconsistencies

1. Links produced by :ref: render based on the capitalization of the link target. Links produced by the Docutil syntax render based on the capitalization of the link reference. I would expect these to render identically.

Thanks

Sphinx is amazing and I use it every day. Thanks for creating and maintaining such as amazing tool!

[Thosse]

Is there any progress on this so far?
I'm trying to introduce sphinx at my company and stumbled over this.
Although it's not a deal breaker,, bugs like this make sphinx frustrating to work with.

[picnixz]

None that I am aware of. I can look at it next year when I'll have more time. Or look at it when attempting to fix all the autodoc bugs.

I think the issue may be related to how inventories are serialized and created or how the references are looked up to.

[docktermj]

Any progress?

[docktermj]

Case in point. Sphinx creates HTML anchors with mixed case letters. Example:

• http://hub.senzing.com/g2-sdk-python-next/senzing.html#senzing.g2product.G2Product.license

But documentation that tries to reference the anchor, such as

        A convenience method for
        :ref:`license<senzing.g2product.G2Product.license>`.

Gets this error:

/home/senzing/senzing.git/g2-sdk-python-next/src/senzing/g2product.py:docstring of senzing.g2product_abstract.G2ProductAbstract.license_as_dict:1: WARNING: undefined label: 'senzing.g2product.g2product.license'

[goerz]

@docktermj Can you clarify whether this is the same problem as #12008?

[docktermj]

It does look similar. Once #12008 is fixed, I can try my test case again.