tree 11bbd189a1d38e2831f8693411485a713eb1dfe9
parent 42a1d4662865d8b2f3a6e5d52655e966759f6224
author Ben Wagner <bungeman@chromium.org> 1755552831 -0700
committer Pdfium LUCI CQ <pdfium-scoped@luci-project-accounts.iam.gserviceaccount.com> 1755552831 -0700

Change UseTTCharmapUnicode to prefer MSSymbol

Prior to "Treat all Unicode character maps like MSUnicode" [0] only the
cmap(3,1) (Windows,Unicode BMP) was considered as Unicode. After that
change, all Unicode cmaps like cmap(0,*) (Unicode,*) are considered as
Unicode. This fixes a number of issues with embedded fonts that do not
have a cmap(3,1).

However, this caused a regression in the case of embedded fonts with
Unicode cmap that isn't cmap(3,1) which also have a cmap(3,0)
(Windows,Symbol). In this case the Unicode cmap is now chosen over the
Symbol cmap. The Symbol cmap has special rules to augment the cmap as
well as special rules around converting to Unicode which will not be
applied to a Unicode cmap.

This changes the rule to prefer cmap(3,1) as before, then any other
Unicode cmap so long as there is no cmap(3,0). This restores the
previous behavior while still using Unicode cmaps when they are
available.

[0] https://pdfium.googlesource.com/pdfium/+/5da0e90faa40079145dc146f70bf186d3ad5e93f

Bug: 438810722, 439629188, 439635779
Change-Id: I247bb739fcb39b177923a7d4f3821df70dbca4fe
Reviewed-on: https://pdfium-review.googlesource.com/c/pdfium/+/135030
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Ben Wagner <bungeman@google.com>
Reviewed-by: Ben Wagner <bungeman@google.com>
(cherry picked from commit 40111e6fed154aeab93ea26a3e0a691745d13419)
Reviewed-on: https://pdfium-review.googlesource.com/c/pdfium/+/135110