Merge pull request #71 from w3c/tripu/various-fixes

Various fixes after merging #70

Author: tripu

README.md

@@ -1,4 +1,4 @@
-# W3C's i18n Checker 
+# W3C's i18n Checker
 
 This checker performs various tests on a Web Page to determine its level of internationalisation-friendliness. It also summarises key internationalization information about a page, such as character encoding and language declarations, etc.
 
@@ -13,14 +13,12 @@ This software is free/open source, licensed under the terms of the [W3C software
 
 There is a set of [installation notes](https://github.com/w3c/i18n-checker/wiki/Installation-notes) for those who want to work with the source code.
 
-Proposals for changes to the checker must be submitted via pull requests, and will need to be reviewed by someone other than the proposer before merging with the master branch. The file tests/index.php should be run before submitting a pull request, to ensure that the changes don't break existing tests. 
+Proposals for changes to the checker must be submitted via pull requests, and will need to be reviewed by someone other than the proposer before merging with the master branch. The file `www/test.php` should be run before submitting a pull request, to ensure that the changes don't break existing tests.
 
-When submitting a pull requests for a new check, you should 
+When submitting a pull requests for a new check, you should
 
 1. add new tests for that check in tests/data.php
-2. add calls to those tests to tests/index.php, and ensure that none of the previous tests break
+2. add calls to those tests to `www/test.php`, and ensure that none of the previous tests break
 3. add the check to doc/checker.en.php
 4. add parsed data that may be useful elsewhere to the class.Parser.php file, but add the actual test to class.Checker.php
 5. add the full set of messages and links needed for the report to langs/en.properties
-
-

langs/en.properties

@@ -44,7 +44,7 @@ footer_home="Home"
 footer_home_title="Go to the Home Page for The  W3C Internationalization Checker Service"
 footer_translation="Translations"
 footer_translation_title="Help us translate this service"
-footer_version="Version 2"
+footer_version="Version 2.0.3"
 footer_version_title="Follow the link for change log"
 
 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
@@ -395,7 +395,7 @@ rep_lang_malformed_attr_expl[]="Attributes values must contain a maximum of one
 rep_lang_malformed_attr_expl[]="<p><b class="note">Note:</b> This check doesn't count subtags following the <code class='kw' translate='no'>x</code>-, <code class='kw' translate='no'>t-</code> or <code class='kw' translate='no'>u-</code> singletons.</p>"
 rep_lang_malformed_attr_expl[]="<p><b class="note">Note:</b> The information table at the top of this page lists all the language tags used in the page tested. This report doesn't capture all the potential issues related to those language tags. The language tags listed in the table each link to the Language Subtag Lookup tool. You should follow those links to get a fuller picture.</p>"
 rep_lang_malformed_attr_todo[]="Change the attribute values to conform to BCP47 syntax rules."
-rep_lang_malformed_attr_todo[]="You can check whether your language tag value is valid using the 'check' input of the <a href="https://r12a.github.io/apps-subtags/">Language Subtag Lookup</a> tool."
+rep_lang_malformed_attr_todo[]="You can check whether your language tag value is valid using the 'check' input of the <a href="https://r12a.github.io/app-subtags/">Language Subtag Lookup</a> tool."
 rep_lang_malformed_attr_link[]="<a target='_blank' href='http://www.w3.org/International/techniques/authoring-html#gslang'>Language declarations explained</a>"
 rep_lang_malformed_attr_link[]="<a target='_blank' href='http://www.w3.org/International/techniques/authoring-html#langvalues'>Choosing language values</a>"
 

src/class.Checker.php

@@ -255,7 +255,7 @@ private function addInfoLangTags() {
 		$value = null;
 		if ($this->doc->langTags != null) {
 			foreach ($this->doc->langTags as $val) {
-				$results[] = '<a target="_blank" href="http://r12a.github.io/apps-subtags/?check='.$val.'">'.$val.'</a>'; 
+				$results[] = '<a target="_blank" href="http://r12a.github.io/app-subtags/?check='.$val.'">'.$val.'</a>'; 
 				}
 		}
 		$code = count($results) == 0 ? null : 'Click each tag to check it.';

www/versions.php

@@ -14,10 +14,10 @@
 <h2>Change log for the W3C Internationalization (i18n) Checker</h2>
 <p>This page documents changes to the checker. The page <a href="https://www.w3.org/International/quicktips/doc/checker">Internationalization Checker reports</a> lists all checks made, with the report messages and links to tests. New and updated checks listed below link to that page for details.</p>
 <p>Please let us know about bugs and missing features using the <a href="https://github.com/w3c/i18n-checker/issues">feedback form</a>. Detailed change logs can be found in the <a href="https://github.com/w3c/i18n-checker/commits/master">GitHub commit list</a>.</p>
-<h3 id="about">Version 2</h3>
+<h3 id="about">Version 2.0.3</h3>
 
 <div class="bd compact">
-	<p>Version 2 of the checker moves away from checking against particular specifications to checking how a page will work in a browser. For the most part, it assumes that pages will be parsed using an HTML5 compliant parser. Pages served as application/xhtml+xml have some significant differences with regards to character encoding and language declarations, however, and these are taken into account if the checker detects that the page being checked is served as XML.</p>
+	<p>Version 2.0.3 of the checker moves away from checking against particular specifications to checking how a page will work in a browser. For the most part, it assumes that pages will be parsed using an HTML5 compliant parser. Pages served as application/xhtml+xml have some significant differences with regards to character encoding and language declarations, however, and these are taken into account if the checker detects that the page being checked is served as XML.</p>
 	<p>The following new checks were added. Follow the links for details.</p>
 	<ul style="margin-left:3em;">
 	  <li><a href="https://www.w3.org/International/quicktips/doc/checker#rep_charset_bom_diff_encoding">UTF-8 BOM disagrees with another declaration</a></li>