2018.1

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:
l With most emulations, if a file is split on a form feed, the form feed will not be appended to
the output file.
l With the ASCII emulation, tabs within the input data file are replaced by spaces (the
number of spaces is determined within the configuration of the emulation).
l
With the ASCII emulation, if the Remove HP PCL Escapes option is selected, the data
coming out of the splitter will have no escape sequences.
l
The Goto column option of Channel Skip emulation is not supported.
Page 325