1 /***************************************************************************/ 2 /* */ 3 /* ftoption.h */ 4 /* */ 5 /* User-selectable configuration macros (specification only). */ 6 /* */ 7 /* Copyright 1996-2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by */ 8 /* David Turner, Robert Wilhelm, and Werner Lemberg. */ 9 /* */ 10 /* This file is part of the FreeType project, and may only be used, */ 11 /* modified, and distributed under the terms of the FreeType project */ 12 /* license, LICENSE.TXT. By continuing to use, modify, or distribute */ 13 /* this file you indicate that you have read the license and */ 14 /* understand and accept it fully. */ 15 /* */ 16 /***************************************************************************/ 17 18 19 #ifndef __FTOPTION_H__ 20 #define __FTOPTION_H__ 21 22 23 #include <ft2build.h> 24 25 26 FT_BEGIN_HEADER 27 28 /*************************************************************************/ 29 /* */ 30 /* USER-SELECTABLE CONFIGURATION MACROS */ 31 /* */ 32 /* This file contains the default configuration macro definitions for */ 33 /* a standard build of the FreeType library. There are three ways to */ 34 /* use this file to build project-specific versions of the library: */ 35 /* */ 36 /* - You can modify this file by hand, but this is not recommended in */ 37 /* cases where you would like to build several versions of the */ 38 /* library from a single source directory. */ 39 /* */ 40 /* - You can put a copy of this file in your build directory, more */ 41 /* precisely in `$BUILD/freetype/config/ftoption.h', where `$BUILD' */ 42 /* is the name of a directory that is included _before_ the FreeType */ 43 /* include path during compilation. */ 44 /* */ 45 /* The default FreeType Makefiles and Jamfiles use the build */ 46 /* directory `builds/<system>' by default, but you can easily change */ 47 /* that for your own projects. */ 48 /* */ 49 /* - Copy the file <ft2build.h> to `$BUILD/ft2build.h' and modify it */ 50 /* slightly to pre-define the macro FT_CONFIG_OPTIONS_H used to */ 51 /* locate this file during the build. For example, */ 52 /* */ 53 /* #define FT_CONFIG_OPTIONS_H <myftoptions.h> */ 54 /* #include <freetype/config/ftheader.h> */ 55 /* */ 56 /* will use `$BUILD/myftoptions.h' instead of this file for macro */ 57 /* definitions. */ 58 /* */ 59 /* Note also that you can similarly pre-define the macro */ 60 /* FT_CONFIG_MODULES_H used to locate the file listing of the modules */ 61 /* that are statically linked to the library at compile time. By */ 62 /* default, this file is <freetype/config/ftmodule.h>. */ 63 /* */ 64 /* We highly recommend using the third method whenever possible. */ 65 /* */ 66 /*************************************************************************/ 67 68 69 /*************************************************************************/ 70 /*************************************************************************/ 71 /**** ****/ 72 /**** G E N E R A L F R E E T Y P E 2 C O N F I G U R A T I O N ****/ 73 /**** ****/ 74 /*************************************************************************/ 75 /*************************************************************************/ 76 77 78 /*************************************************************************/ 79 /* */ 80 /* Uncomment the line below if you want to activate sub-pixel rendering */ 81 /* (a.k.a. LCD rendering, or ClearType) in this build of the library. */ 82 /* */ 83 /* Note that this feature is covered by several Microsoft patents */ 84 /* and should not be activated in any default build of the library. */ 85 /* */ 86 /* This macro has no impact on the FreeType API, only on its */ 87 /* _implementation_. For example, using FT_RENDER_MODE_LCD when calling */ 88 /* FT_Render_Glyph still generates a bitmap that is 3 times larger than */ 89 /* the original size; the difference will be that each triplet of */ 90 /* subpixels has R=G=B. */ 91 /* */ 92 /* This is done to allow FreeType clients to run unmodified, forcing */ 93 /* them to display normal gray-level anti-aliased glyphs. */ 94 /* */ 95 /* #define FT_CONFIG_OPTION_SUBPIXEL_RENDERING */ 96 97 98 /*************************************************************************/ 99 /* */ 100 /* Many compilers provide a non-ANSI 64-bit data type that can be used */ 101 /* by FreeType to speed up some computations. However, this will create */ 102 /* some problems when compiling the library in strict ANSI mode. */ 103 /* */ 104 /* For this reason, the use of 64-bit integers is normally disabled when */ 105 /* the __STDC__ macro is defined. You can however disable this by */ 106 /* defining the macro FT_CONFIG_OPTION_FORCE_INT64 here. */ 107 /* */ 108 /* For most compilers, this will only create compilation warnings when */ 109 /* building the library. */ 110 /* */ 111 /* ObNote: The compiler-specific 64-bit integers are detected in the */ 112 /* file `ftconfig.h' either statically or through the */ 113 /* `configure' script on supported platforms. */ 114 /* */ 115 #undef FT_CONFIG_OPTION_FORCE_INT64 116 117 118 /*************************************************************************/ 119 /* */ 120 /* If this macro is defined, do not try to use an assembler version of */ 121 /* performance-critical functions (e.g. FT_MulFix). You should only do */ 122 /* that to verify that the assembler function works properly, or to */ 123 /* execute benchmark tests of the various implementations. */ 124 /* #define FT_CONFIG_OPTION_NO_ASSEMBLER */ 125 126 127 /*************************************************************************/ 128 /* */ 129 /* If this macro is defined, try to use an inlined assembler version of */ 130 /* the `FT_MulFix' function, which is a `hotspot' when loading and */ 131 /* hinting glyphs, and which should be executed as fast as possible. */ 132 /* */ 133 /* Note that if your compiler or CPU is not supported, this will default */ 134 /* to the standard and portable implementation found in `ftcalc.c'. */ 135 /* */ 136 #define FT_CONFIG_OPTION_INLINE_MULFIX 137 138 139 /*************************************************************************/ 140 /* */ 141 /* LZW-compressed file support. */ 142 /* */ 143 /* FreeType now handles font files that have been compressed with the */ 144 /* `compress' program. This is mostly used to parse many of the PCF */ 145 /* files that come with various X11 distributions. The implementation */ 146 /* uses NetBSD's `zopen' to partially uncompress the file on the fly */ 147 /* (see src/lzw/ftgzip.c). */ 148 /* */ 149 /* Define this macro if you want to enable this `feature'. */ 150 /* */ 151 #define FT_CONFIG_OPTION_USE_LZW 152 153 154 /*************************************************************************/ 155 /* */ 156 /* Gzip-compressed file support. */ 157 /* */ 158 /* FreeType now handles font files that have been compressed with the */ 159 /* `gzip' program. This is mostly used to parse many of the PCF files */ 160 /* that come with XFree86. The implementation uses `zlib' to */ 161 /* partially uncompress the file on the fly (see src/gzip/ftgzip.c). */ 162 /* */ 163 /* Define this macro if you want to enable this `feature'. See also */ 164 /* the macro FT_CONFIG_OPTION_SYSTEM_ZLIB below. */ 165 /* */ 166 #define FT_CONFIG_OPTION_USE_ZLIB 167 168 169 /*************************************************************************/ 170 /* */ 171 /* ZLib library selection */ 172 /* */ 173 /* This macro is only used when FT_CONFIG_OPTION_USE_ZLIB is defined. */ 174 /* It allows FreeType's `ftgzip' component to link to the system's */ 175 /* installation of the ZLib library. This is useful on systems like */ 176 /* Unix or VMS where it generally is already available. */ 177 /* */ 178 /* If you let it undefined, the component will use its own copy */ 179 /* of the zlib sources instead. These have been modified to be */ 180 /* included directly within the component and *not* export external */ 181 /* function names. This allows you to link any program with FreeType */ 182 /* _and_ ZLib without linking conflicts. */ 183 /* */ 184 /* Do not #undef this macro here since the build system might define */ 185 /* it for certain configurations only. */ 186 /* */ 187 /* #define FT_CONFIG_OPTION_SYSTEM_ZLIB */ 188 189 190 /*************************************************************************/ 191 /* */ 192 /* DLL export compilation */ 193 /* */ 194 /* When compiling FreeType as a DLL, some systems/compilers need a */ 195 /* special keyword in front OR after the return type of function */ 196 /* declarations. */ 197 /* */ 198 /* Two macros are used within the FreeType source code to define */ 199 /* exported library functions: FT_EXPORT and FT_EXPORT_DEF. */ 200 /* */ 201 /* FT_EXPORT( return_type ) */ 202 /* */ 203 /* is used in a function declaration, as in */ 204 /* */ 205 /* FT_EXPORT( FT_Error ) */ 206 /* FT_Init_FreeType( FT_Library* alibrary ); */ 207 /* */ 208 /* */ 209 /* FT_EXPORT_DEF( return_type ) */ 210 /* */ 211 /* is used in a function definition, as in */ 212 /* */ 213 /* FT_EXPORT_DEF( FT_Error ) */ 214 /* FT_Init_FreeType( FT_Library* alibrary ) */ 215 /* { */ 216 /* ... some code ... */ 217 /* return FT_Err_Ok; */ 218 /* } */ 219 /* */ 220 /* You can provide your own implementation of FT_EXPORT and */ 221 /* FT_EXPORT_DEF here if you want. If you leave them undefined, they */ 222 /* will be later automatically defined as `extern return_type' to */ 223 /* allow normal compilation. */ 224 /* */ 225 /* Do not #undef these macros here since the build system might define */ 226 /* them for certain configurations only. */ 227 /* */ 228 /* #define FT_EXPORT(x) extern x */ 229 /* #define FT_EXPORT_DEF(x) x */ 230 231 232 /*************************************************************************/ 233 /* */ 234 /* Glyph Postscript Names handling */ 235 /* */ 236 /* By default, FreeType 2 is compiled with the `psnames' module. This */ 237 /* module is in charge of converting a glyph name string into a */ 238 /* Unicode value, or return a Macintosh standard glyph name for the */ 239 /* use with the TrueType `post' table. */ 240 /* */ 241 /* Undefine this macro if you do not want `psnames' compiled in your */ 242 /* build of FreeType. This has the following effects: */ 243 /* */ 244 /* - The TrueType driver will provide its own set of glyph names, */ 245 /* if you build it to support postscript names in the TrueType */ 246 /* `post' table. */ 247 /* */ 248 /* - The Type 1 driver will not be able to synthesize a Unicode */ 249 /* charmap out of the glyphs found in the fonts. */ 250 /* */ 251 /* You would normally undefine this configuration macro when building */ 252 /* a version of FreeType that doesn't contain a Type 1 or CFF driver. */ 253 /* */ 254 #define FT_CONFIG_OPTION_POSTSCRIPT_NAMES 255 256 257 /*************************************************************************/ 258 /* */ 259 /* Postscript Names to Unicode Values support */ 260 /* */ 261 /* By default, FreeType 2 is built with the `PSNames' module compiled */ 262 /* in. Among other things, the module is used to convert a glyph name */ 263 /* into a Unicode value. This is especially useful in order to */ 264 /* synthesize on the fly a Unicode charmap from the CFF/Type 1 driver */ 265 /* through a big table named the `Adobe Glyph List' (AGL). */ 266 /* */ 267 /* Undefine this macro if you do not want the Adobe Glyph List */ 268 /* compiled in your `PSNames' module. The Type 1 driver will not be */ 269 /* able to synthesize a Unicode charmap out of the glyphs found in the */ 270 /* fonts. */ 271 /* */ 272 #define FT_CONFIG_OPTION_ADOBE_GLYPH_LIST 273 274 275 /*************************************************************************/ 276 /* */ 277 /* Support for Mac fonts */ 278 /* */ 279 /* Define this macro if you want support for outline fonts in Mac */ 280 /* format (mac dfont, mac resource, macbinary containing a mac */ 281 /* resource) on non-Mac platforms. */ 282 /* */ 283 /* Note that the `FOND' resource isn't checked. */ 284 /* */ 285 #define FT_CONFIG_OPTION_MAC_FONTS 286 287 288 /*************************************************************************/ 289 /* */ 290 /* Guessing methods to access embedded resource forks */ 291 /* */ 292 /* Enable extra Mac fonts support on non-Mac platforms (e.g. */ 293 /* GNU/Linux). */ 294 /* */ 295 /* Resource forks which include fonts data are stored sometimes in */ 296 /* locations which users or developers don't expected. In some cases, */ 297 /* resource forks start with some offset from the head of a file. In */ 298 /* other cases, the actual resource fork is stored in file different */ 299 /* from what the user specifies. If this option is activated, */ 300 /* FreeType tries to guess whether such offsets or different file */ 301 /* names must be used. */ 302 /* */ 303 /* Note that normal, direct access of resource forks is controlled via */ 304 /* the FT_CONFIG_OPTION_MAC_FONTS option. */ 305 /* */ 306 #ifdef FT_CONFIG_OPTION_MAC_FONTS 307 #define FT_CONFIG_OPTION_GUESSING_EMBEDDED_RFORK 308 #endif 309 310 311 /*************************************************************************/ 312 /* */ 313 /* Allow the use of FT_Incremental_Interface to load typefaces that */ 314 /* contain no glyph data, but supply it via a callback function. */ 315 /* This allows FreeType to be used with the PostScript language, using */ 316 /* the GhostScript interpreter. */ 317 /* */ 318 /* #define FT_CONFIG_OPTION_INCREMENTAL */ 319 320 321 /*************************************************************************/ 322 /* */ 323 /* The size in bytes of the render pool used by the scan-line converter */ 324 /* to do all of its work. */ 325 /* */ 326 /* This must be greater than 4KByte if you use FreeType to rasterize */ 327 /* glyphs; otherwise, you may set it to zero to avoid unnecessary */ 328 /* allocation of the render pool. */ 329 /* */ 330 #define FT_RENDER_POOL_SIZE 16384L 331 332 333 /*************************************************************************/ 334 /* */ 335 /* FT_MAX_MODULES */ 336 /* */ 337 /* The maximum number of modules that can be registered in a single */ 338 /* FreeType library object. 32 is the default. */ 339 /* */ 340 #define FT_MAX_MODULES 32 341 342 343 /*************************************************************************/ 344 /* */ 345 /* Debug level */ 346 /* */ 347 /* FreeType can be compiled in debug or trace mode. In debug mode, */ 348 /* errors are reported through the `ftdebug' component. In trace */ 349 /* mode, additional messages are sent to the standard output during */ 350 /* execution. */ 351 /* */ 352 /* Define FT_DEBUG_LEVEL_ERROR to build the library in debug mode. */ 353 /* Define FT_DEBUG_LEVEL_TRACE to build it in trace mode. */ 354 /* */ 355 /* Don't define any of these macros to compile in `release' mode! */ 356 /* */ 357 /* Do not #undef these macros here since the build system might define */ 358 /* them for certain configurations only. */ 359 /* */ 360 /* #define FT_DEBUG_LEVEL_ERROR */ 361 /* #define FT_DEBUG_LEVEL_TRACE */ 362 363 364 /*************************************************************************/ 365 /* */ 366 /* Memory Debugging */ 367 /* */ 368 /* FreeType now comes with an integrated memory debugger that is */ 369 /* capable of detecting simple errors like memory leaks or double */ 370 /* deletes. To compile it within your build of the library, you */ 371 /* should define FT_DEBUG_MEMORY here. */ 372 /* */ 373 /* Note that the memory debugger is only activated at runtime when */ 374 /* when the _environment_ variable `FT2_DEBUG_MEMORY' is defined also! */ 375 /* */ 376 /* Do not #undef this macro here since the build system might define */ 377 /* it for certain configurations only. */ 378 /* */ 379 /* #define FT_DEBUG_MEMORY */ 380 381 382 /*************************************************************************/ 383 /* */ 384 /* Module errors */ 385 /* */ 386 /* If this macro is set (which is _not_ the default), the higher byte */ 387 /* of an error code gives the module in which the error has occurred, */ 388 /* while the lower byte is the real error code. */ 389 /* */ 390 /* Setting this macro makes sense for debugging purposes only, since */ 391 /* it would break source compatibility of certain programs that use */ 392 /* FreeType 2. */ 393 /* */ 394 /* More details can be found in the files ftmoderr.h and fterrors.h. */ 395 /* */ 396 #undef FT_CONFIG_OPTION_USE_MODULE_ERRORS 397 398 399 400 /*************************************************************************/ 401 /*************************************************************************/ 402 /**** ****/ 403 /**** S F N T D R I V E R C O N F I G U R A T I O N ****/ 404 /**** ****/ 405 /*************************************************************************/ 406 /*************************************************************************/ 407 408 409 /*************************************************************************/ 410 /* */ 411 /* Define TT_CONFIG_OPTION_EMBEDDED_BITMAPS if you want to support */ 412 /* embedded bitmaps in all formats using the SFNT module (namely */ 413 /* TrueType & OpenType). */ 414 /* */ 415 #define TT_CONFIG_OPTION_EMBEDDED_BITMAPS 416 417 418 /*************************************************************************/ 419 /* */ 420 /* Define TT_CONFIG_OPTION_POSTSCRIPT_NAMES if you want to be able to */ 421 /* load and enumerate the glyph Postscript names in a TrueType or */ 422 /* OpenType file. */ 423 /* */ 424 /* Note that when you do not compile the `PSNames' module by undefining */ 425 /* the above FT_CONFIG_OPTION_POSTSCRIPT_NAMES, the `sfnt' module will */ 426 /* contain additional code used to read the PS Names table from a font. */ 427 /* */ 428 /* (By default, the module uses `PSNames' to extract glyph names.) */ 429 /* */ 430 #define TT_CONFIG_OPTION_POSTSCRIPT_NAMES 431 432 433 /*************************************************************************/ 434 /* */ 435 /* Define TT_CONFIG_OPTION_SFNT_NAMES if your applications need to */ 436 /* access the internal name table in a SFNT-based format like TrueType */ 437 /* or OpenType. The name table contains various strings used to */ 438 /* describe the font, like family name, copyright, version, etc. It */ 439 /* does not contain any glyph name though. */ 440 /* */ 441 /* Accessing SFNT names is done through the functions declared in */ 442 /* `freetype/ftnames.h'. */ 443 /* */ 444 #define TT_CONFIG_OPTION_SFNT_NAMES 445 446 447 /*************************************************************************/ 448 /* */ 449 /* TrueType CMap support */ 450 /* */ 451 /* Here you can fine-tune which TrueType CMap table format shall be */ 452 /* supported. */ 453 #define TT_CONFIG_CMAP_FORMAT_0 454 #define TT_CONFIG_CMAP_FORMAT_2 455 #define TT_CONFIG_CMAP_FORMAT_4 456 #define TT_CONFIG_CMAP_FORMAT_6 457 #define TT_CONFIG_CMAP_FORMAT_8 458 #define TT_CONFIG_CMAP_FORMAT_10 459 #define TT_CONFIG_CMAP_FORMAT_12 460 #define TT_CONFIG_CMAP_FORMAT_14 461 462 463 /*************************************************************************/ 464 /*************************************************************************/ 465 /**** ****/ 466 /**** T R U E T Y P E D R I V E R C O N F I G U R A T I O N ****/ 467 /**** ****/ 468 /*************************************************************************/ 469 /*************************************************************************/ 470 471 /*************************************************************************/ 472 /* */ 473 /* Define TT_CONFIG_OPTION_BYTECODE_INTERPRETER if you want to compile */ 474 /* a bytecode interpreter in the TrueType driver. Note that there are */ 475 /* important patent issues related to the use of the interpreter. */ 476 /* */ 477 /* By undefining this, you will only compile the code necessary to load */ 478 /* TrueType glyphs without hinting. */ 479 /* */ 480 /* Do not #undef this macro here, since the build system might */ 481 /* define it for certain configurations only. */ 482 /* */ 483 /* #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER */ 484 485 486 /*************************************************************************/ 487 /* */ 488 /* If you define TT_CONFIG_OPTION_UNPATENTED_HINTING, a special version */ 489 /* of the TrueType bytecode interpreter is used that doesn't implement */ 490 /* any of the patented opcodes and algorithms. Note that the */ 491 /* TT_CONFIG_OPTION_UNPATENTED_HINTING macro is *ignored* if you define */ 492 /* TT_CONFIG_OPTION_BYTECODE_INTERPRETER; in other words, either define */ 493 /* TT_CONFIG_OPTION_BYTECODE_INTERPRETER or */ 494 /* TT_CONFIG_OPTION_UNPATENTED_HINTING but not both at the same time. */ 495 /* */ 496 /* This macro is only useful for a small number of font files (mostly */ 497 /* for Asian scripts) that require bytecode interpretation to properly */ 498 /* load glyphs. For all other fonts, this produces unpleasant results, */ 499 /* thus the unpatented interpreter is never used to load glyphs from */ 500 /* TrueType fonts unless one of the following two options is used. */ 501 /* */ 502 /* - The unpatented interpreter is explicitly activated by the user */ 503 /* through the FT_PARAM_TAG_UNPATENTED_HINTING parameter tag */ 504 /* when opening the FT_Face. */ 505 /* */ 506 /* - FreeType detects that the FT_Face corresponds to one of the */ 507 /* `trick' fonts (e.g., `Mingliu') it knows about. The font engine */ 508 /* contains a hard-coded list of font names and other matching */ 509 /* parameters (see function `tt_face_init' in file */ 510 /* `src/truetype/ttobjs.c'). */ 511 /* */ 512 /* Here a sample code snippet for using FT_PARAM_TAG_UNPATENTED_HINTING. */ 513 /* */ 514 /* { */ 515 /* FT_Parameter parameter; */ 516 /* FT_Open_Args open_args; */ 517 /* */ 518 /* */ 519 /* parameter.tag = FT_PARAM_TAG_UNPATENTED_HINTING; */ 520 /* */ 521 /* open_args.flags = FT_OPEN_PATHNAME | FT_OPEN_PARAMS; */ 522 /* open_args.pathname = my_font_pathname; */ 523 /* open_args.num_params = 1; */ 524 /* open_args.params = ¶meter; */ 525 /* */ 526 /* error = FT_Open_Face( library, &open_args, index, &face ); */ 527 /* ... */ 528 /* } */ 529 /* */ 530 #define TT_CONFIG_OPTION_UNPATENTED_HINTING 531 532 533 /*************************************************************************/ 534 /* */ 535 /* Define TT_CONFIG_OPTION_INTERPRETER_SWITCH to compile the TrueType */ 536 /* bytecode interpreter with a huge switch statement, rather than a call */ 537 /* table. This results in smaller and faster code for a number of */ 538 /* architectures. */ 539 /* */ 540 /* Note however that on some compiler/processor combinations, undefining */ 541 /* this macro will generate faster, though larger, code. */ 542 /* */ 543 #define TT_CONFIG_OPTION_INTERPRETER_SWITCH 544 545 546 /*************************************************************************/ 547 /* */ 548 /* Define TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED to compile the */ 549 /* TrueType glyph loader to use Apple's definition of how to handle */ 550 /* component offsets in composite glyphs. */ 551 /* */ 552 /* Apple and MS disagree on the default behavior of component offsets */ 553 /* in composites. Apple says that they should be scaled by the scaling */ 554 /* factors in the transformation matrix (roughly, it's more complex) */ 555 /* while MS says they should not. OpenType defines two bits in the */ 556 /* composite flags array which can be used to disambiguate, but old */ 557 /* fonts will not have them. */ 558 /* */ 559 /* http://partners.adobe.com/asn/developer/opentype/glyf.html */ 560 /* http://fonts.apple.com/TTRefMan/RM06/Chap6glyf.html */ 561 /* */ 562 #undef TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED 563 564 565 /*************************************************************************/ 566 /* */ 567 /* Define TT_CONFIG_OPTION_GX_VAR_SUPPORT if you want to include */ 568 /* support for Apple's distortable font technology (fvar, gvar, cvar, */ 569 /* and avar tables). This has many similarities to Type 1 Multiple */ 570 /* Masters support. */ 571 /* */ 572 #define TT_CONFIG_OPTION_GX_VAR_SUPPORT 573 574 575 /*************************************************************************/ 576 /* */ 577 /* Define TT_CONFIG_OPTION_BDF if you want to include support for */ 578 /* an embedded `BDF ' table within SFNT-based bitmap formats. */ 579 /* */ 580 #define TT_CONFIG_OPTION_BDF 581 582 583 /*************************************************************************/ 584 /*************************************************************************/ 585 /**** ****/ 586 /**** T Y P E 1 D R I V E R C O N F I G U R A T I O N ****/ 587 /**** ****/ 588 /*************************************************************************/ 589 /*************************************************************************/ 590 591 592 /*************************************************************************/ 593 /* */ 594 /* T1_MAX_DICT_DEPTH is the maximal depth of nest dictionaries and */ 595 /* arrays in the Type 1 stream (see t1load.c). A minimum of 4 is */ 596 /* required. */ 597 /* */ 598 #define T1_MAX_DICT_DEPTH 5 599 600 601 /*************************************************************************/ 602 /* */ 603 /* T1_MAX_SUBRS_CALLS details the maximum number of nested sub-routine */ 604 /* calls during glyph loading. */ 605 /* */ 606 #define T1_MAX_SUBRS_CALLS 16 607 608 609 /*************************************************************************/ 610 /* */ 611 /* T1_MAX_CHARSTRING_OPERANDS is the charstring stack's capacity. A */ 612 /* minimum of 16 is required. */ 613 /* */ 614 /* The Chinese font MingTiEG-Medium (CNS 11643 character set) needs 256. */ 615 /* */ 616 #define T1_MAX_CHARSTRINGS_OPERANDS 256 617 618 619 /*************************************************************************/ 620 /* */ 621 /* Define this configuration macro if you want to prevent the */ 622 /* compilation of `t1afm', which is in charge of reading Type 1 AFM */ 623 /* files into an existing face. Note that if set, the T1 driver will be */ 624 /* unable to produce kerning distances. */ 625 /* */ 626 #undef T1_CONFIG_OPTION_NO_AFM 627 628 629 /*************************************************************************/ 630 /* */ 631 /* Define this configuration macro if you want to prevent the */ 632 /* compilation of the Multiple Masters font support in the Type 1 */ 633 /* driver. */ 634 /* */ 635 #undef T1_CONFIG_OPTION_NO_MM_SUPPORT 636 637 638 /*************************************************************************/ 639 /*************************************************************************/ 640 /**** ****/ 641 /**** A U T O F I T M O D U L E C O N F I G U R A T I O N ****/ 642 /**** ****/ 643 /*************************************************************************/ 644 /*************************************************************************/ 645 646 647 /*************************************************************************/ 648 /* */ 649 /* Compile autofit module with CJK (Chinese, Japanese, Korean) script */ 650 /* support. */ 651 /* */ 652 #define AF_CONFIG_OPTION_CJK 653 654 /*************************************************************************/ 655 /* */ 656 /* Compile autofit module with Indic script support. */ 657 /* */ 658 #define AF_CONFIG_OPTION_INDIC 659 660 /* */ 661 662 663 /* 664 * Define this variable if you want to keep the layout of internal 665 * structures that was used prior to FreeType 2.2. This also compiles in 666 * a few obsolete functions to avoid linking problems on typical Unix 667 * distributions. 668 * 669 * For embedded systems or building a new distribution from scratch, it 670 * is recommended to disable the macro since it reduces the library's code 671 * size and activates a few memory-saving optimizations as well. 672 */ 673 #define FT_CONFIG_OPTION_OLD_INTERNALS 674 675 676 /* 677 * This macro is defined if either unpatented or native TrueType 678 * hinting is requested by the definitions above. 679 */ 680 #ifdef TT_CONFIG_OPTION_BYTECODE_INTERPRETER 681 #define TT_USE_BYTECODE_INTERPRETER 682 #undef TT_CONFIG_OPTION_UNPATENTED_HINTING 683 #elif defined TT_CONFIG_OPTION_UNPATENTED_HINTING 684 #define TT_USE_BYTECODE_INTERPRETER 685 #endif 686 687 FT_END_HEADER 688 689 690 #endif /* __FTOPTION_H__ */ 691 692 693 /* END */ 694