Thank you adam1991 and oxident for your feedback. Based on the sample file that adam1991 sent we have resolved this issue in the next generation Fiery codebase. If you would like to have a patch for your specific Fiery then please contact your Fiery reseller and request that they open an official defect with KM.

Thanks again for your feedback.