<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Image-Editing on VisorCraft News</title><link>https://www.visorcraft.com/news/tags/image-editing/</link><description>Recent content in Image-Editing on VisorCraft News</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 09 Jul 2026 10:19:00 -0500</lastBuildDate><atom:link href="https://www.visorcraft.com/news/tags/image-editing/index.xml" rel="self" type="application/rss+xml"/><item><title>Arte-Ogre: Why We Test Image Editors with Byte-Identical Round-Trips</title><link>https://www.visorcraft.com/news/2026/07/arte-ogre-byte-identical-round-trips/</link><pubDate>Thu, 09 Jul 2026 10:19:00 -0500</pubDate><guid>https://www.visorcraft.com/news/2026/07/arte-ogre-byte-identical-round-trips/</guid><description>&lt;p&gt;Cut a region of a transparent layer in Photoshop, switch layers, and paste, and the paste lands at &lt;code&gt;(0, 0)&lt;/code&gt;, while in GIMP it lands at the cursor and in Krita at the layer origin, and none of them land where you cut from, because the position is recoverable in some editors, lost in others, and never consistently tested; the position isn&amp;rsquo;t part of the data, and it&amp;rsquo;s a side effect of whichever application happens to be in front of you when you hit paste.&lt;/p&gt;</description></item></channel></rss>