Max Nikulin <maniku...@gmail.com> writes:
> On 20/10/2022 12:07, Ihor Radchenko wrote:
>> When transcoding children (e.g. table rows), the sibling rows can always
>> be accessed using org-export-get-previous-element and
>> org-export-get-next-element.
>
> Decision if escaping is necessary should be based on export result, not
> on the source element.
I am not sure. The export result may originate from constructs like
#+MACRO: pagebreak @@latex:\\@@
Some paragraph {{{pagebreak}}}
src_elisp[:results raw]{(format "@@latex:[%dpt]@@" (or my-spacing-value 0))}
The point is: it can be done on purpose for some reason.
>> I am not sure what you are referring to. If modifying exported string,
>> it will suffer from the same problems as your idea with comment.
>
> It is a brain storm idea, I still unsure it is feasible.
>
> I mean info "(elisp) Text Properties". I do not think they are usually
> ignored by filters. \\ substrings added by ox-latex may have some unique
> property. Export filter searches for occurrences of \\ to check if
> escaping is necessary, but it ignores particular location if the text
> does not have the specific property. I would prefer to mark output of
> export snippets with another property value and do not escape them. It
> is a kind of out of band communication. Unsure if text properties may be
> lost due to string operations in an exporter or vice versa to propagate
> to the source buffer.
I see. I feel like it is too fragile to rely upon. At least, I'd use it
only if there are no better options.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
