Проверка svg на ошибки

As an XML-based language, SVG can be validated just as HTML is. The primary tool for this is the W3C validation service, although others are available. In order to ensure their SVG-infused pages still validate, developers need to be careful in how SVG is added to their code:

SVG Integrated Into HTML5

Perhaps the ideal case, at least in terms of clarity. Simply place your SVG code directly in the body of the HTML5 document: 

<!DOCTYPE html>
	<head>
		<title>SVG</title>
		<meta charset=utf-8>
	</head>
	<body>
		<h1>HTML5 SVG Test</h1>
		<svg height="200" xmlns="http://www.w3.org/2000/svg">
			<circle id="redcircle" cx="50" cy="50" r="50" fill="red" />
		</svg>
	</body>
</html>

The code above will validate as HTML5, while the SVG will appear as a red circle on the page.

Validating A Standalone SVG Document

The next most common scenario: you have a separate .svg file, with SVG integrated into your web page via CSS or an <img>. Feeding a correctly formatted SVG document to the W3C Markup Validation service will result in a valid page, assuming that SVG code has been used correctly: 

<svg version="1.1" xmlns="http://www.w3.org/2000/svg">

The one downside to this last approach is that the SVG document will no longer validate as SVG, but as XML. This isn’t wrong, but it’s possibly less useful.

Enjoy this piece? I invite you to follow me at twitter.com/dudleystorey to learn more.

I used a program called Fritzing to draw some basic Arduino schematics, and then export the output as a SVG. This works just as expected, but then I noticed that the SVG output only looks okay in some browsers and only okay in some versions of Firefox.

Since Fritzing is a open source app I figured that I could look into the code (and maybe help out a little).

But now over to the question, what is a correct SVG supposed to look like? What verifier over at W3C can I use to check the file?

I tried to use the verifiers found on this page: http://validator.w3.org/dev/tests/

But they all complained a lot, especially about the SVG version. The verifiers seem to like version 1.0 and 1.1, but when I look at the top of this file seems to be using version 1.2?

This is the top three lines from the problematic file (reformatted for readability):

<?xml version='1.0' encoding='UTF-8' standalone='no'?>
<!-- Created with Fritzing (http://www.fritzing.org/) -->
<svg width="3.50927in"
     x="0in"
     version="1.2"
     y="0in"
     xmlns="http://www.w3.org/2000/svg"
     height="2.81713in"
     viewBox="0 0 252.667 202.833"
     baseProfile="tiny"
     xmlns:svg="http://www.w3.org/2000/svg">

Is there a specific SVG 1.2 verifier I can use?

Or shall I try to verify the SVG as if it was a classical XML file?

(As a side note, Fritzing seems to use Qt, so if there some QTest I can use it may be useful.)

XML Validator Online is easy to use the XML Validate tool. Copy, Paste, and Validate. This is also called as XML Lint tool.

Validation of a document and its syntax is important to ensure that the XML implementation has correctly and accurately reflected the user’s intentions. Read more about xml validation in next section.

XML validator will check for both well-formedness and validity. It will also give you helpful error messages so you can fix any issues in your XML.

The XML syntax rules are less stringent compared to the formal rules of well-known languages like Java or C. This is because XML was designed for storage and transfer of data in both human-readable form as well as machine-readable form. XML syntax rules are not simple, but with a few guidelines and examples, it’s easy to start using XML in your projects.

XML Syntax Rules:

XML documents must have a top level element, must end with a close tag, XML tags are case insensitive, must be nested correctly XML attributes must be quoted.

What can you do with XML Validation Online?

  • XML Lint helps to validate your XML data.
  • It also works as XML Checker and XML syntax checker.
  • This tool allows loading the XML URL to validate. Use your XML REST URL to validate. Click on the Load URL button, Enter URL and Submit.
  • Users can also validate XML Files by uploading the file. This functionality also referred to as XML File validator
  • It validates SOAP, WSDL, POM , RSS, SVG, SGML, RDF files.
  • It helps to save your validated XML online and Share it on social sites or emails.
  • XML Validator works well on Windows, MAC, Linux, Chrome, Firefox, Edge, and Safari.
  • This XML Linter helps a developer who works with XML data to test and verify.

What is XML?

XML is a markup language designed to provide a standard way to structure data. The introduction of XML was an important step in the shift from document markup languages (such as SGML) to data markup languages.

Example to validate XML

Valid XML Try it. 

<?xml version="1.0" encoding="UTF-8" ?>
<InsuranceCompanies>
   <Top_Insurance_Companies>
	<Name>Berkshire Hathaway ( BRK.A)</Name>
	<Capitalization>$655 billion</Capitalization>
   </Top_Insurance_Companies>
</InsuranceCompanies>

Invalid XML Try it. 

<?xml version="1.0" encoding="UTF-8" ?>
<InsuranceCompanies>
	<Top_Insurance_Companies>
		<Name>Berkshire Hathaway ( BRK.A)</Name>
</InsuranceCompanies>

For Advanced Users

Lua External URL

Load Lua External URL in Browser URL like this https://codebeautify.org/xmlvalidator?url=external-url

https://codebeautify.org/xmlvalidator?url=https://gist.githubusercontent.com/cbmgit/13db101f2b17e30f8626984c18f77b30/raw/InsuranceCompanies.xml

Know more about XML:

  • How to Print XML?
  • Python XML Pretty Print
  • How to create XML file?
  • XML Formatter with Dark Mode

The Nu Html Checker (v.Nu) Chat room Download latest

The Nu Html Checker (v.Nu) helps you catch unintended mistakes in your HTML,
CSS, and SVG. It enables you to batch-check documents from the command
line and from other scripts/apps, and to deploy your own instance of the
checker as a service (like validator.w3.org/nu). Its source code is
available, as are instructions on how to build, test, and run the
code.

A Dockerfile (see Pulling the Docker image below) and npm,
pip, and brew packages are also available.

It is released upstream in these formats:

  • pre-compiled Linux, Windows, and macOS binaries that include an embedded
    Java runtime

  • vnu.jar — a portable version you can use on any system that has Java 8 or
    above installed

  • vnu.war — for deploying the checker service through a servlet container
    such as Tomcat

Note: The vnu.jar and vnu.war files require you to have Java 8 or above
installed. The pre-compiled Linux, Windows, and macOS binaries don’t require you
to have any version of Java already installed at all.

You can get the latest release or run docker run -it --rm -p 8888:8888 ghcr.io/validator/validator:latest, npm install vnu-jar,
npm install --registry=https://npm.pkg.github.com @validator/vnu-jar,
brew install vnu, or pip install html5validator and see the
Usage and Web-based checking sections below. Or automate your document
checking with a frontend such as:

  • Grunt plugin for HTML validation or Gulp plugin for HTML
    validation or Maven plugin for HTML validation

  • html5validator pip package (for integration in Travis CI, CircleCI,
    CodeShip, Jekyll, Pelican, etc.)

  • LMVTFY: Let Me Validate That For You (auto-check JSFiddle/JSBin, etc.,
    links in GitHub issue comments)

Usage

Run the checker with one of the following invocations:

• vnu-runtime-image/bin/vnu OPTIONS FILES (Linux or macOS)

• vnu-runtime-imagebinvnu.bat OPTIONS FILES (Windows)

• java -jar ~/vnu.jar OPTIONS FILES (any system with Java8+ installed)

…where FILES are the documents to check, and OPTIONS are zero or more of
the following options:

--errors-only --Werror --exit-zero-always --stdout --asciiquotes
--user-agent USER_AGENT --no-langdetect --no-stream --filterfile FILENAME
--filterpattern PATTERN --css --skip-non-css --also-check-css --svg
--skip-non-svg --also-check-svg --xml --html --skip-non-html
--format gnu|xml|json|text --help --verbose --version

The Options section below provides details on each option, and the rest of
this section provides some specific examples.

Note: Throughout these examples, replace ~/vnu.jar with the actual path to
that jar file on your system, and replace vnu-runtime-image/bin/vnu and
vnu-runtime-imagebinvnu.bat with the actual path to the vnu or vnu.bat
program on your system — or if you add the vnu-runtime-image/bin or
vnu-runtime-imagebin directory your system PATH environment variable, you
can invoke the checker with just vnu.

To check one or more documents from the command line:

  vnu-runtime-image/bin/vnu      FILE.html FILE2.html FILE3.html...

  vnu-runtime-imagebinvnu.bat  FILE.html FILE2.html FILE3.html...

  java -jar ~/vnu.jar            FILE.html FILE2.html FILE3.html...

Note: If you get a StackOverflowError error when invoking the checker, try
adjusting the thread stack size by providing the -Xss option to java:

  java -Xss512k -jar ~/vnu.jar ...

  vnu-runtime-image/bin/java -Xss512k 
      -m vnu/nu.validator.client.SimpleCommandLineValidator ...

To check all documents in a particular directory DIRECTORY_PATH as HTML:

  java -jar ~/vnu.jar            DIRECTORY_PATH

  vnu-runtime-image/bin/vnu      DIRECTORY_PATH

  vnu-runtime-imagebinvnu.bat  DIRECTORY_PATH

More examples

Note: The examples in this section assume you have the
vnu-runtime-image/bin or vnu-runtime-imagebin directory in your system
PATH environment variable. If you’re using the jar file instead, replace vnu
in the examples with java -jar ~/vnu.jar.

To check all documents in a particular directory DIRECTORY_PATH as HTML, but
skip any documents whose names don’t end with the extensions .html, .htm,
.xhtml, or .xht:

  vnu --skip-non-html DIRECTORY_PATH

To check all documents in a particular directory as CSS:

To check all documents in a particular directory as CSS, but skip any documents
whose names don’t end with the extension .css:

  vnu --skip-non-css DIRECTORY_PATH

To check all documents in a particular directory, with documents whose names end
in the extension .css being checked as CSS, and all other documents being
checked as HTML:

  vnu --also-check-css DIRECTORY_PATH

To check all documents in a particular directory as SVG:

To check all documents in a particular directory as SVG, but skip any documents
whose names don’t end with the extension .svg:

  vnu --skip-non-svg DIRECTORY_PATH

To check all documents in a particular directory, with documents whose names end
in the extension .svg being checked as SVG, and all other documents being
checked as HTML:

  vnu --also-check-svg DIRECTORY_PATH

To check a Web document:

  vnu _URL_

  example: vnu http://example.com/foo

To check standard input:

  vnu -

  example:

  echo '<!doctype html><title>...' | vnu -

  echo '<!doctype html><title>...' | java -jar ~/vnu.jar -

Options

When used from the command line as described in this section, the checker
provides the following options:

—asciiquotes

Specifies whether ASCII quotation marks are substituted for Unicode smart
quotation marks in messages.

default: [unset; Unicode smart quotation marks are used in messages]

—errors-only

Specifies that only error-level messages and non-document-error messages are
reported (so that warnings and info messages are not reported).

default: [unset; all messages reported, including warnings & info messages]

—Werror

Makes the checker exit non-zero if any warnings are encountered (even if
there are no errors).

default: [unset; checker exits zero if only warnings are encountered]

—exit-zero-always

Makes the checker exit zero even if errors are reported for any documents.

default: [unset; checker exits 1 if errors are reported for any documents]

—stdout

Makes the checker report errors and warnings to stdout rather than stderr.

default: [unset; checker reports errors and warnings to stderr]

—filterfile FILENAME

Specifies a filename. Each line of the file contains either a regular
expression or starts with "#" to indicate the line is a comment. Any error
message or warning message that matches a regular expression in the file is
filtered out (dropped/suppressed).

default: [unset; checker does no message filtering]

—filterpattern REGEXP

Specifies a regular expression. Any error message or warning message that
matches the regular expression is filtered out (dropped/suppressed).

As with all other checker options, this option may only be specified once.
So to filter multiple error messages or warning messages, you must provide a
single regular expression that will match all the messages. The typical way
to do that for regular expressions is to OR multiple patterns together using
the "|" character.

default: [unset; checker does no message filtering]

—format format

Specifies the output format for reporting the results.

default: "gnu"

possible values: "gnu", "xml", "json", "text" [see information at URL below]

https://github.com/validator/validator/wiki/Service-%C2%BB-Common-params#out

—help

Shows detailed usage information.

—skip-non-css

Check documents as CSS but skip documents that don’t have *.css extensions.

default: [unset; all documents found are checked]

—css

Force all documents to be checked as CSS, regardless of extension.

default: [unset]

—skip-non-svg

Check documents as SVG but skip documents that don’t have *.svg extensions.

default: [unset; all documents found are checked]

—svg

Force all documents to be checked as SVG, regardless of extension.

default: [unset]

—skip-non-html

Skip documents that don’t have *.html, *.htm, *.xhtml, or *.xht extensions.

default: [unset; all documents found are checked, regardless of extension]

—html

Forces any *.xhtml or *.xht documents to be parsed using the HTML parser.

default: [unset; XML parser is used for *.xhtml and *.xht documents]

—xml

Forces any *.html documents to be parsed using the XML parser.

default: [unset; HTML parser is used for *.html documents]

—also-check-css

Check CSS documents (in addition to checking HTML documents).

default: [unset; no documents are checked as CSS]

—also-check-svg

Check SVG documents (in addition to checking HTML documents).

default: [unset; no documents are checked as SVG]

—user-agent USER_AGENT

Specifies the value of the User-Agent request header to send when checking
HTTPS/HTTP URLs.

default: "Validator.nu/LV"

—no-langdetect

Disables language detection, so that documents are not checked for missing
or mislabeled html[lang] attributes.

default: [unset; language detection & html[lang] checking are performed]

—no-stream

Forces all documents to be be parsed in buffered mode instead of streaming
mode (causes some parse errors to be treated as non-fatal document errors
instead of as fatal document errors).

default: [unset; non-streamable parse errors cause fatal document errors]

—verbose

Specifies "verbose" output. (Currently this just means that the names of
files being checked are written to stdout.)

default: [unset; output is not verbose]

—version

Shows the checker version number.

Web-based checking

The Nu Html Checker — along with being usable as a standalone command-line
client — can be run as an HTTP service, similar to
validator.w3.org/nu, for browser-based checking of HTML documents, CSS
stylesheets, and SVG images over the Web. To that end, the checker is released
as several separate packages:

  • Linux, Windows, and macOS binaries for deploying the checker as a simple
    self-contained service on any system

  • vnu.jar for deploying the checker as a simple self-contained service on a
    system with Java installed

  • vnu.war for deploying the checker to a servlet container such as Tomcat

All deployments expose a REST API that enables checking of HTML documents, CSS
stylesheets, and SVG images from other clients, not just web browsers. And the
Linux, Windows, and macOS binaries and vnu.jar package also include a simple
HTTP client that enables you to either send documents to a locally-running
instance of the checker HTTP service — for fast command-line checking — or to
any remote instance of the checker HTTP service running anywhere on the Web.

The latest releases of the Linux, Windows, and macOS binaries and vnu.jar and
vnu.war packages are available from the validator project at github. The
following are detailed instructions on using them.

Note: Throughout these instructions, replace ~/vnu.jar with the actual
path to that jar file on your system, and replace vnu-runtime-image/bin/java
and vnu-runtime-imagebinjava.exe with the actual path to the checker java
or java.exe program on your system — or if you add the vnu-runtime-image/bin
or vnu-runtime-imagebin directory your system PATH environment variable,
you can invoke the checker with just java nu.validator.servlet.Main 8888.

Standalone web server

To run the checker as a standalone service (using a built-in Jetty server), open
a new terminal window and invoke the checker like this:

java -cp ~/vnu.jar              nu.validator.servlet.Main 8888

vnu-runtime-image/bin/java      nu.validator.servlet.Main 8888

vnu-runtime-imagebinjava.exe  nu.validator.servlet.Main 8888

Then open http://0.0.0.0:8888 in a browser. (To listen on a different
port, replace 8888 with the port number.)

Warning: Future checker releases will bind by default to the address
127.0.0.1. Your checker deployment might become unreachable unless you use the
nu.validator.servlet.bind-address system property to bind the checker to a
different address:

java -cp ~/vnu.jar 
    -Dnu.validator.servlet.bind-address=128.30.52.73 
    nu.validator.servlet.Main 8888

vnu-runtime-image/bin/java 
    -Dnu.validator.servlet.bind-address=128.30.52.73 
    nu.validator.servlet.Main 8888

vnu-runtime-imagebinjava.exe  
    -Dnu.validator.servlet.bind-address=128.30.52.73 
    nu.validator.servlet.Main 8888

When you open http://0.0.0.0:8888 (or whatever URL corresponds to the
nu.validator.servlet.bind-address value you’re using), you’ll see a form
similar to validator.w3.org/nu that allows you to enter the URL of an HTML
document, CSS stylesheet, or SVG image, and have the results of checking that
resource displayed in the browser.

Note: If you get a StackOverflowError error when using the checker, try
adjusting the thread stack size by providing the -Xss option to java:

  java -Xss512k -cp ~/vnu.jar nu.validator.servlet.Main 8888

  vnu-runtime-image/bin/java -Xss512k -m vnu/nu.validator.servlet.Main 8888

Deployment to servlet container

To run the checker inside of an existing servlet container such as Apache Tomcat
you will need to deploy the vnu.war file to that server following its
documentation. For example, on Apache Tomcat you could do this using the
Manager application or simply by copying the file to the webapps
directory (since that is the default appBase setting). Typically you would see
a message similar to the following in the catalina.out log file.

May 7, 2014 4:42:04 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/lib/tomcat7/webapps/vnu.war

Assuming your servlet container is configured to receive HTTP requests sent to
localhost on port 80 and the context root of this application is vnu
(often the default behavior is to use the WAR file’s filename as the context
root unless one is explicitly specified) you should be able to access the
application by connecting to http://localhost/vnu/.

Note: You may want to customize the /WEB-INF/web.xml file inside the WAR
file (you can use any ZIP-handling program) to modify the servlet filter
configuration. For example, if you wanted to disable the inbound-size-limit
filter, you could comment out that filter like this:

<!--
  <filter>
      <filter-name>inbound-size-limit-filter</filter-name>
      <filter-class>nu.validator.servlet.InboundSizeLimitFilter</filter-class>
  </filter>
  <filter-mapping>
      <filter-name>inbound-size-limit-filter</filter-name>
      <url-pattern>/*</url-pattern>
  </filter-mapping>
-->

HTTP client (for fast command-line checking)

The checker is packaged with an HTTP client you can use from the command line to
either send documents to a locally-running instance of the checker HTTP service
— for fast command-line checking — or to a remote instance anywhere on the Web.

To check documents locally using the packaged HTTP client, do this:

  1. Start up the checker as a local HTTP service, as described in the
    Standalone web server section.

  2. Open a new terminal window and invoke the HTTP client like this:

java -cp ~/vnu.jar nu.validator.client.HttpClient FILE.html...

vnu-runtime-image/bin/java nu.validator.client.HttpClient FILE.html...

To send documents to an instance of the checker on the Web, such as
html5.validator.nu/, use the nu.validator.client.host and
nu.validator.client.port options, like this:

java -cp ~/vnu.jar -Dnu.validator.client.port=80 
    -Dnu.validator.client.host=html5.validator.nu 
    nu.validator.client.HttpClient FILE.html...

…or like this:

vnu-runtime-image/bin/java -Dnu.validator.client.port=80 
    -Dnu.validator.client.host=html5.validator.nu 
    nu.validator.client.HttpClient FILE.html...

Other options are documented below.

HTTP client options

When using the packaged HTTP client for sending documents to an instance of the
checker HTTP service for checking, you can set Java system properties to control
configuration options for the checker behavior.

For example, you can suppress warning-level messages and only show error-level
ones by setting the value of the nu.validator.client.level system property to
error, like this:

java -Dnu.validator.client.level=error 
       -cp ~/vnu.jar nu.validator.client.HttpClient FILE.html...

…or like this:

vnu-runtime-image/bin/java -Dnu.validator.client.level=error 
       -cp ~/vnu.jar nu.validator.client.HttpClient FILE.html...

Most of the properties listed below map to the common input parameters for the
checker service, as documented at
github.com/validator/validator/wiki/Service-»-Common-params.

nu.validator.client.host

Specifies the hostname of the checker for the client to connect to.

default: "127.0.0.1"

nu.validator.client.port

Specifies the hostname of the checker for the client to connect to.

default: "8888"

example: java -Dnu.validator.client.port=8080 -jar ~/vnu.jar FILE.html

nu.validator.client.level

Specifies the severity level of messages to report; to suppress
warning-level messages, and only show error-level ones, set this property to
"error".

default: [unset]

possible values: "error"

example: java -Dnu.validator.client.level=error -jar ~/vnu.jar FILE.html

nu.validator.client.parser

Specifies which parser to use.

default: "html"; or, for *.xhtml input files, "xml"

possible values: [see information at URL below]

https://github.com/validator/validator/wiki/Service-%C2%BB-Common-params#parser

nu.validator.client.charset

Specifies the encoding of the input document.

default: [unset]

nu.validator.client.content-type

Specifies the content-type of the input document.

default: "text/html"; or, for *.xhtml files, "application/xhtml+xml"

nu.validator.client.out

Specifies the output format for messages.

default: "gnu"

possible values: [see information at URL below]

https://github.com/validator/validator/wiki/Service-%C2%BB-Common-params#out

nu.validator.client.asciiquotes

Specifies whether ASCII quotation marks are substituted for Unicode smart
quotation marks in messages.

default: "yes"

possible values: "yes" or "no"

HTTP servlet options

nu.validator.servlet.bind-address

Binds the validator service to the specified IP address.

default: 0.0.0.0 [causes the checker to listen on all interfaces]

possible values: The IP address of any network interface

example: -Dnu.validator.servlet.bind-address=127.0.0.1

nu.validator.servlet.connection-timeout

Specifies the connection timeout.

default: 5000

possible values: number of milliseconds

example: -Dnu.validator.servlet.connection-timeout=5000

nu.validator.servlet.socket-timeout

Specifies the socket timeout.

default: 5000

possible values: number of milliseconds

example: -Dnu.validator.servlet.socket-timeout=5000

Pulling the Docker image

You can pull the checker Docker image from
https://ghcr.io/validator/validator in the GitHub container registry.

To pull and run the latest version of the checker:

  docker run -it --rm -p 8888:8888 ghcr.io/validator/validator:latest

To pull and run a specific tag/version of the checker from the container
registry — for example, the 17.11.1 version:

  docker run -it --rm -p 8888:8888 ghcr.io/validator/validator:17.11.1

To bind the checker to a specific address (rather than have it listening on all
interfaces):

  docker run -it --rm -p 128.30.52.73:8888:8888
  ghcr.io/validator/validator:latest

To make the checker run with a connection timeout and socket timeout different
than the default 5 seconds, use the CONNECTION_TIMEOUT_SECONDS and
SOCKET_TIMEOUT_SECONDS environment variables:

  docker run -it --rm 
     -e CONNECTION_TIMEOUT_SECONDS=15 
     -e SOCKET_TIMEOUT_SECONDS=15 
     -p 8888:8888 
     validator/validator

To make the checker run with particular Java system properties set, use the
JAVA_TOOL_OPTIONS environment variable:

  docker run -it --rm 
     -e JAVA_TOOL_OPTIONS=-Dnu.validator.client.asciiquotes=yes  
     -p 8888:8888 
     validator/validator

To define a service named vnu for use with docker compose, create a Compose
file named docker-compose.yml (for example), with contents such as the
following:

  version: '2' services:
    vnu:
      image: validator/validator ports:
        - "8888:8888"
      network_mode: "host" #so "localhost" refers to the host machine.

Build instructions

Follow the steps below to build, test, and run the checker such that you can
open http://0.0.0.0:8888/ in a Web browser to use the checker Web UI.

  1. Make sure you have git, python, and JDK 8 or above installed.

  2. Set the JAVA_HOME environment variable:

    export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 <— Ubuntu, etc.

    export JAVA_HOME=$(/usr/libexec/java_home) <— MacOS

  3. Create a working directory:

    git clone https://github.com/validator/validator.git

  4. Change into your working directory:

    cd validator

  5. Start the checker Python script:

    python ./checker.py all

The first time you run the checker Python script, you’ll need to be online and
the build will need time to download several megabytes of dependencies.

The steps above will build, test, and run the checker such that you can open
http://0.0.0.0:8888/ in a Web browser to use the checker Web UI.

Warning: Future checker releases will bind by default to the address
127.0.0.1. Your checker deployment might become unreachable unless you use the
--bind-address option to bind the checker to a different address:

    python ./checker.py --bind-address=128.30.52.73 all

Use python ./checker.py --help to see command-line options for controlling the
behavior of the script, as well as build-target names you can call separately;
e.g.:

  • python ./checker.py build # to build only

  • python ./checker.py build # test to build and test

  • python ./checker.py run # to run only

  • python ./checker.py jar # to compile vnu.jar

  • python ./checker.py update-shallow &&
      python ./checker.py dldeps &&
      python ./checker.py jar  # compile vnu.jar faster

Я использовал программу под названием Fritzing, чтобы нарисовать некоторые основные схемы Arduino, а затем экспортировать выходные данные в виде SVG. Это работает так, как ожидалось, но потом я заметил, что вывод SVG выглядит только в некоторых браузерах и только в некоторых версиях Firefox.

Поскольку Fritzing — приложение с открытым исходным кодом, я решил, что могу заглянуть в код (и, возможно, немного помочь).

Но теперь на вопрос, на что должен выглядеть правильный SVG? Какой верификатор в W3C можно использовать для проверки файла?

Я попытался использовать верификаторы, найденные на этой странице: http://validator.w3.org/dev/tests/

Но все они очень жаловались, особенно на версию SVG. Верификаторы, похоже, похожи на версии 1.0 и 1.1, но когда я смотрю на вершину этого файла, похоже, используется версия 1.2?

Это три верхние строки из проблемного файла (переформатированные для удобочитаемости):

<?xml version='1.0' encoding='UTF-8' standalone='no'?>
<!-- Created with Fritzing (http://www.fritzing.org/) -->
<svg width="3.50927in"
     x="0in"
     version="1.2"
     y="0in"
     xmlns="http://www.w3.org/2000/svg"
     height="2.81713in"
     viewBox="0 0 252.667 202.833"
     baseProfile="tiny"
     xmlns:svg="http://www.w3.org/2000/svg">

Есть ли какой-нибудь конкретный верификатор SVG 1.2, который я могу использовать?

Или я попытаюсь проверить SVG, как если бы это был классический XML файл?

(Как замечание, Fritzing, похоже, использует Qt, поэтому, если какой-то QTest я могу использовать, это может быть полезно.)

Источник

I used a program called Fritzing to draw some basic Arduino schematics, and then export the output as a SVG. This works just as expected, but then I noticed that the SVG output only looks okay in some browsers and only okay in some versions of Firefox.

Since Fritzing is a open source app I figured that I could look into the code (and maybe help out a little).

But now over to the question, what is a correct SVG supposed to look like? What verifier over at W3C can I use to check the file?

I tried to use the verifiers found on this page: http://validator.w3.org/dev/tests/

But they all complained a lot, especially about the SVG version. The verifiers seem to like version 1.0 and 1.1, but when I look at the top of this file seems to be using version 1.2?

This is the top three lines from the problematic file (reformatted for readability):

<?xml version='1.0' encoding='UTF-8' standalone='no'?>
<!-- Created with Fritzing (http://www.fritzing.org/) -->
<svg width="3.50927in"
     x="0in"
     version="1.2"
     y="0in"
     xmlns="http://www.w3.org/2000/svg"
     height="2.81713in"
     viewBox="0 0 252.667 202.833"
     baseProfile="tiny"
     xmlns:svg="http://www.w3.org/2000/svg">

Is there a specific SVG 1.2 verifier I can use?

Or shall I try to verify the SVG as if it was a classical XML file?

(As a side note, Fritzing seems to use Qt, so if there some QTest I can use it may be useful.)

Источник

As an XML-based language, SVG can be validated just as HTML is. The primary tool for this is the W3C validation service, although others are available. In order to ensure their SVG-infused pages still validate, developers need to be careful in how SVG is added to their code:

SVG Integrated Into HTML5

Perhaps the ideal case, at least in terms of clarity. Simply place your SVG code directly in the body of the HTML5 document: 

<!DOCTYPE html>
	<head>
		<title>SVG</title>
		<meta charset=utf-8>
	</head>
	<body>
		<h1>HTML5 SVG Test</h1>
		<svg height="200" xmlns="http://www.w3.org/2000/svg">
			<circle id="redcircle" cx="50" cy="50" r="50" fill="red" />
		</svg>
	</body>
</html>

The code above will validate as HTML5, while the SVG will appear as a red circle on the page.

Validating A Standalone SVG Document

The next most common scenario: you have a separate .svg file, with SVG integrated into your web page via CSS or an <img>. Feeding a correctly formatted SVG document to the W3C Markup Validation service will result in a valid page, assuming that SVG code has been used correctly: 

<svg version="1.1" xmlns="http://www.w3.org/2000/svg">

The one downside to this last approach is that the SVG document will no longer validate as SVG, but as XML. This isn’t wrong, but it’s possibly less useful.

Enjoy this piece? I invite you to follow me at twitter.com/dudleystorey to learn more.

Источник

Validating SVG ​

This article is part of SVG clean up article.

SVG can contain a lot of stuff that might be dangerous: scripts and external resources.

Style ​

Global <style> and inline style are converted to attributes.

Style complicates the process of analysing an icon structure, which is needed to later get rid of unused elements and parse the palette, so style should go. If style is too complex to parse or style overrides attribute, an exception is thrown.

During clean up, the icon is also checked for bad stuff.

Validation is very strict and opinionated.

Things that will cause validation to fail (function will throw an exception):

  • <script> is found or an event listener is found.
  • Text or font. See below.
  • Any external resources.
  • Raster images. See below.
  • Links.

svg

<svg viewBox="0 0 10 10" xmlns="http://www.w3.org/2000/svg">
 <script>
 // <![CDATA[
 window.addEventListener('DOMContentLoaded', () => {
     alert('Bad stuff!!!');
 })
 // ]]>
 </script>

 <circle cx="5" cy="5" r="4" />
</svg>

svg

<svg width="200" height="200" xmlns="http://www.w3.org/2000/svg">
   <image href="https://example.com/totally-not-a-tracker.png" height="200" width="200"/>
</svg>

Clean up function has a list of all allowed SVG tags and their attributes.

If an unknown tag is encountered, this happens:

  • If a tag belongs to a namespace, such as <rdf:RDF>, it is removed with all its children elements.
  • If a tag does not have a namespace, an exception is thrown.

Attributes ​

Clean up function also checks each attribute on each element.

All attributes that do not affect icon rendering are removed.

If an event listener is found, the function throws an exception.

class attribute is allowed.

Inline style is converted to attributes (before parsing other attributes).

Text and fonts ​

All text tags are not allowed.

Why? Because different operating systems have different fonts, it will cause the icon to render differently.

This rule cannot be disabled.

svg

<svg viewBox="0 0 240 80" xmlns="http://www.w3.org/2000/svg">
 <style>
   .small { font: italic 13px sans-serif; }
   .heavy { font: bold 30px sans-serif; }

   /* Note that the color of the text is set with the    *
    * fill property, the color property is for HTML only */
   .Rrrrr { font: italic 40px serif; fill: red; }

</style>

 <text x="20" y="35" class="small">My</text>
 <text x="40" y="35" class="heavy">cat</text>
 <text x="55" y="55" class="small">is</text>
 <text x="65" y="55" class="Rrrrr">Grumpy!</text>
</svg>

Raster images ​

Sometimes raster images are used by icons for various purposes, usually masks or masked content.

They are not allowed. Why?

  • They do not scale, thus it is no longer a vector icon.
  • Validating them adds unnecessary complications. Having content that cannot be fully validated in SVG is not acceptable.

Clean up ​

Validation is done during clean up process.

It is done with the cleanupSVG() function from Iconify Tools.

Источник

The Nu Html Checker (v.Nu) Chat room Download latest

The Nu Html Checker (v.Nu) helps you catch unintended mistakes in your HTML,
CSS, and SVG. It enables you to batch-check documents from the command
line and from other scripts/apps, and to deploy your own instance of the
checker as a service (like validator.w3.org/nu). Its source code is
available, as are instructions on how to build, test, and run the
code.

A Dockerfile (see Pulling the Docker image below) and npm,
pip, and brew packages are also available.

It is released upstream in these formats:

  • pre-compiled Linux, Windows, and macOS binaries that include an embedded
    Java runtime

  • vnu.jar — a portable version you can use on any system that has Java 8 or
    above installed

  • vnu.war — for deploying the checker service through a servlet container
    such as Tomcat

Note: The vnu.jar and vnu.war files require you to have Java 8 or above
installed. The pre-compiled Linux, Windows, and macOS binaries don’t require you
to have any version of Java already installed at all.

You can get the latest release or run docker run -it --rm -p 8888:8888 ghcr.io/validator/validator:latest, npm install vnu-jar,
npm install --registry=https://npm.pkg.github.com @validator/vnu-jar,
brew install vnu, or pip install html5validator and see the
Usage and Web-based checking sections below. Or automate your document
checking with a frontend such as:

  • Grunt plugin for HTML validation or Gulp plugin for HTML
    validation or Maven plugin for HTML validation

  • html5validator pip package (for integration in Travis CI, CircleCI,
    CodeShip, Jekyll, Pelican, etc.)

  • LMVTFY: Let Me Validate That For You (auto-check JSFiddle/JSBin, etc.,
    links in GitHub issue comments)

Usage

Run the checker with one of the following invocations:

• vnu-runtime-image/bin/vnu OPTIONS FILES (Linux or macOS)

• vnu-runtime-imagebinvnu.bat OPTIONS FILES (Windows)

• java -jar ~/vnu.jar OPTIONS FILES (any system with Java8+ installed)

…where FILES are the documents to check, and OPTIONS are zero or more of
the following options:

--errors-only --Werror --exit-zero-always --stdout --asciiquotes
--user-agent USER_AGENT --no-langdetect --no-stream --filterfile FILENAME
--filterpattern PATTERN --css --skip-non-css --also-check-css --svg
--skip-non-svg --also-check-svg --xml --html --skip-non-html
--format gnu|xml|json|text --help --verbose --version

The Options section below provides details on each option, and the rest of
this section provides some specific examples.

Note: Throughout these examples, replace ~/vnu.jar with the actual path to
that jar file on your system, and replace vnu-runtime-image/bin/vnu and
vnu-runtime-imagebinvnu.bat with the actual path to the vnu or vnu.bat
program on your system — or if you add the vnu-runtime-image/bin or
vnu-runtime-imagebin directory your system PATH environment variable, you
can invoke the checker with just vnu.

To check one or more documents from the command line:

  vnu-runtime-image/bin/vnu      FILE.html FILE2.html FILE3.html...

  vnu-runtime-imagebinvnu.bat  FILE.html FILE2.html FILE3.html...

  java -jar ~/vnu.jar            FILE.html FILE2.html FILE3.html...

Note: If you get a StackOverflowError error when invoking the checker, try
adjusting the thread stack size by providing the -Xss option to java:

  java -Xss512k -jar ~/vnu.jar ...

  vnu-runtime-image/bin/java -Xss512k 
      -m vnu/nu.validator.client.SimpleCommandLineValidator ...

To check all documents in a particular directory DIRECTORY_PATH as HTML:

  java -jar ~/vnu.jar            DIRECTORY_PATH

  vnu-runtime-image/bin/vnu      DIRECTORY_PATH

  vnu-runtime-imagebinvnu.bat  DIRECTORY_PATH

More examples

Note: The examples in this section assume you have the
vnu-runtime-image/bin or vnu-runtime-imagebin directory in your system
PATH environment variable. If you’re using the jar file instead, replace vnu
in the examples with java -jar ~/vnu.jar.

To check all documents in a particular directory DIRECTORY_PATH as HTML, but
skip any documents whose names don’t end with the extensions .html, .htm,
.xhtml, or .xht:

  vnu --skip-non-html DIRECTORY_PATH

To check all documents in a particular directory as CSS:

  vnu --css DIRECTORY_PATH

To check all documents in a particular directory as CSS, but skip any documents
whose names don’t end with the extension .css:

  vnu --skip-non-css DIRECTORY_PATH

To check all documents in a particular directory, with documents whose names end
in the extension .css being checked as CSS, and all other documents being
checked as HTML:

  vnu --also-check-css DIRECTORY_PATH

To check all documents in a particular directory as SVG:

  vnu --svg DIRECTORY_PATH

To check all documents in a particular directory as SVG, but skip any documents
whose names don’t end with the extension .svg:

  vnu --skip-non-svg DIRECTORY_PATH

To check all documents in a particular directory, with documents whose names end
in the extension .svg being checked as SVG, and all other documents being
checked as HTML:

  vnu --also-check-svg DIRECTORY_PATH

To check a Web document:

  vnu _URL_

  example: vnu http://example.com/foo

To check standard input:

  vnu -

  example:

  echo '<!doctype html><title>...' | vnu -

  echo '<!doctype html><title>...' | java -jar ~/vnu.jar -

Options

When used from the command line as described in this section, the checker
provides the following options:

—asciiquotes

Specifies whether ASCII quotation marks are substituted for Unicode smart
quotation marks in messages.

default: [unset; Unicode smart quotation marks are used in messages]

—errors-only

Specifies that only error-level messages and non-document-error messages are
reported (so that warnings and info messages are not reported).

default: [unset; all messages reported, including warnings & info messages]

—Werror

Makes the checker exit non-zero if any warnings are encountered (even if
there are no errors).

default: [unset; checker exits zero if only warnings are encountered]

—exit-zero-always

Makes the checker exit zero even if errors are reported for any documents.

default: [unset; checker exits 1 if errors are reported for any documents]

—stdout

Makes the checker report errors and warnings to stdout rather than stderr.

default: [unset; checker reports errors and warnings to stderr]

—filterfile FILENAME

Specifies a filename. Each line of the file contains either a regular
expression or starts with "#" to indicate the line is a comment. Any error
message or warning message that matches a regular expression in the file is
filtered out (dropped/suppressed).

default: [unset; checker does no message filtering]

—filterpattern REGEXP

Specifies a regular expression. Any error message or warning message that
matches the regular expression is filtered out (dropped/suppressed).

As with all other checker options, this option may only be specified once.
So to filter multiple error messages or warning messages, you must provide a
single regular expression that will match all the messages. The typical way
to do that for regular expressions is to OR multiple patterns together using
the "|" character.

default: [unset; checker does no message filtering]

—format format

Specifies the output format for reporting the results.

default: "gnu"

possible values: "gnu", "xml", "json", "text" [see information at URL below]

https://github.com/validator/validator/wiki/Service-%C2%BB-Common-params#out

—help

Shows detailed usage information.

—skip-non-css

Check documents as CSS but skip documents that don’t have *.css extensions.

default: [unset; all documents found are checked]

—css

Force all documents to be checked as CSS, regardless of extension.

default: [unset]

—skip-non-svg

Check documents as SVG but skip documents that don’t have *.svg extensions.

default: [unset; all documents found are checked]

—svg

Force all documents to be checked as SVG, regardless of extension.

default: [unset]

—skip-non-html

Skip documents that don’t have *.html, *.htm, *.xhtml, or *.xht extensions.

default: [unset; all documents found are checked, regardless of extension]

—html

Forces any *.xhtml or *.xht documents to be parsed using the HTML parser.

default: [unset; XML parser is used for *.xhtml and *.xht documents]

—xml

Forces any *.html documents to be parsed using the XML parser.

default: [unset; HTML parser is used for *.html documents]

—also-check-css

Check CSS documents (in addition to checking HTML documents).

default: [unset; no documents are checked as CSS]

—also-check-svg

Check SVG documents (in addition to checking HTML documents).

default: [unset; no documents are checked as SVG]

—user-agent USER_AGENT

Specifies the value of the User-Agent request header to send when checking
HTTPS/HTTP URLs.

default: "Validator.nu/LV"

—no-langdetect

Disables language detection, so that documents are not checked for missing
or mislabeled html[lang] attributes.

default: [unset; language detection & html[lang] checking are performed]

—no-stream

Forces all documents to be be parsed in buffered mode instead of streaming
mode (causes some parse errors to be treated as non-fatal document errors
instead of as fatal document errors).

default: [unset; non-streamable parse errors cause fatal document errors]

—verbose

Specifies "verbose" output. (Currently this just means that the names of
files being checked are written to stdout.)

default: [unset; output is not verbose]

—version

Shows the checker version number.

Web-based checking

The Nu Html Checker — along with being usable as a standalone command-line
client — can be run as an HTTP service, similar to
validator.w3.org/nu, for browser-based checking of HTML documents, CSS
stylesheets, and SVG images over the Web. To that end, the checker is released
as several separate packages:

  • Linux, Windows, and macOS binaries for deploying the checker as a simple
    self-contained service on any system

  • vnu.jar for deploying the checker as a simple self-contained service on a
    system with Java installed

  • vnu.war for deploying the checker to a servlet container such as Tomcat

All deployments expose a REST API that enables checking of HTML documents, CSS
stylesheets, and SVG images from other clients, not just web browsers. And the
Linux, Windows, and macOS binaries and vnu.jar package also include a simple
HTTP client that enables you to either send documents to a locally-running
instance of the checker HTTP service — for fast command-line checking — or to
any remote instance of the checker HTTP service running anywhere on the Web.

The latest releases of the Linux, Windows, and macOS binaries and vnu.jar and
vnu.war packages are available from the validator project at github. The
following are detailed instructions on using them.

Note: Throughout these instructions, replace ~/vnu.jar with the actual
path to that jar file on your system, and replace vnu-runtime-image/bin/java
and vnu-runtime-imagebinjava.exe with the actual path to the checker java
or java.exe program on your system — or if you add the vnu-runtime-image/bin
or vnu-runtime-imagebin directory your system PATH environment variable,
you can invoke the checker with just java nu.validator.servlet.Main 8888.

Standalone web server

To run the checker as a standalone service (using a built-in Jetty server), open
a new terminal window and invoke the checker like this:

java -cp ~/vnu.jar              nu.validator.servlet.Main 8888

vnu-runtime-image/bin/java      nu.validator.servlet.Main 8888

vnu-runtime-imagebinjava.exe  nu.validator.servlet.Main 8888

Then open http://0.0.0.0:8888 in a browser. (To listen on a different
port, replace 8888 with the port number.)

Warning: Future checker releases will bind by default to the address
127.0.0.1. Your checker deployment might become unreachable unless you use the
nu.validator.servlet.bind-address system property to bind the checker to a
different address:

java -cp ~/vnu.jar 
    -Dnu.validator.servlet.bind-address=128.30.52.73 
    nu.validator.servlet.Main 8888

vnu-runtime-image/bin/java 
    -Dnu.validator.servlet.bind-address=128.30.52.73 
    nu.validator.servlet.Main 8888

vnu-runtime-imagebinjava.exe  
    -Dnu.validator.servlet.bind-address=128.30.52.73 
    nu.validator.servlet.Main 8888

When you open http://0.0.0.0:8888 (or whatever URL corresponds to the
nu.validator.servlet.bind-address value you’re using), you’ll see a form
similar to validator.w3.org/nu that allows you to enter the URL of an HTML
document, CSS stylesheet, or SVG image, and have the results of checking that
resource displayed in the browser.

Note: If you get a StackOverflowError error when using the checker, try
adjusting the thread stack size by providing the -Xss option to java:

  java -Xss512k -cp ~/vnu.jar nu.validator.servlet.Main 8888

  vnu-runtime-image/bin/java -Xss512k -m vnu/nu.validator.servlet.Main 8888

Deployment to servlet container

To run the checker inside of an existing servlet container such as Apache Tomcat
you will need to deploy the vnu.war file to that server following its
documentation. For example, on Apache Tomcat you could do this using the
Manager application or simply by copying the file to the webapps
directory (since that is the default appBase setting). Typically you would see
a message similar to the following in the catalina.out log file.

May 7, 2014 4:42:04 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/lib/tomcat7/webapps/vnu.war

Assuming your servlet container is configured to receive HTTP requests sent to
localhost on port 80 and the context root of this application is vnu
(often the default behavior is to use the WAR file’s filename as the context
root unless one is explicitly specified) you should be able to access the
application by connecting to http://localhost/vnu/.

Note: You may want to customize the /WEB-INF/web.xml file inside the WAR
file (you can use any ZIP-handling program) to modify the servlet filter
configuration. For example, if you wanted to disable the inbound-size-limit
filter, you could comment out that filter like this:

<!--
  <filter>
      <filter-name>inbound-size-limit-filter</filter-name>
      <filter-class>nu.validator.servlet.InboundSizeLimitFilter</filter-class>
  </filter>
  <filter-mapping>
      <filter-name>inbound-size-limit-filter</filter-name>
      <url-pattern>/*</url-pattern>
  </filter-mapping>
-->

HTTP client (for fast command-line checking)

The checker is packaged with an HTTP client you can use from the command line to
either send documents to a locally-running instance of the checker HTTP service
— for fast command-line checking — or to a remote instance anywhere on the Web.

To check documents locally using the packaged HTTP client, do this:

  1. Start up the checker as a local HTTP service, as described in the
    Standalone web server section.

  2. Open a new terminal window and invoke the HTTP client like this:

java -cp ~/vnu.jar nu.validator.client.HttpClient FILE.html...

vnu-runtime-image/bin/java nu.validator.client.HttpClient FILE.html...

To send documents to an instance of the checker on the Web, such as
html5.validator.nu/, use the nu.validator.client.host and
nu.validator.client.port options, like this:

java -cp ~/vnu.jar -Dnu.validator.client.port=80 
    -Dnu.validator.client.host=html5.validator.nu 
    nu.validator.client.HttpClient FILE.html...

…or like this:

vnu-runtime-image/bin/java -Dnu.validator.client.port=80 
    -Dnu.validator.client.host=html5.validator.nu 
    nu.validator.client.HttpClient FILE.html...

Other options are documented below.

HTTP client options

When using the packaged HTTP client for sending documents to an instance of the
checker HTTP service for checking, you can set Java system properties to control
configuration options for the checker behavior.

For example, you can suppress warning-level messages and only show error-level
ones by setting the value of the nu.validator.client.level system property to
error, like this:

java -Dnu.validator.client.level=error 
       -cp ~/vnu.jar nu.validator.client.HttpClient FILE.html...

…or like this:

vnu-runtime-image/bin/java -Dnu.validator.client.level=error 
       -cp ~/vnu.jar nu.validator.client.HttpClient FILE.html...

Most of the properties listed below map to the common input parameters for the
checker service, as documented at
github.com/validator/validator/wiki/Service-»-Common-params.

nu.validator.client.host

Specifies the hostname of the checker for the client to connect to.

default: "127.0.0.1"

nu.validator.client.port

Specifies the hostname of the checker for the client to connect to.

default: "8888"

example: java -Dnu.validator.client.port=8080 -jar ~/vnu.jar FILE.html

nu.validator.client.level

Specifies the severity level of messages to report; to suppress
warning-level messages, and only show error-level ones, set this property to
"error".

default: [unset]

possible values: "error"

example: java -Dnu.validator.client.level=error -jar ~/vnu.jar FILE.html

nu.validator.client.parser

Specifies which parser to use.

default: "html"; or, for *.xhtml input files, "xml"

possible values: [see information at URL below]

https://github.com/validator/validator/wiki/Service-%C2%BB-Common-params#parser

nu.validator.client.charset

Specifies the encoding of the input document.

default: [unset]

nu.validator.client.content-type

Specifies the content-type of the input document.

default: "text/html"; or, for *.xhtml files, "application/xhtml+xml"

nu.validator.client.out

Specifies the output format for messages.

default: "gnu"

possible values: [see information at URL below]

https://github.com/validator/validator/wiki/Service-%C2%BB-Common-params#out

nu.validator.client.asciiquotes

Specifies whether ASCII quotation marks are substituted for Unicode smart
quotation marks in messages.

default: "yes"

possible values: "yes" or "no"

HTTP servlet options

nu.validator.servlet.bind-address

Binds the validator service to the specified IP address.

default: 0.0.0.0 [causes the checker to listen on all interfaces]

possible values: The IP address of any network interface

example: -Dnu.validator.servlet.bind-address=127.0.0.1

nu.validator.servlet.connection-timeout

Specifies the connection timeout.

default: 5000

possible values: number of milliseconds

example: -Dnu.validator.servlet.connection-timeout=5000

nu.validator.servlet.socket-timeout

Specifies the socket timeout.

default: 5000

possible values: number of milliseconds

example: -Dnu.validator.servlet.socket-timeout=5000

Pulling the Docker image

You can pull the checker Docker image from
https://ghcr.io/validator/validator in the GitHub container registry.

To pull and run the latest version of the checker:

  docker run -it --rm -p 8888:8888 ghcr.io/validator/validator:latest

To pull and run a specific tag/version of the checker from the container
registry — for example, the 17.11.1 version:

  docker run -it --rm -p 8888:8888 ghcr.io/validator/validator:17.11.1

To bind the checker to a specific address (rather than have it listening on all
interfaces):

  docker run -it --rm -p 128.30.52.73:8888:8888
  ghcr.io/validator/validator:latest

To make the checker run with a connection timeout and socket timeout different
than the default 5 seconds, use the CONNECTION_TIMEOUT_SECONDS and
SOCKET_TIMEOUT_SECONDS environment variables:

  docker run -it --rm 
     -e CONNECTION_TIMEOUT_SECONDS=15 
     -e SOCKET_TIMEOUT_SECONDS=15 
     -p 8888:8888 
     validator/validator

To make the checker run with particular Java system properties set, use the
JAVA_TOOL_OPTIONS environment variable:

  docker run -it --rm 
     -e JAVA_TOOL_OPTIONS=-Dnu.validator.client.asciiquotes=yes  
     -p 8888:8888 
     validator/validator

To define a service named vnu for use with docker compose, create a Compose
file named docker-compose.yml (for example), with contents such as the
following:

  version: '2' services:
    vnu:
      image: validator/validator ports:
        - "8888:8888"
      network_mode: "host" #so "localhost" refers to the host machine.

Build instructions

Follow the steps below to build, test, and run the checker such that you can
open http://0.0.0.0:8888/ in a Web browser to use the checker Web UI.

  1. Make sure you have git, python, and JDK 8 or above installed.

  2. Set the JAVA_HOME environment variable:

    export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 <— Ubuntu, etc.

    export JAVA_HOME=$(/usr/libexec/java_home) <— MacOS

  3. Create a working directory:

    git clone https://github.com/validator/validator.git

  4. Change into your working directory:

    cd validator

  5. Start the checker Python script:

    python ./checker.py all

The first time you run the checker Python script, you’ll need to be online and
the build will need time to download several megabytes of dependencies.

The steps above will build, test, and run the checker such that you can open
http://0.0.0.0:8888/ in a Web browser to use the checker Web UI.

Warning: Future checker releases will bind by default to the address
127.0.0.1. Your checker deployment might become unreachable unless you use the
--bind-address option to bind the checker to a different address:

    python ./checker.py --bind-address=128.30.52.73 all

Use python ./checker.py --help to see command-line options for controlling the
behavior of the script, as well as build-target names you can call separately;
e.g.:

  • python ./checker.py build # to build only

  • python ./checker.py build test # to build and test

  • python ./checker.py run # to run only

  • python ./checker.py jar # to compile vnu.jar

  • python ./checker.py update-shallow &&
      python ./checker.py dldeps &&
      python ./checker.py jar       # to compile vnu.jar faster

Open Source Agenda is not affiliated with «Validator Validator» Project. README Source: validator/validator

Источник

Понравилась статья? Поделить с друзьями:
  • Проверка ssd на ошибки windows 10 программа
  • Проверка ssd диска на ошибки windows 10 скачать
  • Проверка ssd диска ubuntu на ошибки
  • Проверка ssd plextor на ошибки
  • Проверка ram на ошибки windows 10