tests::newdoc::a_profile_brings_the_color_profile_its_file_carries and
tests::saveoptions::an_embedded_profile_is_restored give their front
document a non-sRGB RGB profile. That profile becomes the process-wide
active color settings and stays active until a document without one
comes to the front. Every color the engine test process renders goes
through those settings, so the test
tests::rasterfilters::each_effect_changes_the_canvas_and_draws_the_same_twice
could draw the same art in two colors and fail with "<effect> is
deterministic".
The two tests now run again in a child process of the test binary
through a shared helper, tests::in_own_process. The SVG Drop Shadow test
for a non-sRGB working space uses the helper in place of its own copy,
and the GLOBAL doc comment in tests/colormgmt.rs names this route.
The rasterfilters test now checks that the color settings are the
defaults before it draws and that nothing replaced them while it drew.
A test that changes them in the same process makes it fail with "another
test changed the color settings while this one drew".
With the three tests run together (--test-threads=3) on Linux, the
rasterfilters test failed 10 of 10 runs without the child processes,
each time with that message, and passed 10 of 10 with them.
A save as .ai or .ait (file.saveCopy, file.saveAs, document.save and
file.saveAsTemplate) set range to "all" before the file was written.
The one exception was a legacy .ai of version 7 given a range, which
its encoder checks. Every other save accepted an artboard, artboards or
range that names an artboard the document does not have (artboards: [5]
on a document of three artboards) and wrote every artboard.
document.export refuses the same value.
The save now refuses such a value with the export's error, under the
name of the command that was run, and writes no file. A range that is
not text, such as range: 42, was also replaced by "all". The save now
leaves it for the encoder, which refuses it as an export does. An
artboard the document has, or an empty artboards list, is still saved
with every artboard, and a legacy .ai still writes the artboards of its
range.
Option errors and notes for a .ai save called the file a
"PDF-compatible .ai" even when the save wrote a version 7 file
(aiVersion: "7") or a file without PDF content (pdfCompatible: false).
- Option errors: a version 7 .ai is now called a "legacy .ai
(version 7)" in the errors for its artboard, artboards and range
options. A .ai saved without PDF content is called a
"non-PDF-compatible .ai" in every .ai option error (includeLinked and
embedProfiles included), and a "non-PDF-compatible .ait template"
when Save as Template writes it. aiVersion: "7" takes precedence over
pdfCompatible: false, as it does when the file is written.
- The error for encoding a version 7 .ai of several artboards as one
file names the legacy .ai.
- The note for a native option the file does not read (version,
preview, precision) names the same kind of file.
- The error for aiVersion: "7" on a .ait template no longer says that a
.ait template is always PDF-compatible, since Save as Template writes
one without PDF content. It now reads "aiVersion 7 writes legacy .ai
files, not .ait templates", with its rows in the message catalogs
updated.
A PDF-compatible file keeps its name.
A .ai saved with pdfCompatible false warned that other apps show empty
pages, also when the file carries the editing copy of its art. With the
editing copy the warning now says that apps that read its editing data
open it; with editingData false it is unchanged.