diff options
| author | Jane Liu <janeliulwq@google.com> | 2017-07-19 13:10:50 -0400 |
|---|---|---|
| committer | Chromium commit bot <commit-bot@chromium.org> | 2017-07-19 19:09:39 +0000 |
| commit | 67ccef73bf664b7cdb4c6eed7acbaa4163c22a80 (patch) | |
| tree | 718061bc21fd52eab1bc70a8b9be97585f1d79f8 /testing/fx_string_testhelpers.h | |
| parent | eed247e9cb3b0e9ce5dcb8bf6ee7673c9dd3e544 (diff) | |
| download | pdfium-67ccef73bf664b7cdb4c6eed7acbaa4163c22a80.tar.xz | |
Use CFX_WideString in CPDF_NameTree functions to strip BOMchromium/3162
PDFium doesn't strip BOMs during parsing, but we should strip BOMs when
retrieving parsed strings in CPDF_NameTree to ensure consistency and
appropriate function behavior. See the bug for more info.
As outlined in Bug=pdfium:593, the solution is to call GetUnicodeText()
instead of GetString(). I added a GetUnicodeTextAt() function in
CPDF_Array, which is symmetrical to GetUnicodeTextFor() in
CPDF_Dictionary.
I then changed the input variable types to CPDF_NameTree functions to
be CFX_WideString instead of CFX_ByteString, and modified all the
calls to them.
I also added a unit test for nametree, which would fail prior to this
change. Nametrees with non-unicode names are already tested by embedder
tests.
Bug=pdfium:820
Change-Id: Id69d7343632f83d1f5180348c0eea290f478183f
Reviewed-on: https://pdfium-review.googlesource.com/8091
Reviewed-by: dsinclair <dsinclair@chromium.org>
Commit-Queue: Jane Liu <janeliulwq@google.com>
Diffstat (limited to 'testing/fx_string_testhelpers.h')
0 files changed, 0 insertions, 0 deletions