Re: Trailing whitespace after export snippets without a transcoder

[Max Nikulin <manikulin@gmail.com>]

On 20/04/2024 18:14, Ihor Radchenko wrote:
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=a6d9fd82e
> 
>      Back-end developers should pay attention to the fact that white spaces
>      before and after an ignored export snippet now are accumulated in the
>      output.
> 
> I have no clue about the rationale of this special behaviour - it dates
> back to the days when Org export was merged. It is also not documented
> anywhere, AFAIK.

I would not expect that the space after the following export snippet is 
ignored in the case of ox-html or ox-latex backend:

     A space@@ascii:*@@ character.

The space may be put inside the export snippet if the intention is to 
omit it for output formats other than plain text. So current behavior is 
perfectly reasonable and flexible enough.

The issue is empty lines that serve as paragraph separators and that may 
appear due to expansion of a macro or due to skipped export snippets. 
Perhaps transcoders of other elements, e.g. links, may return empty 
strings as well.