Re: [kde-linux] okular weirdness



Duncan posted on Wed, 26 Aug 2009 07:40:44 +0000 as excerpted:

Meanwhile, I believe it's safe to say it's either a setting in okular,
or some weirdness in your poppler. I suspect some okular setting, but
as you say you tried that and I haven't yet...

I came up with one possible okular setting to check. Under Settings,
Configure Backends, here, I just have Ghostscript, and it has only a
single setting, a Use platform fonts checkbox.

If I'm not mistaken, if that's checked, it'll use fonts on your computer
instead of fonts as they may have shipped in the PDF. If it's unchecked,
it should use fonts from the PDF, which may be different than those on
the computer.

What I'm wondering is if it's using different fonts on the different
computers, and using a really fat one, maybe, on the wide display
computer. Assuming you're using the same backend there, try setting all
computers to unchecked, so they should use what's in the PDF regardless
of what's on the individual computer. In theory, it should then look the
same, because it's using the fonts in the PDF itself.

If that fixes it and it looks different when that checkbox is checked on
all your machines, maybe you have a different font on one of the boxes
that's not on the others, or are missing a font on the one box that IS on
the others. It could also be that you had the box checked in the one
case and unchecked in the other.

Otherwise... I don't know. Just to be sure, check this:

In systemsettings, look and feel, appearance, fonts, at the bottom,
there's a checkbox, Force fonts DPI. You may wish to try that.
Depending on the setting (96 or 120 DPI), it'll make your fonts larger or
smaller, but they should stay the same aspect ratio if your computer is
set for square pixels as when it's disabled. If for some reason your
computer (well, X) thinks your pixels aren't square, it may use a strange
aspect ratio, making your fonts all either tall and thin or short and
fat. But, you said it was only okular, and that would affect at least
all of kde, so I doubt that's it. I /still/ think it has to be either an
okular issue or perhaps a backend issue, but I don't know enough about
pdf to know where to look or what to poke at to try to fix it.

--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman

___________________________________________________
This message is from the kde-linux mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.



Relevant Pages

  • Re: "Save as pdf" re-sizes my Word document.
    ... > get frozen into my .pdf, but the scaling isn't getting frozen in. ... I think you're saying that the look of the Mac fonts don't even ... When printing a PDF the user ...
    (microsoft.public.mac.office.word)
  • Re: Print PDF - the file name convention options
    ... In Acrobat Preferences start with Advanced settings> fonts and take it from ... Word MVP web site http://word.mvps.org ... I'll look into your suggestion about creating ISO19005-1 compliant PDF ...
    (microsoft.public.word.docmanagement)
  • Re: Gnostice eDocEngine
    ... Also on the ssue of embedding unused Truetype fonts, ... Your response in this ng makes me hopeful for the near future, ... > Hello Willem, ... PDF eForms and report export components ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Problems converting PDF to PDF/A with ghostscript
    ... despite the note in Acrobat stating the file is being viewed in PDF/A ... All that measn is that the PDF file contains a PDF/A note in the ... must be complete fonts, so there isn't really any way around that one. ...
    (comp.lang.postscript)
  • Re: Problems converting PDF to PDF/A with ghostscript
    ... despite the note in Acrobat stating the file is being viewed in PDF/A ... All that measn is that the PDF file contains a PDF/A note in the ... must be complete fonts, so there isn't really any way around that one. ...
    (comp.lang.postscript)