Jonas Bernoulli <jo...@bernoul.li> writes:
>> * lisp/ox-texinfo.el (org-texinfo--sanitize-content): Sanitize commas
>> everywhere to make sure that we do not end up with text commas being
>> interpreted as argument separator in @command{arg1, arg2, ...}. This
>> approach will produce @comma{} even when it is not necessary, but it
>> is the safest approach.
>
> Could you please find a more localized solution? I would expect that
> this can be done in org-texinfo-link instead. Replacing every comma
> with @comma{} makes the resulting texinfo much harder to read.
It indeed makes texinfo harder to read, but the original bug did not
only reveal problems with @uref. At least, commands like @email (or
anything else that can accept multiple arguments) are also bugged.
Unfortunately, I am not very familiar with Texinfo (and ox-texinfo does
not have a dedicated maintainer). So, given that comma appears to be
special in various Texinfo constructs, I went with the safest option
available.
If someone who knows Texinfo syntax and how comma is used there can
provide information on where exactly "," is special, it would help
creating a clearner fix.
For the time being, I judged that ugly texi sources are better than
buggy export.
--
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>
