@@ -25,7 +25,7 @@ projects, and optionally to a specific external project.
25
25
A link like ``:external:ref:`comparison manual <comparisons>` `` will then link
26
26
to the label "comparisons" in whichever configured external project, if it
27
27
exists,
28
- and a link like ``:external:python+ ref:`comparison manual <comparisons>` `` will
28
+ and a link like ``:external+python: ref:`comparison manual <comparisons>` `` will
29
29
link to the label "comparisons" only in the doc set "python", if it exists.
30
30
31
31
Behind the scenes, this works as follows:
@@ -173,7 +173,7 @@ linking:
173
173
174
174
For example, with ``intersphinx_disabled_reftypes = ['std:doc'] ``
175
175
a cross-reference ``:doc:`installation` `` will not be attempted to be
176
- resolved by intersphinx, but ``:external:otherbook+ doc:`installation` `` will
176
+ resolved by intersphinx, but ``:external+otherbook: doc:`installation` `` will
177
177
be attempted to be resolved in the inventory named ``otherbook `` in
178
178
:confval: `intersphinx_mapping `.
179
179
At the same time, all cross-references generated in, e.g., Python,
@@ -207,10 +207,10 @@ The Intersphinx extension provides the following role.
207
207
then the key of the project, as specified in :confval: `intersphinx_mapping `,
208
208
is added as well to get the two forms
209
209
210
- - ``:external:invname+ domain:reftype:`target` ``,
211
- e.g., ``:external:python+ py:class:`zipfile.ZipFile` ``, or
212
- - ``:external:invname+ reftype:`target` ``,
213
- e.g., ``:external:python+ doc:`installation` ``.
210
+ - ``:external+invname: domain:reftype:`target` ``,
211
+ e.g., ``:external+python: py:class:`zipfile.ZipFile` ``, or
212
+ - ``:external+invname: reftype:`target` ``,
213
+ e.g., ``:external+python: doc:`installation` ``.
214
214
215
215
Showing all links of an Intersphinx mapping file
216
216
------------------------------------------------
0 commit comments