Minutes of the UPDF Working Group Meeting
July 10, 2000

Meeting Attendees
Mark VanderWiele	IBM
Roderick Acosta		AFGA
Norbert Schade		Oak Technology
Tom Hastings		Xerox (partly)

Although Bitstream was not present in the meeting, Shawn Flynn met with Norbert 
Schade for half a day at Oak right before the meeting to provide Bitstream’s input.

The whole meeting was determined to the specification of device font handling, 
where download was not yet part of it. So we concentrated all our efforts on device 
resident fonts.

The base for the discussion was a new version of the device font specification 
document and a chart of the element structure created from the corresponding DTD 
file. Both documents have been made public to the UPDF group before the meeting.

Major items discussed
? Modifying attributes implemented inside the device resident font section or 
outside to be able to use it for download, too?
Decision: cross-functional
? Discuss the way fixed pitch, proportional and mixed spacing fonts (like in the 
Asian market) will be supported.
? Subfonts have been discussed in detail.
FontIDs must be unique within a FontVendor.
The FontVendor will be a parameter when referencing to a subfont.
? Discuss the way lines like Underline shall be handled.
? Decide on Panose as the only useful font classification available.
? Make metrics names more Windows independent.
? How are resident fonts scaled in a printer driver?
? Kerning will be restricted to Kerning pairs until further requirement from driver 
developers.
? The Parameter converter was considered the right idea to get the necessary 
flexibility for formulas and other needs for field input.
The parameter list may be extended over time.

Open items
? User defined character set handling
Major components are defined, but this section is not finished.
? Character substitution table must be specified more in detail including the 
expected driver behavior.
Will there be an operating system default substitution table?
? We generally agreed the operating system character sets seem to be the right 
collection tables. This needs further discussion.
Where will all the tables come from?
? Eventhandlers have to be discussed more in detail.
There will be Pre-conditions, Events and Post-conditions.

Road map for the near future
? Font download is not on the list for the next months.
? We think about Asian fonts, whereever necessary to solve the problems as early 
as possible. Any input appreciated. The problem will be solved completely at a 
later time.
? Implement all comments into the specification document and the DTD file.
Schedule: end of July
? Contact Adobe.
Will they provide their fonts in the Universal Device Font Description Format?
Schedule: end of July
? Contact Apple.
How are fonts implemented in their operating system?
Schedule: end of July
? Work on attributes of elements to specify the allowed parameters.
Schedule: partly done til Chicago. Fill remaining attributes with dummies to 
provide a complete set for testing. Will be edited later.
? Create at least one sample XML file for device resident font with AGFA and at 
least one with Bitstream.
Schedule: have it ready for Chicago. Discuss problems in Chicago.
? Prepare detailed project planning for AGFA and Bitstream for Universal Device 
Font Description Format export from their internal font database.
Discuss necessary input parameters.
Schedule: discussion in Chicago.
? Think about the chance of any kind of a sample implementation of the sample 
XML font files in a driver.
Schedule: discussion in Chicago.
? Solve remaining problems with Asian fonts.
Schedule: UPDF meeting in Hawaii.