The following comparisons are intended to refer to visible differences in printed output. All fields can differ in location and size. Specific properties of each field type may also differ. See the following tables for details.
Field Location: The following table shows field location differences. Locations are relative measurements.
Shifting of fields is considered unacceptable and problematic only if it is greater than 1/10 of an inch and causes overlap with other fields on the label. Instances of shifting that are greater than 1/10 of an inch are classified as low priority if there is no overlap with other fields.
If the LPS labels themselves have overlapping fields, then the migrated labels will have similar overlap. This is expected and acceptable.
|
|
Original location |
||
|
|
|
Fields have shifted, but are in the same general location and are not overlapping any other fields. |
|
|
|
|
Fields have shifted more than 1/10 of an inch and are causing an overlap. |
Text Size: Due to migration, text size may contract or expand, but a text field should not expand so much that it overlaps another field. This applies to variable text, fixed text, paragraph, and text box fields. Text should not expand or contract by more than 15%. Instances of text expansion by more than 15% are classified as low priority if text does not overlap other fields.
|
|
Original text, box for reference. |
|
|
|
|
Original text has contracted but is acceptable. |
|
|
|
Original text expanded so that it overlaps another field. |
Line thickness: The following table shows line thickness. Line thickness is a relative measurement but is measured in pixels. A difference in line thickness that is greater than 1 pixel is unacceptable.
|
|
Original thickness |
|
|
|
|
Line thickness difference is acceptable. |
|
|
|
Line thickness difference is unacceptable because it overlaps another field. |
Formula data sources: Formulas migrate from LPS to Loftware Cloud. However, formulas may have implementation differences in Loftware Cloud and adjustments may be needed.
Script and Formula Interoperability: In LPS, it is possible to reference the result of formulas in scripts. This is possible due to order of operations in LPS. The order of operations is different in Loftware Cloud. LPS scripts do not convert and migrate to Loftware Cloud, but instead must be recreated using VBScript or Python code. To facilitate the interoperability of scripts and formulas, formulas that are referenced in LPS scripts need to be included in the recreated Loftware Cloud script.
Barcode data: Many barcode symbologies encode a specific set of characters. LPS and Loftware Cloud will both encode data that contains expected characters. LPS and Loftware Cloud differ when characters are encountered that the symbology does not support. If a character cannot be encoded, Loftware Cloud will fail the print job due to unencodable character.
For example, the following Interleaved 2 of 5 barcode is printed in LPS with the given data "1234abcd".
This barcode scans to "1234", dropping the letters in LPS. When migrated to Loftware Cloud with the same data, the label fails to print because the data is not valid for an Interleaved 2 of 5 barcode.
Resolution of this issue may include a formula, script, business rule, or changing the input data.