Good morning. The following difference seems like it could be relevant. As an aside, I have found it more informative to download the .html files and manually inspect them, rather than to look at Chrome's Elements tree, since that itself seems to get confused by what appears to me to be a list started w/ but ended w/ . In summary, I think that the translation of the @multitable is itself fine, but that the prior presence of @itemize @bullet ... , with its mismatch
... , confuses Chrome. and causes it to (not) render the table (from @multitable) properly. ---------------------------------------------------------------------------------------- (a) in the (shorter) https://www.gnu.org/software/emacs/manual/html_node/flymake/Starting-Flymake.html : closes, the list, and this documentation "node" renders fine.

Syntax checks happen “on-the-fly”. Each check is started whenever:

OK: ---------------------------------------------------------------------------------------- (b) however, in the (longer & problematic) (mono) https://www.gnu.org/software/emacs/manual/html_mono/flymake.html

Syntax checks happen “on-the-fly”. Each check is started whenever:

BAD:
  • flymake-mode is started, unless flymake-start-on-flymake-mode is nil;
  • the buffer is saved, unless flymake-start-on-save-buffer is nil;
  • some changes were made to the buffer more than 0.5 seconds ago (the delay is configurable in flymake-no-changes-timeout).
  • When the user invokes the command flymake-start. OK:
  • ---------------------------------------------------------------------------------------- I *guess* that this latter "unclosed"
    is what causes trouble further down in this file, even though (a new, matching)
    &
    match up there. (I haven't yet figured out how to rebuild the manuals to do more direct experiments/isolation.) ----------------------------------------------------------------------------------------

    The following statuses are defined:

    OK: OK:
    [nerrors nwarnings ...]Normal operation. nerrors and nwarnings are, respectively, the total number of errors and warnings found during the last buffer check, for all backends. They may be followed by other totals for other types of diagnostics (see Customizing Flymake error types).
    WaitSome Flymake backends haven’t reported since the last time they where questioned. It is reasonable to assume that this is a temporary delay and Flymake will resume normal operation soon.
    !All the configured Flymake backends have disabled themselves: Flymake cannot annotate the buffer and action from the user is needed to investigate and remedy the situation (see Troubleshooting).
    ?There are no applicable Flymake backends for this buffer, thus Flymake cannot annotate it. To fix this, a user may look to extending Flymake and add a new backend (see Extending Flymake).
    ---------------------------------------------------------------------------------------- -Lester On Fri, Aug 23, 2024 at 3:06 AM Eli Zaretskii wrote: > > From: Lester Longley > > Date: Thu, 22 Aug 2024 17:01:37 -0400 > > Cc: 72761@debbugs.gnu.org > > > > Re: the second issue, the problem seems to start here, with this: style="float:left" width="100%"> > > element (see PROBLEM below), which > > (a) seems out of place > > (b) is never closed w/ "
    , as best I can see (as per inspection > of saved output from curl > > "https://www.gnu.org/software/emacs/manual/html_mono/flymake.html") > > Instead, this "" seems to be closed with a mismatched "" > > No, there _is_ a
    , see below, where I copied the "page source" > from my browser. > > > I am unfamiliar w/ Texinfo, but I nonetheless don't see any "obvious" > reason that a element should be > > emitted at the above location, based on the below excerpt from > > > https://git.savannah.gnu.org/cgit/emacs.git/tree/doc/misc/flymake.texi?h=emacs-29#n115 > (I'm just guessing on > > the corresponding version of this file currently used for the online > documentation) > > No, that table is the translation of @multitable. > >

    The following statuses are defined: >

    >
    > > > > >
    [nerrors nwarnings > ...]Normal operation. nerrors and > nwarnings are, respectively, > the total number of errors and warnings found during the last buffer > check, for all backends. They may be followed by other totals for > other types of diagnostics (see href="#Flymake-error-types">Customizing Flymake error types).
    WaitSome Flymake > backends haven’t reported since the last time they > where questioned. It is reasonable to assume that this is a temporary > delay and Flymake will resume normal operation soon.
    !All the > configured Flymake backends have disabled themselves: Flymake > cannot annotate the buffer and action from the user is needed to > investigate and remedy the situation (see href="#Troubleshooting">Troubleshooting).
    ?There are no > applicable Flymake backends for this buffer, thus Flymake > cannot annotate it. To fix this, a user may look to extending Flymake > and add a new backend (see Extending > Flymake).
    > > I guess I will ask the Texinfo developers to take a look. > > Thanks. >