#### Summary: I have the following **Preferences** settings applied:  When I draw a double-sided arrow and save the drawing as a native Inkscape SVG, it has the following attributes set on the `<marker>` elements: ``` $ grep auto original-from-inkscape.svg orient="auto-start-reverse" orient="auto-start-reverse" ``` But when I save as a plain SVG or export to SVG, I still get the same attributes: ``` $ grep auto save-as-plain-svg.svg orient="auto-start-reverse" orient="auto-start-reverse" $ grep auto export.svg orient="auto-start-reverse" orient="auto-start-reverse" ``` These attributes cause the Batik rendering library to reject the images, making the tools in our software chain unhappy (Apache FOP, Oxygen XML). #### Steps to reproduce: 1. Download the image below. 2. Be sure marker preferences are set as above. 3. Open the "original-from-inkscape.svg" drawing. 4. Save in various SVG formats, check for the `auto-start-reverse` attribute value.  #### What happened? The `orient="auto-start-reverse"` attribute was set on `<marker>` elements, despite attempts to save as compliant SVG 1.1 files. Relevant forum discussion [here](https://inkscape.org/forums/beyond/save-as-svg-11/). #### What should have happened? There should be some way of creating SVG files that do not use `orient="auto-start-reverse"`. It is also unclear to me which export/save methods/formats use the marker settings in **Preferences**. I would prefer if the native Inkscape SVG could save as a compliant SVG 1.1 file so I don't have to keep two versions of the SVG file around, one for editing and one for publishing. #### Version info Inkscape 1.2.1 (9c6d41e410, 2022-07-14) GLib version: 2.72.2 GTK version: 3.24.34 glibmm version: 2.66.4 gtkmm version: 3.24.6 libxml2 version: 2.9.14 libxslt version: 1.1.35 Cairo version: 1.17.6 Pango version: 1.50.7 HarfBuzz version: 4.4.1 OS version: Windows 10 20H2