|
Home of the Electronic EULA Abstract |
 |
 |
 |
|
The EEULAA website is devoted to working towards a computerized form of the EULA (End User License Agreement), Personalization, and designer recommendations for fonts. For short we're calling this generically an electronic EULA abstract or EEULAA.
 Initially, we hope that this site will enable stakeholders to produce proposals and working prototypes of systems that utilize abstract EULAs. Ultimately, we intend to build these prototypes into real software - font editing tools, websites, operating systems, and applications.
You can see the current thinking on the Permissions fields, Personalization Fields, and Recommendations fields on their respective pages.
|
|
Last Updated on Sunday, 22 November 2009 00:04 |
|
Read more...
|
|
Call for Public Comment
As of 23 November 2009 we have a second draft of the specifications for the EPAR table. You can see the proposed datafields on the Permissions, Personalization and Recommendations pages. We're soliciting public comments, so if you have an opinion about what should be included, excluded, or changed please let us know by email to
This e-mail address is being protected from spambots. You need JavaScript enabled to view it
. Or write your comments in the wiki for everyone to see. |
|
Last Updated on Sunday, 22 November 2009 00:18 |
|
|
 Font embedding refers to technology that saves fonts (or subsets of fonts) inside document files. The aim of this is that recipients of the document can see it as it was designed, without having to have the fonts already installed on their computer. The benefits for publishers are obvious.:
Restrictions on embedding
For many years it has concerned type designers and foundries that font embedding entails their data moving, inside documents, to places where it is not licensed. It has not been possible to assure foundries that font data is not extractable from documents containing embedded fonts.
Embedding bits
Around 1991 Microsoft extended the TrueType specification to allow font developers to specify under what conditions their fonts may be embedded inside documents. At that time, before the web and mass use of e-mail, it was probably thought that documents would not often travel widely. Thus the first form of the specification does not offer much control to font developers. For more, see embedding bits.
|
|
Read more...
|
|
|
