16bit hash

["Martin v. Löwis"]

> If the UniqueID is used it must be unique when used in the printer
> (where I cannot control which other UniqueID's might be present).

I don't know much about PostScript; googling around gives

http://fontforge.sourceforge.net/UniqueID.html

that says that you should not use them anymore, and

http://www.adobe.com/devnet/opentype/archives/id.html

says you should not make up values, but officially register them;
a certain range is available for testing without registration;
that should not be used in production mode.

> Luckily the cheap option of not using the UniqueID at all is available,
> but chances are some printer ps interpreter will barf if it's not
> present and then I need a fairly robust way to generate reasonable
> candidates.

See above article. It was always the case that a printer should not
barf; it just might have to re-render all glyphs. However, it seems
that today's printers have advanced caching, making the mechanism
irrelevant.

Regards,
Martin