texinfo-commits
[Top][All Lists]
Advanced

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

branch master updated: No HTML features list, explain how HTML evolves


From: Patrice Dumas
Subject: branch master updated: No HTML features list, explain how HTML evolves
Date: Wed, 20 Jul 2022 09:14:47 -0400

This is an automated email from the git hooks/post-receive script.

pertusus pushed a commit to branch master
in repository texinfo.

The following commit(s) were added to refs/heads/master by this push:
     new 41fc765858 No HTML features list, explain how HTML evolves
41fc765858 is described below

commit 41fc765858b32d4c5d0b7c73f230b8542c5853f5
Author: Patrice Dumas <pertusus@free.fr>
AuthorDate: Wed Jul 20 15:14:34 2022 +0200

    No HTML features list, explain how HTML evolves
    
    * doc/texinfo.texi (HTML Translation): do not list explicitly
    HTML features used, but rather explain how makeinfo implements
    latest standard features while trying to be backward compatible
    as best as possible too.
---
 ChangeLog        |  9 +++++++++
 doc/texinfo.texi | 49 +++++++++----------------------------------------
 2 files changed, 18 insertions(+), 40 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index caa2eee8ba..05ddf8a79e 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,12 @@
+2022-20-07  Patrice Dumas  <pertusus@free.fr>
+
+       No HTML features list, explain how HTML evolves
+
+       * doc/texinfo.texi (HTML Translation): do not list explicitly
+       HTML features used, but rather explain how makeinfo implements
+       latest standard features while trying to be backward compatible
+       as best as possible too.
+
 2022-20-07  Patrice Dumas  <pertusus@free.fr>
 
        * doc/texinfo.texi (@code{@@setfilename}): state clearly that
diff --git a/doc/texinfo.texi b/doc/texinfo.texi
index 409f6be6bd..065449aa61 100644
--- a/doc/texinfo.texi
+++ b/doc/texinfo.texi
@@ -18133,55 +18133,24 @@ to the output (i.e., suppressing the normal escaping 
of input
 @samp{<}, @samp{>} and @samp{&} characters which have special
 significance in HTML)@.  @xref{Conditional Commands}.
 
+@cindex HTML output, browser compatibility of
 @strong{Standards}:
-It is intentionally not our goal, and not even possible, to pass
+It is intentionally not our goal, and not even always possible, to pass
 through every conceivable validation test without any diagnostics.
 Different validation tests have different goals, often about pedantic
 enforcement of some standard or another.  Our overriding goal is to
 help users, not blindly comply with standards.
 
 Please report output from an
-error-free run of @code{makeinfo} which has @emph{practical} browser
+error-free run of @command{makeinfo} which has @emph{practical} browser
 portability problems as a bug (@pxref{Reporting Bugs}).
 
-@cindex HTML output, browser compatibility of
-Some known use of features by HTML version:
-
-@itemize
-@item
-The HTML@tie{}4 @samp{id} attribute is used.
-
-@item
-The HTML@tie{}4 @samp{lang} attribute on the @samp{<html>} attribute
-is used.
-
-@item
-Some HTML@tie{}4 elements are used: @code{span}, @code{thead}, 
-@code{abbr}, @code{acronym}.
-
-@item
-CSS is used
-
-@item
-Entities that are not in the HTML@tie{}3.2 standard are also used.
-
-@item
-HTML@tie{}3.2 tables are generated for the @code{@@multitable} command
-(@pxref{Multi-column Tables})
-@c but they should degrade reasonably in browsers without table support.
-@end itemize
-
-@ignore
-@pindex html32.pm
-(using
-@samp{--init-file=html32.pm} produced strict HTML@tie{}3.2 output, but
-this has not been tested lately;
-@pxref{Invoking @command{texi2any}}):
-@end ignore
-
-
-
-
+In practice, the HTML produced by @command{makeinfo} is slowly adjusted
+over time towards the latest HTML standard, while also trying to keep
+compatibility with earlier produced HTML.  We use transitional markup
+and try to be slow enough to give time for the diverse HTML readers
+to adjust (and for standards to reincorporate useful features that were
+dropped@dots{}).
 
 
 @node HTML Splitting



reply via email to

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