* eps: delegate scene-writer shading, image stream, and line style syntax to craft-ps
* chore(eps): repin craft-ps to merged craft-libs main (cfcc86242)
- eps: restore linear-time memchr::memmem::find in lex::find so
search_in_a_loop_runs_out_of_the_budget does not hit O(N*M) under
craft_ps::read::lex::find.
- ui-egui: wait for FontDb background scan and ensure >20 font families
in menu_access_stationary_pointer_repeat_and_rerun_do_not_retarget_or_double_invoke
so coverage/minimal runners do not race or fall short of 20 families.
Follow-up to #8400. A Perceptual gradient expands each segment into
stops on its OKLab curve. Between two stops of the same color the round
trip through OKLab rounded the color, so a stretch between two
paper-white stops came out as nearly white RGB. On a PostScript plate
the separator then saw ink there, and an overprinting gradient painted
over the ink below across that stretch.
Gradient::expanded now gives a stop between two stops of the same color
that color, unchanged, for every method. GradientMethod::mix and
Gradient::sample are not changed.
* .ai import: blank area type keeps its frame, blank point type quiet
A text object whose story is blank (nothing but spaces and line ends)
was never made (`Story::node`), so its slot
was left empty and counted in the note "text objects on hidden layers
or hidden objects couldn't be read", shown or not.
A slot of a blank story that neither the text document nor the page
fills is now settled after the page is matched, so the page's type
still takes it where the page has some for it alone:
- Blank area type and type on a path come in as a text object that
keeps its frame or path and draws nothing (`Story::blank_frame_node`),
as VectorCraft's Type tool keeps an empty frame (#85, #154). That
covers a frame the page's spare type went past (`Merged`) too. It is
kept without being weighed against the page, and so are the later
frames of its thread.
- Blank point type draws nothing and has nothing to keep, so it is left
out without a note, as the Type tool discards empty point type.
- A blank slot takes the page's type left over only when no other open
slot can (`readable_first`), so it no longer takes another object's
type by painting order.
- A blank story's thread isn't held against an unread object that takes
one of its frames, and a thread lists only the frames still there.
Its frames are still threaded type to warps and envelopes, which
never take the place of such a frame.
The note for text objects still left out no longer says they are
hidden: "text objects whose type couldn't be read from the file's text
document or its page are left out".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* .ai import: a blank frame an unread object leaves alone isn't threaded type
When an unread object takes one frame of a blank story's two-frame
thread with it, the other frame is no longer threaded in the document,
but warps and envelopes still treated it as threaded type and so never
weighed it against its look. They now get the frames of the threads
actually kept.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Test: the lone blank frame in a warp comes in as its look, no text left
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Conflicts in docs only (status lines, changelog rows and table rows):
main's entries and this branch's are both kept, each once. Main now has
this branch's first File formats row fix (#868) itself.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A diamond gradient whose vector has no length has no inside, and the
renderer draws it with its color at 1 everywhere. With two stops at 1,
that is the first of them, which ends the stretch before it. The EPS
writer painted the last stop instead, so such a diamond came out in the
other color, and on a PostScript plate an overprinting one whose last
stop is paper white knocked out the ink below at Level 3. The writer now
paints the color at 1, and on a plate leaves the ink below when that color
is paper white, at both levels.
an_overprinting_gradient_with_a_hard_stop_at_an_end_keeps_the_ink_below_on_a_postscript_plate
compared each PostScript plate with the PostScript plate of the gradient
alone, so a writer that dropped the gradient from both still passed. It
now also reads the plates at fixed points (halfway along the vector, before
its start for the linear gradient, and past its end) and checks that the
gradient's own cyan prints there, alone and over the cyan below, where the
level's painter puts some down, and that the cyan below prints elsewhere.
- A file's corners are kept only when there are exactly four that the
image can take; a longer list is skipped without decoding it. Corners
the affine map misses stay a distortion, and a scale past the
perspective limit leaves the image at its nearest affine placement.
- Distort checks the corners in a frame local to the quad, so a missed
corner far from the origin is still refused.
- Relink and Unembed refuse a named or selected distorted image before
searching a folder or writing a file. Create Gradient Mesh lists the
distorted images it leaves in `skipped`. Place with Replace refuses
only when the measured image is distorted and the file is not text.
- SVG cuts a distorted image in a scaled symbol instance at the placed
size. EMF pieces store only the pixels inside their clip. PDF mesh
pieces of a CMYK image keep a same-corner mask as its soft mask, color
mask included. Both `.ai` writers write an image at the nesting limit
at its nearest placement with a warning. DXF warns only when it writes
the image.
- The canvas cuts the mesh by the view's largest stretch. Warped images
with a singular placement keep finite corners.
- docs/mcp.md and docs/plugins.md describe the tolerances, the DXF and
WMF fallback, the partial result of Create Gradient Mesh, and when a
plug-in sees `corners`.
Conflicts in docs only (status lines, changelog rows and table rows):
main's entries and this branch's are both kept, each once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Conflicts in docs only (status lines, changelog rows and table rows):
main's entries and this branch's are both kept, each once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>