PDFlib Text Extraction Toolkit (TET) Manual

More documents

Recommendations

Info

Table 10.8 Document options for TET_open_document( ) and TET_open_document_callback( ) option checkglyphlists decompose encodinghint description (Boolean) If true, TET will check all builtin glyphmapping rules with condition=allfonts before text extraction starts. Otherwise the global glyphmapping rules will not be applied. This option slows down processing, but is useful for certain kinds of TeX documents with glyph names which cannot be mapped to Unicode by default. Default: false (Keyword or option list) Unicode decompositions which will be applied to all characters which have a specified Unicode decomposition tag and are part of the specified Unicode set. These conditions are provided in the suboption name and value. Decompositions can be used to either remove or preserve the distinction between equivalent Unicode characters (see Section 7.3, »Unicode Postprocessing«, page 97). Default:see »Default decompositions«, page 103. However, if the normalize option has a value other than none, all default decompositions are disabled, i.e. setting the normalize option sets the default to decompose=none. However, user-specified decompositions can still be applied. The following keywords can be supplied instead of a list: none No decompositions will be applied. default The default decompositions (see »Default decompositions«, page 103) will be applied before other specified decompositions. The following suboptions for decompositions are supported: canonical, circle, compat, final, font, fraction, initial, isolated, medial, narrow, nobreak, small, square, sub, super, vertical, wide Each of these suboptions accepts a string or keyword which specifies the decomposition’s domain, i.e. the set of Unicode characters to which the decomposition will be applied. A string specifies a Unicode set for the domain. This can be used to restrict decompositions to subsets of the characters with the specified decomposition tag. Characters outside the domain will not be modified. As an alternative to a string for a Unicode set the following keywords can be supplied: _all _none The set of all Unicode characters, i.e. the decomposition will be applied to all characters with the specified decomposition tag. The empty set, i.e. the decomposition will not be applied at all. (String 1 ) The name of an encoding which will be used to determine Unicode mappings for glyph names which cannot be mapped by standard rules, but only by a predefined internal glyph mapping rule. The keyword none can be used to disable all predefined rules. Default: winansi 162 Chapter 10: TET Library API Reference
Table 10.8 Document options for TET_open_document( ) and TET_open_document_callback( ) option fold glyphmapping lineseparator normalize inmemory description (Keyword or list of lists; the first element of each inner list is a Unicode set or keyword, the second element is a Unichar or a keyword) Apply a folding (equivalence mapping) to all characters in a folding domain specified as a Unicode set. The foldings will be applied to all text except separator characters added by the lineseparator or wordseparator options (see see Section 7.3, »Unicode Postprocessing«, page 97). Default: see Table 7.3, page 99. The following keyword can be supplied instead of a list: none No foldings will be applied. The following keyword can be supplied instead of a sublist: default The default foldings will be applied before other specified foldings. The first element of each list specifies the folding’s domain, i.e. the set of Unicode characters to which the folding will be applied. A string specifies a Unicode set for the domain. If a character is included in multiple sets specified within the fold option, the first matching set definition has priority over all others. In order to avoid problems it is recommended to use disjoint sets. As an alternative to a Unicode set the following keyword can be supplied: _dehyphenation The folding will be applied to hyphen characters which have been found within hyphenated words at line breaks. These characters will be flagged in the attributes member returned by TET_get_char_info( ) and the @dehyphenation attribute in TETML. The second element in each list contains the target character or action for the folding. It is specified with one of the following variants: (Unichar) Replace all characters in the domain with the specified Unicode character. remove All characters in the domain will be removed. preserve The characters in the domain will not be modified. unknownchar Replace all characters in the domain with the character specified in the unknownchar option. (List of option lists) A list of option lists where each option list describes a glyph mapping method for one or more font/encoding combinations which cannot reliably be mapped with standard methods. The mappings will be used in least-recently-set order. If the last option list contains the font name wildcard »*«, preceding mappings will no longer be used. Each rule consists of an option list according to Table 10.9. All glyph mappings which match a particular font name will be applied to this font. (default: predefined internal glyph rules will be applied). Note that glyph mapping rules can also be specified as an external resource in the UPR file (see Section 5.2, »Resource Configuration and File Searching«, page 61). (Unichar; Only for granularity=page) Character to be inserted between lines 2 . Default: U+000A (Keyword) Normalize the text output to one of the Unicode normalization forms (default: none): none Do not apply any normalization. nfc Normalization Form C (NFC): canonical decomposition followed by canonical composition nfd Normalization Form D (NFD): canonical decomposition nfkc Normalization Form KC (NFKC): compatibility decomposition followed by canonical composition nfkd Normalization Form KD (NFKD): compatibility decomposition Since the Unicode normalization forms involve canonical and compatibility decompositions, combinations of the options decompose and normalize must be constructed carefully. Setting the normalize option to a value different from none sets the decomposition default to decompose=none. The normalize option is processed after the decompose option. (Boolean; Only for TET_open_document( )) If true, TET will load the complete file into memory and process it from there. This can result in a tremendous performance gain on some systems (especially MVS) at the expense of memory usage. If false, individual parts of the document will be read from disk as needed. Default: false 10.7 Document Functions 163
Page 1 and 2:
ABC Text Extraction Toolkit (TET) V
Page 3 and 4:
Contents 0 First Steps with TET 7 0
Page 5:
8.6 Restrictions and Caveats 121 9
Page 8 and 9:
0.2 Applying the TET License Key Us
Page 10 and 11:
Setting the license key with a TET
Page 12 and 13:
CJK support. TET includes full supp
Page 14 and 15:
The TET Plugin is a free extension
Page 16 and 17:
new connector for the TIKA toolkit
Page 18 and 19:
Table 2.1 TET command-line options
Page 20 and 21:
2.2 Constructing TET Command Lines
Page 22 and 23:
Extract images from file.pdf in a r
Page 24 and 25:
3.2 C Binding TET is written in C w
Page 26 and 27:
3.3 C++ Binding Note For applicatio
Page 28 and 29:
3.4 COM Binding Installing the TET
Page 30 and 31:
The following method of the String
Page 32 and 33:
3.7 Objective-C Binding Although th
Page 34 and 35:
3.8 Perl Binding The TET wrapper fo
Page 36 and 37:
} catch (TETException $e) { print "
Page 38 and 39:
3.11 REALbasic Binding Installing t
Page 40 and 41:
oot :to => "home#demo" > Edit app/c
Page 42 and 43:
tion occurs, the job log shows the
Page 44 and 45:
Acrobat provides only garbage when
Page 46 and 47:
BUILD SUCCESSFUL Total time: 2 seco
Page 48 and 49:
4.3 TET Connector for the Solr Sear
Page 50 and 51:
SQL> GRANT EXECUTE ON CTX_DOC TO HR
Page 52 and 53:
4.5 TET PDF IFilter for Microsoft P
Page 54 and 55:
4.6 TET Connector for the Apache TI
Page 56 and 57:
4.7 TET Connector for MediaWiki Med
Page 59 and 60:
5 Configuration 5.1 Extracting Cont
Page 61 and 62:
5.2 Resource Configuration and File
Page 63 and 64:
product manually, make sure to use
Page 65 and 66:
5.3 Recommendations for common Scen
Page 67 and 68:
Also to ensure text fidelity you ma
Page 69 and 70:
6 Text Extraction 6.1 PDF Document
Page 71 and 72:
How to display with Acrobat X: Tool
Page 73 and 74:
6.2 Page and Text Geometry Default
Page 75 and 76:
width (x, y) beta fontsize baseline
Page 77 and 78:
* Query ascender and descender valu
Page 79 and 80:
6.3 Chinese, Japanese, and Korean T
Page 81 and 82:
Table 6.1 CJK compatibility decompo
Page 83 and 84:
Since the PDF document may map pres
Page 85 and 86:
Separator characters are inserted b
Page 87 and 88:
this situation and recombines both
Page 89 and 90:
Table 6.4 Document styles docstyle=
Page 91 and 92:
7 Advanced Unicode Handling 7.1 Imp
Page 93 and 94:
Composite characters and sequences.
Page 95 and 96:
7.2.2 Filters for Granularity Word
Page 97 and 98:
7.3 Unicode Postprocessing TET offe
Page 99 and 100:
Default foldings. Except for granul
Page 101 and 102:
Compatibility decomposition. Charac
Page 103 and 104:
In contrast, the following option l
Page 105 and 106:
Table 7.7 Unicode normalization for
Page 107 and 108:
7.5 Unicode Mapping for Glyphs Whil
Page 109 and 110:
Fig. 7.2 Sample font reports create
Page 111 and 112: glyphmapping {{fontname=Warnock* to
Page 113 and 114: 8 Image Extraction 8.1 Image Extrac
Page 115 and 116: 8.2 Image Merging and Filtering Ima
Page 117 and 118: 8.3 Placed Images and Image Resourc
Page 119 and 120: 8.5 Geometry of Placed Images Using
Page 121: 8.6 Restrictions and Caveats Image
Page 124 and 125: Various elements and attributes in
Page 126 and 127: c h e n 126 Chapter 9: TET Markup
Page 128 and 129: tet --tetml wordplus file.pdf With
Page 130 and 131: Object ’objects[49]/Subtype’ do
Page 132 and 133: Table 9.3 TETML elements and attrib
Page 134 and 135: 9.4 Transforming TETML with XSLT Ve
Page 136 and 137: document containing the xml process
Page 138 and 139: [TheSansBold-Plain/13.98] 1 [TheSan
Page 141 and 142: 10 TET Library API Reference 10.1 O
Page 143 and 144: List containing one option list wit
Page 145 and 146: Unicode sets. Unicode sets and can
Page 147 and 148: 10.4 Geometric Types Rectangle. A r
Page 149 and 150: Table 10.2 Global options for TET_s
Page 151 and 152: 10.6.2 Setup C TET *TET_new(void) C
Page 153 and 154: C++ int delete_pvf(wstring filename
Page 155 and 156: 10.6.4 Unicode Conversion Function
Page 157 and 158: 10.6.5 Exception Handling C++ wstri
Page 159 and 160: 10.6.6 Logging The logging feature
Page 161: 10.7 Document Functions C++ int ope
Page 165 and 166: Table 10.8 Document options for TET
Page 167 and 168: Table 10.9 Suboptions for the glyph
Page 169 and 170: 10.8 Page Functions C++ int open_pa
Page 171 and 172: Table 10.10 Page options for TET_op
Page 173 and 174: Table 10.11 Suboptions for the cont
Page 175 and 176: Table 10.12 Suboptions for the layo
Page 177 and 178: 10.9 Text and Metrics Retrieval Fun
Page 179 and 180: Bindings C and C++ language binding
Page 181 and 182: 10.10 Image Retrieval Functions C++
Page 183 and 184: C++ int write_image_file(int doc, i
Page 185 and 186: 10.11 TET Markup Language (TETML) F
Page 187 and 188: Java and .NET language bindings: th
Page 189 and 190: estricted pCOS mode if nocopy=false
Page 191: 10.12 pCOS Functions 191
Page 194 and 195: Image Retrieval Functions Function
Page 197 and 198: Index A annotations 71 API referenc
Page 199 and 200: TET command-line tool 17 TET connec
show all

PDFlib Text Extraction Toolkit (TET) Manual

Create successful ePaper yourself

Delete template?

Save as template?