unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Gavin Smith <gavinsmith0123@gmail.com>
Cc: Vincent.b.1@hotmail.fr, 18308@debbugs.gnu.org
Subject: bug#18308: 24.4.50; Info viewer cannot follow menu entry for '(texinfo) @- @hyphenation'
Date: Sat, 23 Aug 2014 15:44:35 -0400	[thread overview]
Message-ID: <E1XLHEp-0005Te-2b@fencepost.gnu.org> (raw)
In-Reply-To: <CAKPWYQ1aV+e6A+WUZEue+gzp1bat7fXLbSiTr9cPbd3n_PPeaw@mail.gmail.com> (message from Gavin Smith on Fri, 22 Aug 2014 21:12:06 +0100)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

    > I think the real fix for this sort of thing is to develop
    > a replacement for the Info reader which uses HTML.
    > That's why I was enthusiastic about that project when it was announced.

    Somebody would have to define how HTML should be used for Texinfo manuals, e.g.:

    * Naming of HTML files for references between nodes and files
    * How indices should be expressed
    * What version of HTML, what constructs are allowed.
    * Where these files are to be stored in the filesystem

That's true -- these tasks are part of the job.

    I don't see the point in writing a browser to read a dialect of HTML
    used for Texinfo manuals when there are already many web browsers out
    there.

This was discussed a few weeks ago.  Ordinary browsers operating on
HTML lack some of the features of Info.  It is not easy to get those
features out of a web browser just by designing the HTML.  We need to
build them onto the ordinary browser facilities.

    Are there reasons to use HTML other than compatiblity?

1. It would interoperate with web browsers.  They would not provide
the added commands/features of Info, but they would be able to display
the manual and you could navigate in it.

2. HTML provides lots of markup and display facilities that Info
lacks.  We could define a new format of our own, but that would
be gratuitous incompatibility -- why not use HTML?


-- 
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org  www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
  Use Ekiga or an ordinary phone call.






  parent reply	other threads:[~2014-08-23 19:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-21  8:45 bug#18308: 24.4.50; Info viewer cannot follow menu entry for '(texinfo) @- @hyphenation' Vincent Belaïche
2014-08-21 14:12 ` Eli Zaretskii
2014-08-21 16:30 ` Vincent Belaïche
2014-08-21 22:23 ` Vincent Belaïche
2014-08-22  6:36   ` Eli Zaretskii
2014-08-22 17:17     ` Richard Stallman
2014-08-22 20:12       ` Gavin Smith
2014-08-22 20:57         ` Eli Zaretskii
2014-08-23 19:44         ` Richard Stallman [this message]
2014-08-24 14:05       ` Stefan Monnier
2014-08-24 23:41         ` Richard Stallman
2014-08-25 15:05           ` Stefan Monnier
2014-08-25 19:11             ` Richard Stallman
2014-08-25  2:07         ` Tom Tromey
2014-08-25 19:10           ` Richard Stallman
2014-08-22 17:56     ` Gavin Smith
2014-08-26 15:58       ` Glenn Morris
2014-08-22 13:01 ` Vincent Belaïche
2014-08-22 13:36   ` Eli Zaretskii
2014-08-22 22:04 ` Vincent Belaïche
2014-08-22 22:09   ` Glenn Morris
2014-08-31 22:37   ` Gavin Smith
     [not found]   ` <CAKPWYQ2r6y7spGnwU+34BQDMYRikEGoROP0BAJ5mLR0g4d7jTg@mail.gmail.com>
2014-09-01 19:40     ` Vincent Belaïche
2014-09-01 21:37       ` Gavin Smith
2014-09-01 21:53       ` Karl Berry
     [not found]       ` <201409012153.s81LrtTi021549@freefriends.org>
2014-09-02 21:44         ` Vincent Belaïche

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=E1XLHEp-0005Te-2b@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=18308@debbugs.gnu.org \
    --cc=Vincent.b.1@hotmail.fr \
    --cc=gavinsmith0123@gmail.com \
    /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).