Re: Are 'placement' and 'float' "obsolete terms" in inline images export

2024-01-02 Thread Juan Manuel Macías
Apologies for my delay in answering all the interesting questions you raised in this last message. November and December have been horrible work days for me (all publishers are always in a hurry) and I haven't been able to attend to the mailing list as I would like... Ihor Radchenko writes: >

Re: Are 'placement' and 'float' "obsolete terms" in inline images export

2023-10-26 Thread Ihor Radchenko
Juan Manuel Macías writes: >> What about :wrap? > > I like :wrap. What's more, remembering that old thread where > some questions about code before/after the image were discussed, > what if the expected value of :wrap were a kind of template? This would > allow code to be placed before and/or

Re: Are 'placement' and 'float' "obsolete terms" in inline images export

2023-10-23 Thread Juan Manuel Macías
Ihor Radchenko writes: >> 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. > > As I said above, I feel

Re: Are 'placement' and 'float' "obsolete terms" in inline images export

2023-10-23 Thread Ihor Radchenko
Juan Manuel Macías 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

Re: Are 'placement' and 'float' "obsolete terms" in inline images export

2023-10-22 Thread Juan Manuel Macías
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