Update edDraftURI

gap-analysis/index.html

@@ -22,7 +22,7 @@
       noRecTrack:           true,
       shortName:            "clreq-gap",
       copyrightStart:       "2018",
-      edDraftURI:           "https://w3c.github.io/clreq/gap-analysis/",
+      edDraftURI:           "https://www.w3.org/International/clreq/gap-analysis/",
 
       // if this is a LCWD, uncomment and set the end of its review period
       // lcEnd: "2009-08-05",
@@ -37,14 +37,14 @@
 
       group: 		"i18n",
       github: 		"w3c/clreq",
-	  
+
 	preProcess: [
 		() => { addPrompts() },
 		async () => { await getAllData('clreq','doc:clreq') }
 		],
 
 	postProcess: [
-		async function importStyleSheet() { 
+		async function importStyleSheet() {
 			const elems = document.querySelectorAll(`link[rel='stylesheet'][data-import]`)
 			await Promise.all(
 				[...elems].map(async link => {
@@ -82,20 +82,20 @@ <h2>Introduction</h2>
 <p>This page documents difficulties people encounter when trying to use the Chinese language in both Simplified and Traditional scripts on the Web. </p>
 <p>Having identified an issue, it investigates the current status with regards to web specifications and implementations by user agents (browsers, e-readers, etc.), and attempts to prioritise the severity of the issue for web users.  </p>
 <p>A summary of this report and others can be found as part of the <a href="https://w3c.github.io/typography/gap-analysis/language-matrix.html" style="font-size: 140%;">language matrix</a>.</p>
-    
+
     <section id="workflow">
     <h3>Work flow</h3>
     <p><span style="font-weight:bold; font-size: 140%;">This version of the document is a preliminary analysis</span></p>
 
     <p>Gap analysis work usually starts with a <strong>preliminary analysis</strong>, conducted quickly by one or a small group of experts. Then a more <strong>detailed analysis</strong> is carried out, involving a wider range of experts. The detailed analysis may involve the development of tests, in order to illustrate issues and track results for browsers. The next phase is <strong>ongoing maintenance</strong>. It is expected that the resulting document will not be frozen: as gaps are fixed, this should be noted in the document. It is also possible that new gaps are noticed or arise, and they can be added to this document when that happens.</p>
-    
+
     <p>As the gap analysis develops, the requirements for features that are problematic should be described in the companion document, <a href="https://www.w3.org/TR/clreq/">Requirements for Chinese Text Layout</a>. Links to the appropriate part of that document should be added to this document as the material is created. Note that the requirements document should not contain any technology-specific information: all of that belongs here.</p>
     </section>
-    
+
     <section id="prioritization">
     <h3>Prioritization</h3>
     <p>This document not only describes gaps, it also attempts to prioritise them in terms of the impact on the local user. The prioritisation is indicated by colour.</p>
-        
+
         <p>Key:</p>
   <ul style="list-style-type: none;">
         <li class="ok"></li>
@@ -105,16 +105,16 @@ <h3>Prioritization</h3>
         <li class="broken"></li>
         <li class="tbd"></li>
         </ul>
-    
+
     <p>It is important to note that these colours do not indicate to what extent a particular feature is broken. They indicate the impact of a broken or missing feature on the content author or end user.</p>
     <p>Basic styling is the level that would be generally accepted as sufficient for most Web pages. Advanced level support would include additional features one might expect to include in ebooks or other advanced typographic formats. There may be features of a script or language that are not supported on the Web, but that are not generally regarded as necessary (usually archaic or obscure features). In this case, the feature can be described here, but the status should be marked as OK.</p>
     <p>The decision as to what priority level is assigned to a described gap is down to the experts doing the gap analysis. It may not always be straightforward to decide. If a given section in this document refers to more than one feature that is broken, each with different impacts on Web users, the priority for the section should be the lowest denominator.</p>
     <p>A cell can be scored as OK if the feature in question is specified in an appropriate specification, and is supported by user agents. A specification that is in CR or later and has two implementations in 'major' browsers will count. This means that the feature may not be supported in all browsers yet. (At some point in the future we may try to distinguish, visually, whether support is available in a specification but still pending in major browsers or applications.) </p>
     </section>
 </section>
-    
-    
-    
+
+
+
 
 
 <section id="direction">
@@ -146,9 +146,9 @@ <h3>Bidirectional text</h3>
 
 <section id="h_characters_and_phrases">
 <h2>Characters and phrases</h2>
-    
-    
-    
+
+
+
 <section id="charset" class="ok">
 <h3>Characters &amp; encoding</h3>
 <p id="prompt-charset" class="status_prompt promptStub"></p>
@@ -227,7 +227,7 @@ <h3>Grapheme/word segmentation &amp; selection</h3>
 
 <div id="insert-segmentation"></div>
 </section>
- 
+
 
 
 <section id="punctuation_etc" class="tbd">
@@ -236,9 +236,9 @@ <h3>Inline features &amp; punctuation</h3><p id="prompt-punctuation_etc" class="
 
 <div id="insert-punctuation_etc"></div>
 </section>
-   
-    
-    
+
+
+
 <section id="text_decoration" class="tbd">
 <h3>Text decoration</h3>
 <p id="prompt-text_decoration" class="status_prompt promptStub"></p>
@@ -252,8 +252,8 @@ <h3>Text decoration</h3>
 <section id="quotations" class="tbd">
 <h3>Quotations</h3>
 <p id="prompt-quotations" class="status_prompt promptStub"></p>
-	
-	
+
+
 <div id="insert-quotations"></div>
 </section>
 
@@ -285,7 +285,7 @@ <h3>Data formats &amp; numbers</h3>
 <section id="h_lines_and_paragraphs">
 <h2>Lines and Paragraphs</h2>
 
- 
+
 <section id="line_breaking" class="tbd">
 <h3>Line breaking</h3>
 <p id="prompt-line_breaking" class="status_prompt promptStub"></p>
@@ -423,7 +423,7 @@ <h3>What else?</h3>
 
 <div id="insert-other"></div>
     </section>
-    
+
 </section>
 
 

homepage/index.html

@@ -109,7 +109,7 @@ <h2 id="docs" style="margin-top: 0"> <a href="#docs">Work aims</a> </h2>
 <ul>
 <li><strong>Chinese script gap analysis</strong></li>
 <li><strong>Requirements for Chinese Text Layout 中文排版需求</strong><br/>
-<a href="https://w3c.github.io/clreq/">Editor's draft</a> • <a href="https://github.com/w3c/clreq/">GitHub</a></li>
+<a href="https://www.w3.org/International/clreq/">Editor's draft</a> • <a href="https://github.com/w3c/clreq/">GitHub</a></li>
 </ul>
 <p>Documents will be produced in Chinese and English, and regular information about the status of the work and key discussion points will be forwarded to the English-language lists for wide review.</p>
         <p>The group <a href="../charter/">charter</a> also allows review of draft specifications

homepage/index.zh-hans.html

@@ -99,7 +99,7 @@ <h2 id="docs" style="margin-top: 0"> <a href="#docs">工作目标</a> </h2>
 <ul>
 <li><strong>Chinese script gap analysis</strong></li>
 <li><strong>Requirements for Chinese Text Layout 中文排版需求</strong><br/>
-<a href="https://w3c.github.io/clreq/">编辑草案</a> • <a href="https://github.com/w3c/clreq/">GitHub</a></li>
+<a href="https://www.w3.org/International/clreq/">编辑草案</a> • <a href="https://github.com/w3c/clreq/">GitHub</a></li>
 </ul>
 <p>文档将以中文和英文编写，并定期提供有关工作状况和重点讨论的信息，并将其提交到英文邮件列表，供广泛审阅。</p>
         <p>任务组<a href="../charter/">章程</a>还允许审查其他工作组制定的标准草案，并提供相关W3C规范和资源的翻译。任务组还可以根据W3C的<a href="http://www.w3.org/2004/10/27-testcases">提供测试样例政策</a>的条款，并与任何相关的工作组协调，选择产生其他非规范性的可交付成果，如测试用例和错误报告。
@@ -135,4 +135,4 @@ <h2 id="communication"><a href="#communication">联络</a></h2>
   licensing</a> rules apply. Your interactions with this site are in
   accordance with our <a href="https://www.w3.org/Consortium/Legal/privacy-statement#Public">public</a> and <a href="https://www.w3.org/Consortium/Legal/privacy-statement#Members">Member</a> privacy statements.</small></p>
 </body>
-</html>
+</html>

index.html

@@ -19,7 +19,7 @@
   shortName: "clreq",
   noRecTrack: true,
   copyrightStart: "2015",
-  edDraftURI: "https://w3c.github.io/clreq/",
+  edDraftURI: "https://www.w3.org/International/clreq/",
 
   maxTocLevel: 3,