From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 37846-done@debbugs.gnu.org
Subject: bug#37846: @acronym not handled correctly in synopsis or descriptions
Date: Wed, 29 Jan 2020 15:21:32 +0100 [thread overview]
Message-ID: <87pnf27383.fsf@gnu.org> (raw)
In-Reply-To: <87h842r3xt.fsf@cbaines.net> (Christopher Baines's message of "Mon, 21 Oct 2019 07:46:38 +0100")
Hi Chris,
Christopher Baines <mail@cbaines.net> skribis:
> When rendering synopsis or descriptions as plain text, acronyms are not
> handled correctly, they're just omitted entirely.
>
> Flexible objects for representing @acronym{UFO, unified font object}
> data
>
> ->
>
> Flexible objects for representing data
>
>
> @acronym{FIFE, Flexible Isometric Free Engine} is a
> multi-platform\nisometric game engine. Python bindings are included
> allowing users to create\ngames using Python as well as C++.
>
> ->
>
> is a multi-platform isometric game engine. Python bindings are
> included allowing users to create games using Python as well as C++.
>
>
> I believe this is a bug in Guile, but it could also be a problem with
> the texinfo markup.
Fixed in Guile commit ff14b77ff527f297438b83614db0c1d56322ec42 (on
‘master’, which corresponds to 3.0.x, but we could backport to
‘stable-2.2’).
Thanks,
Ludo’.
next parent reply other threads:[~2020-01-29 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87h842r3xt.fsf@cbaines.net>
2020-01-29 14:21 ` Ludovic Courtès [this message]
2020-01-29 16:33 ` bug#37846: @acronym not handled correctly in synopsis or descriptions Christopher Baines
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.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnf27383.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=37846-done@debbugs.gnu.org \
--cc=mail@cbaines.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.
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).