unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: sirgazil <sirgazil@zoho.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 24981@debbugs.gnu.org
Subject: bug#24981: [Website] All pages fail the HTML validation test
Date: Thu, 7 Dec 2017 08:33:09 -0500	[thread overview]
Message-ID: <d758aaa8-4fa4-b31e-4886-d9530c356d17@zoho.com> (raw)
In-Reply-To: <87tvx2buei.fsf@gnu.org>

On 07/12/17 07:21, Ludovic Courtès wrote:
> Hello,
> 
> sirgazil <sirgazil@zoho.com> skribis:
> 
>> With the new website online, all pages pass the HTML validation,
>> except for the Packages page, which has a </p> tag for no opened P
>> element in every package description,
> 
> Oh, how’s that possible?  A bug in Guile’s ‘sxml->xml’?

I haven't take a look at the code yet. But I plan to do so after I 
upgrade Guix to 0.14.


>> and uses obsolete TT element in links to patches.
> 
> I didn’t know <tt> is obsolete.  Would <code> be OK here?
> 

Depending on the meaning of the texinfo command that is converted to TT 
one could use CODE, a SPAN with a class or any of the other elements 
recommended here: 
https://www.w3.org/TR/html5/obsolete.html#non-conforming-features.

> We’d need to adjust Guile’s stexi modules accordingly.
> 
> Thanks,
> Ludo’.
> 

  reply	other threads:[~2017-12-07 13:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21 19:29 bug#24981: [Website] All pages fail the HTML validation test Luis Felipe López Acevedo
2016-11-23 21:45 ` Ludovic Courtès
2016-11-24  0:25   ` Luis Felipe López Acevedo
2016-11-24  9:17     ` Ludovic Courtès
2017-12-06 19:06 ` sirgazil
2017-12-07 12:21   ` Ludovic Courtès
2017-12-07 13:33     ` sirgazil [this message]
2017-12-09 15:17     ` sirgazil
2017-12-09 21:15       ` Ludovic Courtès
2019-02-06 17:08 ` sirgazil
2019-02-08 22:00   ` Ludovic Courtès
2019-02-08 14:14 ` sirgazil

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=d758aaa8-4fa4-b31e-4886-d9530c356d17@zoho.com \
    --to=sirgazil@zoho.com \
    --cc=24981@debbugs.gnu.org \
    --cc=ludo@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).