From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Alexandre Garreau Newsgroups: gmane.emacs.devel,gmane.comp.tex.texinfo.bugs,gmane.comp.gnu.gettext.bugs Subject: Re: [bug-gettext] ELPA and gettext.el Date: Sun, 20 Jan 2019 19:10:48 +0100 Message-ID: <87ef97td1z.fsf@portable.galex-713.eu> References: <87zhrxxvsv.fsf@portable.galex-713.eu> <05edc689-8d29-345e-3cc8-98a511f34025@cs.ucla.edu> <18002249.PFuSW9TAes@omega> NNTP-Posting-Host: ciao.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=-=-=" X-Trace: ciao.gmane.org 1548007858 171241 195.159.176.228 (20 Jan 2019 18:10:58 GMT) X-Complaints-To: usenet@ciao.gmane.org NNTP-Posting-Date: Sun, 20 Jan 2019 18:10:58 +0000 (UTC) User-Agent: Gnus (5.13), GNU Emacs 25.1.1 (i686-pc-linux-gnu, GTK+ Version 3.22.11) of 2017-09-15, modified by Debian Cc: Glenn Morris , Paul Eggert , emacs-devel@gnu.org, bug-gettext@gnu.org To: Bruno Haible , bug-texinfo@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 20 19:10:56 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1glHYb-000iT3-Kh for ged-emacs-devel@m.gmane.org; Sun, 20 Jan 2019 19:10:53 +0100 Original-Received: from localhost ([127.0.0.1]:42807 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1glHYk-0003jS-LO for ged-emacs-devel@m.gmane.org; Sun, 20 Jan 2019 13:11:02 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:39262) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1glHYa-0003jG-7e for emacs-devel@gnu.org; Sun, 20 Jan 2019 13:10:52 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1glHYZ-0007In-4w for emacs-devel@gnu.org; Sun, 20 Jan 2019 13:10:52 -0500 Original-Received: from portable.galex-713.eu ([2a00:5884:8305::1]:40246) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1glHYY-0007ID-TD; Sun, 20 Jan 2019 13:10:51 -0500 Original-Received: from localhost ([::1] helo=portable.galex-713.eu) by portable.galex-713.eu with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1glHYW-0006Te-Fc; Sun, 20 Jan 2019 19:10:48 +0100 PGP-FINGERPRINT: E109 9988 4197 D7CB B0BC 5C23 8DEB 24BA 867D 3F7F Accept-Language: fr, en, eo, it In-Reply-To: <18002249.PFuSW9TAes@omega> (Bruno Haible's message of "Sun, 20 Jan 2019 11:58:31 +0100") X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:5884:8305::1 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:232544 gmane.comp.tex.texinfo.bugs:9576 gmane.comp.gnu.gettext.bugs:1920 Archived-At: --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2019-01-20 at 11:58, Bruno Haible wrote: > Can ELPA packages also provide HTML-format documentation (generated from > texinfo sources) in a canonical way? HTML rendering is decent, 'info' ren= dering > in Emacs is inferior (use of fixed-width font for plain text, use of _xxx_ > for @emph instead of slanted/italic face, etc.). Therefore I would want > to provide the documentation in HTML at least. A more mixed opinion about texinfo HTML output ergonomics: As you note HTML output is here typographically superior=E2=80=A6 though, e= macs is perfectly able to use a variable-width font and italic face, probably quite easily, but won=E2=80=99t (currently), afaik, be able to justify text. Now note texinfo HTML output paragraphs are by default not justified, and allow by default the display of way too large visual lines (longer than the emacs 72 chars, and a looooot more than the famous =E2=80=9Coptima= l=E2=80=9D 66-character limit), and, thought that=E2=80=99d be only a question of gene= ric CSS, currently HTML output is pretty old, and absolutely not semantical at all. So with current HTML output you=E2=80=99d have to make a custom-info-output-like plugin or browser to, from currenty, unsemantical, HTML output, get as much semantics as the emacs info format, which allow way better interaction and search. A more semantical pure strict XHTML(2.0?) or HTML5 output would allow such interaction by a decent browser (which currently doesn=E2=80=99t exist= in nature imho). Now about ELPA doc: I often saw markdown (or alike, such as org-mode) one-page documentations, which, on several package searching utilities, automatically convert to HTML, with the typographical features you mentioned. --=-=-= Content-Type: multipart/related; boundary="==-=-=" --==-=-= Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

On 2019-01-20 at 11:58, Bruno Haible wrote:

Can ELPA packages also provide HTML-format documentation (generated from texinfo sources) in a canonical way? HTML rendering is decent, 'info' rende= ring in Emacs is inferior (use of fixed-width font for plain text, use of xxx for @emph instead of slanted/italic face, etc.). Therefore I would want to provide the documentation in HTML at least.

A more mixed opinion about texinfo HTML output ergonomics:

As you note HTML output is here typographically superior=E2=80=A6 though, e= macs is perfectly able to use a variable-width font and italic face, probably quite easily, but won=E2=80=99t (currently), afaik, be able to justify text.

Now note texinfo HTML output paragraphs are by default not justified, and allow by default the display of way too large visual lines (longer than the emacs 72 chars, and a looooot more than the famous =E2=80=9Coptima= l=E2=80=9D 66-character limit), and, thought that=E2=80=99d be only a question of gene= ric CSS, currently HTML output is pretty old, and absolutely not semantical at all. So with current HTML output you=E2=80=99d have to make a custom-info-output-like plugin or browser to, from currenty, unsemantical, HTML output, get as much semantics as the emacs info format, which allow way better interaction and search.

A more semantical pure strict XHTML(2.0?) or HTML5 output would allow such interaction by a decent browser (which currently doesn=E2=80=99t exist= in nature imho).

Now about ELPA doc: I often saw markdown (or alike, such as org-mode) one-page documentations, which, on several package searching utilities, automatically convert to HTML, with the typographical features you mentioned.

--==-=-=-- --=-=-=--