Microsoft opentype font file properties extension windows 7

Full Specifications. What's new in version 1. Release August 10, Date Added December 19, Version 1. Operating Systems. Additional Requirements None. Total Downloads Downloads Last Week 1. Report Software. Related Software. NexusFont Free. If a font resource does contain more than one table of a given type, behaviour is unpredictable: apps or platforms may select one of the tables arbitrarily, or may reject the font as invalid. Additional tables and associated tags may be defined to support other platforms.

Some font development tools may also define special tables. Fonts that contain such additional tables can still qualify as OpenType fonts if they satisfy requirements of this specification. For custom tables defined outside this specification, an external specification of such a table may permit multiple tables of that type within a single font resource. When other vendors define custom tags, they should notify Microsoft to ensure forward compatibility in the event of future expansion of OpenType.

All tables must begin on four-byte boundaries, and any remaining space between tables must be padded with zeros. The length of each table should be recorded in the table record with the actual length of data, not the padded length. Note: The requirement for four-byte alignment applies to top-level tables only and does not extend to sub-table offsets, records, or fields within tables or records.

Some tables have an internal structure with subtables located at specified offsets, and as a result, it is possible to construct a font with data for different tables interleaved. In general, top-level tables should be arranged contiguously without overlapping the ranges of distinct tables. In any case, however, table lengths measure a contiguous range of bytes that encompasses all of the data for a table.

This applies to any subtables as well as to top-level tables. Table checksums are the unsigned sum of the uint32 units of a given table. In C, the following function can be used to determine a checksum:. Note: This function assumes that the length of any table is a multiple of four bytes, or that tables are padded with zero to four-byte aligned offsets. Actual table lengths recorded in the TableDirectory should not include padding, however.

To accommodate data with a length that is not a multiple of four, the above algorithm must be modified to treat the data as though it contains zero padding to a length that is a multiple of four. When generating font data, to calculate and write the 'head' table checksum and checksumAdjustment field, do the following:.

An application attempting to verify that the 'head' table has not changed should calculate the checksum for that table assuming the checksumAdjustment value is zero, rather than the actual value in the font, before comparing the result with the 'head' table record in the table directory.

Within a font collection file see below , table checksums must reflect the tables as they are in the collection file. The checksumAdjustment field in the 'head' table is not used for collection files and may be set to zero. The format for font collections allows font tables that are identical between two or more fonts to be shared.

By allowing multiple fonts to share glyph sets and other common font tables, font collections can result in a significant saving of file space. For example, a group of Japanese fonts may each have their own designs for the kana glyphs, but share identical designs for the kanji. With ordinary OpenType font files, the only way to include the common kanji glyphs is to copy their glyph data into each font.

Since the kanji represent much more data than the kana, this results in a great deal of wasteful duplication of glyph data. Font collections were defined to solve this problem. Note: Even though the original definition of a Font Collection as part of the TrueType specification was intended to be used with fonts containing TrueType outlines, and this constraint was maintained in earlier OpenType versions, this is no longer a constraint in OpenType.

Font collection files may contain various types of outlines or a mix of them , regardless of whether or not fonts have layout tables present. Note: An OpenType variable font is functionally equivalent to multiple non-variable fonts. Variable fonts do not need to be contained within a collection file.

A collection file can include one or even multiple variable fonts, however, and may even combine variable and non-variable fonts. A font collection file consists of a single TTC Header table, one or more Table Directories each corresponding to a different font resource , and a number of OpenType tables.

The TTC file must contain a complete table directory for each font resource. The same TableDirectory format is used for each font in a collection file as in a non-collection file. OpenType fonts can also include typographic refinements such as true small caps, different styles of figures, and extensive sets of ligatures and alternates, as well as complete sets of accented characters and diacritical marks.

Different applications have differing levels of support for all the OpenType features. OpenType version 1. The standard was published in , and is now freely available for download from ITTF website. The Type 1 data can be rasterized by a Type 1 rasterizer such as Adobe Type Manager if installed, or converted to TrueType data for rasterization by the TrueType rasterizer.

The exact rasterization behavior will be a function of the rasterizers present in the system, and user preference. This font format is a superset of the existing TrueType and Type 1 formats, which is designed to provide great support for type in print and on-screen.

In addition, the subsetting and compression technology of OpenType makes the OpenType initiative especially relevant to the Internet and the World Wide Web, since it allows for fast download of type.

So far as customers are concerned, fonts just work. OpenType handles all fonts with a unified registry, which means that both Type 1 and TrueType fonts will be reliably supported across all platforms. In addition, by working together Adobe and Microsoft will drive innovations in quality and on-screen support, resulting in better more viewable fonts for customers.

Was this reply helpful? Yes No. Sorry this didn't help. Thanks for your feedback. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse.