List for cgit developers and users
 help / color / mirror / Atom feed
From: john at keeping.me.uk (John Keeping)
Subject: [PATCH 1/5] ui-shared: HTML-ize DOCTYPE and <html>
Date: Wed, 11 May 2016 19:56:19 +0100	[thread overview]
Message-ID: <20160511185619.GG4296@serenity.lan> (raw)
In-Reply-To: <1462989858-15825-2-git-send-email-wub@partyvan.eu>

On Wed, May 11, 2016 at 06:04:14PM +0000, Juuso Lapinlampi wrote:
> Get rid of the XHTML headers, bringing cgit slowly to the modern age of
> HTML.

This seems like a reasonable aim, but don't we need to actually *be*
HTML(5?) as well in order to do this?  Currently we close <input/> and
<img/> tags even though HTML is explicit that this shouldn't be done.

I think we need to fix all of those as well if we're going to claim to
be HTML rather than XHTML.  I suspect that would be a bit big to review
as a single patch, but I certainly think that it should be applied as a
single patch series.

> ---
>  ui-shared.c | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/ui-shared.c b/ui-shared.c
> index 9a38aa9..1ded2d6 100644
> --- a/ui-shared.c
> +++ b/ui-shared.c
> @@ -12,8 +12,7 @@
>  #include "html.h"
>  
>  static const char cgit_doctype[] =
> -"<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n"
> -"  \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n";
> +"<!DOCTYPE html>"\n";
>  
>  static char *http_date(time_t t)
>  {
> @@ -723,7 +722,7 @@ void cgit_print_docstart(void)
>  
>  	char *host = cgit_hosturl();
>  	html(cgit_doctype);
> -	html("<html xmlns='http://www.w3.org/1999/xhtml' xml:lang='en' lang='en'>\n");
> +	html("<html lang='en'>\n");
>  	html("<head>\n");
>  	html("<title>");
>  	html_txt(ctx.page.title);
> -- 
> 2.8.1
> 
> _______________________________________________
> CGit mailing list
> CGit at lists.zx2c4.com
> http://lists.zx2c4.com/mailman/listinfo/cgit


  reply	other threads:[~2016-05-11 18:56 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11 18:04 [PATCH 0/5] Convert to HTML, fix HTML validation issues wub
2016-05-11 18:04 ` [PATCH 1/5] ui-shared: HTML-ize DOCTYPE and <html> wub
2016-05-11 18:56   ` john [this message]
2016-05-11 19:28     ` wub
2016-05-12 15:31     ` Jason
2016-05-12 15:32   ` Jason
2016-05-12 18:58     ` wub
2016-05-12 19:04       ` Jason
2016-05-12 15:38   ` Jason
2016-05-11 18:04 ` [PATCH 2/5] Revert "ui-summary: add "rel='vcs-git'" to clone URL links" wub
2016-05-11 18:44   ` john
2016-05-12 15:34     ` Jason
2016-05-12 15:37       ` pabs3
2016-05-12 15:47         ` Jason
2016-05-12 15:49           ` pabs3
2016-05-12 15:51             ` Jason
2016-05-12 16:16               ` pabs3
2016-05-12 16:22                 ` Jason
2016-05-12 19:09       ` wub
2016-05-13  0:26         ` pabs3
2016-05-12 16:49     ` pabs3
2016-05-11 18:04 ` [PATCH 3/5] Revert "ui-shared: add rel-vcs microformat links to HTML header" wub
2016-05-11 18:45   ` john
2016-05-11 20:28     ` wub
2016-05-11 18:04 ` [PATCH 4/5] ui: Fix bad value for attribute action on form elements wub
2016-05-11 18:50   ` john
2016-05-12 15:41   ` Jason
2016-05-12 19:22     ` wub
2016-05-12 19:27       ` Jason
2016-05-12 19:29         ` Jason
2016-05-12 19:36         ` wub
2016-05-12 19:39           ` Jason
2016-05-11 18:04 ` [PATCH 5/5] ui-shared: Remove a name attribute with an empty value wub
2016-05-11 18:52   ` john
2016-05-12 15:43   ` Jason

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=20160511185619.GG4296@serenity.lan \
    --to=cgit@lists.zx2c4.com \
    /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 NNTP newsgroup(s).