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 :placement can be used for more than just "placement". For example, this: ┌──── │ #+ATTR_LaTeX: :float minipage :placement {\textwidth} │ [[file:/usr/share/texmf-dist/tex/latex/mwe/example-image-a.jpg]] └──── produces in LaTeX this: ┌──── │ \begin{minipage}{\textwidth} │ \centering │ \includegraphics[width=.9\linewidth]{/usr/share/texmf-dist/tex/latex/mwe/example-image-a.jpg} │ \end{minipage} └──── (in this case :placement is exported as the required minipage argument, which is its width). 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} :center nil :width \textwidth │ [[file:/usr/share/texmf-dist/tex/latex/mwe/example-image-a.jpg]] │ @@latex:\vspace{2ex}@@ │ #+CAPTION: subcaption 2 │ #+ATTR_LaTeX: :float subfigure :placement {.4\textwidth} :center nil :width \textwidth │ [[file:/usr/share/texmf-dist/tex/latex/mwe/example-image-a.jpg]] │ @@latex:\hfill@@ │ #+CAPTION: subcaption3 │ #+ATTR_LaTeX: :float subfigure :placement {.4\textwidth} :center nil :width \textwidth │ [[file:/usr/share/texmf-dist/tex/latex/mwe/example-image-a.jpg]] │ #+end_figure └──── (In all three subfigures, :placement is exported as the subfigure environment argument, which designates the width of each subfigure). I think this is a case where certain elements of Org have evolved (consciously or unconsciously) ahead of the names, and these names have become somewhat outdated. There is not only the case of :placement. Even :float seems imprecise, since can be used to create a minipage, and the minipage environment is not a float environment. Would it be worth making those names obsolete (with backward compatibility, of course) and replacing them with slightly more precise ones? I think that new names would give the user an idea of more variety of uses, like the examples I have put here. Best regards, Juan Manuel