PDFlib 8 Windows COM/.NET Tutorial

More documents

Recommendations

Info

In addition to the internal table, the fullwidth characters U+FF01 to U+FF5E will be replaced with the corresponding ISO 8859-1 characters (i.e. U+0021 to U+007E) if the fullwidth variants are not available in the font. > Decompose Unicode ligatures into their constituent glyphs (e.g. replace U+FB00 Latin small ligature ff with the sequence U+0066 f, U+0066 f). > Select glyphs with the same Unicode semantics according to their glyph name. In particular, all glyph name suffixes separated with a period will be removed if the corresponding glyph is not available (e.g. replace A.swash with A; replace g.alt with g). If none of these methods delivers a glyph for the Unicode value, the character specified in the replacementchar option will be used. If the corresponding glyph itself is not available in the font (or the replacementchar option was not specified), U+00A0 (NO-BREAK SPACE) and U+0020 (SPACE) will be tried. If these are still unavailable, glyph ID 0 (the missing glyph symbol) will be used. For PDF/A-1, PDF/X-4 and PDF/X-5 input codes which map to glyph ID 0 will be skipped. Cookbook A full code sample can be found in the Cookbook topic fonts/glyph_replacement. 5.3.3 Transforming Glyph IDs The determined glyph IDs are not yet final since several transformations may have to be applied before final output can be created. The details of these transformations depend on the font and several options. The steps below will be performed for all encodings except non-Unicode CMaps with keepnative=true. Vertical glyphs. For fonts in vertical writing mode some glyphs may be replaced by their vertical counterparts. This substitution requires a vert OpenType layout feature table in the font. OpenType layout features. OpenType features can create ligatures, swash characters, small caps, and many other typographic variations by replacing one or more glyph IDs with other values. OpenType features are discussed in Section 6.3, »OpenType Layout Features«, page 158. OpenType layout features are relevant only for suitable fonts (see »Requirements for OpenType layout features«, page 160), and are applied according to the features option. Complex script shaping. Shaping reorders the text and determines the appropriate variant glyph according to the position of a character (e.g. initial, middle, final, or isolated form of Arabic characters). Shaping is discussed in Section 6.4, »Complex Script Output«, page 164. It is relevant only for suitable fonts (see »Requirements for shaping«, page 166, and is applied according to the shaping option. 126 Chapter 5: Font Handling (Edition for COM, .NET, and REALbasic)
5.4 Loading Fonts 5.4.1 Selecting an Encoding for Text Fonts Fonts can be loaded explicitly with the load_font( ) function or implicitly by supplying the fontname and encoding options to certain functions such as add/create_textflow( ) or fill_textblock( ). Regardless of the method used for loading a font, a suitable encoding must be specified. The encoding determines > in which text formats PDFlib expects the supplied text; > which glyphs in a font can be used; > how text on the page and the glyph data in the font will be stored in the PDF output document. PDFlib’s text handling is based on the Unicode standard 1 , almost identical to ISO 10646. Since most modern development environments support the Unicode standard our goal is to make it as easy as possible to use Unicode strings for creating PDF output. However, developers who don’t work with Unicode are not required to switch their application to Unicode since legacy encodings can be used as well. The choice of encoding depends on the font, the available text data, and some programming aspects. In the remainder of this section we will provide an overview of the different classes of encodings as an aid for selecting a suitable encoding. Unicode encoding. With encoding=unicode you can pass Unicode strings to PDFlib. This encoding is supported for all font formats. Depending on the language binding in use, the Unicode string data type provided by the programming language (e.g. Java) can be used, or byte arrays containing Unicode in one of the UTF-8, UTF-16, or UTF-32 formats with little- or big-endian byte ordering (e.g. C). With encoding=unicode all glyphs in a font can be addressed; complex script shaping and OpenType layout features are supported. PDFlib checks whether the font contains a glyph for a requested Unicode value. If no glyph is available, a substitute glyph can be pulled from the same or another font (see Section 5.4.6, »Fallback Fonts«, page 139). Some font types in PDF (Type 1, Type 3, and OpenType fonts based on glyph names) support only single-byte text. However, PDFlib takes care of this situation to make sure that more than 255 different characters can be used even for these font types. The disadvantage of encoding=unicode is that text in traditional single- or multi-byte encodings (except ISO 8859-1) cannot be used. Single-byte encodings. 8-bit encodings (also called single-byte encodings) map each byte in a text string to a single character, and are thus limited to 255 different characters at a time (the value 0 is not available). This type of encoding is supported for all font formats. PDFlib checks whether the font contains glyphs which match the selected encoding. If a minimum number of usable glyphs is not reached, PDFlib will log a warning message. If no usable glyph at all for the selected encoding is available in the font, font loading will fail with the message font doesn’t support encoding. PDFlib checks whether the font contains a glyph for a requested input value. If no glyph is available, a substitute glyph can be pulled from the same or another font (see Section 5.4.6, »Fallback Fonts«, page 139). 1. See www.unicode.org 5.4 Loading Fonts 127
Page 1 and 2:
ABC PDFlib, PDFlib+PDI, PPS A libra
Page 3 and 4:
Contents 0 Applying the PDFlib Lice
Page 5 and 6:
5.2 Unicode Characters and Glyphs 1
Page 7 and 8:
8.4 Matchboxes 243 8.4.1 Decorating
Page 9 and 10:
0 Applying the PDFlib License Key R
Page 11 and 12:
Licensing options. Different licens
Page 13 and 14:
1 Introduction 1.1 Roadmap to Docum
Page 15 and 16:
1.2 PDFlib Programming What is PDFl
Page 17 and 18:
1.3 What’s new in PDFlib/PDFlib+P
Page 19 and 20:
1.3.3 PDFlib Block Plugin and PDFli
Page 21 and 22:
1.4 Features in PDFlib Table 1.1 li
Page 23 and 24:
Table 1.1 Feature list for PDFlib t
Page 25 and 26:
1.6 Additional Features in PPS Tabl
Page 27 and 28:
2 PDFlib Language Bindings Note It
Page 29 and 30:
2.3 COM Binding COM (Component Obje
Page 31 and 32:
Supply your license key at runtime
Page 33 and 34:
eference calls for an int type argu
Page 35 and 36:
2.5 C++ Binding (This section is on
Page 37 and 38:
2.7 .NET Binding Note Detailed info
Page 39 and 40:
2.8 Objective-C Binding (This secti
Page 41 and 42:
2.10 PHP Binding (This section is o
Page 43 and 44:
2.12 REALbasic Binding Installing t
Page 45 and 46:
2.14 Ruby Binding (This section is
Page 47 and 48:
3 Creating PDF Documents 3.1 Genera
Page 49 and 50:
Enable warning logging in the devel
Page 51 and 52:
Table 3.1 Resource categories suppo
Page 53 and 54:
myencoding=myencoding.enc . ICCProf
Page 55 and 56:
2 GB file size limit: The PDF/A-1 s
Page 57 and 58: Visualizing coordinates. In order t
Page 59 and 60: Table 3.2 Minimum and maximum page
Page 61 and 62: Instead of creating a path object w
Page 63 and 64: Proxy for the target page. PDFlib c
Page 65 and 66: 3.3.2 Protecting Documents with PDF
Page 67 and 68: 3.4 Web-Optimized (Linearized) PDF
Page 69 and 70: Cookbook A full code sample can be
Page 71 and 72: HKS® colors. The HKS color system
Page 73 and 74: Use the file name determined in the
Page 75 and 76: 3.6 Interactive Elements Cookbook C
Page 81 and 82: 3.7 Georeferenced PDF Cookbook A fu
Page 83 and 84: Examples for projected coordinate s
Page 85 and 86: 4 Unicode and Legacy Encodings This
Page 87 and 88: 4.2 Single-Byte (8-Bit) Encodings 8
Page 89 and 90: exclam 33 0x0021 ... If no Unicode
Page 91 and 92: p.set_parameter("SearchPath", "/pat
Page 93 and 94: Objective-C > Python > REALbasic >
Page 95 and 96: If an escape sequence cannot be res
Page 97 and 98: Character references are not substi
Page 99 and 100: 5 Font Handling 5.1 Font Formats 5.
Page 101 and 102: SING fonts usually contain only a s
Page 103 and 104: 5.2 Unicode Characters and Glyphs 5
Page 105 and 106: complex script shaping and OpenType
Page 107: 5.3.2 Converting Unicode Values to
Page 111 and 112: Glyphid encoding. PDFlib supports e
Page 113 and 114: If you know the character code you
Page 115 and 116: TrueType and OpenType fonts. The fo
Page 117 and 118: .tte .ttf .otf .gai .afm .pfm .ttc
Page 119 and 120: The keywords are case-insensitive.
Page 121 and 122: Caveats. Note the following when wo
Page 123 and 124: Add Gaiji characters to a font. Thi
Page 125 and 126: Legal aspects of font embedding. It
Page 127 and 128: 5.6 Querying Font Information info_
Page 129 and 130: Query the font-specific name of a g
Page 131 and 132: 6 Text Output 6.1 Text Output Metho
Page 133 and 134: descender = p.info_font(font, "desc
Page 137 and 138: 6.3 OpenType Layout Features Cookbo
Page 139 and 140: Table 6.1 Supported OpenType featur
Page 141 and 142: will prevent them from being replac
Page 143 and 144: 6.4 Complex Script Output Cookbook
Page 145 and 146: Requirements for shaping. A font fo
Page 147 and 148: 6.4.3 Complex Script Shaping The sh
Page 149 and 150: You can use the writingdirx keyword
Page 151 and 152: 6.5 Chinese, Japanese, and Korean T
Page 153 and 154: The keepnative option is false by d
Page 155 and 156: The vert feature (vertical writing)
Page 157 and 158: 7 Importing Images and PDF Pages PD
Page 159 and 160:
String optlist13 = "OPI-1.3 { ALDIm
Page 161 and 162:
GIF images. PDFlib supports all GIF
Page 163 and 164:
channels which are identified by na
Page 165 and 166:
In order to colorize an image with
Page 167 and 168:
You can not re-use individual eleme
Page 169 and 170:
Encrypted PDF documents without the
Page 171 and 172:
Positioning an image in the box. We
Page 173 and 174:
Fig. 7.4 The rotate option Fig. 7.5
Page 175 and 176:
Fig. 7.8 Adjusting the page size. L
Page 177 and 178:
8 Text and Table Formatting 8.1 Pla
Page 179 and 180:
Generated output Option list for fi
Page 181 and 182:
To illustrate the size of the match
Page 183 and 184:
Long Distance Glider with sensation
Page 185 and 186:
8.2 Multi-Line Textflows In additio
Page 187 and 188:
normal text. Font, font size, and e
Page 189 and 190:
leftindent = 15 parindent = 20 lead
Page 191 and 192:
Explicitly setting options. Note th
Page 193 and 194:
leftindent = &indent parindent = -
Page 195 and 196:
To fold the famous rocket looper pr
Page 197 and 198:
8.2.8 Controlling the standard Line
Page 199 and 200:
Our paper planes are the ideal way
Page 201 and 202:
French text. As a result, the guill
Page 203 and 204:
String imageoptlist = "scale=2"; p.
Page 205 and 206:
8.3 Table Formatting The table form
Page 207 and 208:
tbl = p.add_table_cell(tbl, 1, 1, "
Page 209 and 210:
In addition, we want the baseline o
Page 211 and 212:
8.3.3 Table and Column Widths When
Page 213 and 214:
if (tbl == -1) throw new Exception(
Page 215 and 216:
esult = p.fit_table(tbl, llx, lly,
Page 217 and 218:
Figure 8.38 shows how the Textflow
Page 219 and 220:
Continue the table in the next fitb
Page 221 and 222:
To increase the box height to match
Page 223 and 224:
Fig. 8.43 Using the image matchbox
Page 225 and 226:
9 The pCOS Interface The pCOS (PDFl
Page 227 and 228:
10 PDF Versions and Standards 10.1
Page 229 and 230:
Table 10.1 PDFlib features which re
Page 231 and 232:
10.3 PDF/X for Print Production 10.
Page 233 and 234:
Table 10.2 Operations which must be
Page 235 and 236:
10.3.3 Output Intent and Standard O
Page 237 and 238:
Table 10.5 Compatible PDF/X input l
Page 239 and 240:
10.4.2 Generating PDF/A-conforming
Page 241 and 242:
Additional requirements and restric
Page 243 and 244:
While PDFlib can correct certain it
Page 245 and 246:
Table 10.13 Predefined XMP schemas
Page 247 and 248:
tree is created in multiple travers
Page 249 and 250:
All parts of a Textflow (all calls
Page 251 and 252:
* 1 create header */ p.set_text_pos
Page 253 and 254:
Acrobat’s Accessibility Checker.
Page 255 and 256:
11 PPS and the PDFlib Block Plugin
Page 257 and 258:
11.2 Overview of the Block Concept
Page 259 and 260:
Table 11.1 Comparison of PDF form f
Page 261 and 262:
Fig. 11.1 Visualization of Blocks I
Page 263 and 264:
Fig. 11.3 Grid preferences in Acrob
Page 265 and 266:
Note Do not confuse the default val
Page 267 and 268:
PDFlib Blocks choose PDFlib Blocks,
Page 269 and 270:
If you do not want to keep the conv
Page 271 and 272:
Fig. 11.4 Preview PDF for the conta
Page 273 and 274:
PDF/X-3:2002, PDF/X-3:2003 PDF/X-4,
Page 275 and 276:
Placing the imported page on top of
Page 277 and 278:
The third method, i.e. filling a PD
Page 279 and 280:
11.6.2 Rectangle Properties Rectang
Page 281 and 282:
Table 11.7 Text appearance properti
Page 283 and 284:
11.6.5 Text Formatting Properties T
Page 285 and 286:
Table 11.9 Text formatting properti
Page 287 and 288:
Table 11.11 Fitting properties for
Page 289 and 290:
11.6.7 Properties for default Conte
Page 291 and 292:
Querying custom properties. Custom
Page 293 and 294:
Data types for Block properties. Pr
Page 295 and 296:
endobj /Name /job_title /Subtype /T
Page 297 and 298:
A Revision History Date Changes Jun
Page 299 and 300:
Index A Acrobat plugin for creating
Page 301 and 302:
N name strings 108 in non-Unicode c
Page 304:
ABC PDFlib GmbH Franziska-Bilek-Weg
show all

PDFlib 8 Windows COM/.NET Tutorial

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?