Bug 52980 - [pdffonts] Feature request: additional column to indicate disk space consumption of embedded fonts
Summary: [pdffonts] Feature request: additional column to indicate disk space consumpt...
Status: RESOLVED MOVED
Alias: None
Product: poppler
Classification: Unclassified
Component: utils (show other bugs)
Version: unspecified
Hardware: Other All
: medium enhancement
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-30 22:12 UTC by pipitas
Modified: 2018-08-21 11:19 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description pipitas 2012-07-30 22:12:59 UTC 
I was extremely pleased when I discovered the additional column for 'encoding' in the output of 'pdffonts'. Thanks a lot for this recent feature, I really appreciate it  :-)

May I ask for another feature that would fit well into this list?

  * Give additional info about the size of each (embedded)
    font (in bytes or kBytes) as consumed inside the PDF!

This info could frequently be very useful to know, not only for debugging purposes. Users are often interested in knowing how much space is consumed by each resource category in a PDF file. Fonts are one of the most important ones.
Comment 1 Adrian Johnson 2012-07-30 22:30:28 UTC 
The font list is already very long. It may be better to provide an option to enable this. Maybe something like "-extra" (I can't think of a better name right now) that displays Name, Object ID, and Size. This leaves room to add additional columns in future.
Comment 2 pipitas 2012-07-30 23:08:27 UTC 
Ok, if the default listing is already too "wide" to seat an additional column, using a special option '-extra' or '-space' to show this info would be OK with me  :-)
Comment 3 Albert Astals Cid 2012-07-31 21:01:46 UTC 
[off topic]
Kurt is that you?
[/off topic]
Comment 4 pipitas 2012-07-31 23:23:36 UTC 
@comment #3: Yes.  :-)
Comment 5 GitLab Migration User 2018-08-21 11:19:37 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/poppler/poppler/issues/623.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.