| Q: | How are browsers without support
for "embedded fonts" handled? |
| A: | Even browsers that do not support
font embedding are fully supported. Web pages are partially formatted on
the server and text set in non-standard fonts
are transmitted as images to these browsers. |
| Q: | Is there a visual difference
between pages viewed by browsers that support font embedding and
those that do not? |
| A: | No, there would be no difference.
Page layout is identical regardless of how the text on a page is being rendered by a browser.
|
| Q: | Does FAIRY support grayscale fonts? |
| A: | Yes, grayscale fonts (also known as "antialiased"
or "smooth" fonts) are supported, regardless of if a browser supports font
embedding or not.
|
| Q: | Is FAIRY related to
Microsoft WEFT? |
| A: | We developed both applications.
WEFT is a tool that is used to create fonts for specific web pages,
while FAIRY is a complete solution for presenting
formatted text of any language on the Internet.
We have also worked on the core font embedding functionality
in the Windows operating systems, used by Microsoft Office and IE. |
| Q: | What is the difference in speed
between browsers that support font embedding and those that do not? |
| A: | Performance depends on network
bandwidth, computer CPU speed, disk speed, and other factors.
Browsers that support font embedding may or may not be faster
than browsers that do not support these fonts. |
| Q: | Does FAIRY degrade the performance
of the web server that is hosting FAIRY? |
| A: | No, not typically. For some pages,
it will boost the performance as FAIRY is able to make smarter and
more optimal choices about encoding formats and font formats than a
human would. Also, FAIRY will produce compressed web page pages
that support the Content-Encoding:gzip part of the HTTP/1.1 protocol.
Processed page are thus much smaller than the original page. |
