| Summary: | show fonts used in PS/PDF-file in metainfo tag | ||
|---|---|---|---|
| Product: | [Applications] kfile-plugins | Reporter: | Joerg de la Haye <haye> |
| Component: | ps | Assignee: | Carsten Pfeiffer <pfeiffer> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | wishlist | CC: | bradh, luis |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Joerg de la Haye
2003-06-25 16:34:53 UTC
I've looked at using a new feature in Poppler, but under some circumstances this may take a very long time (several minutes). Would it be enough to sample the first few pages? Unfortunately not for professional use. And that's where this feature is mostly needed. The average user isnt really interested in which fonts are in there. And a professional user needs to be *sure* which fonts are in there and which not. Mistakes here can be expensive in production later. So guessing from the first pages is not really an option IMO. Fonts can quite often appear later in a document. Take for example back pages or pages between chapters. They often have a different design, sometimes using different/additional fonts and appear later in a document. When I hover over a movie file for example there is first no thumbnail but the other information is there. After some time the missing thumbnail appears. Cant some kind of delay mechanism be applied here? I agree with Comment #2, it isn't enough to sample the first pages only. But I can't imagine that this is too hard to implement. For pdf-files you should have a look at the command line tool "pdffonts" which is part of the xpdf utilities. It shows all the fonts used inside a pdf, and it gives you a fairly quick output, even if it is a larger file (I've tested it with a 5,3 MB pdf containing text and several images on 265 pages). I'm not sure how to solve it for ps-files, but if you create a ps within KDE (e.g. a text with koffice) and use an editor to a look at the new ps-file there's a postscript tag "DocumentFonts" which lists all the fonts used in the given document. I have played with it within poppler, and it isn't going to be very hard (except that sometimes the font labels are a bit strange, not sure why). But it is slow - 25 seconds on my 1.2GHz laptop to extract the fonts from the PDF specification. That is a lot of stuff to work through in a directory of PDF files... I'd be happier doing it inside KPDF. Note that I haven't looked at the Postscript issues at all - I'm just considering the PDF part first. As poppler is based on xpdf it should be nearly the same code as used in the pdffonts-tool, I guess. Maybe you're right and it makes more sense to implement that font function as a part of the document properties in KPDF than to put it in a metainfo tag. You are right in that it is nearly the same code. However pdffonts is also quite slow. If you are happy just to have that functionality in KPDF, then please close this wishlist item. I'm closing this wishlist item, as it seems to be not so easy to implement it in a metainfo tag and kpdf already gives you the font information. |