Stop using Encoding array to get unicode from charcode in Type 3 fonts

Stop using Encoding array to get unicode from charcode in Type 3 fonts

We should not fill out the m_Encoding for Type3 fonts. This way, we
stop getting garbage characters from text extraction. Guessing that
unicode == charcode (in the absence of ToUnicode) is our best bet.

BUG=pdfium:642
Review-Url: https://codereview.chromium.org/2643543002
Committed: https://pdfium.googlesource.com/pdfium/+/21ae2b7297e005576afeb9f0230d1f69b3abc857

[npm, 2017-01-17 22:40:36]

Description was changed from

==========
Stop using Encoding array to get unicode from charcode in Type 3 fonts

We should not fill out the m_Encoding for Type3 fonts. This way, we
stop getting garbage characters from text extraction. Guessing that
unicode == charcode (in the absence of ToUnicode) is our best bet.

BUG=pdfium:642
==========

to

==========
Stop using Encoding array to get unicode from charcode in Type 3 fonts

We should not fill out the m_Encoding for Type3 fonts. This way, we
stop getting garbage characters from text extraction. Guessing that
unicode == charcode (in the absence of ToUnicode) is our best bet.

BUG=pdfium:642
==========

[npm, 2017-01-17 22:40:36]

npm@chromium.org changed reviewers:
+ dsinclair@chromium.org, tsepez@chromium.org, weili@chromium.org

[npm, 2017-01-17 22:40:55]

ptal

[Tom Sepez, 2017-01-17 23:01:55]

lgtm

[npm, 2017-01-17 23:03:55]

The CQ bit was checked by npm@chromium.org

[commit-bot: I haz the power, 2017-01-17 23:04:03]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-17 23:15:38]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1484694235600540, "parent_rev":
"a715f524e66a1fd8b974f6e2af0db3c23b8c5190", "commit_rev":
"21ae2b7297e005576afeb9f0230d1f69b3abc857"}

[commit-bot: I haz the power, 2017-01-17 23:15:41]

Description was changed from

==========
Stop using Encoding array to get unicode from charcode in Type 3 fonts

We should not fill out the m_Encoding for Type3 fonts. This way, we
stop getting garbage characters from text extraction. Guessing that
unicode == charcode (in the absence of ToUnicode) is our best bet.

BUG=pdfium:642
==========

to

==========
Stop using Encoding array to get unicode from charcode in Type 3 fonts

We should not fill out the m_Encoding for Type3 fonts. This way, we
stop getting garbage characters from text extraction. Guessing that
unicode == charcode (in the absence of ToUnicode) is our best bet.

BUG=pdfium:642

Review-Url: https://codereview.chromium.org/2643543002
Committed:
https://pdfium.googlesource.com/pdfium/+/21ae2b7297e005576afeb9f0230d1f69b3ab...
==========

[commit-bot: I haz the power, 2017-01-17 23:15:41]

Committed patchset #1 (id:1) as
https://pdfium.googlesource.com/pdfium/+/21ae2b7297e005576afeb9f0230d1f69b3ab...