[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using Emacs nXML mode to validate XHTML5 using the v.Nu schemas: sup
From: |
Graham Hannington |
Subject: |
Re: Using Emacs nXML mode to validate XHTML5 using the v.Nu schemas: support for HTTP-based schema URI? |
Date: |
Wed, 16 Mar 2016 22:09:10 +0800 |
> Do you know how/when/where those missing files get generated?
How: yes.
By the v.Nu Python build script, build.py:
https://github.com/validator/validator/blob/master/build/build.py
When: no.
At least, not precisely. Imprecisely, the bleeding obvious ;-): whenever a
v.Nu developer, or anyone else who clones the repo, decides to build v.Nu
from source.
Certainly, whenever the v.Nu developers decide it's time for a new
release:
https://github.com/validator/validator/releases
If that's not what you meant by "when": for details on when, during the
build process, the missing files are generated, see the source of
build.py.
Where: that depends on what you mean by "where", and probably not for the
facetious reasons you're imagining ;-).
All of the schema files are delivered in the .jar (or .war; but I've been
using the .jar) in one "flat" directory (with no subdirectories):
nu/validator/localentities/files/
That directory contains a file named entitymap. Each line of that file
maps a file name in that directory to a URI. Here is an example line for a
schema file:
http://s.validator.nu/html5/block.rnc schema_html5_block_rnc
The extension-less file names are an underscore-delimited concatenation of
the directory path, file name, and extension of the corresponding source
file from the repo (or a similar-looking confection, for files that are
created during the build).
So the answer to "where" has more to do with those internal v.Nu schema
URIs than the actual "physical" location (directory path) of the files in
the generated .jar.
In terms of those URIs, the missing files are generated in the html5
directory.
One file, rdf.rnc is moved from the repo .drivers directory to the "build
only" rdf directory.
There are other differences, too.
For more details, you can perform your own comparison by following the
steps in the readme at:
https://github.com/unsoup/validator#comparing-the-source-and-distributed-schemas
Or ask me, and I'll send you a detailed report from, say, WinMerge (what I
typically use), or your free diff tool of choice.
Graham
Fundi Software Pty Ltd 2016 ABN 89 009 120 290
This message has been scanned for malware by Websense. www.websense.com
- Using Emacs nXML mode to validate XHTML5 using the v.Nu schemas: support for HTTP-based schema URI?, Graham Hannington, 2016/03/15
- Re: Using Emacs nXML mode to validate XHTML5 using the v.Nu schemas: support for HTTP-based schema URI?, Stefan Monnier, 2016/03/15
- Re: Using Emacs nXML mode to validate XHTML5 using the v.Nu schemas: support for HTTP-based schema URI?, Graham Hannington, 2016/03/16
- Re: Using Emacs nXML mode to validate XHTML5 using the v.Nu schemas: support for HTTP-based schema URI?, Stefan Monnier, 2016/03/16
- Re: Using Emacs nXML mode to validate XHTML5 using the v.Nu schemas: support for HTTP-based schema URI?,
Graham Hannington <=
- Message not available
- Re: Using Emacs nXML mode to validate XHTML5 using the v.Nu schemas: support for HTTP-based schema URI?, Graham Hannington, 2016/03/17
- Re: Using Emacs nXML mode to validate XHTML5 using the v.Nu schemas: support for HTTP-based schema URI?, Stefan Monnier, 2016/03/17
- On-the-fly validation of (X)HTML5 using the v.Nu REST API, Graham Hannington, 2016/03/31
- Re: On-the-fly validation of (X)HTML5 using the v.Nu REST API, Emanuel Berg, 2016/03/31
- Re: On-the-fly validation of (X)HTML5 using the v.Nu REST API, Stefan Monnier, 2016/03/31
- Re: On-the-fly validation of (X)HTML5 using the v.Nu REST API, Emanuel Berg, 2016/03/31
- Re: Using Emacs nXML mode to validate XHTML5 using the v.Nu schemas: support for HTTP-based schema URI?, Graham Hannington, 2016/03/16