unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Graham Hannington" <graham_hannington@fundi.com.au>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
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	[thread overview]
Message-ID: <OF9F145584.2906F048-ON48257F78.0049AFF9-48257F78.004E4B3C@LocalDomain> (raw)
In-Reply-To: <jwvio0mehmm.fsf-monnier+emacs@gnu.org>

> 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



  reply	other threads:[~2016-03-16 14:09 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 [this message]
     [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
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=OF9F145584.2906F048-ON48257F78.0049AFF9-48257F78.004E4B3C@LocalDomain \
    --to=graham_hannington@fundi.com.au \
    --cc=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).