public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Benson Muite <benson_muite@emailplus.org>
To: gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs, patch] OpenMP update for gcc-13/changes.html + projects/gomp/
Date: Fri, 24 Feb 2023 14:10:49 +0300	[thread overview]
Message-ID: <ecace150-a741-e642-b597-a373422f10ed@emailplus.org> (raw)
In-Reply-To: <b7104949-7657-74e6-10c9-052545867247@emailplus.org>

On 2/24/23 10:32, Benson Muite via Gcc-patches wrote:
> On 2/24/23 04:02, Gerald Pfeifer wrote:
>> On Thu, 23 Feb 2023, Tobias Burnus wrote:
>>> PS: I also removed a stray </code>, but admittedly only after the
>>> commit. I found it by manually running those through the w3 validator
>>> site. However, I did not see an automatic email, either it takes longer
>>> or does it no longer run? It did in the past!
>>
>> You are right, and this is a sore / sad point: validator.w3.org that we
>> used in the past now only supports interactive sessions. And they even
>> broke support for the Referer header, so I also had to remove the checking 
>> link I had embedded in all of our pages.
>>
>> These days I invoke the validator (via a version of the original script) 
>> when I see a commit. Which indeed leads to many orders of magnitude longer 
>> delays.
>>
>> Sadly I don't have a better alternative. :-(
>>
> Could one of the following be used or used to generate a better workflow:
> https://html-validate.org/usage/cli.html - written in Javascript, but
> has a command line interface
> https://github.com/validator/validator - packaged, but a little
> cumbersome, may need a wrapper
> https://github.com/w3c-validators/w3c_validators - Wrapper written in
> Ruby, with a nice interface to validate a local file
> 
html-tidy could work well. Written in C. A typical session from Git
Sources following [1]:

git pull
cd gcc
./configure
mkdir HTML
makeinfo --html --no-split -Idoc -Idoc/include -o HTML doc/gcc.texi
tidy -f HTML/errs.txt -imu HTML/gcc.html

Typical current reported errors are
line 23080 column 22 - Warning: nested emphasis <samp>
line 40445 column 11 - Warning: nested emphasis <code>
line 3541 column 1 - Warning: <span> anchor "index-g_002b_002b" already
defined
line 54489 column 1 - Warning: <table> lacks "summary" attribute


[1]
https://unix.stackexchange.com/questions/493013/how-to-build-the-gcc-html-documentation-from-source-into-a-single-page

      reply	other threads:[~2023-02-24 11:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 10:59 Tobias Burnus
2023-02-22 23:29 ` Gerald Pfeifer
2023-02-23 14:50   ` Tobias Burnus
2023-02-24  1:02     ` Gerald Pfeifer
2023-02-24  7:32       ` Benson Muite
2023-02-24 11:10         ` Benson Muite [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ecace150-a741-e642-b597-a373422f10ed@emailplus.org \
    --to=benson_muite@emailplus.org \
    --cc=gcc-patches@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).