From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Haines Brown Newsgroups: gmane.emacs.help Subject: Re: Windows: changing (bitmap) font causes set-face-attribute error Date: Thu, 18 Nov 2010 15:40:20 -0500 Message-ID: <87ipzul617.fsf@engels.HistoricalMaterialism.info> References: <2f2d0199-bf61-450f-8c27-f6d0b9d18484@d8g2000yqf.googlegroups.com> <36ed0696-5e99-483a-9c94-f656414109ca@32g2000yqz.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1291948735 18046 80.91.229.12 (10 Dec 2010 02:38:55 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 10 Dec 2010 02:38:55 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Dec 10 03:38:50 2010 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PQssi-0006WW-NN for geh-help-gnu-emacs@m.gmane.org; Fri, 10 Dec 2010 03:38:49 +0100 Original-Received: from localhost ([127.0.0.1]:44978 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PQssh-0005RS-D4 for geh-help-gnu-emacs@m.gmane.org; Thu, 09 Dec 2010 21:38:47 -0500 Original-Path: usenet.stanford.edu!postnews.google.com!news1.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail Original-NNTP-Posting-Date: Thu, 18 Nov 2010 14:41:49 -0600 Original-Newsgroups: gnu.emacs.help User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) Cancel-Lock: sha1:G5tE2IqSavHUqDQueN4RLNfNXrc= Original-Lines: 25 X-Usenet-Provider: http://www.giganews.com Original-X-Trace: sv3-HhtO6PsPCnr8FAb/RAjBAnwo87RCbBY2OkeSd1UPra+jgjdyBS+N3H0yAkHZ5LQmR/v39PAfBRy6l8/!oF7I5r2gHvZPghdmOOv4duQUIsPT/By9OeuauotwLeK4j5O1xIlFxoeDttXlzZZn+/UWzHj67Lk= Original-X-Complaints-To: abuse@giganews.com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 2249 Original-Xref: usenet.stanford.edu gnu.emacs.help:182525 X-Mailman-Approved-At: Thu, 09 Dec 2010 20:09:03 -0500 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:77214 Archived-At: Elena writes: > Running the font through FontForge (on Linux) fixed the issue. Elena, thanks, but I'm too ignorant to understand your suggestion. First, what font? Are there certain fonts which emacs uses to display a pdf file? How would I know what they are? Is emacs for some reason converting TrueType fonts to bitmaps without anti-aliasing? If this a single font like Times New Roman, or is a collection of fonts, like all TrueType fonts? Fontforge serves to convert font formats. What format do I need to convert from and to? If these were not questions enough, I'd still like to know what is going on. your answer implies that my problem with PDF fonts is a known issue, or at leat it is known to you. What is the cause of the problem? Is it associated with the migration from emacs 22 to 23? Why does the initial page of a PDF look fine, but the remaining pages are almost illegible? Is my problem that the font used is not anti-aliased? If not, why isn't it? Haines Brown