From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Printing Date: Mon, 30 Mar 2009 21:04:37 +0200 Message-ID: References: <5f0660120903280331y780c80b7i57a8115dc4b029eb@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1238440362 7121 80.91.229.12 (30 Mar 2009 19:12:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 30 Mar 2009 19:12:42 +0000 (UTC) Cc: rms@gnu.org, cmr.pent@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 30 21:14:00 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LoMuT-0005xs-NT for ged-emacs-devel@m.gmane.org; Mon, 30 Mar 2009 21:12:38 +0200 Original-Received: from localhost ([127.0.0.1]:60924 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LoMt6-0003F5-8v for ged-emacs-devel@m.gmane.org; Mon, 30 Mar 2009 15:11:12 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LoMn5-0002gT-O1 for emacs-devel@gnu.org; Mon, 30 Mar 2009 15:04:59 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LoMn0-0002ae-Uv for emacs-devel@gnu.org; Mon, 30 Mar 2009 15:04:59 -0400 Original-Received: from [199.232.76.173] (port=39868 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LoMn0-0002aN-QI for emacs-devel@gnu.org; Mon, 30 Mar 2009 15:04:54 -0400 Original-Received: from mail-fx0-f166.google.com ([209.85.220.166]:63583) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LoMmm-0003WM-Dx; Mon, 30 Mar 2009 15:04:40 -0400 Original-Received: by fxm10 with SMTP id 10so2015761fxm.42 for ; Mon, 30 Mar 2009 12:04:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=IO7uqq06UHJR0nuP3sLr4km9gEcmo+TQ/CUvRkp/xPY=; b=qqxksLwcfCsL2RMywy1paYde2f19nuj36GMBl/H7/Rz9+m7x6mqoY6J6lUdJur8lCN 5KV/d2FSDw4FUJDItnhOC0z0yuoo9ddn4WxN85C1w9oMxNFZ4j1Z+TL8sba2kCF8EFcw sLf9c2HH4MXAeZC+O18ERDs4f386Mb7X/2B3c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=FKR30vYDa2uKw90k5Kr9qqkEOK23z4ZR+6GHA+mDS0FekFNY9sy9S4L9dllF9IN2dW SLJ++jpJm7Vm4uxjDJyrO2FxV2wybuAYfmWM52eNtcOA7rZkT7aaBg/rJ0vvJSOv1gGi AHxr9PHKpgJ9ETjW+XZ6x2fQ7j0ENZ//l6ntA= Original-Received: by 10.223.105.16 with SMTP id r16mr4308482fao.24.1238439877928; Mon, 30 Mar 2009 12:04:37 -0700 (PDT) In-Reply-To: X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:109924 Archived-At: On Mon, Mar 30, 2009 at 8:41 PM, Eli Zaretskii wrote: >> Date: Mon, 30 Mar 2009 08:36:01 +0200 >> From: Lennart Borgman >> Cc: rms@gnu.org, cmr.pent@gmail.com, emacs-devel@gnu.org >> >> On Mon, Mar 30, 2009 at 5:10 AM, Eli Zaretskii wrote: >> > One way to fix this would be to update our default for >> > ps-mule-font-info-database so that it handles Unicode -- assuming that >> > modern PostScript printers indeed support large subranges of the >> > Unicode codespace. =C2=A0I'm not an expert on printing, so I wouldn't = know >> > if this is possible. >> >> Since printing with Emacs through the web browser (using >> htmlfontify.el) does work it seems like modern printers do support >> this. Or am I missing something? > > You are missing the fact that I was talking about PostScript printing, > not printing via the Windows printer API. I am not sure about that. Could someone who have this problem and have a PostScript printer try printing through the web browser, please?