From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: RTF import/export emacs (was: New Emacs features via Google Summer of Code (or other similar stipend schemes)) Date: Sun, 18 Aug 2024 21:16:05 +0300 Message-ID: <86y14ty9wa.fsf@gnu.org> References: <87bk20yoya.fsf@dataswamp.org> <86zfpjirkg.fsf@gnu.org> <877ccnj9dp.fsf@localhost> <86bk1zhrf5.fsf@gnu.org> <874j7qkj97.fsf@localhost> <87y152x5v8.fsf@dataswamp.org> <87r0aui7ay.fsf@localhost> <8634nahu9u.fsf@gnu.org> <87bk1xima6.fsf@localhost> <87jzgeyrum.fsf@localhost> <86le0uypnp.fsf@gnu.org> <87ttfixabd.fsf@localhost> <86frr2ymos.fsf@gnu.org> <87a5hax7c1.fsf@localhost> <86a5h9zznj.fsf@gnu.org> <874j7hyk4c.fsf@localhost> <79dc51f6-4c7d-e660-1116-30fa92e2918e@gmail.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3279"; mail-complaints-to="usenet@ciao.gmane.io" Cc: yantar92@posteo.net, acorallo@gnu.org, emacs-devel@gnu.org, stefankangas@gmail.com To: Jim Porter Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Aug 18 20:17:02 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sfkSc-0000ij-1x for ged-emacs-devel@m.gmane-mx.org; Sun, 18 Aug 2024 20:17:02 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sfkRx-00017a-Da; Sun, 18 Aug 2024 14:16:21 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sfkRv-000178-Dl for emacs-devel@gnu.org; Sun, 18 Aug 2024 14:16:19 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sfkRu-00015C-Px; Sun, 18 Aug 2024 14:16:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=ZigdQnYfvCW/HMe8Mr2M5X9RIKloYHzfKf2woLM9jfE=; b=o1eZaTO7NE/S 5pGRGDRbWCR1WCYcpJ63zaAzb5sCcguTcMBTvrc/CQ6beNTo0MyEQEJRgbHNKXn14JEc7kKEkanmh 1lgDSNyMuiAFGd/Vl+1sTm8I+ffC8BOu3vGQ0I9DoUS6DKQoxOov4uERaOmM2iMlPWVpICaEzBVKA d02OT2YvVrOHJxtDBk8OT1j0qcnkvkf3/Is2pprzu9QMItMchG672EU0q6dtXxsLnPbWLSIRe7fUX S6PjZsqyNtcxf+1amqPZQWsN2S2MayO0XNDFvQt7Mm9jdLk5FnspJGEfM8iM124z0o+vzlI6kAwW6 esTjUl/yA3jk//22HxHJ3g==; In-Reply-To: <79dc51f6-4c7d-e660-1116-30fa92e2918e@gmail.com> (message from Jim Porter on Sun, 18 Aug 2024 10:37:51 -0700) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:322899 Archived-At: > Date: Sun, 18 Aug 2024 10:37:51 -0700 > Cc: acorallo@gnu.org, emacs-devel@gnu.org, stefankangas@gmail.com > From: Jim Porter > > On 8/18/2024 7:35 AM, Ihor Radchenko wrote: > >>> Some text flowing around the images > >>> ... > >>> Or text and image displayed on top of each other. > >> > >> We aren't afraid of that in EWW and shr.el, are we? We could use the > >> same technique here. > > > > You mean slicing? This may work for flowing text around, but it will not > > work for overlaying images and text. > > EWW/shr.el don't actually use slicing for flowing text, as far as I > know. I suppose that could work, but I'd be worried about > miscalculations causing the slices to be misaligned (for example if we > tried to support the CSS 'float: right' property). Using :align-to should allow us to align the slices horizontally (if that is what you had in mind). > In short, EWW/shr.el's strategy for flowing text around images is to > simply ignore it (unless I'm misunderstanding part of that code). Right, and the display of RTF could do the same. > For RTF support, I don't know if Emacs needs to support all (or even > most) features of RTF to still be useful. If Emacs showed images on > their own line no matter what the RTF document requests, that's still a > big improvement over not being able to view RTF documents at all. I say let's start from the text parts: the fonts, the faces, the indentation, the numbered and unnumbered lists, etc. If we can pull that out, we will already have a terrifically useful feature. Rome wasn't built in a day.