all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 33967@debbugs.gnu.org, a@ajgrf.com
Subject: bug#33967: [Feature Request] Use proportional fonts in Info-mode
Date: Mon, 07 Jan 2019 05:36:40 +0200	[thread overview]
Message-ID: <83lg3xyw8n.fsf@gnu.org> (raw)
In-Reply-To: <87ef9ps5ed.fsf@mail.linkov.net> (message from Juri Linkov on Mon, 07 Jan 2019 02:00:42 +0200)

> From: Juri Linkov <juri@linkov.net>
> Cc: a@ajgrf.com,  33967@debbugs.gnu.org
> Date: Mon, 07 Jan 2019 02:00:42 +0200
> 
> > 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.

I don't think we should invent our own HTML-Info conventions.  There's
a person actively working on that for the Texinfo project; when that
job is done, we should support whatever comes out of that.  If you
want to be part of that work, please contact the Texinfo developers.





  reply	other threads:[~2019-01-07  3:36 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
2019-01-07  3:36         ` Eli Zaretskii [this message]
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

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

  git send-email \
    --in-reply-to=83lg3xyw8n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33967@debbugs.gnu.org \
    --cc=a@ajgrf.com \
    --cc=juri@linkov.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.