But PDF is only used for rendering, which is permissible by most font embedding licenses.
For .ora, however, the expectation is to use those fonts for editing (the text) and that's NOT permissible by such licenses. It's why Adobe Acrobat (and other PDF tools) require you to have the font installed in the OS to be able to edit text in a PDF - even if the font is embedded. It may be that "libre fonts" are configured to allow "edit embedding" (as defined in the permissions bits of the TTF/OTF format) - but that means users wouldn't be able to use the fonts that come with platforms such as Mac OS X or Windows as those definitely aren't set as such. As we discussed at the meeting - I strongly recommend you don't go down this path and simply assume/expect that the font is installed. Leonard On Fri, May 28, 2010 at 1:56 AM, Marcos Diaz <[email protected]> wrote: > About text layer fonts (maybe someone touched this topic in the BOF and I > missed it) it's possible to include the used fonts as a .ttf files into the > .ora?, I think .pdf works in this way (because I never seen a font issue > with .pdf files), I know this could imply some licensing issues... well, > this raises other kind of philosophical discussion: > > "Should the OpenRaster spec ensure the users are working only with libre > stuff?" > > Additionally, it's possible to set up a central database with blacklisted > fonts to advice the user he is saving a document with non-libre fonts? maybe > this could disable some metadata-license options... BTW is the > metadata-license field just text? > > > -- > Marcos Díaz <[email protected]> > Nathive project developer > http://www.nathive.org/ > > _______________________________________________ > CREATE mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/create > >
_______________________________________________ CREATE mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/create
