Hunting down non-HTTPS links
This commit is contained in:
parent
210f011a09
commit
3af5bbab4a
3
TODO
3
TODO
@ -1,4 +1,3 @@
|
||||
* HTTPS for all links (grep http:// *.xml)
|
||||
* lsr.atom (requires some porting)
|
||||
* link to find-subtags
|
||||
* post search engine
|
||||
* validity HTML and CSS and Atom
|
||||
|
11
index.xml
11
index.xml
@ -5,13 +5,16 @@
|
||||
<li><a href="whatare.html">What are language tags?</a></li>
|
||||
<li><a href="why-tagging.html">Why tagging</a>?</li>
|
||||
<li>Tag <a href="tag-wisely.html">wisely</a></li>
|
||||
<li>The <wikipedia name="IETF language code">Wikipedia article</wikipedia></li>
|
||||
<li>The <wikipedia name="IETF language code">Wikipedia
|
||||
article</wikipedia></li>
|
||||
<li><a href="search.html">Search the language registry</a></li>
|
||||
<li>The <a
|
||||
href="https://www.w3.org/International/articles/language-tags/">excellent
|
||||
article from the W3C</a> about language tags</li>
|
||||
<li>Also from the <wikipedia>W3C</wikipedia>, a <a href="http://www.w3.org/International/tutorials/language-decl/">tutorial "Declaring Language in XHTML and HTML"</a></li>
|
||||
<li><a href="https://r12a.github.io/app-subtags/index.html">Search subtags online in the registry</a> (some explanations are provided, but this tool is more useful if you know the concepts behind the registry)</li>
|
||||
<li>Browse <a href="http://unicode.org/cldr/utility/languageid.jsp">language tags</a> and see their meaning</li>
|
||||
<li>Also from the <wikipedia>W3C</wikipedia>, a <a href="https://www.w3.org/International/tutorials/language-decl/">tutorial "Declaring Language in XHTML and HTML"</a></li>
|
||||
<li><a href="https://r12a.github.io/app-subtags/index.html">Another
|
||||
way to search subtags online in the registry</a> (some explanations are provided, but this tool is more useful if you know the concepts behind the registry)</li>
|
||||
<li>Browse <a href ="https://util.unicode.org/UnicodeJsps/languageid.jsp">language tags</a> and see their meaning</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="menu3">
|
||||
|
@ -7,7 +7,7 @@ probably already there. But, if it is not, you can ask for the
|
||||
registration of a new subtag. This text explains how, but the
|
||||
complete and authoritative explanation is in <a
|
||||
href="https://www.rfc-editor.org/info/rfc5646">RFC 5646</a>,
|
||||
specially its section 3.5, <a href="http://tools.ietf.org/html/rfc5646#section-3.5">Registration Procedure for Subtags</a>". It is
|
||||
specially its section 3.5, <a href="https://datatracker.ietf.org/doc/html/rfc5646#section-3.5">Registration Procedure for Subtags</a>". It is
|
||||
recommended to read at least this section.</p>
|
||||
<p>Before you start, a warning: the process takes time, documentation
|
||||
and the ability to defend your proposal and to back it with facts and
|
||||
@ -29,7 +29,7 @@ you want the IETF to make another choice). We then concentrate on
|
||||
"variant" subtags.</li>
|
||||
</ul>
|
||||
<p>The process is the following (it is a simplified version; did I
|
||||
tell you to read the full story in <a href="http://tools.ietf.org/html/rfc5646#section-3.5">section 3.5</a> of <a
|
||||
tell you to read the full story in <a href="https://datatracker.ietf.org/doc/html/rfc5646#section-3.5">section 3.5</a> of <a
|
||||
href="https://www.rfc-editor.org/info/rfc5646">RFC 5646</a>?):</p>
|
||||
<ol>
|
||||
<li>Collect background information, typically references to published
|
||||
@ -37,7 +37,7 @@ descriptions of the language or dialect. A Wikipedia page is possible but
|
||||
may be insufficient, specially since the page may change
|
||||
easily. Stable references are preferred.</li>
|
||||
<li>Choose a subtag which must conform to the syntax rules explained
|
||||
in RFC 5646 (<a href="http://tools.ietf.org/html/rfc5646#section-2.1">section 2.1</a>). A variant subtag must be either a string of
|
||||
in RFC 5646 (<a href="https://datatracker.ietf.org/doc/html/rfc5646#section-2.1">section 2.1</a>). A variant subtag must be either a string of
|
||||
five to eight alphanumeric characters, <em>or</em> a string of four
|
||||
alphanumeric characters, starting with a digit. So, <code><wikipedia
|
||||
name="Valencia (province)">valencian</wikipedia></code> is illegal
|
||||
|
@ -13,12 +13,14 @@ whitespace optional-comment":
|
||||
2006-11-15 registry, they may be valid now, the current registry is <lsr-version/>!)</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="http://unicode.org/cldr/data/tools/java/org/unicode/cldr/util/data/langtagTest.txt">ICU test suite</a></li>
|
||||
<li>ICU test suite, now apparently only <a
|
||||
href="https://android.googlesource.com/platform/external/cldr/+/refs/heads/cldr-release-32-0-1/tools/java/org/unicode/cldr/util/data/langtagTest.txt">in
|
||||
the Android source code</a></li>
|
||||
<li>From the <wikipedia name="Formal grammar">grammar</wikipedia> in
|
||||
the RFC, you can use programs like <a href="http://www.quut.com/abnfgen/">abnfgen</a> or <a
|
||||
href="http://www.bortzmeyer.org/eustathius-test-grammars.html">eusthathius</a> to generate tags for testing a
|
||||
the RFC, you can use programs like <a href="https://www.quut.com/abnfgen/">abnfgen</a> or <a
|
||||
href="https://www.bortzmeyer.org/eustathius-test-grammars.html">eusthathius</a> to generate tags for testing a
|
||||
parser. <em>Warning</em>: these tags will follow the grammar but may
|
||||
not be well-formed, since some rules are not in the grammar (for
|
||||
instance the rule that no two singletons must be identical).</li>
|
||||
</ul>
|
||||
</page>
|
||||
</page>
|
||||
|
@ -61,6 +61,6 @@ because it brings no short-term benefits. Things are becoming better
|
||||
but certainly too slowly.</p>
|
||||
<h2>More readings</h2>
|
||||
<ul>
|
||||
<li><a href="http://www.w3.org/TR/i18n-html-tech-lang/#ri20050208.091505539">Why specify language?</a> by the W3C</li>
|
||||
<li><a href="https://www.w3.org/TR/i18n-html-tech-lang/#ri20050208.091505539">Why specify language?</a> by the W3C</li>
|
||||
</ul>
|
||||
</page>
|
||||
|
Loading…
Reference in New Issue
Block a user