|Oracle® Outside In File ID Developer's Guide
Part Number E12875-02
File ID is part of Oracle's family of OEM products known as Outside In Technology, a powerful document extraction, conversion and viewing technology that can access the information in more than 500 file formats.
There may be references to other Outside In Technology SDKs within this manual. To obtain complete documentation for any other Outside In product, see:
and click on Outside In Technology.
The updated list of supported formats is linked from the page
http://www.outsideinsdk.com/. Look for the data sheet with the latest supported formats.
New File IDs have been added.
FI Defines, value and LO strings are :
FI_FLASH9, 1727, "Macromedia Flash 9"
FI_FLASH10, 1728, "Macromedia Flash 10"
FI_WIN_EXPLORERCMD, 2400, "Microsoft Windows Explorer Command File"
FI_7Z, 1826, "7z Archive File"
FI_TRILLIAN_TEXT, 1341, "Trillian Text Log File"
FI_TRILLIAN_XML, 1342, "Trillian XML Log File"
FI_LIVEMESSENGER, 1343, "Microsoft Live Messenger Log File"
FI_AOLMESSENGER, 1344, "AOL Messenger Log File"
FI_WINDOWSHELP, 2402, "Windows Help File"
FI_WIN_COMPILEDHELP, 2403, "Windows Compiled Help File"
FI_WIN_SHORTCUT, 2401, "Windows shortcut"
FI_TRUETYPEFONT, 2404, "TrueType Font File"
FI_TRUETYPECOLLECTION, 2405, "TrueType Font Collection File"
FI_TRUETYPEFONT_MAC, 2406, "TrueType (MAC) Font File"
FI_OUTLOOK_MSG_MAIL, 1143, "MS Outlook Mail File"
FI_OUTLOOK_OFT_MAIL, 1311, "Outlook Mail Form Template"
FI_OUTLOOK_MSG_APPT, 1345, "MS Outlook Appointment File"
FI_OUTLOOK_OFT_APPT, 1346, "Outlook Appointment Form Template"
FI_OUTLOOK_MSG_JOURNAL, 1347, "MS Outlook Journal File"
FI_OUTLOOK_OFT_JOURNAL, 1348, "Outlook Journal Form Template"
FI_OUTLOOK_MSG_CONTACT, 1349, "MS Outlook Contact File"
FI_OUTLOOK_OFT_CONTACT, 1350, "Outlook Contact Form Template"
FI_OUTLOOK_MSG_NOTE, 1351, "MS Outlook Note File"
FI_OUTLOOK_OFT_NOTE, 1352, "Outlook Note Form Template"
FI_OUTLOOK_MSG_TASK, 1353, "MS Outlook Task File"
FI_OUTLOOK_OFT_TASK, 1354, "Outlook Task Form Template"
For backward compatability - we will define previous FIs to the MAIL ids.
#define FI_OUTLOOK_MSG FI_OUTLOOK_MSG_MAIL
#define FI_OUTLOOK_OFT FI_OUTLOOK_OFT_MAIL
OIT's internal error processing has been updated and propagation of error codes throughout OIT has been improved. In many cases the error codes reported by OIT will now more accurately reflect the actual cause of the error. DAERR is now functionally the same as SCCERR and OIT API functions that return DAERR may return any of the SCCERR values defined in sccerr.h.
The Outside In File ID API allows developers to identify files using the same technology that all Outside In products use internally. This specification uses a 16-bit value called the ID or type ID to identify different file formats. These IDs are defined in sccfi.h.
This API includes the following functions:
FIIdFile: Returns an ID given a file.
FIIdFileEx: Returns an ID and an ID name given a file.
FIGetFirstId: Returns the first ID in the range of IDs used by this API.
FIGetNextId: Returns the next ID in the range of IDs used by the API.
Each Outside In product has an sdk directory, under which there is a subdirectory for each platform on which the product ships (for example, fi/sdk/fi_win-x86-32_sdk). Under each of these directories are the following three subdirectories:
docs: Contains both a PDF and HTML version of the product manual.
redist: Contains only the files that the customer is allowed to redistribute. These include all the compiled modules, filter support files, .xsd and .dtd files, cmmap000.bin, and third-party libraries, like freetype.
sdk: Contains the other subdirectories that used to be at the root-level of an sdk: common, lib (windows only), resource, samplefiles, and samplecode (previously samples). In addition, one new subdirectory has been added, demo, that holds all of the compiled sample apps and other files that are needed to demo the products. These are files that the customer should not redistribute (.cfg files, exportmaps, and so forth.).
In the root platform directory (for example, fi/sdk/fi_win-x86-32_sdk), there are two files:
README: Explains the contents of the sdk, and that makedemo must be run in order to use the sample applications.
makedemo (either .bat or .sh – platform-based): This script will either copy (on Windows) or Symlink (on UNIX) the contents of …/redist into …/sdk/demo, so that sample applications can then be run out of the demo directory.