emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jonas Bernoulli <jonas@bernoul.li>
To: Ihor Radchenko <yantar92@posteo.net>, 8dcc <8dcc.git@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Texinfo: Commas in URL text are not escaped
Date: Sun, 27 Oct 2024 23:31:44 +0100	[thread overview]
Message-ID: <87iktd9nzj.fsf@bernoul.li> (raw)
In-Reply-To: <87ed4cwkzm.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

> 8dcc <8dcc.git@gmail.com> writes:
>
>> When exported to Texinfo using `org-texinfo-export-to-texinfo',
>> generates the following file:
>>
>>   ...
>>   @uref{https://example.com, Foo}
>>
>>   @uref{https://example.com, Foo, Bar}
>>   ...
>>
>> The comma on the text of the second URL is being interpreted by Texinfo
>> as an argument separator, which in the case of `@uref', only the third
>> argument is displayed, hiding the second argument and the actual URL
>> when exporting the file.
>
> Fixed, on main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=39264d3d41
> Thanks for reporting!

> * 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.

     Cheers,
     Jonas


  reply	other threads:[~2024-10-27 22:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 10:43 [BUG] Texinfo: Commas in URL text are not escaped 8dcc
2024-10-19  8:33 ` Ihor Radchenko
2024-10-27 22:31   ` Jonas Bernoulli [this message]
2024-10-28 19:06     ` Ihor Radchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87iktd9nzj.fsf@bernoul.li \
    --to=jonas@bernoul.li \
    --cc=8dcc.git@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).