unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Graham Hannington" <graham_hannington@fundi.com.au>
To: Emanuel Berg <embe8573@student.uu.se>
Cc: help-gnu-emacs@gnu.org
Subject: Re: On-the-fly validation of (X)HTML5 using the v.Nu REST API
Date: Fri, 1 Apr 2016 12:50:50 +0800	[thread overview]
Message-ID: <OF3A3E5F86.0BBA1934-ON48257F88.0016E6D7-48257F88.001B3174@LocalDomain> (raw)
In-Reply-To: <87mvpey1lg.fsf@debian.uxu>

Hi Emanuel,

Re:

> I haven't heard of XHTML for years.

XHTML lives on as the XML serialization of HTML5.

From the current W3C Editor's draft of HTML 5.1, and also the WHATWG HTML 
Living Standard:

> HTML vs XHTML
> This specification defines an abstract language ...
> There are various concrete syntaxes that can be used to transmit 
resources that use this abstract language,
> two of which are defined in this specification. ...
> The first such concrete syntax is the HTML syntax.
> The second concrete syntax is the XHTML syntax, which is an application 
of XML.

at:

http://w3c.github.io/html/introduction.html#html-vs-xhtml

and:

https://html.spec.whatwg.org/multipage/introduction.html#html-vs-xhtml

Note this from WHATWG:

> For a number of years, both [W3C and WHATWG] groups then worked 
together.
> In 2011, however, the groups came to the conclusion that they had 
different goals:
> the W3C wanted to publish a "finished" version of "HTML5",
> while the WHATWG wanted to continue working on a Living Standard for 
HTML,
> continuously maintaining the specification rather than freezing it in a 
state with known problems,
> and adding new features as needed to evolve the platform.
>
> Since then, the WHATWG has been working on this specification (amongst 
others),
> and the W3C has been copying fixes made by the WHATWG into their fork of 
the document
> (which also has other changes).

at:

https://html.spec.whatwg.org/multipage/introduction.html#history-2

Re:

> And what I heard then, the W3C disencouraged the use of it in favor of 
HTML5.

Could you please point me to the URL of a web page where the W3C does 
this?

Re:

> how would one benefit from on-the-fly validation?

One example: validation errors are caught as you type them, so you don't 
end up with a document that is riddled with errors that you only find out 
about when you save.

This also depends on personal preference and particular circumstances: 
sometimes I prefer on-the-fly, sometimes not.

With that Atom package I mentioned, you can choose to validate either on 
the fly or only when you save.

Either way - on the fly or only when you save - validation is integrated 
with editing: the editor highlights the validation errors in situ. You 
don't have to run a validation report outside of the editor.

Re:

> For HTML, I use validate(1), the "Offline HTMLHelp.com Validator", which 
is in the Debian repos pack wdg-html-validator. Worth checking out!

If I go to:

http://www.htmlhelp.com/tools/validator/direct.html.en

and then replace the <!DOCTYPE ...> with:

<!DOCTYPE html>

the validator responds:

> Document Checked
> Character encoding: ISO-8859-1
> Level of HTML: Unknown
>
> Errors and Warnings
> Line 1, character 15:
> <!DOCTYPE html>
> Error: no internal or external document type declaration subset; will 
parse without validation

How do you (by which I mean: you, Emanuel) validate HTML5?

Regards,
Graham Hannington

Fundi Software Pty Ltd  2016  ABN 89 009 120 290


This message has been scanned for malware by Websense. www.websense.com



  parent reply	other threads:[~2016-04-01  4:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15  6:03 Using Emacs nXML mode to validate XHTML5 using the v.Nu schemas: support for HTTP-based schema URI? Graham Hannington
2016-03-15 14:40 ` Stefan Monnier
2016-03-16  8:45   ` Graham Hannington
2016-03-16 12:27     ` Stefan Monnier
2016-03-16 14:09       ` Graham Hannington
     [not found]         ` <jwv7fh2z5eb.fsf-monnier+emacs@gnu.org>
2016-03-17  9:37           ` Graham Hannington
2016-03-17 12:38             ` Stefan Monnier
2016-03-31  5:37               ` On-the-fly validation of (X)HTML5 using the v.Nu REST API Graham Hannington
2016-03-31 17:54                 ` Emanuel Berg
2016-03-31 18:20                   ` Stefan Monnier
2016-03-31 18:40                     ` Emanuel Berg
2016-04-01  9:22                     ` Graham Hannington
2016-04-01 13:10                       ` Stefan Monnier
2016-04-01 19:13                       ` Emanuel Berg
2016-04-01  4:50                   ` Graham Hannington [this message]
2016-04-01 19:08                     ` Emanuel Berg
2016-03-16 14:47     ` Using Emacs nXML mode to validate XHTML5 using the v.Nu schemas: support for HTTP-based schema URI? Graham Hannington

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=OF3A3E5F86.0BBA1934-ON48257F88.0016E6D7-48257F88.001B3174@LocalDomain \
    --to=graham_hannington@fundi.com.au \
    --cc=embe8573@student.uu.se \
    --cc=help-gnu-emacs@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).