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