After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 164843 - GUI to display fonts in document
GUI to display fonts in document
Status: RESOLVED FIXED
Product: evince
Classification: Core
Component: general
git master
Other All
: Normal enhancement
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on: 169583
Blocks:
 
 
Reported: 2005-01-21 18:16 UTC by Ralph Aichinger
Modified: 2005-06-15 09:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
PDF Properties Page (35.11 KB, image/png)
2005-02-22 18:54 UTC, Bryan W Clark
Details

Description Ralph Aichinger 2005-01-21 18:16:11 UTC
The only thing I always missed in gpdf was a 
menu entry to display the fonts used in a document.
I always had to use Adobe Acrobat for this, until
I discovered pdffonts from the xpdf distribution:

client21% pdffonts Downloads/AGaramondPro-Regular.pdf
name                                 type         emb sub uni object ID
------------------------------------ ------------ --- --- --- ---------
EHFHOF+AdobeCorpID-Adobe             Type 1C      yes yes yes     54  0
EHFIEB+AdobeCorpID-MyriadRg          Type 1C      yes yes no      52  0
EHFIHF+00MyriadPro-Bold              Type 1C      yes yes no      64  0
EHFIIL+00MyriadPro-Regular           Type 1C      yes yes no      63  0
EHFIOH+00AGaramondPro-Regular        Type 1C      yes yes yes     69  0
EHFKBF+01AGaramondPro-Regular        Type 1C      yes yes yes     79  0
EHFHEM+TimesNewRoman                 TrueType     yes yes no      59  0
EHFIEB+AdobeCorpID-MyriadRg          Type 1C      yes yes no       7  0
EHFIHF+00MyriadPro-Bold              Type 1C      yes yes no       8  0
EHFNKA+02AGaramondPro-Regular        Type 1C      yes yes yes      9  0
EHFPKA+03AGaramondPro-Regular        Type 1C      yes yes yes     10  0
EHFFLB+TimesNewRoman                 CID TrueType yes yes yes     11  0
EHGAAH+LucidaSansUnicode             TrueType     yes yes no      12  0
EHFIHF+00MyriadPro-Bold              Type 1C      yes yes no      13  0


It would be really cool to have this functionality in the GUI if ever 
evince gets a way to display document metadata. It is often helpful
for diagnosing PDF problems, for finding out what fonts certain
corporations use, etc.
Comment 1 Bryan W Clark 2005-02-08 00:15:09 UTC
If you're interested in developing a patch for this, you can probably use the
code from xpdf for the pdffonts app and combine it with the gpdf property page
viewer to create the document meta-data view.

http://cvs.gnome.org/viewcvs/gpdf/xpdf/nautilus-pdf-property-page.cc?view=auto
Comment 2 Bryan W Clark 2005-02-22 16:59:31 UTC
For anyone who wants to work on this, here's a little bit on how we'd like to
see it implemented.

Create a standard File->Properties menu item
   If there are no properties for the document being viewed this is disabled

OnClick open a small dialog 
  First tab has Author, Title, and all the other information you see in the
nautilus properties page that gpdf has had for a while.  
  Second tab has Fonts used by this document.

Differentiate which fonts this system has that the document is using and which
fonts the system doesn't have which the document wants.  Display Name, Type,
Unicode, Embedded, and Subset.  Make sure the Name is a nice name, not the junk
that pdffonts spits out.
Comment 3 Martin Kretzschmar 2005-02-22 17:11:34 UTC
> nautilus properties page that gpdf has had for a while.

which you won't see in a de-bonobo-ified nautilus ;)

However, if you still have gpdf, there's a nice File->Properties menu item ;-)

The only junk that you can easily remove from pdffonts output is the XXXXXX+
which is prepended to font subsets. (cf. PDF Reference)
Comment 4 Bryan W Clark 2005-02-22 18:54:45 UTC
Created attachment 37796 [details]
PDF Properties Page

A Screenshot of the properties page in case people have abandoned gpdf so
hastily.
Comment 5 Diego González 2005-03-04 10:53:03 UTC
it would also be quite good if some of this information could be modified, for
example: subject, author, title and keywords are clear examples of stuff that
could be modifed.
Comment 6 Bryan W Clark 2005-03-04 16:52:10 UTC
I don't think we're going to go into editing documents, at least I'd rather keep
things (in the programming and interface) as simple as possible by not doing
editing.  There are plenty of other ways to edit and create PDFs, we should
leave it to that.

We're just a simple viewer, no more no less. ;-)
Comment 7 Marco Pesenti Gritti 2005-06-04 13:06:25 UTC
I sent a patch on the poppler list to add initial backend for this...
Comment 8 Marco Pesenti Gritti 2005-06-04 18:08:05 UTC
Initial implementation is in cvs, still defined out until poppler patch lands
Comment 9 Bryan W Clark 2005-06-14 20:06:04 UTC
Isn't this fonts properties tab in CVS now?