[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: On being web-friendly and why info must die

From: Thien-Thi Nguyen
Subject: Re: On being web-friendly and why info must die
Date: Sun, 07 Dec 2014 05:02:00 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)

() Eli Zaretskii <address@hidden>
() Fri, 05 Dec 2014 22:17:24 +0200

   That would be fine by me, at least.  The back-end can
   certainly be replaced, provided that the replacement
   allows as efficient reading and consulting the
   documentation as the Info format and its Emacs viewer.

   The issue here is mainly about the Texinfo source.  It
   doesn't make sense to switch to another language, exactly
   as it doesn't make sense to switch a C-based project to
   C++ or Java, when all the main developers don't work and
   aren't proficient in these languages.  It's a death blow
   to the project.

Right.  Texinfo for input is fine.  Tell the kids it's like
vitamin E for their mofo anti-aliased twitch-pix hangover...

Anyone interested in hacking IXIN (a proposed "middle-end"
or intermediate form for Texinfo) please search for threads
w/ that word in the texinfo mailing lists a bit (maybe two
or three years) back, and see:


for release tarballs.  The unreleased changes are:

 ! [p] Release: 1.8
  * [q] [maint] Reformat NEWS; nfc.
  * [q] [maint] Reformat NEWS; nfc.
  * [q^] No longer distribute {epsf,texinfo}.tex.
  * [q~2] [spec int] Fix typo: Include "(news)" heading.
 +* [p] Release: 1.8

In the context of Emacs, the proof-of-concept IXIN-viewing
program could use a rewrite using shr.el low-level routines,
instead of its own ad-hoc renderer.  Or, just look at the
code as a cautionary tale before running away screaming.  :-D

Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]