Re: Are 'placement' and 'float' "obsolete terms" in inline images exported to LaTeX?

2023-10-06 Thread Ihor Radchenko
Juan Manuel Macías writes: > Ihor Radchenko writes: > >>> In tables there is more consistency because :float is a float >>> environment (table or any arbitrary value) and :environment is a table >>> environment (tabular or any arbitrary value). Here :placement :options >>> and :align act as what

Re: Are 'placement' and 'float' "obsolete terms" in inline images exported to LaTeX?

2023-10-06 Thread Juan Manuel Macías
Ihor Radchenko writes: >> In tables there is more consistency because :float is a float >> environment (table or any arbitrary value) and :environment is a table >> environment (tabular or any arbitrary value). Here :placement :options >> and :align act as what is expected of them: >> >>

Re: Are 'placement' and 'float' "obsolete terms" in inline images exported to LaTeX?

2023-10-06 Thread Ihor Radchenko
Juan Manuel Macías writes: > Ihor Radchenko writes: > >> Further, we also provide :environment and :options attributes that do >> the same thing, but without special treatment of standard >> t/multicolumn/wrap/sideways/nil values in :float. > > t/multicolumn/wrap/sideways/nil... and any

Re: Are 'placement' and 'float' "obsolete terms" in inline images exported to LaTeX?

2023-10-04 Thread Juan Manuel Macías
Ihor Radchenko writes: > Further, we also provide :environment and :options attributes that do > the same thing, but without special treatment of standard > t/multicolumn/wrap/sideways/nil values in :float. t/multicolumn/wrap/sideways/nil... and any arbitrary value (see lines 14125 and 14262 in

Re: Are 'placement' and 'float' "obsolete terms" in inline images exported to LaTeX?

2023-10-04 Thread Ihor Radchenko
Juan Manuel Macías writes: >> I am not sure about obsolete - I see not reason to obsolete the intended >> use case. Your example is rather an abuse. > > Why abuse? First, it works like a charm. Second, if :float can support > any string as an environment name, why not minipage or subfigure? As

Re: Are 'placement' and 'float' "obsolete terms" in inline images exported to LaTeX?

2023-10-02 Thread Juan Manuel Macías
Ihor Radchenko writes: >> ┌ >> │ #+caption: Main caption >> │ #+begin_figure >> │ #+CAPTION: subcaption 1 >> │ #+ATTR_LaTeX: :float subfigure :placement {\textwidth} :center nil :width >> \textwidth >> │ [[file:/usr/share/texmf-dist/tex/latex/mwe/example-image-a.jpg]] >> ... >> I think this

Re: Are 'placement' and 'float' "obsolete terms" in inline images exported to LaTeX?

2023-10-02 Thread Ihor Radchenko
Juan Manuel Macías writes: > An example of more "unexpected" (but very practical) uses is this one > with three subfigures and the subcaption package: > > ┌ > │ #+caption: Main caption > │ #+begin_figure > │ #+CAPTION: subcaption 1 > │ #+ATTR_LaTeX: :float subfigure :placement {\textwidth}

Re: Are 'placement' and 'float' "obsolete terms" in inline images exported to LaTeX?

2023-10-01 Thread Juan Manuel Macías
Juan Manuel Macías writes: > Since the header arg :float now supports any string in inline images[...] Sorry, I meant "the LaTeX attribute :float ..."

Are 'placement' and 'float' "obsolete terms" in inline images exported to LaTeX?

2023-10-01 Thread Juan Manuel Macías
I don't know if this nomenclature issue that I'm going to raise is excessively formalist, but here it goes. Since the header arg :float now supports any string in inline images exported to latex (that is, ':float foo' is exported as the environment \begin{foo}…\end{foo}), the header arg