| 47 |
href="http://suika.fam.cx/~wakaba/pbin/accounts/edit">your user |
href="http://suika.fam.cx/~wakaba/pbin/accounts/edit">your user |
| 48 |
page</a>. |
page</a>. |
| 49 |
|
|
| 50 |
<p>Then, |
<p>Then: |
| 51 |
|
|
| 52 |
<dl> |
<dl> |
| 53 |
|
|
| 77 |
<section id=intro> |
<section id=intro> |
| 78 |
<h2>Introduction to the interactive translation interface</h2> |
<h2>Introduction to the interactive translation interface</h2> |
| 79 |
|
|
| 80 |
<p>For the translating of HTML5 specifications, a new interactive |
<p>For the translating work of the HTML5 specification, a new |
| 81 |
paragraph-level editing interface has been developed. Since the HTML5 |
interactive paragraph-level editing interface has been developed. |
| 82 |
specification adopts a new specification development model — |
Since the HTML5 specification adopts a new specification development |
| 83 |
publishing a large Editor's Draft with sections in different levels of |
model — publishing a large Editor's Draft with sections in |
| 84 |
maturity, in daily basis — it is unrealistic to follow the |
different levels of maturity, in daily basis — it is unrealistic |
| 85 |
traditional model for the development of a Japanese translation of a |
to follow the traditional model for the development of a Japanese |
| 86 |
technical specification — obtaining a copy of a relatively |
translation of a technical specification — obtaining a copy of a |
| 87 |
stable Working Draft or a final Recommendation, translating the whole |
relatively stable Working Draft or a final Recommendation, translating |
| 88 |
document at once, and then publishing the finalized Japanese |
the whole document at once, and then publishing the finalized Japanese |
| 89 |
translation. |
translation. |
| 90 |
|
|
| 91 |
<p>The new interactive translation editing interface (and its backend |
<p>The new interactive translation editing interface (and its backend |
| 97 |
translated version of a paragraph can be added or modified by just |
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 |
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 |
Web browser. You no longer have to prepare your environment for the |
| 100 |
translatioon work; you just need an interactive standard-compliant Web |
translation work; you just need an interactive standard-compliant Web |
| 101 |
browser. |
browser. |
| 102 |
|
|
| 103 |
<li><strong>Paragraph-level editing</strong>. The minimum unit of |
<li><strong>Paragraph-level editing</strong>. The minimum unit of |
| 131 |
<h2>How to use Web interface</h2> |
<h2>How to use Web interface</h2> |
| 132 |
|
|
| 133 |
<p>By double-clicking a paragraph that can be translated, or that has |
<p>By double-clicking a paragraph that can be translated, or that has |
| 134 |
been translated, a editing form is shown as below: |
been translated, a editing form is shown as below:</p> |
| 135 |
|
|
| 136 |
<blockquote> |
<blockquote> |
| 137 |
|
|
| 224 |
<dt><code>step</code><dd>Steps. |
<dt><code>step</code><dd>Steps. |
| 225 |
</dl> |
</dl> |
| 226 |
|
|
| 227 |
<p>Any other tags may also be specified. Tags are case-ensitive. |
<p>Any other tags may also be specified. Tags are case-sensitive. |
| 228 |
|
|
| 229 |
<dt>The “Save and close” button |
<dt>The “Save and close” button |
| 230 |
|
|
| 254 |
<p><strong>Use <i lang=ja>desu‐masu</i> style</strong>. |
<p><strong>Use <i lang=ja>desu‐masu</i> style</strong>. |
| 255 |
|
|
| 256 |
<p><strong><a href="#rfc2119">Markup RFC 2119 keywords</a></strong>, |
<p><strong><a href="#rfc2119">Markup RFC 2119 keywords</a></strong>, |
| 257 |
otherwise what is requirement and what is not would become unclear, |
otherwise what is requirement and what is not might become unclear. |
| 258 |
since there is no upper‐ and lowercase letters in the Japanese |
Note that keywords in non-normative parts (e.g. examples) of the spec |
| 259 |
script. Note that keywords in non-normative parts (e.g. examples) of |
are <em>not</em> RFC 2119 keywords, so don't markup them. |
| 260 |
the spec are <em>not</em> RFC 2119 keywords, so don't markup them. |
|
| 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 |
|
|
| 274 |
<p class=ed>More to come... |
<p class=ed>More to come...</p> |
| 275 |
|
|
| 276 |
|
</section> |
| 277 |
|
|
| 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 |
|
permit. <!-- Competing translation projects should improve the |
| 290 |
|
quality of their products, as does competeing implementations of a |
| 291 |
|
spec do. --> |
| 292 |
|
|
| 293 |
</section> |
</section> |
Parent Directory
| 
Revision Log
| 
Patch