]> git.r.bdr.sh - rbdr/super-polarity/blob
93e9eb565b3717be49d6ff0c068bb25d1fd7c0a0
[rbdr/super-polarity] /
1 /***************************************************************************/
2 /* */
3 /* ftoption.h */
4 /* */
5 /* User-selectable configuration macros (specification only). */
6 /* */
7 /* Copyright 1996-2013 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 wider than */
89 /* the original size in case this macro isn't defined; however, each */
90 /* triplet of 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 /* Bzip2-compressed file support. */
193 /* */
194 /* FreeType now handles font files that have been compressed with the */
195 /* `bzip2' program. This is mostly used to parse many of the PCF */
196 /* files that come with XFree86. The implementation uses `libbz2' to */
197 /* partially uncompress the file on the fly (see src/bzip2/ftbzip2.c). */
198 /* Contrary to gzip, bzip2 currently is not included and need to use */
199 /* the system available bzip2 implementation. */
200 /* */
201 /* Define this macro if you want to enable this `feature'. */
202 /* */
203 /* #define FT_CONFIG_OPTION_USE_BZIP2 */
204
205
206 /*************************************************************************/
207 /* */
208 /* Define to disable the use of file stream functions and types, FILE, */
209 /* fopen() etc. Enables the use of smaller system libraries on embedded */
210 /* systems that have multiple system libraries, some with or without */
211 /* file stream support, in the cases where file stream support is not */
212 /* necessary such as memory loading of font files. */
213 /* */
214 /* #define FT_CONFIG_OPTION_DISABLE_STREAM_SUPPORT */
215
216
217 /*************************************************************************/
218 /* */
219 /* DLL export compilation */
220 /* */
221 /* When compiling FreeType as a DLL, some systems/compilers need a */
222 /* special keyword in front OR after the return type of function */
223 /* declarations. */
224 /* */
225 /* Two macros are used within the FreeType source code to define */
226 /* exported library functions: FT_EXPORT and FT_EXPORT_DEF. */
227 /* */
228 /* FT_EXPORT( return_type ) */
229 /* */
230 /* is used in a function declaration, as in */
231 /* */
232 /* FT_EXPORT( FT_Error ) */
233 /* FT_Init_FreeType( FT_Library* alibrary ); */
234 /* */
235 /* */
236 /* FT_EXPORT_DEF( return_type ) */
237 /* */
238 /* is used in a function definition, as in */
239 /* */
240 /* FT_EXPORT_DEF( FT_Error ) */
241 /* FT_Init_FreeType( FT_Library* alibrary ) */
242 /* { */
243 /* ... some code ... */
244 /* return FT_Err_Ok; */
245 /* } */
246 /* */
247 /* You can provide your own implementation of FT_EXPORT and */
248 /* FT_EXPORT_DEF here if you want. If you leave them undefined, they */
249 /* will be later automatically defined as `extern return_type' to */
250 /* allow normal compilation. */
251 /* */
252 /* Do not #undef these macros here since the build system might define */
253 /* them for certain configurations only. */
254 /* */
255 /* #define FT_EXPORT(x) extern x */
256 /* #define FT_EXPORT_DEF(x) x */
257
258
259 /*************************************************************************/
260 /* */
261 /* Glyph Postscript Names handling */
262 /* */
263 /* By default, FreeType 2 is compiled with the `psnames' module. This */
264 /* module is in charge of converting a glyph name string into a */
265 /* Unicode value, or return a Macintosh standard glyph name for the */
266 /* use with the TrueType `post' table. */
267 /* */
268 /* Undefine this macro if you do not want `psnames' compiled in your */
269 /* build of FreeType. This has the following effects: */
270 /* */
271 /* - The TrueType driver will provide its own set of glyph names, */
272 /* if you build it to support postscript names in the TrueType */
273 /* `post' table. */
274 /* */
275 /* - The Type 1 driver will not be able to synthesize a Unicode */
276 /* charmap out of the glyphs found in the fonts. */
277 /* */
278 /* You would normally undefine this configuration macro when building */
279 /* a version of FreeType that doesn't contain a Type 1 or CFF driver. */
280 /* */
281 #define FT_CONFIG_OPTION_POSTSCRIPT_NAMES
282
283
284 /*************************************************************************/
285 /* */
286 /* Postscript Names to Unicode Values support */
287 /* */
288 /* By default, FreeType 2 is built with the `PSNames' module compiled */
289 /* in. Among other things, the module is used to convert a glyph name */
290 /* into a Unicode value. This is especially useful in order to */
291 /* synthesize on the fly a Unicode charmap from the CFF/Type 1 driver */
292 /* through a big table named the `Adobe Glyph List' (AGL). */
293 /* */
294 /* Undefine this macro if you do not want the Adobe Glyph List */
295 /* compiled in your `PSNames' module. The Type 1 driver will not be */
296 /* able to synthesize a Unicode charmap out of the glyphs found in the */
297 /* fonts. */
298 /* */
299 #define FT_CONFIG_OPTION_ADOBE_GLYPH_LIST
300
301
302 /*************************************************************************/
303 /* */
304 /* Support for Mac fonts */
305 /* */
306 /* Define this macro if you want support for outline fonts in Mac */
307 /* format (mac dfont, mac resource, macbinary containing a mac */
308 /* resource) on non-Mac platforms. */
309 /* */
310 /* Note that the `FOND' resource isn't checked. */
311 /* */
312 #define FT_CONFIG_OPTION_MAC_FONTS
313
314
315 /*************************************************************************/
316 /* */
317 /* Guessing methods to access embedded resource forks */
318 /* */
319 /* Enable extra Mac fonts support on non-Mac platforms (e.g. */
320 /* GNU/Linux). */
321 /* */
322 /* Resource forks which include fonts data are stored sometimes in */
323 /* locations which users or developers don't expected. In some cases, */
324 /* resource forks start with some offset from the head of a file. In */
325 /* other cases, the actual resource fork is stored in file different */
326 /* from what the user specifies. If this option is activated, */
327 /* FreeType tries to guess whether such offsets or different file */
328 /* names must be used. */
329 /* */
330 /* Note that normal, direct access of resource forks is controlled via */
331 /* the FT_CONFIG_OPTION_MAC_FONTS option. */
332 /* */
333 #ifdef FT_CONFIG_OPTION_MAC_FONTS
334 #define FT_CONFIG_OPTION_GUESSING_EMBEDDED_RFORK
335 #endif
336
337
338 /*************************************************************************/
339 /* */
340 /* Allow the use of FT_Incremental_Interface to load typefaces that */
341 /* contain no glyph data, but supply it via a callback function. */
342 /* This is required by clients supporting document formats which */
343 /* supply font data incrementally as the document is parsed, such */
344 /* as the Ghostscript interpreter for the PostScript language. */
345 /* */
346 #define FT_CONFIG_OPTION_INCREMENTAL
347
348
349 /*************************************************************************/
350 /* */
351 /* The size in bytes of the render pool used by the scan-line converter */
352 /* to do all of its work. */
353 /* */
354 /* This must be greater than 4KByte if you use FreeType to rasterize */
355 /* glyphs; otherwise, you may set it to zero to avoid unnecessary */
356 /* allocation of the render pool. */
357 /* */
358 #define FT_RENDER_POOL_SIZE 16384L
359
360
361 /*************************************************************************/
362 /* */
363 /* FT_MAX_MODULES */
364 /* */
365 /* The maximum number of modules that can be registered in a single */
366 /* FreeType library object. 32 is the default. */
367 /* */
368 #define FT_MAX_MODULES 32
369
370
371 /*************************************************************************/
372 /* */
373 /* Debug level */
374 /* */
375 /* FreeType can be compiled in debug or trace mode. In debug mode, */
376 /* errors are reported through the `ftdebug' component. In trace */
377 /* mode, additional messages are sent to the standard output during */
378 /* execution. */
379 /* */
380 /* Define FT_DEBUG_LEVEL_ERROR to build the library in debug mode. */
381 /* Define FT_DEBUG_LEVEL_TRACE to build it in trace mode. */
382 /* */
383 /* Don't define any of these macros to compile in `release' mode! */
384 /* */
385 /* Do not #undef these macros here since the build system might define */
386 /* them for certain configurations only. */
387 /* */
388 /* #define FT_DEBUG_LEVEL_ERROR */
389 /* #define FT_DEBUG_LEVEL_TRACE */
390
391
392 /*************************************************************************/
393 /* */
394 /* Autofitter debugging */
395 /* */
396 /* If FT_DEBUG_AUTOFIT is defined, FreeType provides some means to */
397 /* control the autofitter behaviour for debugging purposes with global */
398 /* boolean variables (consequently, you should *never* enable this */
399 /* while compiling in `release' mode): */
400 /* */
401 /* _af_debug_disable_horz_hints */
402 /* _af_debug_disable_vert_hints */
403 /* _af_debug_disable_blue_hints */
404 /* */
405 /* Additionally, the following functions provide dumps of various */
406 /* internal autofit structures to stdout (using `printf'): */
407 /* */
408 /* af_glyph_hints_dump_points */
409 /* af_glyph_hints_dump_segments */
410 /* af_glyph_hints_dump_edges */
411 /* */
412 /* As an argument, they use another global variable: */
413 /* */
414 /* _af_debug_hints */
415 /* */
416 /* Please have a look at the `ftgrid' demo program to see how those */
417 /* variables and macros should be used. */
418 /* */
419 /* Do not #undef these macros here since the build system might define */
420 /* them for certain configurations only. */
421 /* */
422 /* #define FT_DEBUG_AUTOFIT */
423
424
425 /*************************************************************************/
426 /* */
427 /* Memory Debugging */
428 /* */
429 /* FreeType now comes with an integrated memory debugger that is */
430 /* capable of detecting simple errors like memory leaks or double */
431 /* deletes. To compile it within your build of the library, you */
432 /* should define FT_DEBUG_MEMORY here. */
433 /* */
434 /* Note that the memory debugger is only activated at runtime when */
435 /* when the _environment_ variable `FT2_DEBUG_MEMORY' is defined also! */
436 /* */
437 /* Do not #undef this macro here since the build system might define */
438 /* it for certain configurations only. */
439 /* */
440 /* #define FT_DEBUG_MEMORY */
441
442
443 /*************************************************************************/
444 /* */
445 /* Module errors */
446 /* */
447 /* If this macro is set (which is _not_ the default), the higher byte */
448 /* of an error code gives the module in which the error has occurred, */
449 /* while the lower byte is the real error code. */
450 /* */
451 /* Setting this macro makes sense for debugging purposes only, since */
452 /* it would break source compatibility of certain programs that use */
453 /* FreeType 2. */
454 /* */
455 /* More details can be found in the files ftmoderr.h and fterrors.h. */
456 /* */
457 #undef FT_CONFIG_OPTION_USE_MODULE_ERRORS
458
459
460 /*************************************************************************/
461 /* */
462 /* Position Independent Code */
463 /* */
464 /* If this macro is set (which is _not_ the default), FreeType2 will */
465 /* avoid creating constants that require address fixups. Instead the */
466 /* constants will be moved into a struct and additional intialization */
467 /* code will be used. */
468 /* */
469 /* Setting this macro is needed for systems that prohibit address */
470 /* fixups, such as BREW. */
471 /* */
472 /* #define FT_CONFIG_OPTION_PIC */
473
474
475 /*************************************************************************/
476 /*************************************************************************/
477 /**** ****/
478 /**** S F N T D R I V E R C O N F I G U R A T I O N ****/
479 /**** ****/
480 /*************************************************************************/
481 /*************************************************************************/
482
483
484 /*************************************************************************/
485 /* */
486 /* Define TT_CONFIG_OPTION_EMBEDDED_BITMAPS if you want to support */
487 /* embedded bitmaps in all formats using the SFNT module (namely */
488 /* TrueType & OpenType). */
489 /* */
490 #define TT_CONFIG_OPTION_EMBEDDED_BITMAPS
491
492
493 /*************************************************************************/
494 /* */
495 /* Define TT_CONFIG_OPTION_POSTSCRIPT_NAMES if you want to be able to */
496 /* load and enumerate the glyph Postscript names in a TrueType or */
497 /* OpenType file. */
498 /* */
499 /* Note that when you do not compile the `PSNames' module by undefining */
500 /* the above FT_CONFIG_OPTION_POSTSCRIPT_NAMES, the `sfnt' module will */
501 /* contain additional code used to read the PS Names table from a font. */
502 /* */
503 /* (By default, the module uses `PSNames' to extract glyph names.) */
504 /* */
505 #define TT_CONFIG_OPTION_POSTSCRIPT_NAMES
506
507
508 /*************************************************************************/
509 /* */
510 /* Define TT_CONFIG_OPTION_SFNT_NAMES if your applications need to */
511 /* access the internal name table in a SFNT-based format like TrueType */
512 /* or OpenType. The name table contains various strings used to */
513 /* describe the font, like family name, copyright, version, etc. It */
514 /* does not contain any glyph name though. */
515 /* */
516 /* Accessing SFNT names is done through the functions declared in */
517 /* `freetype/ftsnames.h'. */
518 /* */
519 #define TT_CONFIG_OPTION_SFNT_NAMES
520
521
522 /*************************************************************************/
523 /* */
524 /* TrueType CMap support */
525 /* */
526 /* Here you can fine-tune which TrueType CMap table format shall be */
527 /* supported. */
528 #define TT_CONFIG_CMAP_FORMAT_0
529 #define TT_CONFIG_CMAP_FORMAT_2
530 #define TT_CONFIG_CMAP_FORMAT_4
531 #define TT_CONFIG_CMAP_FORMAT_6
532 #define TT_CONFIG_CMAP_FORMAT_8
533 #define TT_CONFIG_CMAP_FORMAT_10
534 #define TT_CONFIG_CMAP_FORMAT_12
535 #define TT_CONFIG_CMAP_FORMAT_13
536 #define TT_CONFIG_CMAP_FORMAT_14
537
538
539 /*************************************************************************/
540 /*************************************************************************/
541 /**** ****/
542 /**** 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 ****/
543 /**** ****/
544 /*************************************************************************/
545 /*************************************************************************/
546
547 /*************************************************************************/
548 /* */
549 /* Define TT_CONFIG_OPTION_BYTECODE_INTERPRETER if you want to compile */
550 /* a bytecode interpreter in the TrueType driver. */
551 /* */
552 /* By undefining this, you will only compile the code necessary to load */
553 /* TrueType glyphs without hinting. */
554 /* */
555 /* Do not #undef this macro here, since the build system might */
556 /* define it for certain configurations only. */
557 /* */
558 #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER
559
560
561 /*************************************************************************/
562 /* */
563 /* Define TT_CONFIG_OPTION_SUBPIXEL_HINTING if you want to compile */
564 /* EXPERIMENTAL subpixel hinting support into the TrueType driver. This */
565 /* replaces the native TrueType hinting mechanism when anything but */
566 /* FT_RENDER_MODE_MONO is requested. */
567 /* */
568 /* Enabling this causes the TrueType driver to ignore instructions under */
569 /* certain conditions. This is done in accordance with the guide here, */
570 /* with some minor differences: */
571 /* */
572 /* http://www.microsoft.com/typography/cleartype/truetypecleartype.aspx */
573 /* */
574 /* By undefining this, you only compile the code necessary to hint */
575 /* TrueType glyphs with native TT hinting. */
576 /* */
577 /* This option requires TT_CONFIG_OPTION_BYTECODE_INTERPRETER to be */
578 /* defined. */
579 /* */
580 /* #define TT_CONFIG_OPTION_SUBPIXEL_HINTING */
581
582
583 /*************************************************************************/
584 /* */
585 /* If you define TT_CONFIG_OPTION_UNPATENTED_HINTING, a special version */
586 /* of the TrueType bytecode interpreter is used that doesn't implement */
587 /* any of the patented opcodes and algorithms. The patents related to */
588 /* TrueType hinting have expired worldwide since May 2010; this option */
589 /* is now deprecated. */
590 /* */
591 /* Note that the TT_CONFIG_OPTION_UNPATENTED_HINTING macro is *ignored* */
592 /* if you define TT_CONFIG_OPTION_BYTECODE_INTERPRETER; in other words, */
593 /* either define TT_CONFIG_OPTION_BYTECODE_INTERPRETER or */
594 /* TT_CONFIG_OPTION_UNPATENTED_HINTING but not both at the same time. */
595 /* */
596 /* This macro is only useful for a small number of font files (mostly */
597 /* for Asian scripts) that require bytecode interpretation to properly */
598 /* load glyphs. For all other fonts, this produces unpleasant results, */
599 /* thus the unpatented interpreter is never used to load glyphs from */
600 /* TrueType fonts unless one of the following two options is used. */
601 /* */
602 /* - The unpatented interpreter is explicitly activated by the user */
603 /* through the FT_PARAM_TAG_UNPATENTED_HINTING parameter tag */
604 /* when opening the FT_Face. */
605 /* */
606 /* - FreeType detects that the FT_Face corresponds to one of the */
607 /* `trick' fonts (e.g., `Mingliu') it knows about. The font engine */
608 /* contains a hard-coded list of font names and other matching */
609 /* parameters (see function `tt_face_init' in file */
610 /* `src/truetype/ttobjs.c'). */
611 /* */
612 /* Here a sample code snippet for using FT_PARAM_TAG_UNPATENTED_HINTING. */
613 /* */
614 /* { */
615 /* FT_Parameter parameter; */
616 /* FT_Open_Args open_args; */
617 /* */
618 /* */
619 /* parameter.tag = FT_PARAM_TAG_UNPATENTED_HINTING; */
620 /* */
621 /* open_args.flags = FT_OPEN_PATHNAME | FT_OPEN_PARAMS; */
622 /* open_args.pathname = my_font_pathname; */
623 /* open_args.num_params = 1; */
624 /* open_args.params = &parameter; */
625 /* */
626 /* error = FT_Open_Face( library, &open_args, index, &face ); */
627 /* ... */
628 /* } */
629 /* */
630 /* #define TT_CONFIG_OPTION_UNPATENTED_HINTING */
631
632
633 /*************************************************************************/
634 /* */
635 /* Define TT_CONFIG_OPTION_INTERPRETER_SWITCH to compile the TrueType */
636 /* bytecode interpreter with a huge switch statement, rather than a call */
637 /* table. This results in smaller and faster code for a number of */
638 /* architectures. */
639 /* */
640 /* Note however that on some compiler/processor combinations, undefining */
641 /* this macro will generate faster, though larger, code. */
642 /* */
643 #define TT_CONFIG_OPTION_INTERPRETER_SWITCH
644
645
646 /*************************************************************************/
647 /* */
648 /* Define TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED to compile the */
649 /* TrueType glyph loader to use Apple's definition of how to handle */
650 /* component offsets in composite glyphs. */
651 /* */
652 /* Apple and MS disagree on the default behavior of component offsets */
653 /* in composites. Apple says that they should be scaled by the scaling */
654 /* factors in the transformation matrix (roughly, it's more complex) */
655 /* while MS says they should not. OpenType defines two bits in the */
656 /* composite flags array which can be used to disambiguate, but old */
657 /* fonts will not have them. */
658 /* */
659 /* http://www.microsoft.com/typography/otspec/glyf.htm */
660 /* http://fonts.apple.com/TTRefMan/RM06/Chap6glyf.html */
661 /* */
662 #undef TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED
663
664
665 /*************************************************************************/
666 /* */
667 /* Define TT_CONFIG_OPTION_GX_VAR_SUPPORT if you want to include */
668 /* support for Apple's distortable font technology (fvar, gvar, cvar, */
669 /* and avar tables). This has many similarities to Type 1 Multiple */
670 /* Masters support. */
671 /* */
672 #define TT_CONFIG_OPTION_GX_VAR_SUPPORT
673
674
675 /*************************************************************************/
676 /* */
677 /* Define TT_CONFIG_OPTION_BDF if you want to include support for */
678 /* an embedded `BDF ' table within SFNT-based bitmap formats. */
679 /* */
680 #define TT_CONFIG_OPTION_BDF
681
682
683 /*************************************************************************/
684 /*************************************************************************/
685 /**** ****/
686 /**** T Y P E 1 D R I V E R C O N F I G U R A T I O N ****/
687 /**** ****/
688 /*************************************************************************/
689 /*************************************************************************/
690
691
692 /*************************************************************************/
693 /* */
694 /* T1_MAX_DICT_DEPTH is the maximum depth of nest dictionaries and */
695 /* arrays in the Type 1 stream (see t1load.c). A minimum of 4 is */
696 /* required. */
697 /* */
698 #define T1_MAX_DICT_DEPTH 5
699
700
701 /*************************************************************************/
702 /* */
703 /* T1_MAX_SUBRS_CALLS details the maximum number of nested sub-routine */
704 /* calls during glyph loading. */
705 /* */
706 #define T1_MAX_SUBRS_CALLS 16
707
708
709 /*************************************************************************/
710 /* */
711 /* T1_MAX_CHARSTRING_OPERANDS is the charstring stack's capacity. A */
712 /* minimum of 16 is required. */
713 /* */
714 /* The Chinese font MingTiEG-Medium (CNS 11643 character set) needs 256. */
715 /* */
716 #define T1_MAX_CHARSTRINGS_OPERANDS 256
717
718
719 /*************************************************************************/
720 /* */
721 /* Define this configuration macro if you want to prevent the */
722 /* compilation of `t1afm', which is in charge of reading Type 1 AFM */
723 /* files into an existing face. Note that if set, the T1 driver will be */
724 /* unable to produce kerning distances. */
725 /* */
726 #undef T1_CONFIG_OPTION_NO_AFM
727
728
729 /*************************************************************************/
730 /* */
731 /* Define this configuration macro if you want to prevent the */
732 /* compilation of the Multiple Masters font support in the Type 1 */
733 /* driver. */
734 /* */
735 #undef T1_CONFIG_OPTION_NO_MM_SUPPORT
736
737
738 /*************************************************************************/
739 /*************************************************************************/
740 /**** ****/
741 /**** 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 ****/
742 /**** ****/
743 /*************************************************************************/
744 /*************************************************************************/
745
746
747 /*************************************************************************/
748 /* */
749 /* Compile autofit module with CJK (Chinese, Japanese, Korean) script */
750 /* support. */
751 /* */
752 #define AF_CONFIG_OPTION_CJK
753
754 /*************************************************************************/
755 /* */
756 /* Compile autofit module with Indic script support. */
757 /* */
758 #define AF_CONFIG_OPTION_INDIC
759
760 /*************************************************************************/
761 /* */
762 /* Compile autofit module with warp hinting. The idea of the warping */
763 /* code is to slightly scale and shift a glyph within a single dimension */
764 /* so that as much of its segments are aligned (more or less) on the */
765 /* grid. To find out the optimal scaling and shifting value, various */
766 /* parameter combinations are tried and scored. */
767 /* */
768 /* This experimental option is only active if the render mode is */
769 /* FT_RENDER_MODE_LIGHT. */
770 /* */
771 /* #define AF_CONFIG_OPTION_USE_WARPER */
772
773 /* */
774
775
776 /*
777 * Define this variable if you want to keep the layout of internal
778 * structures that was used prior to FreeType 2.2. This also compiles in
779 * a few obsolete functions to avoid linking problems on typical Unix
780 * distributions.
781 *
782 * For embedded systems or building a new distribution from scratch, it
783 * is recommended to disable the macro since it reduces the library's code
784 * size and activates a few memory-saving optimizations as well.
785 */
786 /* #define FT_CONFIG_OPTION_OLD_INTERNALS */
787
788
789 /*
790 * To detect legacy cache-lookup call from a rogue client (<= 2.1.7),
791 * we restrict the number of charmaps in a font. The current API of
792 * FTC_CMapCache_Lookup() takes cmap_index & charcode, but old API
793 * takes charcode only. To determine the passed value is for cmap_index
794 * or charcode, the possible cmap_index is restricted not to exceed
795 * the minimum possible charcode by a rogue client. It is also very
796 * unlikely that a rogue client is interested in Unicode values 0 to 15.
797 *
798 * NOTE: The original threshold was 4 deduced from popular number of
799 * cmap subtables in UCS-4 TrueType fonts, but now it is not
800 * irregular for OpenType fonts to have more than 4 subtables,
801 * because variation selector subtables are available for Apple
802 * and Microsoft platforms.
803 */
804
805 #ifdef FT_CONFIG_OPTION_OLD_INTERNALS
806 #define FT_MAX_CHARMAP_CACHEABLE 15
807 #endif
808
809
810 /*
811 * This macro is defined if either unpatented or native TrueType
812 * hinting is requested by the definitions above.
813 */
814 #ifdef TT_CONFIG_OPTION_BYTECODE_INTERPRETER
815 #define TT_USE_BYTECODE_INTERPRETER
816 #undef TT_CONFIG_OPTION_UNPATENTED_HINTING
817 #elif defined TT_CONFIG_OPTION_UNPATENTED_HINTING
818 #define TT_USE_BYTECODE_INTERPRETER
819 #endif
820
821 FT_END_HEADER
822
823
824 #endif /* __FTOPTION_H__ */
825
826
827 /* END */