CVS log for validator/htdocs/config/validator.conf

Request diff between arbitrary revisions

Fixed a small typo: s/chacking/checking/.

sample conf to enable HTML5 external checker

first pass at implementing language negotiation/selection. Can certainly be improved, but it works

Should not hardcode tidy conf path, make it configurable in main conf file

porting 0.7.4 changes to HEAD:
* SOAP API can be disabled/enabled

Plugging the (old, unused? so far) option to enable/disable the soap output
to the actual API. Changing default to enabled in config file, maintainers
wishing to disable can now use the directive in configuration file, and
validator would then return 503 service not available to output=soap12 requests.

goodbye onsgmls.

Noticed that onsgmls -c is very picky with paths, and will not find the catalogs
if their path has a double slash. Adding a notice accordingly.

Adding application/mathml+xml to list of acceptable media types.
Can't find direct pointer to registration at the moment, but at least
it is in rfc3023.

First cut at limiting recursion; cf. Bug #204.

Implement more sophisticated parsemode determination, and admit to setting
parse mode and not the document's "type". Inline MIME mapping into v.conf.

moving htdocs/config/verbosemsg.cfg to share/templates/en_US.UTF-8/error_messages.cfg
We don't need to give its path in the general config, any more

the verbosemsg file is (supposedly) in the same directory as the other config files - fixing path

re-adding error message explanations - still misses Jim's bit of JS to load them only once.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=906

Don't hardcode en_US in base template path; move it to Perl code instead so
we can conneg that sometime later.

Improve docs.

Add example of and comment for the "Enable SOAP" config var. This was the
last missing var that I'm aware of, and thus this closes Bug #747 when
combined with the other config cleanup.

More config cleanup. Provide SetEnv for base path, and check all paths for
existance and readability (-d and -r). This closes Bug #863.

Landing first cut of new config layout. Clean up various config names,
nuke obsoleted config files, and start to make use of new Types Registry.

There's breakage. There's unfinished pieces (type.cfg). Fun all around! :-)

Cleaning up local paths from sample config.

Merging from branch validator-0_6_0-branch, at tag validator-0_6_7-pre2.
(0.6.7 is missing relnotes and other minor tweaks)

s/URI/URL/g; # Or at least everywhere it's possible/makes sense. :-)

Merging from branch validator-0_6_0-branch, at tag validator-0_6_5-release.

Remove extra slash from XHTML 1.0 Basic image URI, thanks to Jörg Hartmann.
http://lists.w3.org/Archives/Public/www-validator/2003Nov/0044.html

Configurable template path, thanks to Struan Donald.
http://lists.w3.org/Archives/Public/www-validator/2003Nov/0059.html

Land developer snapshot WS framework. Disabled by default (including
loading the relevant modules only if enabled) and if the modules are
missing. Not really functioning, but gives a starting point for further
development. Proof-of-Concept code in Perl and Python has been written and
will likely land along with more fleshed out framework code.

Landing new error explanations code. Now uses OpenSP's message IDs to
catch each emitted message and a Config::General config file to store
custom explanations. An intended future development is context-sensitive
hints and tips, l10n/i18n, and overriding of the messages themselves.

For now it shows the original error message and merely includes the
verbose explanation. A future enhancement would be to supress the
original error message alltogether and display our own customized
version (which is possibly localized based on Accept-Language headers).

A minimal script for parsing the OpenSP message file is included and
should be relatively easy to modify to support migrating error
explanations and other value-add data if and when OpenSP updates.

The major unresolved points remaining revolve around presentation:

  * Should explanations be triggered by the Verbose switch?
    Or should they merely become more verbose with it enabled?

  * Can we use JavaScript to display explanations on demand?
    (Jim is working on it, but we'll see whether he can come
     up with something that will scale well (both up and down)).

  * How best to encourage users to submit improved explanations?

  * Is it appropriate to include the "Help Wanted" spiels in the
    production release?

Otherwise this code should be reasonably solid.

Add trailing newline at end of file.

* Implement option to disable validating resources at private IP addresses,
  and have them disabled by default.  Config option: "Allow Private IPs".
* The Net::IP module is required now.

Enable data: URI scheme.

Enable data: URI scheme.

s/MarkUp/Markup/ for consistency with other w3.org.

s/MarkUp/Markup/ for consistency with w3.org.

Applying patches from Dave Evans (with minor tweaks).
See <http://lists.w3.org/Archives/Public/www-validator/2003Jan/0005.html>

Landing new config code. Badges are borken, the link to the relevant spec
from "This page is valid Foo" is borken, and there is a good chance the
DOCTYPE Override is borken. Otherwise this should be more or less working.

Make use of Config::General's -InterPolateVars option.

Remove no longer used Header/Footer params.

Adding validator.conf (renamed check.cfg) on 0.6.0-branch (was added only
on HEAD during rename).

Tweak CSS for template code.

Renaming check.cfg to validator.conf to fit in with new config scheme.