texinfo-commits
[Top][All Lists]
Advanced

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

branch master updated: * doc/texinfo.texi (HTML Translation): Edit and t


From: Gavin D. Smith
Subject: branch master updated: * doc/texinfo.texi (HTML Translation): Edit and trim.
Date: Fri, 03 Jun 2022 08:00:59 -0400

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

gavin pushed a commit to branch master
in repository texinfo.

The following commit(s) were added to refs/heads/master by this push:
     new efd2274e1f * doc/texinfo.texi (HTML Translation): Edit and trim.
efd2274e1f is described below

commit efd2274e1fc352566f92765caff8130d18890bd9
Author: Gavin Smith <gavinsmith0123@gmail.com>
AuthorDate: Fri Jun 3 13:00:51 2022 +0100

    * doc/texinfo.texi (HTML Translation): Edit and trim.
---
 ChangeLog        |   4 ++
 doc/texinfo.texi | 120 +++++++++++++++++++++++++++----------------------------
 2 files changed, 64 insertions(+), 60 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index b5cfbfd5cf..6a096556bd 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2022-06-03  Gavin Smith  <gavinsmith0123@gmail.com>
+
+       * doc/texinfo.texi (HTML Translation): Edit and trim.
+
 2022-06-03  Gavin Smith  <gavinsmith0123@gmail.com>
 
        Minor manual modernizations
diff --git a/doc/texinfo.texi b/doc/texinfo.texi
index 77d34ee4bf..d17a5edacf 100644
--- a/doc/texinfo.texi
+++ b/doc/texinfo.texi
@@ -18035,71 +18035,21 @@ for a brief overview of all the output formats.
 
 @cindex HTML translation
 
-@cindex HTML output, browser compatibility of
-First, the HTML generated by @command{makeinfo} is standard
-HTML@tie{}4.  When first written, it also tried to be compatible with 
-earlier standards (e.g., HTML@tie{}2.0, RFC-1866).
-
-Please report output from an
-error-free run of @code{makeinfo} which has practical browser
-portability problems as a bug (@pxref{Reporting Bugs}).
-
-@pindex html32.pm
-Some known exceptions to HTML@tie{}3.2 (using
-@samp{--init-file=html32.pm} produced strict HTML@tie{}3.2 output, but
-this has not been tested lately;
-@pxref{Invoking @command{texi2any}}):
-
-@enumerate
-@item
-HTML@tie{}3.2 tables are generated for the @code{@@multitable} command
-(@pxref{Multi-column Tables}), but they should degrade reasonably in
-browsers without table support.
-
-@item
-The HTML@tie{}4 @samp{id} attribute is used.
+The HTML generated by @command{makeinfo} generates standard HTML
+output.  The output is intentionally quite plain for maximum portability
+and accessibility.
 
-@item
-The HTML@tie{}4 @samp{lang} attribute on the @samp{<html>} attribute
-is used.
-
-@item
-Entities that are not in the HTML@tie{}3.2 standard are also used.
+You can customize the output via CSS (@pxref{HTML CSS}) or other
+means (@pxref{Customization Variables}).  If you cannot accomplish
+a reasonable customization, feel free to report that.
 
-@item
-CSS is used (@pxref{HTML CSS}).
-
-@item
-Some HTML@tie{}4 elements are used: @code{span}, @code{thead}, 
-@code{abbr}, @code{acronym}.
-
-@end enumerate
-
-To achieve maximum portability and accessibility among browsers (both
-graphical and text-based), systems, and users, the HTML output is
-intentionally quite plain and generic.  It has always been our goal
-for users to be able to customize the output to their wishes via CSS
-(@pxref{HTML CSS}) or other means (@pxref{Customization Variables}).
-If you cannot accomplish a reasonable customization, feel free to
-report that.
-
-However, we do not wish to depart from our basic goal of widest
+@ignore
+We do not wish to depart from our basic goal of widest
 readability for the core output.  For example, using fancy CSS may
 make it possible for the HTML output to more closely resemble the
 @TeX{} output in some details, but this result is not even close to
 being worth the ensuing difficulties.
-
-It is also intentionally not our goal, and not even 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.
-
-To repeat what was said at the top: please report output from an
-error-free run of @code{makeinfo} which has @emph{practical} browser
-portability problems as a bug (@pxref{Reporting Bugs}).
-
-A few other points about the HTML output:
+@end ignore
 
 @cindex Navigation bar, in HTML output
 @strong{Navigation bar:} By default, a navigation bar is inserted at the
@@ -18110,7 +18060,7 @@ in split output support Info-like navigation with 
browsers which implement
 this feature.
 
 @cindex Footnote styles, in HTML
-@strong{Footnotes:} for HTML, when the footnote style is @samp{end},
+@strong{Footnotes:} For HTML, when the footnote style is @samp{end},
 or if the output is not split, footnotes are put at the end of the
 output.  If the footnote style is set to @samp{separate}, and the
 output is split, they are placed in a separate file.  @xref{Footnote
@@ -18126,6 +18076,56 @@ 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}.
 
+@strong{Standards}:
+It is intentionally not our goal, and not even 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
+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
+
+
+
+
+
 
 @node HTML Splitting
 @section HTML Splitting



reply via email to

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