$Header: /home/benavrhm/RCS/fonts.txt,v 1.11 2003/02/10 10:12:32 benavrhm Exp benavrhm
$
Requirements for Star Office Fonts
Jonathan Ben-Avraham <[EMAIL PROTECTED]>
January 28, 2003
Edited by Ilko Hoepping on January, 29th, 2003
Incorporating comments from Herbert Duerr, February 4, 2003
1. Introduction
This document is intended for font vendors who wish to provide fonts for Sun
Microsystem's Star Office and Open Office products.
This document covers technical specifications for Star Office fonts only. It
does not cover licensing issues between Sun Microsystems and font vendors.
The fonts that Sun requires differ from fonts that vendors normally supply to
product developers. This document explains these special requirements and the
reasons for them.
2. General Requirements
This section contains general requirements for all fonts supplied for Star
Office or Open Office.
2.1. Rendering at Small Sizes
We require fonts that support quality rendering at small sizes. The market for
Star Office includes platforms that support TrueType hinting and platforms that
do not. We require all fonts to work equally well both types of platform.
2.1.1 TrueType Hinting
The fonts must allow quality rendering at small sizes from eight to twenty
pixels height by means of TrueType-hints.
2.1.2 Embedded Bitmaps
In order to obtain quality rendering on systems that do not use TrueType
hinting, Star Office requires fonts with pre-rendered glyphs in the fonts.
We call these glyphs "embedded bitmaps". There are various strategies that
the font vendor can use to create pre-rendered glyphs. For example, it is
possible to render a TrueType hinted font in the pixel sizes that Star Office
requires on a reference system using TrueType hinting and then copy the
rendered images back into the font.
All fonts must have have pre-rendered glyphs. The glyphs must be embedded
directly into the font file using the standard EBDT and EBLC tables.
The font must have embedded bitmaps for all glyphs from a height of eight
pixels to a height of 20 pixels.
2.2 Font Encoding
All fonts should be Unicode encoded fonts.
2.3 Outline Data
The glyph outline data for all fonts must be in TrueType format.
2.4 Font names
The font file must contain the name of the font in English and also in the
language that the font is intended to support so that the users can use the
native language name of the font when selecting the font from a menu of fonts.
For example, Arabic font files must contain the name of the font in Arabic
characters as well as Latin characters.
3. Specific Requirements
There are two classes of fonts that Sun needs for Star Office;
A. UI Fonts
B. Publishing Fonts
The requirements for these classes are defined in the following subsections.
3.1 UI Fonts
UI fonts are fonts for use in the user interface of Star Office for menus,
dialog boxes, messages and other similar texts.
3.1.1 Star Office and Open Office require only one UI font. Vendors can offer
one or more candidate fonts.
3.1.2 UI fonts should be san serif fonts.
3.1.3 UI fonts must be provided in regular and bold weights.
3.1.4 UI fonts can be either TrueType fonts or OpenType with TrueType outlines.
3.2 Publishing Fonts
Publishing fonts are fonts used in the documents that the user writes using
Star Office or Open Office. Users often use more than one font in a document.
3.2.1 We need a variety families for publishing fonts but this variety must
include the four most commonly used families in Microsoft Office. The names of
these families differ for different languages.
3.2.2 Publishing fonts must be supplied in regular, bold, italic and bold
italic weights.
3.2.3 Publishing fonts must be OpenType fonts with TrueType glyph outlines.
--
EE 77 7F 30 4A 64 2E C5 83 5F E7 49 A6 82 29 BA ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- [EMAIL PROTECTED] - tel: +972.2.679.5364, http://www.tkos.co.il -
