katex v3

Cargo.toml

@@ -1,7 +1,7 @@
 [package]
 name = "thumbor"
 description = "A Rust client for the Thumbor image service"
-version = "0.1.7"
+version = "0.1.8"
 repository = "https://github.com/SteelAlloy/thumbor-rs"
 documentation = "https://docs.rs/thumbor"
 readme = "README.md"
@@ -30,4 +30,3 @@ hmac = "0.12.1"
 sha1 = "0.10.6"
 base64ct = { version = "1.6.0", features = ["alloc"] }
 bon = "2.3.0"
-katex-doc = "0.1.0"

src/endpoint.rs

@@ -160,33 +160,27 @@ pub struct Endpoint {
     /// The image size argument specifies the size of the image that will be
     /// returned by the service. Thumbor uses smart [crop_and_resize_algorithms](https://thumbor.readthedocs.io/en/latest/crop_and_resize_algorithms.html)
     ///
-    /// If you omit one of the dimensions or use zero as a value (as in $`300x`$,
-    /// $`300x0`$, $`x200`$, $`0x200`$, and so on), Thumbor will determine that dimension as
-    /// to be proportional to the original image. Say you have an $`800x600`$ image
-    /// and ask for a $`400x0`$ image. Thumbor will infer that since $`400`$ is half of
-    /// $`800`$, then the height you are looking for is half of $`600`$, which is $`300px`$.
+    /// If you omit one of the dimensions or use zero as a value (as in $300x$,
+    /// $300x0$, $x200$, $0x200$, and so on), Thumbor will determine that dimension as
+    /// to be proportional to the original image. Say you have an $800x600$ image
+    /// and ask for a $400x0$ image. Thumbor will infer that since $400$ is half of
+    /// $800$, then the height you are looking for is half of $600$, which is $300px$.
     ///
-    /// If you use $`0x0`$, Thumbor will use the original size of the image and thus
+    /// If you use $0x0$, Thumbor will use the original size of the image and thus
     /// won't do any cropping or resizing.
     ///
     /// If you specify one of the dimensions as the string "orig" (as in
-    /// $`origx100`$, $`100xorig`$, $`origxorig`$), thumbor will interpret that you want
+    /// $origx100$, $100xorig$, $origxorig$), thumbor will interpret that you want
     /// that dimension to remain the same as in the original image. Consider an
-    /// image of $`800x600`$. If you ask for a $`300xorig`$ version of it, thumbor will
-    /// interpret that you want a $`300x600`$ image. If you instead ask for a
-    /// $`origx300`$ version, thumbor will serve you an $`800x300`$ image.
+    /// image of $800x600$. If you ask for a $300xorig$ version of it, thumbor will
+    /// interpret that you want a $300x600$ image. If you instead ask for a
+    /// $origx300$ version, thumbor will serve you an $800x300$ image.
     ///
-    /// If you use $`origxorig`$, Thumbor will use the original size of the image
+    /// If you use $origxorig$, Thumbor will use the original size of the image
     /// and thus won't do any cropping or resizing.
     ///
     /// **The default value (in case it is omitted) for this option is to use
     /// proportional size (0) to the original image.**
-    ///
-    /// ```math
-    /// f(x) = \int_{-\infty}^\infty
-    /// \hat f(\xi)\,e^{2 \pi i \xi x}
-    /// \,d\xi
-    /// ```
     #[builder(into)]
     resize: Option<Coords>,