• Applications that are not Unicode-compliant will be unable to reliably handle Creo+ data saved in the Unicode format with strings (notes, annotations, table, and so on) in multiple languages other than English. For example, a Creo+ drawing can now contain both German and Japanese notes. The Creo TOOLKIT application will not be able to read or modify those notes correctly without being Unicode compliant. This could result in data loss or corruption.

• Applications that do not consider the Unicode nature of Creo+ data may try to pass that data directly to the system or third-party APIs that do not recognize it correctly. This could cause data corruption or crashes.

• Applications that do not transcode non-Unicode data into Unicode before using the data as strings inside Creo+ models will generate corrupt and incorrect models.