From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id eBzmAoaQNWX6RQEAauVa8A:P1 (envelope-from ) for ; Sun, 22 Oct 2023 23:13:42 +0200 Received: from aspmx1.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id eBzmAoaQNWX6RQEAauVa8A (envelope-from ) for ; Sun, 22 Oct 2023 23:13:42 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 73004632C8 for ; Sun, 22 Oct 2023 23:13:41 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=qBdPZE8i; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1698009222; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=j0Pwp6eOSBuZj11ZXgRmLHHdbvwMAyjU/A45fXLDXzU=; b=T8XGvmso3/MCTTAjdcL+4jflhLJaDz3AoGM0DrLJ0P84K/ActuAggHY0cLQPVY4NIT8Lqc Dfe5q8a7SvtiUKwSBROfqajGllnh2rIdKaq+nqx5dfgis5t5AeRqHzlq8ImJ36p/8q6AZA kuRSBnFzrZRSnkjiOZCjU+bVdPv6q312ZRROxNAzkRTacNR3YAdx1ajWrmgxOppOlLTyln iWgK1Sg4Q65XHoUc1mn8/mJuXGlGkaO00En+uXHTl1AbycP7uQphWsIHH5c9zhVVoO6KM4 FjXIY0V63mhSZRjIMKzoCqFc2vl7iHCFD1cOff0lZDab5rVzifSgJ0PR60ZjRw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=qBdPZE8i; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Seal: i=1; s=key1; d=yhetil.org; t=1698009222; a=rsa-sha256; cv=none; b=TSNPHzIdYlublLPS3yUmOW+GSHf+cw/c3M9wxsXLJtG4vzDFgJYEvSuaCbi9tnb21Qg72t c1I0AWepnsCpS0QL8M1tMFlZantBERMgP9qbGIl5LwhnrscqBHxWA5BnMSdAOfgASPxukF E7Ltx97NkLnPgm56JDD8we5b1DkBYUMy/zeK+PZ/gem14K63pDrvW8ZqEJW0nzI1GUR0aU d/5xDxB8J8DXmBG3z+qYbaXf9bIN5R6qB9b9LgR5aIH+LZBfKfxtXe2FWZI7B1VKKMvWRF J/D+CJzBBlVDMiEoC25lDlO49c09lLM5/4H+TTCvvvuX5KskyrB0d88agDbDsQ== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qufkk-0002Yo-VC; Sun, 22 Oct 2023 17:12:55 -0400 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 1qufkd-0002YS-9x for emacs-orgmode@gnu.org; Sun, 22 Oct 2023 17:12:48 -0400 Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qufkZ-0007J5-Pm for emacs-orgmode@gnu.org; Sun, 22 Oct 2023 17:12:47 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 70605240027 for ; Sun, 22 Oct 2023 23:12:41 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1698009161; bh=IKPEngbyq+FoRtylLrKchV92KOP7Jy+jqD4En0COON0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version: Content-Transfer-Encoding:From; b=qBdPZE8iXiwPV8KRwewdHkhePYqMp0/M958tgMxcAw+391aw0D7Y18WbuKnYPuNtu tM4p7vTnJuficDda8mfcnJWzbl+h7UdHTlTsJ0jTcxtdvzxjgrPHjScTAmuD6dvz32 Wy2dvGOB8uTiG4uRhmEpIHxTqU7bMxS/QlG7fKx+yDbW40HyizsWLgQ2Cou7pG+pp9 8GgA/i+lqVtYgFZMf0qsGMs+QFG86A4Aokjr7ajWoDjXh4iwEDnxbTNiaIhZF4/IFa REwT/tdxJF+1J94XAf8t93RiA7TGKZqlHoFjs1JGktrxt+F327y7A6Z26+GguOgZw5 NrFqPtGNy5NJg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4SD9yK09Hfz6tw3; Sun, 22 Oct 2023 23:12:40 +0200 (CEST) From: =?utf-8?Q?Juan_Manuel_Mac=C3=ADas?= To: Ihor Radchenko Cc: orgmode Subject: Re: Are 'placement' and 'float' "obsolete terms" in inline images export Date: Sun, 22 Oct 2023 21:12:38 +0000 Message-ID: <877cneicop.fsf@posteo.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=185.67.36.65; envelope-from=maciaschain@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -3.80 X-Spam-Score: -3.80 X-Migadu-Queue-Id: 73004632C8 X-Migadu-Scanner: mx2.migadu.com X-TUID: mH2m35X4bQIf Ihor, sorry for the late reply. Ihor Radchenko writes: > So, the difference between :environment and :float is that :float also > encapsulates \caption in addition to the actual environment (like > tabularx or includegraphics) used for transcoded exported element. > I can see how :float+:placement can be imprecise and that the existing > :environment indeed serves a different purpose. (It might be worth > clarifying this distinction in the manual - it seems arbitrary from > the first glance). > But what would be the better name then? I think the problem is limited to images, where there is no "double" environment as in the case of tables (float environment that encloses an environment to generate the table, and :placement points to the correct environment). In the case of images, I am afraid that the new features have advanced the meaning of the old ones. Previously, :float only supported t/nil ("figure" by default, in case of t) along with a few explicit "float" environments, such as sidewaysfigure or wrapfigure. Since :float now can accept any string as an environment name, Pandora's box has been opened and the meaning of the old :float has been left behind: for example, we can put :float minipage, and minipage is not a float environment. Something similar has happened to :placement. My suggestion is to add a :environment attribute next to another :environment-options attr (or something like that, to introduce any arbitrary LaTeX code). A LaTeX image can be enclosed in many environment types, float or non-float. However, :float can still be useful for certain combinations. For example, a minipage environment cannot include a caption (it produces an error of the type "LaTeX Error: \caption outside float"). Then you would have to put something like #+ATTR_LaTeX: :float nil :environment minipage :environment-options {\linew= idth} #+CAPTION: caption [[file:foo.png]] =3D=3D> \begin{minipage}{\linewidth} \includegraphics[width=3D.9\linewidth]{foo.png} \captionof{figure}{caption} \end{minipage} Anyway, I find pros and cons of all this: - pros: a intended feature is added, although with :float and :placement the same thing can be achieved (sometimes), but here the effect is not intended (in origin). - cons: redundancy, more complexity in the code (and probably more confusio= n for the user?). --=20 Juan Manuel Mac=C3=ADas=20