Fix image refs, restore old images

honno · honno · commit 58f2e59c9110 · 2023-01-07T09:17:46.000Z
diff --git a/spec/2021.12/API_specification/data_types.rst b/spec/2021.12/API_specification/data_types.rst
@@ -72,7 +72,7 @@ IEEE 754 double-precision (64-bit) binary floating-point number (see IEEE 754-20
 
    ``complex64`` and ``complex128`` data types are expected to be included in the next version of this standard and to have the following casting rules (will be added to :ref:`type-promotion`):
 
-   .. image:: /_static/images/dtype_promotion_complex.png
+   .. image:: ../../_static/images/dtype_promotion_complex.png
 
    See `array-api/issues/102 <https://github.com/data-apis/array-api/issues/102>`_ for more details
 
diff --git a/spec/2021.12/API_specification/type_promotion.rst b/spec/2021.12/API_specification/type_promotion.rst
@@ -7,7 +7,7 @@ Type Promotion Rules
 
 Type promotion rules can be understood at a high level from the following diagram:
 
-.. image:: /_static/images/dtype_promotion_lattice.png
+.. image:: ../../_static/images/dtype_promotion_lattice_no_complex.png
     :target: Type promotion diagram
 
 *Type promotion diagram. Promotion between any two types is given by their join on this lattice. Only the types of participating arrays matter, not their values. Dashed lines indicate that behavior for Python scalars is undefined on overflow. Boolean, integer and floating-point dtypes are not connected, indicating mixed-kind promotion is undefined.*
diff --git a/spec/2021.12/assumptions.md b/spec/2021.12/assumptions.md
@@ -35,7 +35,7 @@ such a coupling. Facilitation support of multiple array types in downstream
 libraries is an important use case however, the assumed dependency structure
 for that is:
 
-![dependency assumptions diagram](_static/images/dependency_assumption_diagram.png)
+![dependency assumptions diagram](../_static/images/dependency_assumption_diagram.png)
 
 Array libraries may know how to interoperate with each other, for example by
 constructing their own array type from that of another library or by shared
diff --git a/spec/2021.12/purpose_and_scope.md b/spec/2021.12/purpose_and_scope.md
@@ -111,7 +111,7 @@ Furthermore, meta-topics included in this standard include:
 The concrete set of functionality that is in scope for this version of the
 standard is shown in this diagram:
 
-![Scope of array API](_static/images/scope_of_array_API.png)
+![Scope of array API](../_static/images/scope_of_array_API.png)
 
 
 **Goals** for the API standard include:
diff --git a/spec/2022.12/API_specification/type_promotion.rst b/spec/2022.12/API_specification/type_promotion.rst
@@ -7,7 +7,7 @@ Type Promotion Rules
 
 Type promotion rules can be understood at a high level from the following diagram:
 
-.. image:: /_static/images/dtype_promotion_lattice.png
+.. image:: ../../_static/images/dtype_promotion_lattice.png
     :target: Type promotion diagram
 
 *Type promotion diagram. Promotion between any two types is given by their join on this lattice. Only the types of participating arrays matter, not their values. Dashed lines indicate that behavior for Python scalars is undefined on overflow. Boolean, integer and floating-point dtypes are not connected, indicating mixed-kind promotion is undefined.*
diff --git a/spec/2022.12/assumptions.md b/spec/2022.12/assumptions.md
@@ -35,7 +35,7 @@ such a coupling. Facilitation support of multiple array types in downstream
 libraries is an important use case however, the assumed dependency structure
 for that is:
 
-![dependency assumptions diagram](_static/images/dependency_assumption_diagram.png)
+![dependency assumptions diagram](../_static/images/dependency_assumption_diagram.png)
 
 Array libraries may know how to interoperate with each other, for example by
 constructing their own array type from that of another library or by shared
diff --git a/spec/2022.12/purpose_and_scope.md b/spec/2022.12/purpose_and_scope.md
@@ -111,7 +111,7 @@ Furthermore, meta-topics included in this standard include:
 The concrete set of functionality that is in scope for this version of the
 standard is shown in this diagram:
 
-![Scope of array API](_static/images/scope_of_array_API.png)
+![Scope of array API](../_static/images/scope_of_array_API.png)
 
 
 **Goals** for the API standard include:
diff --git a/spec/_static/images/dtype_promotion_complex.png b/spec/_static/images/dtype_promotion_complex.png
diff --git a/spec/_static/images/dtype_promotion_lattice_no_complex.png b/spec/_static/images/dtype_promotion_lattice_no_complex.png
diff --git a/spec/draft/API_specification/type_promotion.rst b/spec/draft/API_specification/type_promotion.rst
@@ -7,7 +7,7 @@ Type Promotion Rules
 
 Type promotion rules can be understood at a high level from the following diagram:
 
-.. image:: /_static/images/dtype_promotion_lattice.png
+.. image:: ../../_static/images/dtype_promotion_lattice.png
     :target: Type promotion diagram
 
 *Type promotion diagram. Promotion between any two types is given by their join on this lattice. Only the types of participating arrays matter, not their values. Dashed lines indicate that behavior for Python scalars is undefined on overflow. Boolean, integer and floating-point dtypes are not connected, indicating mixed-kind promotion is undefined.*
diff --git a/spec/draft/assumptions.md b/spec/draft/assumptions.md
@@ -35,7 +35,7 @@ such a coupling. Facilitation support of multiple array types in downstream
 libraries is an important use case however, the assumed dependency structure
 for that is:
 
-![dependency assumptions diagram](_static/images/dependency_assumption_diagram.png)
+![dependency assumptions diagram](../_static/images/dependency_assumption_diagram.png)
 
 Array libraries may know how to interoperate with each other, for example by
 constructing their own array type from that of another library or by shared
diff --git a/spec/draft/purpose_and_scope.md b/spec/draft/purpose_and_scope.md
@@ -111,7 +111,7 @@ Furthermore, meta-topics included in this standard include:
 The concrete set of functionality that is in scope for this version of the
 standard is shown in this diagram:
 
-![Scope of array API](_static/images/scope_of_array_API.png)
+![Scope of array API](../_static/images/scope_of_array_API.png)
 
 
 **Goals** for the API standard include:
