[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: fonts used by evince



On Sun, 10 Jun 2012 19:44:12 +0200, Paul Seyfert wrote:

> On 10.06.2012 17:27, Camaleón wrote:
 
>> Not embedding the fonts is a problem if you are planing to redistribute
>> a document that uses mathematical symbols. In such cases, is better to
>> include the fonts in the document although doing so will increase the
>> resulting file size.
> 
> actually I have no idea how to tell cernroot to embed fonts. anyhow i
> definitely cannot force all other root users to always embed fonts. So
> even if I embed fonts the problem will reappear when I get files from
> collaborators.

I don't know about that application ("cernroot") so I can't tell how to 
configure the output to force the fonts embedding. I know this can be 
done from GS tools (ps2pdf) or another dedicated PDF programs such pdftk, 
but what I use most is OOo Writer and exporting as PDF/A-1 which seems to 
force all the fonts are embedded in the resulting file.

>> I also get the wrong characters (infinite symbol "∞" instead micro "µ")
>> in Evince.
>> 
>>> name                                 type              emb sub uni
>>> object ID
>> (...)
>>> ZapfDingbats                         Type 1            no  no no 20  0
>> 
>> The only tipography I don't have installed in my system is
>> "ZapfDingbats" and this font is included within Acrobat Reader. This
>> can be problem here.
> 
> okay. do you know where I could get it from? is there a package with
> ZapfDingbats or can I get it from the acroread directories?

Some fonts are not for free (free → cost). Anyway, I already have 
"Dingbats" installed in my systems (I can see it available from OOo 
Writer). This font should be enough as a replacement.

> something else which came to my mind: is there a way to tell a missing
> font from having a wrong font?

Yes, it is explained in the bug report I pointed before.

>> Tip: if you don't want to embed the fonts, try using unicode symbols
>> instead using specific font foundries.
> 
> hm, this I could try. But again that would only fix the creation part of
> the pdf files. I'm more focussed on the displaying part of the problem.
> i.e. I want to be able to display this specific type of fontless pdf
> with exactly the fonts used in there (official collaboration style /
> corporate design / ...).

Then you'll have to deal with a proper font substitution in your system.

>> Evince should use the available font paths which are defined in
>> "/etc/fonts/fonts.conf". You can be hitting:
> 
> the fonts.conf on the debian machine (where evince doesn't find the
> font) and the ubuntu machine (where evince finds the font) are
> identical. however I'm still searching for something conclusive in the
> included conf.d directories. all entries with zapf are the same on both
> systems.

I wonder if the *Dingbats is the real problem here. If you had access to 
the original document you can ensure the symbols that display wrongly are 
infact using the ZapfDingbats fonts. I think so but is just to be sure.

>> https://bugs.freedesktop.org/show_bug.cgi?id=21395#c6
> 
> This fix is already in my fonts.conf

You mean you already had a "~/.fonts.conf" file created in your home 
profile with the required data on it? The bug recommends adding:

<alias binding="same">
   <family>ZapfDingbats</family>
   <accept><family>Dingbats</family></accept>
 </alias>

Is that what you have and is not working? :-?

Greetings,

-- 
Camaleón


Reply to: