8.5

Warning
Splitters do not modify the metadata that is currently active within your process. This means that, if you
are intending to use metadata along with a process using splitters, you can either use the "Metadata
Sequencer" on page465 instead of a splitter, or (re)create the metadata after the splitter.
About Using Emulations with Splitters
When an emulation is used with a splitter action task, the job file is emulated, cut to pieces and de-emulated.
Most times, the emulation/de-emulation process is completely transparent. However, in some cases, there
may be minute differences.
When using the ASCII or Channel Skip emulation, if there are missing line feed characters (when lines end
with a single carriage return in ASCII, or when lines start with a No line feed channel in Channel Skip), the
output data will be different from the input data, but the change will not be significant.
Let us imagine that a splitter action task processes the following data file using the ASCII emulation:
Data line1 of page 1<cr><lf>
Data line2 of page 1<cr>
Last data line of page 1<cr><lf>
Data line1 of page 2<cr><lf>
...and so forth...
Once split, the first file generated by the action task would look like this:
Data line1 of page 1<cr><lf>
Data line2 of page 1<cr>
Data line2 of page 1<cr><lf>
Last data line of page 1<cr>
But when opened with PlanetPress Design or a PlanetPress Workflow using the ASCII emulation, the data
in the generated file would look exactly like the data in the original. The same would hold true for the
Channel Skip emulation.
Note the following details about emulations and their options: