These files are binary test files that were publicly available
on the Internet and were reproduced here to test the logic of
the respective plugin.  They are not under the "GPL", but
assumed to be reproducable (especially in this context) as they
are used for compatibility testing and their content is often
so trivial that they may not be copyrightable in the first place.
In other cases, they were distributed liberally by the original
authors.


Provenance of the MS Office samples
===================================

The files below were added for the `msoffice' plugin and for the
extensions to the `ole2' plugin that extract the names of the people
who edited a document (https://bugs.gnunet.org/view.php?id=2096).
Because that is precisely the kind of information the plugins are
meant to surface, the provenance and the licensing status of each
file is recorded here explicitly.

Files taken from Govdocs1
-------------------------

Govdocs1 is a research corpus of about one million documents that were
collected by Simson Garfinkel et al. from web servers in the .gov
domain, and which is published for research use at
https://digitalcorpora.org/corpora/file-corpora/files/ with the
statement that the files "are freely available for research and may be
(to the best of our knowledge) freely redistributed".  Works of the
U.S. federal government are not subject to copyright protection in the
United States (17 U.S.C. section 105), so these files are believed to
be in the public domain there; as with the pre-existing test files
above, they are reproduced here for compatibility testing.

Each file was renamed; the original number is the file's identifier
within the corpus and is given below.

  msoffice_word.docx        govdocs1 732704.docx
                            Word 2007 document, "Database Deployment
                            Request".  Carries core and extended
                            properties and one tracked insertion whose
                            timestamp is in local time, five hours off
                            the UTC modification date.

  msoffice_excel.xlsx       govdocs1 610528.xlsx
                            Excel 2007 workbook (National Park
                            Service).

  msoffice_powerpoint.pptx  govdocs1 392790.pptx
                            PowerPoint 2007 presentation (Department
                            of Veterans Affairs).

  msoffice_biff4.xls        govdocs1 149599.xls
                            An Excel worksheet written as a bare BIFF
                            record stream, i.e. without an OLE2
                            container, which is how Excel 2 to Excel 4
                            stored files.  Its only meta data is the
                            user name "FCC" in the WRITEACCESS record
                            of the File Protection Block.

  ole2_powerpoint.ppt       govdocs1 167115.ppt
                            PowerPoint 97-2003 presentation (FDA,
                            Center for Drug Evaluation and Research).
                            Its `Current User' stream names
                            "FDA.CDER", which differs from both the
                            author and the last-saved-by recorded in
                            the summary information -- a good example
                            of why the stream is worth reading.

All five name organisations or role accounts rather than private
individuals.  That was a deliberate selection criterion: many
documents in the corpus name identifiable people, and there is no
reason to republish those here when a functionally equivalent sample
does not.

Synthetic files
---------------

The public corpora predate Office 2013, so they contain none of the
parts that tie an author name to a directory identity, and no
documents that had been circulated for review.  The following two
files were therefore written by hand for this test suite.  They are
valid OPC packages, they are part of libextractor and covered by its
licence, and every name and address in them is fictitious
(example.com is reserved for documentation by RFC 2606).

  msoffice_review.docx      Word document with the `_AuthorEmail' and
                            `_AuthorEmailDisplayName' custom
                            properties that Outlook leaves behind when
                            a document is sent out for review, a
                            comment, tracked changes by two authors,
                            and a word/people.xml part mapping author
                            names to an e-mail address and to a
                            Windows SID.

  msoffice_shared.xlsx      Workbook with <fileSharing userName="...">
                            (the OOXML descendant of the BIFF
                            FILESHARING record), a classic cell
                            comment author list, the threaded comment
                            `persons' part, and a shared workbook
                            revision log naming who changed the
                            workbook and when.


Provenance of the RTF samples
=============================

The files below were added for the `rtf' plugin, which extracts the
same class of information from Rich Text Format documents: who wrote
them, who last saved them, who made each tracked change and when.
They come from the same Govdocs1 corpus described above, under the
same terms, and were selected under the same criterion -- they name
organisations, role accounts or login names rather than identifiable
private individuals.

  rtf_nih.rtf               govdocs1 003332.rtf
                            National Institute of Neurological
                            Disorders and Stroke.  `\author' and
                            `\operator' are both the role account
                            "NINDS", `\*\company' is "NIH".

  rtf_fda.rtf               govdocs1 942656.rtf
                            Announcement of a meeting of the Medical
                            Imaging Drugs Advisory Committee.  Written
                            by the same "CDER USER" account as the
                            PowerPoint sample above.

  rtf_nasa.rtf              govdocs1 806272.rtf
                            Goddard Space Flight Center.  Created
                            under the login "WLBEHNKE" but last saved
                            by "INTELLISOURCE", the contractor running
                            the office -- which is why `\author' and
                            `\operator' are reported separately.

  rtf_fta.rtf               govdocs1 882751.rtf
                            Federal Transit Administration document
                            produced by scanning software, which left
                            its own name in `\author' and a custom
                            document property in `\*\userprops'.

  rtf_doe_mac.rtf           govdocs1 534437.rtf
                            Review of the Yucca Mountain Igneous
                            Consequences Peer Review Panel report.
                            Written with Word for the Macintosh, which
                            says so by declaring the Mac OS Roman
                            character set; the apostrophe in the title
                            is encoded as `\'d5', which decodes
                            correctly only if that declaration is
                            honoured.

Synthetic file
--------------

  rtf_review.rtf            Written by hand for this test suite, and
                            hence part of libextractor and covered by
                            its licence.  Every name and address in it
                            is fictitious (example.org is reserved for
                            documentation by RFC 2606).  It covers the
                            paths that carry personal data and that
                            therefore should not be exercised with a
                            real document: a `\*\revtbl' revision
                            table with two authors, the `\revauth',
                            `\revauthdel' and `\crauth' flavours of
                            revision mark with their packed time
                            stamps, `\*\atnid' / `\*\atnauthor' /
                            `\*\atndate' for a comment, the Outlook
                            `_AuthorEmail' review properties, a
                            `\*\template' path from the authoring
                            machine, and both the `\uN' and the
                            `\'hh' character escapes.
