diff options
Diffstat (limited to 'files/ja/mdn/guidelines')
8 files changed, 21 insertions, 21 deletions
diff --git a/files/ja/mdn/guidelines/code_guidelines/css/index.html b/files/ja/mdn/guidelines/code_guidelines/css/index.html index 4f4449ba5c..c237604255 100644 --- a/files/ja/mdn/guidelines/code_guidelines/css/index.html +++ b/files/ja/mdn/guidelines/code_guidelines/css/index.html @@ -139,7 +139,7 @@ font-family: sans-serif;</pre> direction | fill-mode | play-state | name */ animation: 3s ease-in 1s 2 reverse both paused slidein;</pre> -<p>As an example, the first value that can be parsed as a {{cssxref("time", "<time>")}} is assigned to the {{cssxref("animation-duration")}}, and the second one is assigned to {{cssxref("animation-delay")}}. For more details, read the full <a href="/en-US/docs/Web/CSS/animation#Syntax">animation syntax</a> details.</p> +<p>As an example, the first value that can be parsed as a {{cssxref("time", "<time>")}} is assigned to the {{cssxref("animation-duration")}}, and the second one is assigned to {{cssxref("animation-delay")}}. For more details, read the full <a href="/ja/docs/Web/CSS/animation#Syntax">animation syntax</a> details.</p> <h3 id="Use_double_quotes_around_values" name="Use_double_quotes_around_values">値の周りには二重引用符を使用する</h3> @@ -210,7 +210,7 @@ background-image: linear-gradient(to bottom, red, black);</pre> /*CSS for really wide screens*/ }</pre> -<p>This has many advantages, outlined in our <a href="/en-US/docs/Web/Apps/Progressive/Responsive/Mobile_first">Mobile First</a> article.</p> +<p>This has many advantages, outlined in our <a href="/ja/docs/Web/Apps/Progressive/Responsive/Mobile_first">Mobile First</a> article.</p> <h2 id="Selectors" name="Selectors">セレクター</h2> diff --git a/files/ja/mdn/guidelines/code_guidelines/html/index.html b/files/ja/mdn/guidelines/code_guidelines/html/index.html index 167160be4b..e674d8ca22 100644 --- a/files/ja/mdn/guidelines/code_guidelines/html/index.html +++ b/files/ja/mdn/guidelines/code_guidelines/html/index.html @@ -27,7 +27,7 @@ translation_of: MDN/Guidelines/Code_guidelines/HTML </li> <li><a href="/ja/docs/MDN/Contribute/Guidelines/Code_guidelines/HTML#General_markup_coding_style">一般的なマークアップコーディングスタイル</a> <ul> - <li><a href="https://developer.mozilla.org/ja/docs/MDN/Contribute/Guidelines/Code_guidelines/HTML#Use_lowercase">小文字を使う</a></li> + <li><a href="/ja/docs/MDN/Contribute/Guidelines/Code_guidelines/HTML#Use_lowercase">小文字を使う</a></li> <li><a href="/ja/docs/MDN/Contribute/Guidelines/Code_guidelines/HTML#Trailing_slashes">末尾のスラッシュ</a></li> <li><a href="/ja/docs/MDN/Contribute/Guidelines/Code_guidelines/HTML#Quoting_attributes">属性の引用</a></li> <li><a href="/ja/docs/MDN/Contribute/Guidelines/Code_guidelines/HTML#Use_double_quotes">ダブルクォートを使う</a></li> diff --git a/files/ja/mdn/guidelines/code_guidelines/index.html b/files/ja/mdn/guidelines/code_guidelines/index.html index 3ce931004f..ed2cb9de33 100644 --- a/files/ja/mdn/guidelines/code_guidelines/index.html +++ b/files/ja/mdn/guidelines/code_guidelines/index.html @@ -25,7 +25,7 @@ translation_of: MDN/Guidelines/Code_guidelines </div> <div class="note"> -<p><strong>Note</strong>: If you want advice on the styling of code as it appears on an MDN article, rather than the code content, see our <a href="/en-US/docs/MDN/Contribute/Guidelines/Writing_style_guide#Code_sample_style_and_formatting">Writing style guide</a>.</p> +<p><strong>Note</strong>: If you want advice on the styling of code as it appears on an MDN article, rather than the code content, see our <a href="/ja/docs/MDN/Contribute/Guidelines/Writing_style_guide#Code_sample_style_and_formatting">Writing style guide</a>.</p> </div> <h2 id="Article_structure">Article structure</h2> @@ -33,11 +33,11 @@ translation_of: MDN/Guidelines/Code_guidelines <p>This article contains general high-level best practices for writing MDN code examples. Its subarticles are as follows:</p> <ul> - <li><a href="/en-US/docs/MDN/Contribute/Guidelines/Code_guidelines/General">General guidelines for all code</a> — both syntactical and for styling/displaying examples</li> - <li><a href="/en-US/docs/MDN/Contribute/Guidelines/Code_guidelines/HTML">HTML guidelines</a></li> - <li><a href="/en-US/docs/MDN/Contribute/Guidelines/Code_guidelines/CSS">CSS guidelines</a></li> - <li><a href="/en-US/docs/MDN/Contribute/Guidelines/Code_guidelines/JavaScript">JavaScript guidelines</a></li> - <li><a href="/en-US/docs/MDN/Contribute/Guidelines/Code_guidelines/Shell">Shell prompt guidelines</a></li> + <li><a href="/ja/docs/MDN/Contribute/Guidelines/Code_guidelines/General">General guidelines for all code</a> — both syntactical and for styling/displaying examples</li> + <li><a href="/ja/docs/MDN/Contribute/Guidelines/Code_guidelines/HTML">HTML guidelines</a></li> + <li><a href="/ja/docs/MDN/Contribute/Guidelines/Code_guidelines/CSS">CSS guidelines</a></li> + <li><a href="/ja/docs/MDN/Contribute/Guidelines/Code_guidelines/JavaScript">JavaScript guidelines</a></li> + <li><a href="/ja/docs/MDN/Contribute/Guidelines/Code_guidelines/Shell">Shell prompt guidelines</a></li> </ul> <h2 id="General_best_practices">General best practices</h2> diff --git a/files/ja/mdn/guidelines/conventions_definitions/index.html b/files/ja/mdn/guidelines/conventions_definitions/index.html index 74b90bcc78..e5a5b9a12f 100644 --- a/files/ja/mdn/guidelines/conventions_definitions/index.html +++ b/files/ja/mdn/guidelines/conventions_definitions/index.html @@ -46,7 +46,7 @@ translation_of: MDN/Guidelines/Conventions_definitions <li>仕様の定義が安定していて、変化しそうにない。</li> </ul> -<p>ここでは<em>または</em>が重要です。 — 通常、ある技術に複数の主要なブラウザーが対応した場合、仕様は安定するでしょうが、これは常に言えるわけではありません。また、技術によっては安定した仕様書がありよく使用されてはいるものの、ブラウザーでのネイティブな対応がない場合もあります (<a href="/en-US/docs/Related/IMSC">IMSC</a> などがその例)。</p> +<p>ここでは<em>または</em>が重要です。 — 通常、ある技術に複数の主要なブラウザーが対応した場合、仕様は安定するでしょうが、これは常に言えるわけではありません。また、技術によっては安定した仕様書がありよく使用されてはいるものの、ブラウザーでのネイティブな対応がない場合もあります (<a href="/ja/docs/Related/IMSC">IMSC</a> などがその例)。</p> <h3 id="Archived_pages" name="Archived_pages">アーカイブページ</h3> diff --git a/files/ja/mdn/guidelines/css_style_guide/index.html b/files/ja/mdn/guidelines/css_style_guide/index.html index 7501925e4a..6aa8dff5e9 100644 --- a/files/ja/mdn/guidelines/css_style_guide/index.html +++ b/files/ja/mdn/guidelines/css_style_guide/index.html @@ -215,13 +215,13 @@ function works(){ <ul class="card-grid"> <li><span>CSS リファレンス</span> - <p>An <a href="/en-US/docs/Web/CSS/Reference" title="en-US/docs/CSS/CSS_Reference">exhaustive reference</a> for <u>seasoned Web developers</u> describing every property and concept of CSS.</p> + <p>An <a href="/ja/docs/Web/CSS/Reference" title="en-US/docs/CSS/CSS_Reference">exhaustive reference</a> for <u>seasoned Web developers</u> describing every property and concept of CSS.</p> </li> <li><span>CSS チュートリアル</span> - <p>A <a href="/en-US/docs/CSS/Getting_Started" title="en-US/docs/CSS/Getting_Started">step-by-step introduction</a> to help <u>complete beginners</u> get started. It presents all the needed fundamentals.</p> + <p>A <a href="/ja/docs/CSS/Getting_Started" title="en-US/docs/CSS/Getting_Started">step-by-step introduction</a> to help <u>complete beginners</u> get started. It presents all the needed fundamentals.</p> </li> <li><span>CSS3 デモ</span> - <p>A <a href="/en-US/demos/tag/tech:css3" title="https://developer.mozilla.org/en-US/demos/tag/tech:css3">collection of demos</a> showing the <u>latest CSS technologies</u> in action: a boost for the creativity.</p> + <p>A <a href="/ja/demos/tag/tech:css3" title="/en-US/demos/tag/tech:css3">collection of demos</a> showing the <u>latest CSS technologies</u> in action: a boost for the creativity.</p> </li> </ul> diff --git a/files/ja/mdn/guidelines/does_this_belong_on_mdn/index.html b/files/ja/mdn/guidelines/does_this_belong_on_mdn/index.html index 1b8f12161e..4ab2aeab2b 100644 --- a/files/ja/mdn/guidelines/does_this_belong_on_mdn/index.html +++ b/files/ja/mdn/guidelines/does_this_belong_on_mdn/index.html @@ -22,7 +22,7 @@ translation_of: MDN/Guidelines/Does_this_belong_on_MDN <li>文書の性質 (これはどんな種類の文書か)</li> </ul> -<p>MDN への寄稿は、すべて特定のオープンソースライセンスに該当することに注意してください。これは <a href="/en-US/docs/MDN/About">MDN について</a>ページに<a href="/ja/docs/MDN/About#copyrights_and_licenses">詳細に記されています</a>。</p> +<p>MDN への寄稿は、すべて特定のオープンソースライセンスに該当することに注意してください。これは <a href="/ja/docs/MDN/About">MDN について</a>ページに<a href="/ja/docs/MDN/About#copyrights_and_licenses">詳細に記されています</a>。</p> <div class="note"> <p><strong>注</strong>: MDN Web Docs を利用したり、投稿したりする際には、Mozilla の<a href="https://www.mozilla.org/en-US/about/legal/terms/mozilla/">ウェブサイトおよびコミュニケーション利用規約</a>が適用されることに注意してください。この文書を確認して、 Mozilla のサイトで投稿できること、できないことを確認してください。</p> diff --git a/files/ja/mdn/guidelines/video/index.html b/files/ja/mdn/guidelines/video/index.html index 4ce9b87b9f..dcd39e1d80 100644 --- a/files/ja/mdn/guidelines/video/index.html +++ b/files/ja/mdn/guidelines/video/index.html @@ -39,7 +39,7 @@ translation_of: MDN/Guidelines/Video <p>We tend to most commonly use video when describing some kind of instruction sequence or multi-step workflow that would be hard to describe concisely in words: <em>"do this, then do that, then this will happen"</em>. It is especially useful when trying to describe processes that cross over multiple applications or windows, and include GUI interactions that might not be simple to describe: <em>"now click on the button near the top-left that looks a bit like a duck"</em>.</p> -<p>In such cases it is often more effective to just <strong>show</strong> what you mean. We most commonly use videos when explaining features of the <a href="/en-US/docs/Tools">Firefox DevTools</a>.</p> +<p>In such cases it is often more effective to just <strong>show</strong> what you mean. We most commonly use videos when explaining features of the <a href="/ja/docs/Tools">Firefox DevTools</a>.</p> <h2 id="What_should_MDN_videos_look_like">What should MDN videos look like?</h2> @@ -57,7 +57,7 @@ translation_of: MDN/Guidelines/Video </li> </ul> -<p>To explain something more complex, you can use a blend of short videos and screenshots, interspersed with text. The text can help reinforce the points made in the video, and the user can rely on the text or the video as they choose. See <a href="https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector/How_to/Work_with_animations#Animation_inspector">Working with the Animation Inspector</a> for a good example.</p> +<p>To explain something more complex, you can use a blend of short videos and screenshots, interspersed with text. The text can help reinforce the points made in the video, and the user can rely on the text or the video as they choose. See <a href="/ja/docs/Tools/Page_Inspector/How_to/Work_with_animations#Animation_inspector">Working with the Animation Inspector</a> for a good example.</p> <p>In addition, you should consider the following tips:</p> @@ -193,7 +193,7 @@ translation_of: MDN/Guidelines/Video <p>Remember to pause for a second or two at the end, to show the result of the flow.</p> <div class="note"> -<p><strong>Note</strong>: If you are using a really simple tool like QuickTime Player and post production is not an option for some reason, you should get your windows set up in the right size to show the area you want to show. In the Firefox DevTools, you can use the <a href="/en-US/docs/Tools/Rulers">Rulers Tool</a> to make sure the viewport is at the right aspect ratio for the recording.</p> +<p><strong>Note</strong>: If you are using a really simple tool like QuickTime Player and post production is not an option for some reason, you should get your windows set up in the right size to show the area you want to show. In the Firefox DevTools, you can use the <a href="/ja/docs/Tools/Rulers">Rulers Tool</a> to make sure the viewport is at the right aspect ratio for the recording.</p> </div> <h3 id="Post-production">Post-production</h3> @@ -225,6 +225,6 @@ translation_of: MDN/Guidelines/Video <p>\{{EmbedYouTube("you-tube-url-slug")}}</p> -<p>The single property taken by the macro call is the string of characters at the end of the video URL, not the whole URL. For example, the video embedded in our <a href="/en-US/docs/Tools/Page_Inspector/3-pane_mode">Page inspector 3-pane mode</a> article is available at https://www.youtube.com/watch?v=ELS2OOUvxIw, so the required macro call looks like this:</p> +<p>The single property taken by the macro call is the string of characters at the end of the video URL, not the whole URL. For example, the video embedded in our <a href="/ja/docs/Tools/Page_Inspector/3-pane_mode">Page inspector 3-pane mode</a> article is available at https://www.youtube.com/watch?v=ELS2OOUvxIw, so the required macro call looks like this:</p> <p>\{{EmbedYouTube("ELS2OOUvxIw")}}</p> diff --git a/files/ja/mdn/guidelines/writing_style_guide/index.html b/files/ja/mdn/guidelines/writing_style_guide/index.html index 0e9d715f87..b4fcdc4a10 100644 --- a/files/ja/mdn/guidelines/writing_style_guide/index.html +++ b/files/ja/mdn/guidelines/writing_style_guide/index.html @@ -118,7 +118,7 @@ translation_of: MDN/Guidelines/Writing_style_guide <p>ここで、 <code>strokeText()</code> メソッドのより良い概要を見てみましょう。</p> <div class="example-good"> -<p>{{domxref("CanvasRenderingContext2D")}} の <code><strong>strokeText()</strong></code> メソッドは、 <a href="/en-US/docs/Web/API/Canvas_API">Canvas 2D API</a> の一部で、指定された文字列の文字の輪郭を、指定された X 座標と Y 座標で示された位置に描画します。テキストは、コンテキストの現在の {{domxref("CanvasRenderingContext2D.font", "font")}} を使用して描画され、 {{domxref("CanvasRenderingContext2D.textAlign", "textAlign")}}, {{domxref("CanvasRenderingContext2D.textBaseline", "textBaseline")}}, {{domxref("CanvasRenderingContext2D.direction", "direction")}} の各プロパティに従って揃えられます。</p> +<p>{{domxref("CanvasRenderingContext2D")}} の <code><strong>strokeText()</strong></code> メソッドは、 <a href="/ja/docs/Web/API/Canvas_API">Canvas 2D API</a> の一部で、指定された文字列の文字の輪郭を、指定された X 座標と Y 座標で示された位置に描画します。テキストは、コンテキストの現在の {{domxref("CanvasRenderingContext2D.font", "font")}} を使用して描画され、 {{domxref("CanvasRenderingContext2D.textAlign", "textAlign")}}, {{domxref("CanvasRenderingContext2D.textBaseline", "textBaseline")}}, {{domxref("CanvasRenderingContext2D.direction", "direction")}} の各プロパティに従って揃えられます。</p> <p>詳細とさらなる例については、学習エリアの<a href="/ja/docs/Learn/JavaScript/Client-side_web_APIs/Drawing_graphics">図形の描画</a>の<a href="/ja/docs/Learn/JavaScript/Client-side_web_APIs/Drawing_graphics#text">テキスト</a>や、このテーマに関するメインの記事「<a href="/ja/docs/Web/API/Canvas_API/Tutorial/Drawing_text">テキストの描画</a>」を参照してください。</p> </div> @@ -142,7 +142,7 @@ translation_of: MDN/Guidelines/Writing_style_guide <li>If the code is intricate, uses the API being documented, or is technically creative, you should provide a more detailed explanation.</li> </ul> -<p>When adding <a href="/en-US/docs/MDN/Structures/Live_samples">live samples</a>, it's helpful to be aware that all of the {{HTMLElement("pre")}} blocks in the area that contains the sample are concatenated together before running the example, which lets you break any or all of the HTML, CSS, and JavaScript into multiple segments, each optionally with its own descriptions, headings, and so forth. This makes documenting code incredibly powerful and flexible.</p> +<p>When adding <a href="/ja/docs/MDN/Structures/Live_samples">live samples</a>, it's helpful to be aware that all of the {{HTMLElement("pre")}} blocks in the area that contains the sample are concatenated together before running the example, which lets you break any or all of the HTML, CSS, and JavaScript into multiple segments, each optionally with its own descriptions, headings, and so forth. This makes documenting code incredibly powerful and flexible.</p> <h4 id="Overly-short_articles_are_hard_to_find">Overly-short articles are hard to find</h4> @@ -365,7 +365,7 @@ var toolkitProfileService = Components.classes["@mozilla.org/toolkit/profile-ser <h4 id="Expansion">略語の展開</h4> -<p>ある用語についてページ内で初めて言及がある場合は、ユーザにとって馴染みがないと思われる略語を展開しましょう。よく分からなければ、展開するかもしくは記事や、用語の説明をする <a href="/en-US/docs/Glossary">glossary</a> の項目へのリンクを貼りましょう。</p> +<p>ある用語についてページ内で初めて言及がある場合は、ユーザにとって馴染みがないと思われる略語を展開しましょう。よく分からなければ、展開するかもしくは記事や、用語の説明をする <a href="/ja/docs/Glossary">glossary</a> の項目へのリンクを貼りましょう。</p> <ul> <li><span class="correct"><strong>正しい</strong></span>: "XUL (XML User Interface Language) is Mozilla's XML-based language..."</li> |