Remove the document tagged code as it is unused.

Remove the document tagged code as it is unused.

The fpdf_tagged.h, tagged_int.h and doc_tagged.cpp code is currently unused
and can be removed.

Committed: https://pdfium.googlesource.com/pdfium/+/dbfc3522a6ee24d17f2c50a5dcc465db52a280ee

[dsinclair, 2016-07-28 13:53:02]

The CQ bit was checked by dsinclair@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-07-28 13:53:09]

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

[dsinclair, 2016-07-28 13:54:24]

dsinclair@chromium.org changed reviewers:
+ thestig@chromium.org, weili@chromium.org

[dsinclair, 2016-07-28 13:54:24]

PTAL.

[commit-bot: I haz the power, 2016-07-28 14:12:21]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-07-28 14:12:22]

Dry run: This issue passed the CQ dry run.

[Lei Zhang, 2016-07-28 19:35:13]

lgtm

There's ~80 pages of PDF spec dedicated to Logical Structure (including
StructTreeRoot) and Tagged PDF, but there's no PDFium APIs for any of it, so
this is useless as is.

[dsinclair, 2016-07-28 19:59:31]

The CQ bit was checked by dsinclair@chromium.org

[dsinclair, 2016-07-28 19:59:32]

The patchset sent to the CQ was uploaded after l-g-t-m from thestig@chromium.org
Link to the patchset: https://codereview.chromium.org/2188213002/#ps20001
(title: "Rebase to master")

[commit-bot: I haz the power, 2016-07-28 19:59:40]

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, 2016-07-28 20:17:31]

Description was changed from

==========
Remove the document tagged code as it is unused.

The fpdf_tagged.h, tagged_int.h and doc_tagged.cpp code is currently unused
and can be removed.
==========

to

==========
Remove the document tagged code as it is unused.

The fpdf_tagged.h, tagged_int.h and doc_tagged.cpp code is currently unused
and can be removed.

Committed:
https://pdfium.googlesource.com/pdfium/+/dbfc3522a6ee24d17f2c50a5dcc465db52a2...
==========

[commit-bot: I haz the power, 2016-07-28 20:17:33]

Committed patchset #2 (id:20001) as
https://pdfium.googlesource.com/pdfium/+/dbfc3522a6ee24d17f2c50a5dcc465db52a2...

[npm, 2016-08-25 22:49:17]

npm@chromium.org changed reviewers:
+ npm@chromium.org

[npm, 2016-08-25 22:49:17]

This code is being used by the android foxit viewer. Should we revert this CL?

[Lei Zhang, 2016-08-25 22:55:57]

On 2016/08/25 22:49:17, npm wrote:
> This code is being used by the android foxit viewer. Should we revert this CL?

I guess we can. Is there an internal bug somewhere that refers to this?

We should tell them to not use CPDF code and go through public/ APIs, if we
haven't already. (See list of bugs I've filed) Otherwise we get surprises like
this.

We should probably also add some unit tests after we put this code back in.

[npm, 2016-08-26 14:33:17]

No internal bug that I'm aware of, just tried upgrading pdfium in google3 and
building the android pdfviewer. It didn't work because of several #includes of
files we have moved/deleted.

[npm, 2016-08-26 16:55:17]

A revert of this CL (patchset #2 id:20001) has been created in
https://codereview.chromium.org/2279323002/ by npm@chromium.org.

The reason for reverting is: Code being used by Android foxit viewer.