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

Re: fonts used by evince



On Tue, 12 Jun 2012 01:10:59 +0100, Brian wrote:

> On Mon 11 Jun 2012 at 20:59:23 +0000, Camaleón wrote:
> 
>> On Mon, 11 Jun 2012 19:14:09 +0100, Brian wrote:
>>
>>> As I have described I have no problem seeing the pdf as its maker
>>> intended.
>  
>> Neither I have it in wheezy but in lenny the two sample PDF files
>> render with the wrong character. In both systems I have "symbol.ttf"
>> installed under the same path ("/usr/local/share/fonts/*.ttf").
> 
> The only symbol.ttf I can find in Wheezy at
> 
>    http://www.debian.org/distrib/packages
> 
> is in the libwine package. Is that the correct file? I hope so, because
> I went to a lot of trouble to download and install it. :)

I hope you did not install "libwine" just to test this (you can download 
the .deb file and grabb only the required file).

I'm using the original Windows TrueType fonts (what I always do is copy/
paste the fonts from my Windows machine to my Linux systems) but well, 
for our purpose we can expect that both "symbol.ttf" files (libwine and 
windows) are the same :-)

> Bad news: libwine has symbol.ttf in /usr/share/wine/fonts and the OP's
> pdf displays mu, as it should.
> 
> Good news (maybe): moving symbol.ttf to /usr/share/fonts reproduces the
> OP's problem - mu is displayed as a proportionality symbol.

For this I can't tell, the OP will have to confirm.

> I may as well throw in something I came across earlier today:
> 
>    https://bugzilla.redhat.com/show_bug.cgi?id=700729

I experience the same problem with the mentioned PDF in the above bug 
(using lenny and the windows symbol.ttf font by default).

> But this is a different distribution and, in any case, the location of
> the Debian wine fonts doesn't affect the pdf. The OP needs to move files
> out of the fonts directory to isolate the cause. 

Yes, I would start from there: moving "symbol.ttf" (if present) or 
listing all the symbol fonts he has in the system and placing them in a 
different place other than the usual, one by one and testing each time.

> Either that or, as a way of working round it, use mupdf, which has the
> fonts compliled into the binary.

Then "mu" does the same as Acrobat Raeder: it uses its own fonts.

Greetings,

-- 
Camaleón


Reply to: