From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: ndame Newsgroups: gmane.emacs.devel Subject: Re: Nicer looking Info - html manual +css Date: Sun, 19 Jan 2020 15:53:31 +0000 (GMT) Message-ID: References: <7930E155-E181-4D4C-B39E-5A05F732D667@traduction-libre.org> <83a76jzdd2.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_665_1138611331.1579449211520" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="102566"; mail-complaints-to="usenet@ciao.gmane.io" Cc: "stefan@marxist.se" , "emacs-devel@gnu.org" To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jan 19 17:05:10 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1itD4X-000QWU-Tq for ged-emacs-devel@m.gmane-mx.org; Sun, 19 Jan 2020 17:05:10 +0100 Original-Received: from localhost ([::1]:51176 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1itD4W-0000mq-Vk for ged-emacs-devel@m.gmane-mx.org; Sun, 19 Jan 2020 11:05:09 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47476) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1itD3e-0000G9-VE for emacs-devel@gnu.org; Sun, 19 Jan 2020 11:04:19 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1itD3c-00005v-43 for emacs-devel@gnu.org; Sun, 19 Jan 2020 11:04:14 -0500 Original-Received: from fmfe12.onbox.hu ([46.107.16.205]:48880 helo=web-out.onbox.hu) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1itD3Y-0008UM-6H; Sun, 19 Jan 2020 11:04:08 -0500 X-fm-smtp-source: yes Original-Received: from localhost (localhost [84.236.16.194]) by web-out.onbox.hu (Postfix) with SMTP id 48103T3DJ7z4g2; Sun, 19 Jan 2020 17:04:05 +0100 (CET) In-Reply-To: <83a76jzdd2.fsf@gnu.org> X-AccountId: 57978162 X-Originating-Ip: 84.236.16.194 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedugedrudefgdekfecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucggtfgfnhhsuhgsshgtrhhisggvpdcuhfftgffgofetkffnnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvkfgjfhfugggtihesrgdtregstddtudenucfhrhhomhepnhgurghmvgcuoegvmhgrtghsuhhsvghrsehfrhgvvghmrghilhdrhhhuqeenucfkphepkeegrddvfeeirdduiedrudelgeenucfrrghrrghmpehhvghloheppdhinhgvthepkeegrddvfeeirdduiedrudelgedpmhgrihhlfhhrohhmpegvmhgrtghsuhhsvghrsehfrhgvvghmrghilhdrhhhupdhrtghpthhtohepvghlihiisehgnhhurdhorhhgnecuvehluhhsthgvrhfuihiivgeptd DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=simple/relaxed; t=1579449845; s=20181004; d=freemail.hu; h=Date:From:To:Cc:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type; l=5992; bh=kSfSVvVtWyTeO7VtLlD2WIr0XfcNKD3XQteXNMNn+a0=; b=BcIJfaJLMptFb2LcsPpa7GdKZKe8N90vnF+QwQb2OgRxNgl/Y+wqGUAE4UnNaJA3 bCCXKEbLSwCTZddIncnxxCpN2FYBvTE9tvPy9wiMCSZNGGU4lgYMZRUJ97SH5Yd5TRN 6BR6zGEQfsF+sq+KVp9ajINISeUjg64JdAJBRHN4kcva1iiam2ea2Dmwydez4IAhh63 /wPAU9sjTHeJRqZqAirngNYQCFmIpGO0f8SMCIJA6QiAXOKkOGEj2kAe0yQPYQTxHsX NYW9oA+vkMS7qisKTbcs04FYode6rr/r1gVwoUCdVAmgn590aOkTE+Eop859dZ1HZSD PqHyrDUiFA== X-detected-operating-system: by eggs.gnu.org: FreeBSD 9.x [fuzzy] X-Received-From: 46.107.16.205 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:244377 Archived-At: ------=_Part_665_1138611331.1579449211520 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > What is the markup to which you allude here? Please elaborate, > because I don't think I understand what you mean. I just checked the source and output files. Here's an example. This an example code in the orignal texinfo file: =C2=A0 In this example, point is between the @samp{a} and the @samp{c}. =C2=A0 @example =C2=A0 @group =C2=A0 ---------- Buffer: foo ---------- =C2=A0 Gentlemen may cry ``Pea@point{}ce! Peace!,'' =C2=A0 but there is no peace. =C2=A0 ---------- Buffer: foo ---------- =C2=A0 @end group =C2=A0 @group =C2=A0 (string (preceding-char)) =C2=A0 =C2=A0 =C2=A0 =C2=A0@result{} "a" =C2=A0 (string (following-char)) =C2=A0 =C2=A0 =C2=A0 =C2=A0@result{} "c" =C2=A0 @end group =C2=A0 @end example This is the HTML output and as you can see the example markup is kept here in the form of a pre+class: =C2=A0 
=C2=A0 =C2=A0 =C2=A0 =C2=A0---------- Buffer: foo ----------
=C2=A0 =C2=A0 =C2=A0 =C2=A0Gentlemen may cry ``Pea-!-ce! Peace!,''
=C2=A0 =C2=A0 =C2=A0 =C2=A0but there is no peace.
=C2=A0 =C2=A0 =C2=A0 =C2=A0---------- Buffer: foo ----------

=C2=A0 =C2=A0 =C2=A0 =C2=A0(string (preceding-char))
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ⇒ "a"
=C2=A0 =C2=A0 =C2=A0 =C2=A0(string (following-char))
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ⇒ "c"
=C2=A0
Here's the emacs info version, no trace of the example tag here: =C2=A0 In this example, point is between the =E2=80=98a=E2=80=99 and the = =E2=80=98c=E2=80=99. =C2=A0 =C2=A0 =C2=A0 =C2=A0---------- Buffer: foo ---------- =C2=A0 =C2=A0 =C2=A0 =C2=A0Gentlemen may cry ``Pea=E2=98=85ce! Peace!,'' =C2=A0 =C2=A0 =C2=A0 =C2=A0but there is no peace. =C2=A0 =C2=A0 =C2=A0 =C2=A0---------- Buffer: foo ---------- =C2=A0 =C2=A0 =C2=A0 =C2=A0(string (preceding-char)) =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=87=92 "a" =C2=A0 =C2=A0 =C2=A0 =C2=A0(string (following-char)) =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=87=92 "c" So if I'm not mistaken when the emacs info files are created, the @example tag is dropped completely from the output. If this is the case then it could be better to keep the @example tags in some form in the emacs info output too and hide them with a face, for example.=C2=A0 If the tag is kept then the source code examples in the info documentation can get a face, so their appearance can be customized. Without the tag it's not possible, because there is no info in the file about where the code examples begin and end. =C2=A0 ------=_Part_665_1138611331.1579449211520 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit > What is the markup to which you allude here? Please elaborate,
> because I don't think I understand what you mean.


I just checked the source and output files. Here's an example.


This an example code in the orignal texinfo file:


  In this example, point is between the @samp{a} and the @samp{c}.

  @example
  @group
  ---------- Buffer: foo ----------
  Gentlemen may cry ``Pea@point{}ce! Peace!,''
  but there is no peace.
  ---------- Buffer: foo ----------
  @end group
  @group
  (string (preceding-char))
       @result{} "a"
  (string (following-char))
       @result{} "c"
  @end group
  @end example



This is the HTML output and as you can see the example markup is kept
here in the form of a pre+class:


  <pre class="example">
       ---------- Buffer: foo ----------
       Gentlemen may cry ``Pea-!-ce! Peace!,''
       but there is no peace.
       ---------- Buffer: foo ----------

       (string (preceding-char))
            &rArr; "a"
       (string (following-char))
            &rArr; "c"
  </pre>



Here's the emacs info version, no trace of the example tag here:


  In this example, point is between the ‘a’ and the ‘c’.

       ---------- Buffer: foo ----------
       Gentlemen may cry ``Pea★ce! Peace!,''
       but there is no peace.
       ---------- Buffer: foo ----------

       (string (preceding-char))
            ⇒ "a"
       (string (following-char))
            ⇒ "c"




So if I'm not mistaken when the emacs info files are created, the
@example tag is dropped completely from the output. If this is the
case then it could be better to keep the @example tags in some form in
the emacs info output too and hide them with a face, for example. 

If the tag is kept then the source code examples in the info
documentation can get a face, so their appearance can be
customized. Without the tag it's not possible, because there is no
info in the file about where the code examples begin and end.
  ------=_Part_665_1138611331.1579449211520--