A PDF/X-3 or PDF/X-4 export tagged every CMYK color with an ICC-based
space of the same profile that the output intent embeds. In PDF/X-3 and PDF/X-4, CMYK colors in the
profile of a CMYK output intent are now DeviceCMYK, and the profile is
written once, as the output intent's DestOutputProfile (ISO 32000-1,
14.11.5:
https://opensource.adobe.com/dc-acrobat-sdk-docs/pdfstandards/PDF32000_2008.pdf#page=641).
- With output.profiles none and a CMYK output intent, PDF/X-3 and PDF/X-4
write every CMYK color as DeviceCMYK, unless colors are converted to a
CMYK destination of another profile, which keeps its tag. Before, those
standards tagged every color whatever profiles said.
- RGB and gray colors stay tagged, and so do CMYK colors and images in
another profile.
- A CMYK image that carries the output intent's profile is DeviceCMYK,
and so is every CMYK image when none makes CMYK colors DeviceCMYK. A
CMYK JPEG then loses its ICC_PROFILE segments.
- Transparency groups blend in DeviceCMYK when CMYK colors are
DeviceCMYK, also when the file has no ICC-based CMYK space.
- Files without a standard keep the tags that profiles asks for.
- The Save PDF dialog's note for PDF/X-3 and PDF/X-4 says that CMYK
colors in the output intent's profile are written as DeviceCMYK.
Docs: docs/mcp.md, docs/target-app-parity.md and the document.exportPdf
params text.
A kept command result now takes its menu item's current label and menu
path when the menu state changes, so Show Grid reads Hide Grid once the
grid shows, and a command that no menu lists any more drops out. The
results are brought up to date only when the menus' state hash changes,
with the menu entries looked up by command and params. Help commands
reject parameters that are not an object.
A floating Tools panel dropped on the canvas's left edge, right of panels
docked on the left, stayed floating unless Window > Toolbars > Keep Tools
Beside the Canvas was on. The canvas's left edge is now always a target:
a drop there docks Tools beside the canvas and turns the setting on, and a
drop on the window's left edge docks it there and turns the setting off,
so the menu item's check mark shows where Tools is.
This changes one existing behavior: with the setting on and panels docked
on the left, a drop on the window's left edge used to dock Tools beside the
canvas and keep the setting on. It now docks Tools at the window's edge and
turns the setting off.
With no panels docked on the left, both edges put Tools in the same place
(left of any toolbars made with New Toolbar docked there), so a drop on
either docks it where the setting puts it and leaves the setting as it is.
So does a drop in the column both edges share when left-side panels are
collapsed to icons narrower than the window's edge strip. A release in the
frame right after Tools floats out of its place at the window's edge skips
the canvas-edge strip, which that frame laid out right of the docked panel.
Part of #7837
Part of #6889. While the samples are shown, a row under the filters
offers Small, Medium and Large, as the font browser overview and the
user guide describe the sample size control. With Enable in-menu font
previews off, the row is not shown, as the user guide describes.
VectorCraft's own rules: a click sets Preferences › Type › Font Preview
Size (`fontPreviewSize`), so every font menu takes the new row height,
and the host writes the preferences file as it does when Preferences is
confirmed. The current size is selected, and a click on it changes
nothing. A saved value that is none of the three sizes shows Medium,
and a click replaces it. The change adds no undo step and leaves a font
previewed on the selected type in place.
https://helpx.adobe.com/illustrator/desktop/design-with-text/fonts-and-scripts/font-options-overview.htmlhttps://web.archive.org/web/20210601162814/https://helpx.adobe.com/pdf/illustrator_reference.pdf#page=485
Docs: docs/target-app-parity.md evidence line.
Running a script or a plug-in now ends the spot color base's link, as a
batch step already did, so a script that deletes the spot color and makes
another of the same name does not make the new one the base. Commands that
only list scripts or plug-ins keep the link.
While the link waits for an Undo, the color it captures before a command is
the one the guide shows, not that of a new spot color of the same name.
The Enclosing Lasso Tool joins the Lasso group in both shipped
toolbars, right after the Lasso, and stays in Object › Plug-ins ›
Enclosing Lasso. The All Tools drawer lists it once, under Select, and
Edit › Keyboard Shortcuts › Tools lists it once. It has no default
shortcut, and the Lasso keeps Q. A toolbar the user already edited
keeps its saved layout; Reset Toolbar adds the tool.
Fixes#6117
object.setBounds and guide.move move direct-selected anchors through the
same path as object.move, so they already followed the Interpolate
Control Points preference. They now list `interpolate` in their params
text and reject a value that is not true or false, also when the change
only scales the anchors or only guides are selected. A test covers both
commands with the preference on and off and with the param.
When Add to Swatches brought a library pattern whose art links to a global
or spot color, and the document had that name for another color, the
pattern was relinked to the document's color. Adding the library's color
then made a numbered copy that the pattern did not use. The color now comes
in under a numbered name and the pattern links to it, as an added color
does, and the check for a pattern already in the document compares it the
same way.
Help kept each result's shortcut, label and menu path from the moment of
the search. After a shortcut changed, reopening Help or choosing a kept
result still showed and returned the old binding, and a change of the
interface language left the old labels in place.
The kept results now take the current shortcuts, labels and menu paths
when Help reopens, when a result is chosen or shown, and when the panel
draws after a change. The query, the order of the results and the
selected result stay as they were.
main now has sentences for Guides & Grid, so `a_row_without_a_description_leaves_the_line_empty`
points at Slices › Show Slice Numbers, which has no sentence. `docs/target-app-parity.md` keeps
main's General line once and adds Type to the categories that have sentences.
Look::takes let a glyph filled only join a run whose glyphs were also
stroked, so after mode 2 text a mode 0 glyph took the run's stroke:
`2 Tr (B) Tj 0 Tr (C) Tj` came in as "BC" stroked throughout. A glyph
now joins only a run drawn alike (fill, stroke, overprints), so a glyph
filled only starts a run of its own and takes a stroke only when the
matched-stroke path (#8039) strokes it.
flush_stroke no longer strokes a whole run in place: a whole run goes
through the split and join code, so fill and stroke rendering glyph by
glyph still builds one stroked run.
A Swatch Options rename of the spot color base keeps it the base, also
as a command.batch step, and so do an Undo and a Redo of the rename.
Deleting the swatch or its color group, merging it into another, making
it a process color or closing its document ends the link, so a later
spot color of the same name does not become the base until it is chosen
again. The base keeps the color it showed.
A batch's Activate Document, New, Open, Close and Move Document steps
are followed, so steps in another document leave the link alone. When
the swatch goes in a way the panel does not follow, the link waits for
an Undo or Redo, and the next other command ends it.
A PDF/X-4 export wrote xmp:ModifyDate and xmp:CreateDate in its XMP
metadata but no xmp:MetadataDate. The PDF/X-4 metadata edit now adds
xmp:MetadataDate next to xmp:ModifyDate, with the same value, and grows
the stream's /Length to match. When the export dates the file as modified
later, post::modification_date already rewrites every xmp:MetadataDate,
so the two dates stay equal.
PDF/X-1a, PDF/X-3, PDF/A and plain PDF exports are unchanged.
A fill and a stroke at the same opacity below 1 were joined into one
type object whose opacity then applies to both together, losing the
darker overlap the file composites. stroke_filled now takes a stroke
only when the fill and the stroke are opaque.
An upright glyph filled and stroked was kept as an outline for the
reshaped-outline fallback while upright glyphs filled only were not;
it is no longer kept either, so such a line can't come in as the
outlines of its stroked glyphs alone.
Docs: the #8015 entries say what is left (translucent type, and a TJ
that starts a new line part way through).