From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: HTML-Info design Date: Mon, 29 Dec 2014 18:04:57 +0200 Message-ID: <83iogujvbq.fsf@gnu.org> References: <87ioh4nf8k.fsf@ferrier.me.uk> <83y4pzptpx.fsf@gnu.org> <871tnr1gqo.fsf@ferrier.me.uk> <83bnmvowdb.fsf@gnu.org> <83ppbanqhe.fsf@gnu.org> <87vbl2xigp.fsf@ferrier.me.uk> <83ioh2nlow.fsf@gnu.org> <87sig6xech.fsf@ferrier.me.uk> <83fvc5ni0u.fsf@gnu.org> <87k31fwwyv.fsf@ferrier.me.uk> <87bnmq9ibf.fsf@ferrier.me.uk> <87lhlrx5fc.fsf@building.gnus.org> <878uhrcr5l.fsf@building.gnus.org> <83sifzjflk.fsf@gnu.org> <87fvbyagaw.fsf@building.gnus.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1419869166 12657 80.91.229.3 (29 Dec 2014 16:06:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 29 Dec 2014 16:06:06 +0000 (UTC) Cc: stephen@xemacs.org, rms@gnu.org, monnier@iro.umontreal.ca, nferrier@ferrier.me.uk, emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 29 17:05:57 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Y5cpL-0005Ht-5R for ged-emacs-devel@m.gmane.org; Mon, 29 Dec 2014 17:05:51 +0100 Original-Received: from localhost ([::1]:33831 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y5cpK-0003Ld-Ih for ged-emacs-devel@m.gmane.org; Mon, 29 Dec 2014 11:05:50 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51073) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y5coo-0003Gy-49 for emacs-devel@gnu.org; Mon, 29 Dec 2014 11:05:22 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y5coi-00050y-Hv for emacs-devel@gnu.org; Mon, 29 Dec 2014 11:05:18 -0500 Original-Received: from mtaout23.012.net.il ([80.179.55.175]:45729) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y5coi-0004zC-At; Mon, 29 Dec 2014 11:05:12 -0500 Original-Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0NHC00400PNK7000@a-mtaout23.012.net.il>; Mon, 29 Dec 2014 18:05:11 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NHC004PCQ0M4U50@a-mtaout23.012.net.il>; Mon, 29 Dec 2014 18:05:11 +0200 (IST) In-reply-to: <87fvbyagaw.fsf@building.gnus.org> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.175 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:180839 Archived-At: > From: Lars Ingebrigtsen > Cc: stephen@xemacs.org, emacs-devel@gnu.org, monnier@iro.umontreal.ca, nferrier@ferrier.me.uk, rms@gnu.org > Date: Mon, 29 Dec 2014 11:41:59 +0100 > > > What's non-pretty with how we do this now? What features are missing? > > We don't know (before redisplay) how wide a piece of text is, so we > can't fill the text. This makes it impossible to use proportional fonts > in common layouts like > > first column with second column with > some flowing text here some other text > here Not sure why you say "impossible". First, to align the right-hand pane of the text you could use '(space :align-to HPOS)' display spec after each line of the text on the left-hand pane. Granted, that might waste some screen real estate, since you would need to be conservative about the amount of text you put in the left-hand pane, to avoid overrunning the right-hand pane. So a capability to know the display width in advance is indeed desirable. Fortunately, such a capability already exists, I think: see the function 'font-get-glyphs'. Does it solve your problem? If not, what API would you like to have? In any case, I don't think Info manuals use such a layout, at least not yet, so it's not a show-stopper.