This class describes rules which can be used to tune process of copying encoding data for cases when TrueType symbolic font has more than one encoding. Some PDF documents after conversion into PDF/A format could give an error More than one encoding in symbolic TrueType fonts cmap. What is a reason of this error All TrueType symbolic fonts have special table cmap in its internal data. This table maps character codes to glyph indices. And this table could contain different encoding subtables which describe encodings used. See advanced info about cmap tables at https//developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6cmap.html. Usually cmap table contains several encoding subtables but PDF/A standard requires that either only one encoding subtable must be left for this font in PDF/A document or there must be a 30 encoding subtable among this font subtables. And key question here - what data must be taken from another subtables to copy into destination encoding table 30 Majority of fonts have well-formed cmap tables where every encoding subtable is fully consistent with another subtable. But some fonts have cmap tables with collisions - where for example one subtable has glyph index 100 for unicode 100 but another subtable has glyph index 200 for the same unicode 100. To solve this problems special strategy needed. By default following strategy used mac subtable10 is looked for. If this table is found only this data used to fill destination table 30. If mac subtable is not found then all subtables except 30 are iterated and used to copy data into destination 30 subtable. Also mapping for every unicodeunicode glyph index is copied into destination table only if destination table does not have this unicode at current moment. So for example if first subtabe has glyph index 100 for unicode 100 and next subtable has glyph index 200 for the same unicode 100 only data from first subtable unicode100 glyph index 100 will be copied. So each previous subtable takes precedence over the next. Properties of this class PdfASymbolicFontEncodingStrategy./pdfasymbolicfontencodingstrategy help tune default behaviour. If property PreferredCmapEncodingTable./pdfasymbolicfontencodingstrategy/preferredcmapencodingtable of type CMapEncodingTableType./pdfasymbolicfontencodingstrategy.queueitem.cmapencodingtabletype is set then relevant subtable will be used in precedence to mac subtable10. Value MacTable from enumeration CMapEncodingTableType./pdfasymbolicfontencodingstrategy.queueitem.cmapencodingtabletype has no sense in this case cause it points on the same mac subtable 10 which will be used by default. Property CmapEncodingTablesPriorityQueue./pdfasymbolicfontencodingstrategy/cmapencodingtablespriorityqueue discards all priorities for any subtable. If this property is set then only subtables from declared queue will be used in specified order. If subtables specified are not found then default iteration of all subtables and copy strategy described above will be used. Object QueueItem./pdfasymbolicfontencodingstrategy.queueitem specifies encoding subtable used. This subtable can be set via combination of membersPlatformID PlatformSpecificId or via CMapEncodingTableType./pdfasymbolicfontencodingstrategy.queueitem.cmapencodingtabletype enumeration. In case when the font has no 30 subtable some other subtable will be used to maintain the PDF/A compatibility. The choice of the subtable to use is made under the same rules as described earlier so that PreferredCmapEncodingTable./pdfasymbolicfontencodingstrategy/preferredcmapencodingtable and CmapEncodingTablesPriorityQueue./pdfasymbolicfontencodingstrategy/cmapencodingtablespriorityqueue properties are used to determine the resultant subtable and if the font doesnt have the requested subtables either then any existant subtable will be used....table maps character codes to glyph indices. And this table could...for example one subtable has glyph index 100 for unicode 100, but...