From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 33967@debbugs.gnu.org, a@ajgrf.com
Subject: bug#33967: [Feature Request] Use proportional fonts in Info-mode
Date: Mon, 07 Jan 2019 02:00:42 +0200 [thread overview]
Message-ID: <87ef9ps5ed.fsf@mail.linkov.net> (raw)
In-Reply-To: <29a0d099-3af3-446e-9f0f-d5c2aacfcaf9@www.fastmail.com>
>> > AFAIK, there's work under way to improve the HTML output so that it
>> > could provide the features we want from a GNU manual reader, and then
>> > switch the GNU Info readers to supporting that. But this is a
>> > long-term goal, and cannot be reached by changes in Emacs alone.
>>
>> It's easy to add HTML support to the Emacs Info reader
>> with the help of shr.el HTML renderer, but I guess this
>> should wait until the stand-alone Info reader supports HTML.
>
> The problem is not to render HTML per se, the problem is to support
> the Info features like index search in HTML, something I don't know
> what would it take until we see what makeinfo emits.
We can get index entries from the links found in the Index HTML pages
that makeinfo already emits, i.e. the same way that the Info reader
already parses .info files, it can parse .html files that should be simpler
since there is less ambiguity in HTML format.
next prev parent reply other threads:[~2019-01-07 0:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 20:35 bug#33967: [Feature Request] Use proportional fonts in Info-mode Alex Griffin
[not found] ` <mailman.6730.1546547831.1284.bug-gnu-emacs@gnu.org>
2019-01-03 21:23 ` Alan Mackenzie
2019-01-03 21:41 ` Alex Griffin
2019-01-04 5:58 ` Glenn Morris
2019-01-04 6:50 ` Eli Zaretskii
2019-01-05 21:51 ` Juri Linkov
2019-01-06 3:35 ` Eli Zaretskii
2019-01-07 0:00 ` Juri Linkov [this message]
2019-01-07 3:36 ` Eli Zaretskii
2019-01-07 21:49 ` Juri Linkov
2019-01-06 19:41 ` Richard Stallman
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ef9ps5ed.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=33967@debbugs.gnu.org \
--cc=a@ajgrf.com \
--cc=eliz@gnu.org \
/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.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).