On Mon, Mar 09, 2026 at 07:43:12PM +0100, Patrice Dumas wrote:
>
> My feeling is that it would be more consistent, when there is
> spaces_before_argument/spaces_after_argument, to have all the spaces
> together, though not in the same text element. So
> spaces_before_argument and spaces_after_argument should become arrays of
> text elements.
I realized that there is another case which should be taken into
account, a comment at end of line after/before the spaces, like
@uref{ @c a comment
aaaa @c another one
, b}
I am starting to wonder if it wouldn't be better to leave all the spaces
and comments as regular content in brace commands in the tree and let
the converter remove leading spaces and trailing spaces, by
calling a function that modifies the tree, by removing spaces after
conversion of each of the arguments, or by having a state where spaces
are ignored (which would not be really fit for removing trailing spaces,
actually).
Any idea on that subject?
In any case, I do not think that it is a good idea to mark leading
spaces for each line especially.
--
Pat
