The rings background is a 501x456 GIF that blurs on any hi-DPI screen - #910
Merged
Conversation
The panel decoration was drawn as vector and flattened to a 4KB indexed GIF some time around 2007, with the panel colour baked in as an opaque backdrop. Refitting its four ellipse boundaries recovers the original geometry, so it goes back to being what it was: two elliptical annuli, 553 bytes of SVG, with a transparent background that now composites over the panel instead of having to match it. Rasterised at the same size, the only pixels that differ from the GIF are single-pixel anti-aliasing fringes along the four boundaries. Nothing survives a 3x3 erosion of that difference, so no edge has moved. Dark mode still drops the image rather than inverting it, since the ring lavender is a light-panel tone whichever way the file stores it. The engine keeps its own embedded copy of this GIF for the backblue.gif it writes into mirrors. That one is untouched: the filename and byte length are a contract with pages already on disk. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Xavier Roche <roche@httrack.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The panel decoration was drawn as vector and flattened to a 4KB indexed GIF around 2007, with the panel colour baked in as an opaque backdrop. It has only two colours, one of them byte-identical to the
background-colorthe same element already paints. Refitting its four ellipse boundaries recovers the original geometry, so it goes back to being what it was: two elliptical annuli, 553 bytes of SVG, transparent so it composites over the panel instead of having to match it.The geometry is fitted, not traced: sub-pixel boundary extraction (the alpha=0.5 crossing between neighbouring pixels, which also uses the sparse anti-aliased pixels) feeding a direct least-squares conic fit, max radial residual 0.57px. Rasterised at the same size, the only pixels that differ from the GIF are single-pixel anti-aliasing fringes along the four boundaries, and none survive a 3x3 erosion of that difference, so no edge has moved. An auto-trace would have produced several KB of bezier soup with the raster wobble baked in.
Test 142 asserted
image/gifon the deleted file. That assertion moves toheader_title_4.gif, and the new asset gets animage/svg+xmlcheck;svgwas already in htsserver's table.The engine keeps its own embedded copy of this GIF for the
backblue.gifit writes into mirrors. That one is untouched: the filename and byte length are a contract with pages already on disk.