1/***************************************************************************/
2/* */
3/* ftoption.h */
4/* */
5/* User-selectable configuration macros (specification only). */
6/* */
7/* Copyright 1996-2018 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 /* If you enable this configuration option, FreeType recognizes an */
81 /* environment variable called `FREETYPE_PROPERTIES', which can be used */
82 /* to control the various font drivers and modules. The controllable */
83 /* properties are listed in the section @properties. */
84 /* */
85 /* You have to undefine this configuration option on platforms that lack */
86 /* the concept of environment variables (and thus don't have the */
87 /* `getenv' function), for example Windows CE. */
88 /* */
89 /* `FREETYPE_PROPERTIES' has the following syntax form (broken here into */
90 /* multiple lines for better readability). */
91 /* */
92 /* { */
93 /* <optional whitespace> */
94 /* <module-name1> ':' */
95 /* <property-name1> '=' <property-value1> */
96 /* <whitespace> */
97 /* <module-name2> ':' */
98 /* <property-name2> '=' <property-value2> */
99 /* ... */
100 /* } */
101 /* */
102 /* Example: */
103 /* */
104 /* FREETYPE_PROPERTIES=truetype:interpreter-version=35 \ */
105 /* cff:no-stem-darkening=1 \ */
106 /* autofitter:warping=1 */
107 /* */
108#define FT_CONFIG_OPTION_ENVIRONMENT_PROPERTIES
109
110
111 /*************************************************************************/
112 /* */
113 /* Uncomment the line below if you want to activate LCD rendering */
114 /* technology similar to ClearType in this build of the library. This */
115 /* technology triples the resolution in the direction color subpixels. */
116 /* To mitigate color fringes inherent to this technology, you also need */
117 /* to explicitly set up LCD filtering. */
118 /* */
119 /* Note that this feature is covered by several Microsoft patents */
120 /* and should not be activated in any default build of the library. */
121 /* When this macro is not defined, FreeType offers alternative LCD */
122 /* rendering technology that produces excellent output without LCD */
123 /* filtering. */
124 /* */
125#define FT_CONFIG_OPTION_SUBPIXEL_RENDERING
126
127
128 /*************************************************************************/
129 /* */
130 /* Many compilers provide a non-ANSI 64-bit data type that can be used */
131 /* by FreeType to speed up some computations. However, this will create */
132 /* some problems when compiling the library in strict ANSI mode. */
133 /* */
134 /* For this reason, the use of 64-bit integers is normally disabled when */
135 /* the __STDC__ macro is defined. You can however disable this by */
136 /* defining the macro FT_CONFIG_OPTION_FORCE_INT64 here. */
137 /* */
138 /* For most compilers, this will only create compilation warnings when */
139 /* building the library. */
140 /* */
141 /* ObNote: The compiler-specific 64-bit integers are detected in the */
142 /* file `ftconfig.h' either statically or through the */
143 /* `configure' script on supported platforms. */
144 /* */
145#undef FT_CONFIG_OPTION_FORCE_INT64
146
147
148 /*************************************************************************/
149 /* */
150 /* If this macro is defined, do not try to use an assembler version of */
151 /* performance-critical functions (e.g. FT_MulFix). You should only do */
152 /* that to verify that the assembler function works properly, or to */
153 /* execute benchmark tests of the various implementations. */
154/* #define FT_CONFIG_OPTION_NO_ASSEMBLER */
155
156
157 /*************************************************************************/
158 /* */
159 /* If this macro is defined, try to use an inlined assembler version of */
160 /* the `FT_MulFix' function, which is a `hotspot' when loading and */
161 /* hinting glyphs, and which should be executed as fast as possible. */
162 /* */
163 /* Note that if your compiler or CPU is not supported, this will default */
164 /* to the standard and portable implementation found in `ftcalc.c'. */
165 /* */
166#define FT_CONFIG_OPTION_INLINE_MULFIX
167
168
169 /*************************************************************************/
170 /* */
171 /* LZW-compressed file support. */
172 /* */
173 /* FreeType now handles font files that have been compressed with the */
174 /* `compress' program. This is mostly used to parse many of the PCF */
175 /* files that come with various X11 distributions. The implementation */
176 /* uses NetBSD's `zopen' to partially uncompress the file on the fly */
177 /* (see src/lzw/ftgzip.c). */
178 /* */
179 /* Define this macro if you want to enable this `feature'. */
180 /* */
181#define FT_CONFIG_OPTION_USE_LZW
182
183
184 /*************************************************************************/
185 /* */
186 /* Gzip-compressed file support. */
187 /* */
188 /* FreeType now handles font files that have been compressed with the */
189 /* `gzip' program. This is mostly used to parse many of the PCF files */
190 /* that come with XFree86. The implementation uses `zlib' to */
191 /* partially uncompress the file on the fly (see src/gzip/ftgzip.c). */
192 /* */
193 /* Define this macro if you want to enable this `feature'. See also */
194 /* the macro FT_CONFIG_OPTION_SYSTEM_ZLIB below. */
195 /* */
196#define FT_CONFIG_OPTION_USE_ZLIB
197
198
199 /*************************************************************************/
200 /* */
201 /* ZLib library selection */
202 /* */
203 /* This macro is only used when FT_CONFIG_OPTION_USE_ZLIB is defined. */
204 /* It allows FreeType's `ftgzip' component to link to the system's */
205 /* installation of the ZLib library. This is useful on systems like */
206 /* Unix or VMS where it generally is already available. */
207 /* */
208 /* If you let it undefined, the component will use its own copy */
209 /* of the zlib sources instead. These have been modified to be */
210 /* included directly within the component and *not* export external */
211 /* function names. This allows you to link any program with FreeType */
212 /* _and_ ZLib without linking conflicts. */
213 /* */
214 /* Do not #undef this macro here since the build system might define */
215 /* it for certain configurations only. */
216 /* */
217 /* If you use a build system like cmake or the `configure' script, */
218 /* options set by those programs have precendence, overwriting the */
219 /* value here with the configured one. */
220 /* */
221#define FT_CONFIG_OPTION_SYSTEM_ZLIB
222
223
224 /*************************************************************************/
225 /* */
226 /* Bzip2-compressed file support. */
227 /* */
228 /* FreeType now handles font files that have been compressed with the */
229 /* `bzip2' program. This is mostly used to parse many of the PCF */
230 /* files that come with XFree86. The implementation uses `libbz2' to */
231 /* partially uncompress the file on the fly (see src/bzip2/ftbzip2.c). */
232 /* Contrary to gzip, bzip2 currently is not included and need to use */
233 /* the system available bzip2 implementation. */
234 /* */
235 /* Define this macro if you want to enable this `feature'. */
236 /* */
237 /* If you use a build system like cmake or the `configure' script, */
238 /* options set by those programs have precendence, overwriting the */
239 /* value here with the configured one. */
240 /* */
241/* #undef FT_CONFIG_OPTION_USE_BZIP2 */
242
243
244 /*************************************************************************/
245 /* */
246 /* Define to disable the use of file stream functions and types, FILE, */
247 /* fopen() etc. Enables the use of smaller system libraries on embedded */
248 /* systems that have multiple system libraries, some with or without */
249 /* file stream support, in the cases where file stream support is not */
250 /* necessary such as memory loading of font files. */
251 /* */
252/* #define FT_CONFIG_OPTION_DISABLE_STREAM_SUPPORT */
253
254
255 /*************************************************************************/
256 /* */
257 /* PNG bitmap support. */
258 /* */
259 /* FreeType now handles loading color bitmap glyphs in the PNG format. */
260 /* This requires help from the external libpng library. Uncompressed */
261 /* color bitmaps do not need any external libraries and will be */
262 /* supported regardless of this configuration. */
263 /* */
264 /* Define this macro if you want to enable this `feature'. */
265 /* */
266 /* If you use a build system like cmake or the `configure' script, */
267 /* options set by those programs have precendence, overwriting the */
268 /* value here with the configured one. */
269 /* */
270#define FT_CONFIG_OPTION_USE_PNG
271
272
273 /*************************************************************************/
274 /* */
275 /* HarfBuzz support. */
276 /* */
277 /* FreeType uses the HarfBuzz library to improve auto-hinting of */
278 /* OpenType fonts. If available, many glyphs not directly addressable */
279 /* by a font's character map will be hinted also. */
280 /* */
281 /* Define this macro if you want to enable this `feature'. */
282 /* */
283 /* If you use a build system like cmake or the `configure' script, */
284 /* options set by those programs have precendence, overwriting the */
285 /* value here with the configured one. */
286 /* */
287/* #undef FT_CONFIG_OPTION_USE_HARFBUZZ */
288
289
290 /*************************************************************************/
291 /* */
292 /* Glyph Postscript Names handling */
293 /* */
294 /* By default, FreeType 2 is compiled with the `psnames' module. This */
295 /* module is in charge of converting a glyph name string into a */
296 /* Unicode value, or return a Macintosh standard glyph name for the */
297 /* use with the TrueType `post' table. */
298 /* */
299 /* Undefine this macro if you do not want `psnames' compiled in your */
300 /* build of FreeType. This has the following effects: */
301 /* */
302 /* - The TrueType driver will provide its own set of glyph names, */
303 /* if you build it to support postscript names in the TrueType */
304 /* `post' table, but will not synthesize a missing Unicode charmap. */
305 /* */
306 /* - The Type 1 driver will not be able to synthesize a Unicode */
307 /* charmap out of the glyphs found in the fonts. */
308 /* */
309 /* You would normally undefine this configuration macro when building */
310 /* a version of FreeType that doesn't contain a Type 1 or CFF driver. */
311 /* */
312#define FT_CONFIG_OPTION_POSTSCRIPT_NAMES
313
314
315 /*************************************************************************/
316 /* */
317 /* Postscript Names to Unicode Values support */
318 /* */
319 /* By default, FreeType 2 is built with the `PSNames' module compiled */
320 /* in. Among other things, the module is used to convert a glyph name */
321 /* into a Unicode value. This is especially useful in order to */
322 /* synthesize on the fly a Unicode charmap from the CFF/Type 1 driver */
323 /* through a big table named the `Adobe Glyph List' (AGL). */
324 /* */
325 /* Undefine this macro if you do not want the Adobe Glyph List */
326 /* compiled in your `PSNames' module. The Type 1 driver will not be */
327 /* able to synthesize a Unicode charmap out of the glyphs found in the */
328 /* fonts. */
329 /* */
330#define FT_CONFIG_OPTION_ADOBE_GLYPH_LIST
331
332
333 /*************************************************************************/
334 /* */
335 /* Support for Mac fonts */
336 /* */
337 /* Define this macro if you want support for outline fonts in Mac */
338 /* format (mac dfont, mac resource, macbinary containing a mac */
339 /* resource) on non-Mac platforms. */
340 /* */
341 /* Note that the `FOND' resource isn't checked. */
342 /* */
343#define FT_CONFIG_OPTION_MAC_FONTS
344
345
346 /*************************************************************************/
347 /* */
348 /* Guessing methods to access embedded resource forks */
349 /* */
350 /* Enable extra Mac fonts support on non-Mac platforms (e.g. */
351 /* GNU/Linux). */
352 /* */
353 /* Resource forks which include fonts data are stored sometimes in */
354 /* locations which users or developers don't expected. In some cases, */
355 /* resource forks start with some offset from the head of a file. In */
356 /* other cases, the actual resource fork is stored in file different */
357 /* from what the user specifies. If this option is activated, */
358 /* FreeType tries to guess whether such offsets or different file */
359 /* names must be used. */
360 /* */
361 /* Note that normal, direct access of resource forks is controlled via */
362 /* the FT_CONFIG_OPTION_MAC_FONTS option. */
363 /* */
364#ifdef FT_CONFIG_OPTION_MAC_FONTS
365#define FT_CONFIG_OPTION_GUESSING_EMBEDDED_RFORK
366#endif
367
368
369 /*************************************************************************/
370 /* */
371 /* Allow the use of FT_Incremental_Interface to load typefaces that */
372 /* contain no glyph data, but supply it via a callback function. */
373 /* This is required by clients supporting document formats which */
374 /* supply font data incrementally as the document is parsed, such */
375 /* as the Ghostscript interpreter for the PostScript language. */
376 /* */
377#define FT_CONFIG_OPTION_INCREMENTAL
378
379
380 /*************************************************************************/
381 /* */
382 /* The size in bytes of the render pool used by the scan-line converter */
383 /* to do all of its work. */
384 /* */
385#define FT_RENDER_POOL_SIZE 16384L
386
387
388 /*************************************************************************/
389 /* */
390 /* FT_MAX_MODULES */
391 /* */
392 /* The maximum number of modules that can be registered in a single */
393 /* FreeType library object. 32 is the default. */
394 /* */
395#define FT_MAX_MODULES 32
396
397
398 /*************************************************************************/
399 /* */
400 /* Debug level */
401 /* */
402 /* FreeType can be compiled in debug or trace mode. In debug mode, */
403 /* errors are reported through the `ftdebug' component. In trace */
404 /* mode, additional messages are sent to the standard output during */
405 /* execution. */
406 /* */
407 /* Define FT_DEBUG_LEVEL_ERROR to build the library in debug mode. */
408 /* Define FT_DEBUG_LEVEL_TRACE to build it in trace mode. */
409 /* */
410 /* Don't define any of these macros to compile in `release' mode! */
411 /* */
412 /* Do not #undef these macros here since the build system might define */
413 /* them for certain configurations only. */
414 /* */
415/* #define FT_DEBUG_LEVEL_ERROR */
416/* #define FT_DEBUG_LEVEL_TRACE */
417
418
419 /*************************************************************************/
420 /* */
421 /* Autofitter debugging */
422 /* */
423 /* If FT_DEBUG_AUTOFIT is defined, FreeType provides some means to */
424 /* control the autofitter behaviour for debugging purposes with global */
425 /* boolean variables (consequently, you should *never* enable this */
426 /* while compiling in `release' mode): */
427 /* */
428 /* _af_debug_disable_horz_hints */
429 /* _af_debug_disable_vert_hints */
430 /* _af_debug_disable_blue_hints */
431 /* */
432 /* Additionally, the following functions provide dumps of various */
433 /* internal autofit structures to stdout (using `printf'): */
434 /* */
435 /* af_glyph_hints_dump_points */
436 /* af_glyph_hints_dump_segments */
437 /* af_glyph_hints_dump_edges */
438 /* af_glyph_hints_get_num_segments */
439 /* af_glyph_hints_get_segment_offset */
440 /* */
441 /* As an argument, they use another global variable: */
442 /* */
443 /* _af_debug_hints */
444 /* */
445 /* Please have a look at the `ftgrid' demo program to see how those */
446 /* variables and macros should be used. */
447 /* */
448 /* Do not #undef these macros here since the build system might define */
449 /* them for certain configurations only. */
450 /* */
451/* #define FT_DEBUG_AUTOFIT */
452
453
454 /*************************************************************************/
455 /* */
456 /* Memory Debugging */
457 /* */
458 /* FreeType now comes with an integrated memory debugger that is */
459 /* capable of detecting simple errors like memory leaks or double */
460 /* deletes. To compile it within your build of the library, you */
461 /* should define FT_DEBUG_MEMORY here. */
462 /* */
463 /* Note that the memory debugger is only activated at runtime when */
464 /* when the _environment_ variable `FT2_DEBUG_MEMORY' is defined also! */
465 /* */
466 /* Do not #undef this macro here since the build system might define */
467 /* it for certain configurations only. */
468 /* */
469/* #define FT_DEBUG_MEMORY */
470
471
472 /*************************************************************************/
473 /* */
474 /* Module errors */
475 /* */
476 /* If this macro is set (which is _not_ the default), the higher byte */
477 /* of an error code gives the module in which the error has occurred, */
478 /* while the lower byte is the real error code. */
479 /* */
480 /* Setting this macro makes sense for debugging purposes only, since */
481 /* it would break source compatibility of certain programs that use */
482 /* FreeType 2. */
483 /* */
484 /* More details can be found in the files ftmoderr.h and fterrors.h. */
485 /* */
486#undef FT_CONFIG_OPTION_USE_MODULE_ERRORS
487
488
489 /*************************************************************************/
490 /* */
491 /* Position Independent Code */
492 /* */
493 /* If this macro is set (which is _not_ the default), FreeType2 will */
494 /* avoid creating constants that require address fixups. Instead the */
495 /* constants will be moved into a struct and additional intialization */
496 /* code will be used. */
497 /* */
498 /* Setting this macro is needed for systems that prohibit address */
499 /* fixups, such as BREW. [Note that standard compilers like gcc or */
500 /* clang handle PIC generation automatically; you don't have to set */
501 /* FT_CONFIG_OPTION_PIC, which is only necessary for very special */
502 /* compilers.] */
503 /* */
504 /* Note that FT_CONFIG_OPTION_PIC support is not available for all */
505 /* modules (see `modules.cfg' for a complete list). For building with */
506 /* FT_CONFIG_OPTION_PIC support, do the following. */
507 /* */
508 /* 0. Clone the repository. */
509 /* 1. Define FT_CONFIG_OPTION_PIC. */
510 /* 2. Remove all subdirectories in `src' that don't have */
511 /* FT_CONFIG_OPTION_PIC support. */
512 /* 3. Comment out the corresponding modules in `modules.cfg'. */
513 /* 4. Compile. */
514 /* */
515/* #define FT_CONFIG_OPTION_PIC */
516
517
518 /*************************************************************************/
519 /*************************************************************************/
520 /**** ****/
521 /**** S F N T D R I V E R C O N F I G U R A T I O N ****/
522 /**** ****/
523 /*************************************************************************/
524 /*************************************************************************/
525
526
527 /*************************************************************************/
528 /* */
529 /* Define TT_CONFIG_OPTION_EMBEDDED_BITMAPS if you want to support */
530 /* embedded bitmaps in all formats using the SFNT module (namely */
531 /* TrueType & OpenType). */
532 /* */
533#define TT_CONFIG_OPTION_EMBEDDED_BITMAPS
534
535
536 /*************************************************************************/
537 /* */
538 /* Define TT_CONFIG_OPTION_POSTSCRIPT_NAMES if you want to be able to */
539 /* load and enumerate the glyph Postscript names in a TrueType or */
540 /* OpenType file. */
541 /* */
542 /* Note that when you do not compile the `PSNames' module by undefining */
543 /* the above FT_CONFIG_OPTION_POSTSCRIPT_NAMES, the `sfnt' module will */
544 /* contain additional code used to read the PS Names table from a font. */
545 /* */
546 /* (By default, the module uses `PSNames' to extract glyph names.) */
547 /* */
548#define TT_CONFIG_OPTION_POSTSCRIPT_NAMES
549
550
551 /*************************************************************************/
552 /* */
553 /* Define TT_CONFIG_OPTION_SFNT_NAMES if your applications need to */
554 /* access the internal name table in a SFNT-based format like TrueType */
555 /* or OpenType. The name table contains various strings used to */
556 /* describe the font, like family name, copyright, version, etc. It */
557 /* does not contain any glyph name though. */
558 /* */
559 /* Accessing SFNT names is done through the functions declared in */
560 /* `ftsnames.h'. */
561 /* */
562#define TT_CONFIG_OPTION_SFNT_NAMES
563
564
565 /*************************************************************************/
566 /* */
567 /* TrueType CMap support */
568 /* */
569 /* Here you can fine-tune which TrueType CMap table format shall be */
570 /* supported. */
571#define TT_CONFIG_CMAP_FORMAT_0
572#define TT_CONFIG_CMAP_FORMAT_2
573#define TT_CONFIG_CMAP_FORMAT_4
574#define TT_CONFIG_CMAP_FORMAT_6
575#define TT_CONFIG_CMAP_FORMAT_8
576#define TT_CONFIG_CMAP_FORMAT_10
577#define TT_CONFIG_CMAP_FORMAT_12
578#define TT_CONFIG_CMAP_FORMAT_13
579#define TT_CONFIG_CMAP_FORMAT_14
580
581
582 /*************************************************************************/
583 /*************************************************************************/
584 /**** ****/
585 /**** 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 ****/
586 /**** ****/
587 /*************************************************************************/
588 /*************************************************************************/
589
590 /*************************************************************************/
591 /* */
592 /* Define TT_CONFIG_OPTION_BYTECODE_INTERPRETER if you want to compile */
593 /* a bytecode interpreter in the TrueType driver. */
594 /* */
595 /* By undefining this, you will only compile the code necessary to load */
596 /* TrueType glyphs without hinting. */
597 /* */
598 /* Do not #undef this macro here, since the build system might */
599 /* define it for certain configurations only. */
600 /* */
601#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER
602
603
604 /*************************************************************************/
605 /* */
606 /* Define TT_CONFIG_OPTION_SUBPIXEL_HINTING if you want to compile */
607 /* subpixel hinting support into the TrueType driver. This modifies the */
608 /* TrueType hinting mechanism when anything but FT_RENDER_MODE_MONO is */
609 /* requested. */
610 /* */
611 /* In particular, it modifies the bytecode interpreter to interpret (or */
612 /* not) instructions in a certain way so that all TrueType fonts look */
613 /* like they do in a Windows ClearType (DirectWrite) environment. See */
614 /* [1] for a technical overview on what this means. See `ttinterp.h' */
615 /* for more details on the LEAN option. */
616 /* */
617 /* There are three possible values. */
618 /* */
619 /* Value 1: */
620 /* This value is associated with the `Infinality' moniker, */
621 /* contributed by an individual nicknamed Infinality with the goal of */
622 /* making TrueType fonts render better than on Windows. A high */
623 /* amount of configurability and flexibility, down to rules for */
624 /* single glyphs in fonts, but also very slow. Its experimental and */
625 /* slow nature and the original developer losing interest meant that */
626 /* this option was never enabled in default builds. */
627 /* */
628 /* The corresponding interpreter version is v38. */
629 /* */
630 /* Value 2: */
631 /* The new default mode for the TrueType driver. The Infinality code */
632 /* base was stripped to the bare minimum and all configurability */
633 /* removed in the name of speed and simplicity. The configurability */
634 /* was mainly aimed at legacy fonts like Arial, Times New Roman, or */
635 /* Courier. Legacy fonts are fonts that modify vertical stems to */
636 /* achieve clean black-and-white bitmaps. The new mode focuses on */
637 /* applying a minimal set of rules to all fonts indiscriminately so */
638 /* that modern and web fonts render well while legacy fonts render */
639 /* okay. */
640 /* */
641 /* The corresponding interpreter version is v40. */
642 /* */
643 /* Value 3: */
644 /* Compile both, making both v38 and v40 available (the latter is the */
645 /* default). */
646 /* */
647 /* By undefining these, you get rendering behavior like on Windows */
648 /* without ClearType, i.e., Windows XP without ClearType enabled and */
649 /* Win9x (interpreter version v35). Or not, depending on how much */
650 /* hinting blood and testing tears the font designer put into a given */
651 /* font. If you define one or both subpixel hinting options, you can */
652 /* switch between between v35 and the ones you define (using */
653 /* `FT_Property_Set'). */
654 /* */
655 /* This option requires TT_CONFIG_OPTION_BYTECODE_INTERPRETER to be */
656 /* defined. */
657 /* */
658 /* [1] https://www.microsoft.com/typography/cleartype/truetypecleartype.aspx */
659 /* */
660/* #define TT_CONFIG_OPTION_SUBPIXEL_HINTING 1 */
661#define TT_CONFIG_OPTION_SUBPIXEL_HINTING 2
662/* #define TT_CONFIG_OPTION_SUBPIXEL_HINTING ( 1 | 2 ) */
663
664
665 /*************************************************************************/
666 /* */
667 /* Define TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED to compile the */
668 /* TrueType glyph loader to use Apple's definition of how to handle */
669 /* component offsets in composite glyphs. */
670 /* */
671 /* Apple and MS disagree on the default behavior of component offsets */
672 /* in composites. Apple says that they should be scaled by the scaling */
673 /* factors in the transformation matrix (roughly, it's more complex) */
674 /* while MS says they should not. OpenType defines two bits in the */
675 /* composite flags array which can be used to disambiguate, but old */
676 /* fonts will not have them. */
677 /* */
678 /* https://www.microsoft.com/typography/otspec/glyf.htm */
679 /* https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6glyf.html */
680 /* */
681#undef TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED
682
683
684 /*************************************************************************/
685 /* */
686 /* Define TT_CONFIG_OPTION_GX_VAR_SUPPORT if you want to include */
687 /* support for Apple's distortable font technology (fvar, gvar, cvar, */
688 /* and avar tables). This has many similarities to Type 1 Multiple */
689 /* Masters support. */
690 /* */
691#define TT_CONFIG_OPTION_GX_VAR_SUPPORT
692
693
694 /*************************************************************************/
695 /* */
696 /* Define TT_CONFIG_OPTION_BDF if you want to include support for */
697 /* an embedded `BDF ' table within SFNT-based bitmap formats. */
698 /* */
699#define TT_CONFIG_OPTION_BDF
700
701
702 /*************************************************************************/
703 /* */
704 /* Option TT_CONFIG_OPTION_MAX_RUNNABLE_OPCODES controls the maximum */
705 /* number of bytecode instructions executed for a single run of the */
706 /* bytecode interpreter, needed to prevent infinite loops. You don't */
707 /* want to change this except for very special situations (e.g., making */
708 /* a library fuzzer spend less time to handle broken fonts). */
709 /* */
710 /* It is not expected that this value is ever modified by a configuring */
711 /* script; instead, it gets surrounded with #ifndef ... #endif so that */
712 /* the value can be set as a preprocessor option on the compiler's */
713 /* command line. */
714 /* */
715#ifndef TT_CONFIG_OPTION_MAX_RUNNABLE_OPCODES
716#define TT_CONFIG_OPTION_MAX_RUNNABLE_OPCODES 1000000L
717#endif
718
719
720 /*************************************************************************/
721 /*************************************************************************/
722 /**** ****/
723 /**** T Y P E 1 D R I V E R C O N F I G U R A T I O N ****/
724 /**** ****/
725 /*************************************************************************/
726 /*************************************************************************/
727
728
729 /*************************************************************************/
730 /* */
731 /* T1_MAX_DICT_DEPTH is the maximum depth of nest dictionaries and */
732 /* arrays in the Type 1 stream (see t1load.c). A minimum of 4 is */
733 /* required. */
734 /* */
735#define T1_MAX_DICT_DEPTH 5
736
737
738 /*************************************************************************/
739 /* */
740 /* T1_MAX_SUBRS_CALLS details the maximum number of nested sub-routine */
741 /* calls during glyph loading. */
742 /* */
743#define T1_MAX_SUBRS_CALLS 16
744
745
746 /*************************************************************************/
747 /* */
748 /* T1_MAX_CHARSTRING_OPERANDS is the charstring stack's capacity. A */
749 /* minimum of 16 is required. */
750 /* */
751 /* The Chinese font MingTiEG-Medium (CNS 11643 character set) needs 256. */
752 /* */
753#define T1_MAX_CHARSTRINGS_OPERANDS 256
754
755
756 /*************************************************************************/
757 /* */
758 /* Define this configuration macro if you want to prevent the */
759 /* compilation of `t1afm', which is in charge of reading Type 1 AFM */
760 /* files into an existing face. Note that if set, the T1 driver will be */
761 /* unable to produce kerning distances. */
762 /* */
763#undef T1_CONFIG_OPTION_NO_AFM
764
765
766 /*************************************************************************/
767 /* */
768 /* Define this configuration macro if you want to prevent the */
769 /* compilation of the Multiple Masters font support in the Type 1 */
770 /* driver. */
771 /* */
772#undef T1_CONFIG_OPTION_NO_MM_SUPPORT
773
774
775 /*************************************************************************/
776 /* */
777 /* T1_CONFIG_OPTION_OLD_ENGINE controls whether the pre-Adobe Type 1 */
778 /* engine gets compiled into FreeType. If defined, it is possible to */
779 /* switch between the two engines using the `hinting-engine' property of */
780 /* the type1 driver module. */
781 /* */
782/* #define T1_CONFIG_OPTION_OLD_ENGINE */
783
784
785 /*************************************************************************/
786 /*************************************************************************/
787 /**** ****/
788 /**** C F F D R I V E R C O N F I G U R A T I O N ****/
789 /**** ****/
790 /*************************************************************************/
791 /*************************************************************************/
792
793
794 /*************************************************************************/
795 /* */
796 /* Using CFF_CONFIG_OPTION_DARKENING_PARAMETER_{X,Y}{1,2,3,4} it is */
797 /* possible to set up the default values of the four control points that */
798 /* define the stem darkening behaviour of the (new) CFF engine. For */
799 /* more details please read the documentation of the */
800 /* `darkening-parameters' property (file `ftdriver.h'), which allows the */
801 /* control at run-time. */
802 /* */
803 /* Do *not* undefine these macros! */
804 /* */
805#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_X1 500
806#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y1 400
807
808#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_X2 1000
809#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y2 275
810
811#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_X3 1667
812#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y3 275
813
814#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_X4 2333
815#define CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y4 0
816
817
818 /*************************************************************************/
819 /* */
820 /* CFF_CONFIG_OPTION_OLD_ENGINE controls whether the pre-Adobe CFF */
821 /* engine gets compiled into FreeType. If defined, it is possible to */
822 /* switch between the two engines using the `hinting-engine' property of */
823 /* the cff driver module. */
824 /* */
825/* #define CFF_CONFIG_OPTION_OLD_ENGINE */
826
827
828 /*************************************************************************/
829 /*************************************************************************/
830 /**** ****/
831 /**** P C F D R I V E R C O N F I G U R A T I O N ****/
832 /**** ****/
833 /*************************************************************************/
834 /*************************************************************************/
835
836
837 /*************************************************************************/
838 /* */
839 /* There are many PCF fonts just called `Fixed' which look completely */
840 /* different, and which have nothing to do with each other. When */
841 /* selecting `Fixed' in KDE or Gnome one gets results that appear rather */
842 /* random, the style changes often if one changes the size and one */
843 /* cannot select some fonts at all. This option makes the PCF module */
844 /* prepend the foundry name (plus a space) to the family name. */
845 /* */
846 /* We also check whether we have `wide' characters; all put together, we */
847 /* get family names like `Sony Fixed' or `Misc Fixed Wide'. */
848 /* */
849 /* If this option is activated, it can be controlled with the */
850 /* `no-long-family-names' property of the pcf driver module. */
851 /* */
852/* #define PCF_CONFIG_OPTION_LONG_FAMILY_NAMES */
853
854
855 /*************************************************************************/
856 /*************************************************************************/
857 /**** ****/
858 /**** 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 ****/
859 /**** ****/
860 /*************************************************************************/
861 /*************************************************************************/
862
863
864 /*************************************************************************/
865 /* */
866 /* Compile autofit module with CJK (Chinese, Japanese, Korean) script */
867 /* support. */
868 /* */
869#define AF_CONFIG_OPTION_CJK
870
871 /*************************************************************************/
872 /* */
873 /* Compile autofit module with fallback Indic script support, covering */
874 /* some scripts that the `latin' submodule of the autofit module doesn't */
875 /* (yet) handle. */
876 /* */
877#define AF_CONFIG_OPTION_INDIC
878
879 /*************************************************************************/
880 /* */
881 /* Compile autofit module with warp hinting. The idea of the warping */
882 /* code is to slightly scale and shift a glyph within a single dimension */
883 /* so that as much of its segments are aligned (more or less) on the */
884 /* grid. To find out the optimal scaling and shifting value, various */
885 /* parameter combinations are tried and scored. */
886 /* */
887 /* This experimental option is active only if the rendering mode is */
888 /* FT_RENDER_MODE_LIGHT; you can switch warping on and off with the */
889 /* `warping' property of the auto-hinter (see file `ftdriver.h' for more */
890 /* information; by default it is switched off). */
891 /* */
892#define AF_CONFIG_OPTION_USE_WARPER
893
894 /*************************************************************************/
895 /* */
896 /* Use TrueType-like size metrics for `light' auto-hinting. */
897 /* */
898 /* It is strongly recommended to avoid this option, which exists only to */
899 /* help some legacy applications retain its appearance and behaviour */
900 /* with respect to auto-hinted TrueType fonts. */
901 /* */
902 /* The very reason this option exists at all are GNU/Linux distributions */
903 /* like Fedora that did not un-patch the following change (which was */
904 /* present in FreeType between versions 2.4.6 and 2.7.1, inclusive). */
905 /* */
906 /* 2011-07-16 Steven Chu <steven.f.chu@gmail.com> */
907 /* */
908 /* [truetype] Fix metrics on size request for scalable fonts. */
909 /* */
910 /* This problematic commit is now reverted (more or less). */
911 /* */
912/* #define AF_CONFIG_OPTION_TT_SIZE_METRICS */
913
914 /* */
915
916
917 /*
918 * This macro is obsolete. Support has been removed in FreeType
919 * version 2.5.
920 */
921/* #define FT_CONFIG_OPTION_OLD_INTERNALS */
922
923
924 /*
925 * This macro is defined if native TrueType hinting is requested by the
926 * definitions above.
927 */
928#ifdef TT_CONFIG_OPTION_BYTECODE_INTERPRETER
929#define TT_USE_BYTECODE_INTERPRETER
930
931#ifdef TT_CONFIG_OPTION_SUBPIXEL_HINTING
932#if TT_CONFIG_OPTION_SUBPIXEL_HINTING & 1
933#define TT_SUPPORT_SUBPIXEL_HINTING_INFINALITY
934#endif
935
936#if TT_CONFIG_OPTION_SUBPIXEL_HINTING & 2
937#define TT_SUPPORT_SUBPIXEL_HINTING_MINIMAL
938#endif
939#endif
940#endif
941
942
943 /*
944 * Check CFF darkening parameters. The checks are the same as in function
945 * `cff_property_set' in file `cffdrivr.c'.
946 */
947#if CFF_CONFIG_OPTION_DARKENING_PARAMETER_X1 < 0 || \
948 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X2 < 0 || \
949 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X3 < 0 || \
950 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X4 < 0 || \
951 \
952 CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y1 < 0 || \
953 CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y2 < 0 || \
954 CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y3 < 0 || \
955 CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y4 < 0 || \
956 \
957 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X1 > \
958 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X2 || \
959 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X2 > \
960 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X3 || \
961 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X3 > \
962 CFF_CONFIG_OPTION_DARKENING_PARAMETER_X4 || \
963 \
964 CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y1 > 500 || \
965 CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y2 > 500 || \
966 CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y3 > 500 || \
967 CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y4 > 500
968#error "Invalid CFF darkening parameters!"
969#endif
970
971FT_END_HEADER
972
973
974#endif /* FTOPTION_H_ */
975
976
977/* END */
978