html5/spec-ja/notes-src.html.u8

<!DOCTYPE HTML>
<html lang=en>
<title>Notes</title>
<link rel=license href="edit/#license" title="You are granted a license to use, reproduce and create derivative works of this document.">
<link rel=stylesheet href="http://suika.fam.cx/www/style/html/xhtml">
<link rel=stylesheet href=ja-style>
<link href=only-ja-style rel="stylesheet" title="Show only Japanese text" id=style-only-ja>
<link href=both-en-ja-style rel="alternate stylesheet" title="Show both English and Japanese texts" id=style-both-en-ja>
<style>
dt {
  display: block;
  font-weight: bolder;
  font-family: sans-serif;
}
dt:after {
  content: ": ";
}
</style>
<script src=ja-script defer async></script>

<h1>Notes</h1>

<ul>
<li><a href=non-normative>HTML5 (Japanese translation)</a>
<li><a href=workers-non-normative>Web Workers (Japanese translation)</a>
</ul>

<ins class=ja-note>
<p><button type=button onclick="
  document.getElementById ('style-only-ja').disabled = false;
  document.getElementById ('style-both-en-ja').disabled = true;
">日本語訳だけ表示 <span lang=en>Show only Japanese translation</span></button>
<p><button type=button onclick="
  document.getElementById ('style-only-ja').disabled = true;
  document.getElementById ('style-both-en-ja').disabled = false;
">英和対訳表示 <span lang=en>Show both English and Japanese texts</span></button>
</ins>

<section id=involved>
<h2>Get involved</h2>

<p><strong>You can take part in this work.</strong>

<p>First, <a href="http://suika.fam.cx/~wakaba/pbin/accounts/add">get
a <code>suika.fam.cx</code> account</a> (if you have not) and join the
<code>spec-ja</code> group from <a
href="http://suika.fam.cx/~wakaba/pbin/accounts/edit">your user
page</a>.

<p>Then:

<dl>

<dt>Translate a paragraph that is not translated yet

<dd>Double-click the paragraph and input the translated text into the
second textbox.

<dt>Fix a typographical error in the translated text
<dt>Fix a paragraph that has been translated incorrectly

<dd>Double-click the paragraph in which the error is found and fix the
error.

<dd>Alternatively, you can report the problem to <a
href="edit/_bugs">the _bugs page</a>.

<dt>Discuss the choice of a Japanese term
<dt>Discuss any other topic

<dd>Write on <a href="edit/_notes">the _notes page</a>.

</dl>

</section>

<section id=intro>
<h2>Introduction to the interactive translation interface</h2>

<p>For the translating work of the HTML5 specification, a new
interactive paragraph-level editing interface has been developed.
Since the HTML5 specification adopts a new specification development
model &mdash; publishing a large Editor's Draft with sections in
different levels of maturity, in daily basis &mdash; it is unrealistic
to follow the traditional model for the development of a Japanese
translation of a technical specification &mdash; obtaining a copy of a
relatively stable Working Draft or a final Recommendation, translating
the whole document at once, and then publishing the finalized Japanese
translation.

<p>The new interactive translation editing interface (and its backend
management tools) enables a different style of the translation work:

<ul>

<li><strong>Use of an interactive Web interface</strong>.  A
translated version of a paragraph can be added or modified by just
choosing the paragraph to add or modify and then editing the text in a
Web browser.  You no longer have to prepare your environment for the
translation work; you just need an interactive standard-compliant Web
browser.

<li><strong>Paragraph-level editing</strong>.  The minimum unit of
text is <dfn>paragraph</dfn> (in this context the contents of a
heading, list item, or table cell is also referred to as “paragraph” 
unless it contains another paragraph).  The Web interface and the
management tools handle text in per-paragraph basis.  Since the
original spec text is frequently updated and paragraphs are frequently
modified or reorganized, handling translated texts in this level seems
better choice than other possibilities (e.g. section-level).</li><!--
Though sentense-level might be more robust, sentenses are not marked
up so that clipping a sentense is not a trivial work. -->

<li><strong>Automatic synchronization with the original spec
text</strong>.  Translation of an old draft version of the
specification is rather harmful, since readers of the translation
don't check whether the text is up-to-date or not in general and
therefore they would not be even aware that what they read is
out-of-date.  This system is so set up that any change to the original
specification text will be reflected to the translated version within
a day.  If a paragraph that was already translated is then updated in
the original text, the paragraph is taken over by the newer English
version.  It would take a step backward, but is better than leaving
out-of-date translation as is.

</ul>

</section>

<section id=ui>
<h2>How to use Web interface</h2>

<p>By double-clicking a paragraph that can be translated, or that has
been translated, a editing form is shown as below:</p>

<blockquote>

<div class="ja-edit-form" style="position: static"><p><label>Original
text:<br><textarea name="en" readonly></textarea></label><br>
(<label><input name="pattern" type="checkbox" disabled>
Pattern</label><span hidden=""> <button type="button">Load original
text</button></span>) </p><p><label>Translated text:<br><textarea
name="ja" readonly></textarea></label></p><p><label>Tags:<br><textarea
name="tags" readonly></textarea></label></p><p><button type="button"
class="ja-save-button" disabled>Save and close</button> <button
type="button" class="ja-close-button" disabled>Close</button>
(<output>Load: 200 OK</output>; see also <a
href="edit/#license">license</a>)</p></div>

</blockquote>

<dl>

<dt>The “Original text” field

<dd>

<p>The original English text in the paragraph of the original
document.  It may contain HTML tags and references as in the original
document.  A run of white space characters is considered equivalent to
a space (U+0020) character.  Leading and trailing white space
characters are ignored.

<dt>The “Translated text” field

<dd>

<p>The translated text for the paragraph.  It may contain HTML tags
and references.

<div id=rfc2119>

<p>In addition, you can use special notation for RFC 2119 keywords as:

<ul lang=ja>
<li><code>しなければ<mark>[[MUST:</mark>なりません<mark>]]</mark>。</code>
<li><code>しては<mark>[[MUST NOT:</mark>なりません<mark>]]</mark>。</code>
<li><code><mark>[[REQUIRED:</mark>必須<mark>]]</mark>です。</code>
<li><code><mark>[[SHOULD:</mark>するべきです<mark>]]</mark>。</code>
<li><code><mark>[[SHOULD NOT:</mark>するべきではありません<mark>]]</mark>。</code>
<li><code>して<mark>[[MAY:</mark>構いません<mark>]]</mark>。</code>
</ul>

</div>

<dt>The “Pattern” flag

<dd>

<p>If this flag is <em>not</em> set, then the “Original text” is
compared with paragraphs in the original document by exact match
(except for the aforementioned white space normalization).  <em>You
should use exact match (leave the flag unchecked) as far as
possible.</em>

<dd>

<p>If this flag is set, the “Original text” is compared with
paragraphs in the original document by pattern matching rule, where a
<code>*</code> character in the “Original text” matches <em>one</em>
or more characters.  If there are more than one patterns matching the
same paragraph, then only the longest pattern is considered as
matching.  When this flag is set, variables
<code>$<var>d</var></code>, where <var>d</var> is the index of the
<code>*</code> (starting with <code>1</code>) in the “Translated text” 
is replaced by the substring matching the corresponding <code>*</code>
in the pattern.

<dt>The “Tags” field

<dd>

<p>The tags associated to this paragraph.  One tag can be specified
in a line.  Tags are not used in general; it can be specified for the
convinience of <a href="find?word=tag:example">the paragraph search</a>.
Common tags are:

  <dl>
  <dt><code>cell</code><dd><code>td</code>/<code>th</code> contents.
  <dt><code>dt</code><dd><code>dt</code> contents.
  <dt><code>headings</code><dd><code>h<var>n</var></code>/<code>caption</code> contents.
  <dt><code>item</code><dd><code>li</code> contents other than steps.
  <dt><code>non-normative</code><dd>Non-normative contents.
  <dt><code>step</code><dd>Steps.
  </dl>

<p>Any other tags may also be specified.  Tags are case-sensitive.

<dt>The “Save and close” button

<dd>

<p>Save changes and close the form.

<dt>The “Close” button

<dd>

<p>Close the form without saving any change.

<dt>Text next to the buttons

<dd>

<p>Progress of transactions is shown here.

</dl>

</section>

<section id=guides>
<h2>Translation Guidelines</h2>

<p><strong>Use <i lang=ja>desu‐masu</i> style</strong>.

<p><strong><a href="#rfc2119">Markup RFC 2119 keywords</a></strong>,
otherwise what is requirement and what is not might become unclear.
Note that keywords in non-normative parts (e.g. examples) of the spec
are <em>not</em> RFC 2119 keywords, so don't markup them.

<p><strong>Avoid <i lang=ja>Katakana</i> words where
possible</strong>.  Don't use <i lang=ja>Katakana</i> words, unless
you are confident in that it is now a common word in Japanese.  If you
have no idea how to translate a technical term, please try to <a
href="http://sciterm.nii.ac.jp/cgi-bin/reference.cgi">check the
practice in other areas</a> or consult at <a href="edit/_notes">the
_notes page</a>.

<p><strong>Append “ー” character</strong> to the <i
lang=ja>Katakana</i> word when the original term ends with ‐ar, ‐er,
or ‐or.  However, avoiding <i lang=ja>Katakana</i> word where
possible is always preferred.

<p class=ed>More to come...</p>

</section>

<section id=sources>
<h2>Source codes of tools and translation data files</h2>

<p>You can get a copy of source codes for the translation tools, as
well as data files for translated paragraphs, from <a
href="http://suika.fam.cx/gate/cvs/markup/html/html5/spec-ja/">their
CVS repository</a>.

<p>You are free to use these tools for other project, or even can you
fork <em>this</em> translation project if you don't want to adhere to
our translation guidelines, as long as the applicable license terms
permit.  <!-- Competing translation projects should improve the
quality of their products, as does competeing implementations of a
spec do. -->

</section>
1	wakaba	1.1	<!DOCTYPE HTML>
2			<html lang=en>
3			<title>Notes</title>
4			<link rel=license href="edit/#license" title="You are granted a license to use, reproduce and create derivative works of this document.">
5			<link rel=stylesheet href="http://suika.fam.cx/www/style/html/xhtml">
6			<link rel=stylesheet href=ja-style>
7			<link href=only-ja-style rel="stylesheet" title="Show only Japanese text" id=style-only-ja>
8			<link href=both-en-ja-style rel="alternate stylesheet" title="Show both English and Japanese texts" id=style-both-en-ja>
9			<style>
10			dt {
11			display: block;
12			font-weight: bolder;
13			font-family: sans-serif;
14			}
15			dt:after {
16			content: ": ";
17			}
18			</style>
19			<script src=ja-script defer async></script>
20
21			<h1>Notes</h1>
22
23			<ul>
24			<li><a href=non-normative>HTML5 (Japanese translation)</a>
25			<li><a href=workers-non-normative>Web Workers (Japanese translation)</a>
26			</ul>
27
28			<ins class=ja-note>
29			<p><button type=button onclick="
30			document.getElementById ('style-only-ja').disabled = false;
31			document.getElementById ('style-both-en-ja').disabled = true;
32			">日本語訳だけ表示 <span lang=en>Show only Japanese translation</span></button>
33			<p><button type=button onclick="
34			document.getElementById ('style-only-ja').disabled = true;
35			document.getElementById ('style-both-en-ja').disabled = false;
36			">英和対訳表示 <span lang=en>Show both English and Japanese texts</span></button>
37			</ins>
38
39			<section id=involved>
40			<h2>Get involved</h2>
41
42			<p><strong>You can take part in this work.</strong>
43
44			<p>First, <a href="http://suika.fam.cx/~wakaba/pbin/accounts/add">get
45			a <code>suika.fam.cx</code> account</a> (if you have not) and join the
46			<code>spec-ja</code> group from <a
47			href="http://suika.fam.cx/~wakaba/pbin/accounts/edit">your user
48			page</a>.
49
50	wakaba	1.2	<p>Then:
51	wakaba	1.1
52			<dl>
53
54			<dt>Translate a paragraph that is not translated yet
55
56			<dd>Double-click the paragraph and input the translated text into the
57			second textbox.
58
59			<dt>Fix a typographical error in the translated text
60			<dt>Fix a paragraph that has been translated incorrectly
61
62			<dd>Double-click the paragraph in which the error is found and fix the
63			error.
64
65			<dd>Alternatively, you can report the problem to <a
66			href="edit/_bugs">the _bugs page</a>.
67
68			<dt>Discuss the choice of a Japanese term
69			<dt>Discuss any other topic
70
71			<dd>Write on <a href="edit/_notes">the _notes page</a>.
72
73			</dl>
74
75			</section>
76
77			<section id=intro>
78			<h2>Introduction to the interactive translation interface</h2>
79
80	wakaba	1.2	<p>For the translating work of the HTML5 specification, a new
81			interactive paragraph-level editing interface has been developed.
82			Since the HTML5 specification adopts a new specification development
83			model — publishing a large Editor's Draft with sections in
84			different levels of maturity, in daily basis — it is unrealistic
85			to follow the traditional model for the development of a Japanese
86			translation of a technical specification — obtaining a copy of a
87			relatively stable Working Draft or a final Recommendation, translating
88			the whole document at once, and then publishing the finalized Japanese
89	wakaba	1.1	translation.
90
91			<p>The new interactive translation editing interface (and its backend
92			management tools) enables a different style of the translation work:
93
94			<ul>
95
96			<li><strong>Use of an interactive Web interface</strong>. A
97			translated version of a paragraph can be added or modified by just
98			choosing the paragraph to add or modify and then editing the text in a
99			Web browser. You no longer have to prepare your environment for the
100	wakaba	1.4	translation work; you just need an interactive standard-compliant Web
101	wakaba	1.1	browser.
102
103			<li><strong>Paragraph-level editing</strong>. The minimum unit of
104			text is <dfn>paragraph</dfn> (in this context the contents of a
105			heading, list item, or table cell is also referred to as “paragraph”
106			unless it contains another paragraph). The Web interface and the
107			management tools handle text in per-paragraph basis. Since the
108			original spec text is frequently updated and paragraphs are frequently
109			modified or reorganized, handling translated texts in this level seems
110			better choice than other possibilities (e.g. section-level).</li><!--
111			Though sentense-level might be more robust, sentenses are not marked
112			up so that clipping a sentense is not a trivial work. -->
113
114			<li><strong>Automatic synchronization with the original spec
115			text</strong>. Translation of an old draft version of the
116			specification is rather harmful, since readers of the translation
117			don't check whether the text is up-to-date or not in general and
118			therefore they would not be even aware that what they read is
119			out-of-date. This system is so set up that any change to the original
120			specification text will be reflected to the translated version within
121			a day. If a paragraph that was already translated is then updated in
122			the original text, the paragraph is taken over by the newer English
123			version. It would take a step backward, but is better than leaving
124			out-of-date translation as is.
125
126			</ul>
127
128			</section>
129
130			<section id=ui>
131			<h2>How to use Web interface</h2>
132
133			<p>By double-clicking a paragraph that can be translated, or that has
134	wakaba	1.2	been translated, a editing form is shown as below:</p>
135	wakaba	1.1
136			<blockquote>
137
138			<div class="ja-edit-form" style="position: static"><p><label>Original
139			text:<br><textarea name="en" readonly></textarea></label><br>
140			(<label><input name="pattern" type="checkbox" disabled>
141			Pattern</label><span hidden=""> <button type="button">Load original
142			text</button></span>) </p><p><label>Translated text:<br><textarea
143			name="ja" readonly></textarea></label></p><p><label>Tags:<br><textarea
144			name="tags" readonly></textarea></label></p><p><button type="button"
145			class="ja-save-button" disabled>Save and close</button> <button
146			type="button" class="ja-close-button" disabled>Close</button>
147			(<output>Load: 200 OK</output>; see also <a
148			href="edit/#license">license</a>)</p></div>
149
150			</blockquote>
151
152			<dl>
153
154			<dt>The “Original text” field
155
156			<dd>
157
158			<p>The original English text in the paragraph of the original
159			document. It may contain HTML tags and references as in the original
160			document. A run of white space characters is considered equivalent to
161			a space (U+0020) character. Leading and trailing white space
162			characters are ignored.
163
164			<dt>The “Translated text” field
165
166			<dd>
167
168			<p>The translated text for the paragraph. It may contain HTML tags
169			and references.
170
171			<div id=rfc2119>
172
173			<p>In addition, you can use special notation for RFC 2119 keywords as:
174
175			<ul lang=ja>
176			<li><code>しなければ<mark>[[MUST:</mark>なりません<mark>]]</mark>。</code>
177			<li><code>しては<mark>[[MUST NOT:</mark>なりません<mark>]]</mark>。</code>
178			<li><code><mark>[[REQUIRED:</mark>必須<mark>]]</mark>です。</code>
179			<li><code><mark>[[SHOULD:</mark>するべきです<mark>]]</mark>。</code>
180			<li><code><mark>[[SHOULD NOT:</mark>するべきではありません<mark>]]</mark>。</code>
181			<li><code>して<mark>[[MAY:</mark>構いません<mark>]]</mark>。</code>
182			</ul>
183
184			</div>
185
186			<dt>The “Pattern” flag
187
188			<dd>
189
190			<p>If this flag is <em>not</em> set, then the “Original text” is
191			compared with paragraphs in the original document by exact match
192			(except for the aforementioned white space normalization). <em>You
193			should use exact match (leave the flag unchecked) as far as
194			possible.</em>
195
196			<dd>
197
198			<p>If this flag is set, the “Original text” is compared with
199			paragraphs in the original document by pattern matching rule, where a
200			<code>*</code> character in the “Original text” matches <em>one</em>
201			or more characters. If there are more than one patterns matching the
202			same paragraph, then only the longest pattern is considered as
203			matching. When this flag is set, variables
204			<code>$<var>d</var></code>, where <var>d</var> is the index of the
205			<code>*</code> (starting with <code>1</code>) in the “Translated text”
206			is replaced by the substring matching the corresponding <code>*</code>
207			in the pattern.
208
209			<dt>The “Tags” field
210
211			<dd>
212
213			<p>The tags associated to this paragraph. One tag can be specified
214			in a line. Tags are not used in general; it can be specified for the
215			convinience of <a href="find?word=tag:example">the paragraph search</a>.
216			Common tags are:
217
218			<dl>
219			<dt><code>cell</code><dd><code>td</code>/<code>th</code> contents.
220			<dt><code>dt</code><dd><code>dt</code> contents.
221			<dt><code>headings</code><dd><code>h<var>n</var></code>/<code>caption</code> contents.
222			<dt><code>item</code><dd><code>li</code> contents other than steps.
223			<dt><code>non-normative</code><dd>Non-normative contents.
224			<dt><code>step</code><dd>Steps.
225			</dl>
226
227	wakaba	1.4	<p>Any other tags may also be specified. Tags are case-sensitive.
228	wakaba	1.1
229			<dt>The “Save and close” button
230
231			<dd>
232
233			<p>Save changes and close the form.
234
235			<dt>The “Close” button
236
237			<dd>
238
239			<p>Close the form without saving any change.
240
241			<dt>Text next to the buttons
242
243			<dd>
244
245			<p>Progress of transactions is shown here.
246
247			</dl>
248
249			</section>
250
251			<section id=guides>
252			<h2>Translation Guidelines</h2>
253
254			<p><strong>Use <i lang=ja>desu‐masu</i> style</strong>.
255
256			<p><strong><a href="#rfc2119">Markup RFC 2119 keywords</a></strong>,
257	wakaba	1.2	otherwise what is requirement and what is not might become unclear.
258			Note that keywords in non-normative parts (e.g. examples) of the spec
259			are <em>not</em> RFC 2119 keywords, so don't markup them.
260
261			<p><strong>Avoid <i lang=ja>Katakana</i> words where
262			possible</strong>. Don't use <i lang=ja>Katakana</i> words, unless
263			you are confident in that it is now a common word in Japanese. If you
264			have no idea how to translate a technical term, please try to <a
265			href="http://sciterm.nii.ac.jp/cgi-bin/reference.cgi">check the
266			practice in other areas</a> or consult at <a href="edit/_notes">the
267			_notes page</a>.
268
269			<p><strong>Append “ー” character</strong> to the <i
270			lang=ja>Katakana</i> word when the original term ends with ‐ar, ‐er,
271			or ‐or. However, avoiding <i lang=ja>Katakana</i> word where
272			possible is always preferred.
273	wakaba	1.1
274	wakaba	1.3	<p class=ed>More to come...</p>
275	wakaba	1.1
276			</section>
277	wakaba	1.5
278			<section id=sources>
279			<h2>Source codes of tools and translation data files</h2>
280
281			<p>You can get a copy of source codes for the translation tools, as
282			well as data files for translated paragraphs, from <a
283			href="http://suika.fam.cx/gate/cvs/markup/html/html5/spec-ja/">their
284			CVS repository</a>.
285
286			<p>You are free to use these tools for other project, or even can you
287			fork <em>this</em> translation project if you don't want to adhere to
288			our translation guidelines, as long as the applicable license terms
289	wakaba	1.6	permit. <!-- Competing translation projects should improve the
290			quality of their products, as does competeing implementations of a
291			spec do. -->
292	wakaba	1.5
293			</section>