Skip to content

Commit

Permalink
tweaks during FPWD publication prep
Browse files Browse the repository at this point in the history
  • Loading branch information
@r12a
r12a committed Jul 17, 2015
1 parent a64ac3f commit 626dbb6
Showing 1 changed file with 13 additions and 12 deletions.
25 changes: 13 additions & 12 deletions index.html
View file
Expand Up @@ -10,6 +10,7 @@
<script class='remove'>
var respecConfig = {
specStatus: "ED",
//publishDate: "2015-07-23",
shortName: "clreq",
noRecTrack: true,
editors: [
Expand Down Expand Up @@ -39,7 +40,7 @@
wgURI: "http://www.w3.org/International/core/",
bugTracker: { new: "https://github.com/w3c/clreq/issues", open: "https://github.com/w3c/clreq/issues" } ,
wgPublicList: "public-i18n-cjk",
wgPatentURI: "http://www.w3.org/2004/01/pp-impl/",
wgPatentURI: "http://www.w3.org/2004/01/pp-impl/32113/status",
edDraftURI: "http://w3c.github.io/clreq/",
otherLinks: [
{
Expand Down Expand Up @@ -71,31 +72,31 @@
<p data-lang="en">This document was created by the <a href="http://www.w3.org/International/groups/chinese-layout/">Chinese Layout Task Force</a> within the W3C Internationalization Interest Group, and in collaboration with the <a href="http://www.w3.org/html/ig/zh/">W3C HTML5 Chinese Interest Group</a>. The <a href="http://www.w3.org/International/core/">Internationalization Working Group</a> has been a great help during the writing of this document. The Chinese Layout Task Force will work with Internationalization Working Group to publish Working Drafts of this document, and to widen the exposure and review of the document. </p>
<!--p data-lang="en">A <a href="zh/"><strong>Chinese version</strong></a> of this document is also available.</p-->
<div class="note">
<p data-lang="zh">如果您希望对本文档进行意见反馈，请<a href="https://github.com/w3c/clreq/issues" style="font-size: 120%;">提交一个github issue</a>。如果您无法提交github issues，您也可以通过以下电子邮件的方式进行反馈。请使用<q>[clreq]</q>作为您的邮件的标题开头。为了方便大家跟踪您的意见反馈，请单独提交每一个意见或者以分开发送单独电子邮件的方式反馈每一个建议。您的每一个建议对我们都是非常重要的。</p>
<!--p data-lang="zh">如果您希望对本文档进行意见反馈，请<a href="https://github.com/w3c/clreq/issues" style="font-size: 120%;">提交一个github issue</a>。如果您无法提交github issues，您也可以通过以下电子邮件的方式进行反馈。请使用<q>[clreq]</q>作为您的邮件的标题开头。为了方便大家跟踪您的意见反馈，请单独提交每一个意见或者以分开发送单独电子邮件的方式反馈每一个建议。您的每一个建议对我们都是非常重要的。</p>
<p data-lang="en">If you wish to make comments regarding this document,
please <a href="https://github.com/w3c/clreq/issues" style="font-size: 120%;">raise a github issue</a>.
If you are unable to use github issues, you may also send
email to the list mentioned below. Please include <q>[clreq]</q> at the start of your
email's subject. To make it easier to track comments, please raise
separate issues or send separate emails for each comment. All comments
are welcome.</p>
<!-- THE FOLLOWING SHOULD BE USED ONCE THE DOCUMENT IS PUBLISHED AS FPWD
are welcome.</p>-->
<!-- THE FOLLOWING SHOULD BE USED ONCE THE DOCUMENT IS PUBLISHED AS FPWD -->
<p data-lang="zh" style="font-weight:bold; font-size:120%">发表对本文档的建议</p>
<p data-lang="zh">如果你对<a href="http://www.w3.org/TR/2015/WD-clreq-20150723/" style="font-size: 120%">/TR下最新版本</a>的文档有任何建议和反馈，请把您的想法整理发布为 <a href="https://github.com/w3c/clreq/issues" style="font-size: 120%;">github issues</a>。若您觉得在GitHub上提出issues比较困难，也可以邮件形式进行反馈（请参考下面的链接）。您的任何建议对本文档都很可贵。</p>
<p data-lang="zh">为便于跟踪您所反馈的问题，请为您所提出的每一个意见点单独成立一个issue或者邮件，并在其中明确指出您所谈到的章节序号和您所阅读的日期版本的URL。</p>
<p data-lang="en" style="font-weight: bold; font-size: 120%">Sending comments on this document</p>
<p data-lang="en">If you wish to make comments regarding this document, please raise them as <a href="https://github.com/w3c/klreq/issues" style="font-size: 120%;">github issues</a> against the <a href="http://www.w3.org/TR/2015/WD-klreq-20150414/" style="font-size: 120%">latest dated version in /TR</a>. Only send comments by email if you are unable to raise issues on github (see links below). All comments are welcome.</p>
<p data-lang="en">If you wish to make comments regarding this document, please raise them as <a href="https://github.com/w3c/klreq/issues" style="font-size: 120%;">github issues</a> against the <a href="http://www.w3.org/TR/2015/WD-clreq-20150723/" style="font-size: 120%">latest dated version in /TR</a>. Only send comments by email if you are unable to raise issues on github (see links below). All comments are welcome.</p>
<p data-lang="en">To make it easier to track comments, please raise separate issues or emails for each comment, and point to the section you are commenting on&nbsp; using a URL for the dated version of the document.</p>
<p data-lang="zh" style="font-weight: bold; font-size: 120%”>发表对本文档的建议</p>
<p data-lang="zh”>如果你对<a href="http://www.w3.org/TR/2015/WD-clreq-20150723/" style="font-size: 120%">/TR下最新版本</a>的文档有任何建议和反馈，请把您的想法整理发布为 <a href="https://github.com/w3c/clreq/issues" style="font-size: 120%;">github issues</a>。若您觉得在GitHub上提出issues比较困难，也可以邮件形式进行反馈（请参考下面的链接）。您的任何建议对本文档都很可贵。</p>
<p data-lang="zh”>为便于跟踪您所反馈的问题，请为您所提出的每一个意见点单独成立一个issue或者邮件，并在其中明确指出您所谈到的章节序号和您所阅读的日期版本的URL。</p>
-->

</div>

<p id="langSwitch"><button id="toZH" onClick="switch2zh();">zh</button>
<button onClick="switch2en();">en</button></p>

<p data-lang="zh">本章节描述了本文档的发布状态。其它更新版本可能会覆盖本文档。W3C的文档列表和最新版本可通过<a href="http://www.w3.org/TR/">W3C技术报告</a>索引访问。 </p>
<p data-lang="zh">以编辑草稿方式发布的文档还没有通过<abbr title="World Wide Web Consortium">W3C</abbr>会员流程的认可。这是一份文档草稿并且会被不断更新。请暂时不要正式引用本文档。</p>
<p data-lang="zh">本文档遵循<abbr title="World Wide Web Consortium">W3C</abbr><a id="sotd_patent" property="w3p:patentRules" href="http://www.w3.org/Consortium/Patent-Policy-20040205/">专利政策</a>（2004-02-05）。<abbr title="World Wide Web Consortium">W3C</abbr>为工作组的产出成果维护着一份<a href="http://www.w3.org/2004/01/pp-impl/" rel="disclosure">公开专利披露列表</a>，此页面也同时涵盖了专利披露说明。若个人发现其有包含<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">必须声明</a>的专利信息，必须按照<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure"><abbr title="World Wide Web Consortium">W3C</abbr>专利政策第六章节</a>披露此信息。</p>
<p data-lang="zh">本文档遵循<a id="w3c_process_revision" href="http://www.w3.org/2014/Process-20140801/"><abbr title="World Wide Web Consortium">W3C</abbr>流程文档</a>（2014-08-01）。</p>
<p data-lang="zh">本文档遵循<abbr title="World Wide Web Consortium">W3C</abbr><a id="sotd_patent_zh" href="http://www.w3.org/Consortium/Patent-Policy-20040205/">专利政策</a>（2004-02-05）。<abbr title="World Wide Web Consortium">W3C</abbr>为工作组的产出成果维护着一份<a href="http://www.w3.org/2004/01/pp-impl/" rel="disclosure">公开专利披露列表</a>，此页面也同时涵盖了专利披露说明。若个人发现其有包含<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">必须声明</a>的专利信息，必须按照<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure"><abbr title="World Wide Web Consortium">W3C</abbr>专利政策第六章节</a>披露此信息。</p>
<p data-lang="zh">本文档遵循<a id="w3c_process_revision_zh" href="http://www.w3.org/2014/Process-20140801/"><abbr title="World Wide Web Consortium">W3C</abbr>流程文档</a>（2014-08-01）。</p>
</div>
<section id="introduction">
<h2><span data-lang="zh">緒論</span>
Expand Down Expand Up @@ -658,7 +659,7 @@ <h4><span data-lang="zh">橫排與直排的主要差異點</span>
<h2><span data-lang="zh">行內文字排版處理</span>
<span data-lang="en">Line composition</span></h2>

<section id="line_composition_rules_for_punctuation_marks2">
<section id="line_composition_rules_for_punctuation_marks">
<h3><span data-lang="zh">標點符號與其排版</span>
<span data-lang="en">Line Composition Rules for Punctuation Marks</span></h3>
<p data-lang="zh">中文標點符號的排版在各地區有不同的處理方式，其中較顯著的差異係其字面分布——繁體中文多使用符號居中的字形樣式，而簡體中文多使用符號尾隨受注文字末端的字形樣式，並依直、橫排有不同的處理。下文將詳述繁、簡中文標點的異同及準確的配置方式。</p>
Expand Down

0 comments on commit 626dbb6

Please sign in to comment.