Font Fusion FAQ



  1. Who has already licensed Font Fusion?
  2. Why should I license Font Fusion?
  3. Can Font Fusion handle double-byte font data for Chinese, Japanese, and Korean?
  4. Can Font Fusion handle Unicode fonts?
  5. Can I use Font Fusion if my output device is a TV?
  6. Can I use Font Fusion if my output device is a color LCD?
  7. Does Font Fusion support fractional positioning?
  8. What is the Font Fusion porting process like?
  9. What is the Font Fusion API like?
  10. How does Font Fusion support native TrueType hints?
  11. How was the Font Fusion logo created?
  12. What is currently the latest Font Fusion release date?

Q. Who has already licensed Font Fusion?

A. Many leading US and international high technology companies. Contact sales for more information.

Q. Why should I license Font Fusion?

A. Font Fusion is simply the best choice. High quality, high performance, small code size, small font size, robust object oriented architecture and OS independence are not just words to us.

Q. Can Font Fusion handle double-byte font data for Chinese, Japanese, and Korean?

A. Yes. Font Fusion provides multiple language support and has been used with fonts with over 32000 characters!

Q. Can Font Fusion handle Unicode fonts?

A. Yes, without difficulty!

Q. Can I use Font Fusion if my output device is a TV?

A. Yes, absolutely! Font Fusion is ideal for this and it has a special TV-mode with TV specific enhancements resulting in superior quality on the TV screen. (You should use T2K_TV_MODE, or T2K_TV_MODE_2.) Additionally Font Fusion has support for colored antialiased borders.

Q. Can I use Font Fusion if my output device is a color LCD?

A. Yes, absolutely! Font Fusion is ideal for this and it has a special LCD option resulting in superior quality on the LCD screen. (You should use T2K_LCD_MODE, or T2K_LCD_MODE_2.)

Q. Does Font Fusion support fractional positioning?

A. Yes, fractional positioning should be used with rotated text.

Q. What is the Font Fusion porting process like?

A. You just need to configure Font Fusion through a ".H file" and then compile with your C or C++ compiler. We think "Porting" is a dirty word. You should never have to change a single line of our ANSI C code in order to get Font Fusion to work with your OS and processor.

Q. What is the Font Fusion API like?

A. The Font Fusion API is simple, logical, object oriented and easy to use :-)

Q. How does Font Fusion support native TrueType hints?

A. It relies on Font Fusion to do everything except the actual TrueType hint byte code interpretation. The TrueType interpreter code (One ".c" file and one ".h" file ) is licensed from Apple Computer, Inc. Basically we use our engineered from scratch Font Fusion as the "body" and then we use the above 2 files as the "heart". This produces the cleanest, and the only object oriented, TrueType rasterizer there is!

Q. How was the Font Fusion logo created?

A. It was drawn directly by Font Fusion itself! Font Fusion is part of the small select group of products capable of drawing its own logo.

Q. What is currently the latest Font Fusion release date?

A. It is version 2.3, released April 2, 2002.


Font Fusion: Home | TrueType Patents Page | White Paper | Contact