Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
cmap [2020/02/23 11:17] christian [Monster from the wild] |
cmap [2020/02/23 13:37] christian [Monster from the wild] |
||
|---|---|---|---|
| Line 126: | Line 126: | ||
| ===== Monster from the wild ===== | ===== Monster from the wild ===== | ||
| + | CMaps are not well defined. Therefore, there are some interesting variations of them in the wild. Here is a small selection of some issues. | ||
| ==== Mappings outside the codespace ==== | ==== Mappings outside the codespace ==== | ||
| - | single byte mappings in a double byte codespace | + | <code postscript> |
| + | %... | ||
| + | 1 begincodespacerange | ||
| + | < | ||
| + | endcodespacerange | ||
| + | 27 beginbfchar | ||
| + | <20> < | ||
| + | <2E> < | ||
| + | <43> < | ||
| + | <44> < | ||
| + | <45> < | ||
| + | %... | ||
| + | </ | ||
| - | ==== Wrong PostScript ==== | + | Here are single byte mappings in a double byte codespace which is not correct according to the documentation. |
| - | using /find instead | + | This can be seen often. These illegal mappings are collected into the ''# |
| + | |||
| + | ==== Wrong PostScript ==== | ||
| - | See [[postscript# | + | On one occasion, I saw a CMap where the PostScript used a non-existing operator (''/ |
| ==== Prevent copying ==== | ==== Prevent copying ==== | ||