「ヘルプ:スタイル/書式と記号」の版間の差分
(セクション見出しの訳出・リンク先を日本語版に変更(ID: 16010 の版での同期部分)) |
|||
1行目: | 1行目: | ||
+ | [[カテゴリ:ヘルプ]] |
||
− | [[Category:Help]] |
||
[[el:Help:Style/Formatting and punctuation]] |
[[el:Help:Style/Formatting and punctuation]] |
||
[[en:Help:Style/Formatting and punctuation]] |
[[en:Help:Style/Formatting and punctuation]] |
||
5行目: | 5行目: | ||
[[pt:Help:Style (Português)/Formatting and punctuation]] |
[[pt:Help:Style (Português)/Formatting and punctuation]] |
||
{{Related articles start}} |
{{Related articles start}} |
||
− | {{Related| |
+ | {{Related|ヘルプ:編集#フォーマット}} |
− | {{Related| |
+ | {{Related|ヘルプ:スタイル#フォーマット}} |
{{Related articles end}} |
{{Related articles end}} |
||
The following directions define how different parts of the content of an article should be highlighted through formatting or punctuation. |
The following directions define how different parts of the content of an article should be highlighted through formatting or punctuation. |
||
+ | ==全般的なルール== |
||
− | ==General rules== |
||
− | These general rules always override [[# |
+ | These general rules always override [[#特定のケース]]. For cases not covered in this guide, [[Wikipedia:ja:Wikipedia:スタイルマニュアル|Wikipedia:Manual of Style]] is the authority reference. |
− | * Do not mix more than one highlighting method except where explicitly allowed by these rules. <br> This rule also applies in the cases where some formatting is already set by CSS rules, for example bold in [[ |
+ | * Do not mix more than one highlighting method except where explicitly allowed by these rules. <br> This rule also applies in the cases where some formatting is already set by CSS rules, for example bold in [[ヘルプ:編集#定義リスト|definition list]] terms. If the preset CSS formatting is not allowed on the affected item (e.g. bold on [[#ファイル名とパス]]), then you have to resort using a different, compatible wiki markup altogether (e.g. [[ヘルプ:編集#箇条書き|bullet points]] instead of a definition list). |
* Do not use different highlighting methods from the ones defined in this manual; this includes, but is not limited to, underlining, blinking, full-word capitalization, colors, asterisks, exclamation marks, emoticons, HTML tags with a {{ic|<nowiki>style</nowiki>}} attribute. |
* Do not use different highlighting methods from the ones defined in this manual; this includes, but is not limited to, underlining, blinking, full-word capitalization, colors, asterisks, exclamation marks, emoticons, HTML tags with a {{ic|<nowiki>style</nowiki>}} attribute. |
||
− | === |
+ | ===一番目の用例=== |
* The first relevant appearance of a term or name in an article (e.g. executable names) can be ''highlighted'' (see below) if regarded as worthy of particular attention, considering the topic of the article or the specific section. The first "relevant" appearance may not be the absolute first appearance of the name: its choice is left to the editor. |
* The first relevant appearance of a term or name in an article (e.g. executable names) can be ''highlighted'' (see below) if regarded as worthy of particular attention, considering the topic of the article or the specific section. The first "relevant" appearance may not be the absolute first appearance of the name: its choice is left to the editor. |
||
* The preferable way of highlighting the name is using a link to a closely related article in the wiki or to an external page, like Wikipedia; if there are no possible pertinent links, '''bold''' can be used as a fallback solution. |
* The preferable way of highlighting the name is using a link to a closely related article in the wiki or to an external page, like Wikipedia; if there are no possible pertinent links, '''bold''' can be used as a fallback solution. |
||
− | : Package and package group names should make use of [[ |
+ | : Package and package group names should make use of [[テンプレート:Pkg]], [[テンプレート:AUR]] or [[テンプレート:Grp]]. |
− | * If the name is already introduced by the title of the article or by a section heading, its first relevant appearance in the body can only be used as a link anchor, but not simply highlighted in bold, except in the case of [[# |
+ | * If the name is already introduced by the title of the article or by a section heading, its first relevant appearance in the body can only be used as a link anchor, but not simply highlighted in bold, except in the case of [[#名前/用語集]]. |
− | * First-instance highlighting can be applied only to the [[# |
+ | * First-instance highlighting can be applied only to the [[#特定のケース]] that explicitly allow it. |
− | === |
+ | ===リンク=== |
* No formatting shall be applied to the anchor text of links. |
* No formatting shall be applied to the anchor text of links. |
||
− | === |
+ | ===名前/用語集=== |
− | * It is allowed, not mandatory, to keep consistent formatting in lists of names or terms, even if normally not all of the items would require to be formatted. This can involve for example all-caps terms, which should not be italic-ized by themselves, or names in a list where most of the items are formatted according to [[# |
+ | * It is allowed, not mandatory, to keep consistent formatting in lists of names or terms, even if normally not all of the items would require to be formatted. This can involve for example all-caps terms, which should not be italic-ized by themselves, or names in a list where most of the items are formatted according to [[#一番目の用例]]. <br> "List" is to be intended in a broad sense, so that for example also all the initial words of a series of subsequent paragraphs could be considered forming a list of terms. |
+ | ==フォーマット/句読点のケース== |
||
− | ==Cases by formatting/punctuation== |
||
− | Cases marked by <sup>1</sup> are affected by [[# |
+ | Cases marked by <sup>1</sup> are affected by [[#一番目の用例]]. Cases marked by <sup>m</sup> apply to monospaced text. |
− | === |
+ | ===斜体=== |
Use the MediaWiki syntax {{ic|<nowiki>''italic text''</nowiki>}} instead of {{ic|<nowiki><i></nowiki>}} tags. |
Use the MediaWiki syntax {{ic|<nowiki>''italic text''</nowiki>}} instead of {{ic|<nowiki><i></nowiki>}} tags. |
||
− | *[[# |
+ | *[[#実行ファイル/アプリケーションの名前]]<sup>1</sup> |
+ | *[[#ファイルの拡張子]] |
||
− | *[[#File extensions]] |
||
− | *[[# |
+ | *[[#リポジトリの名前]]<sup>1</sup> |
− | *[[# |
+ | *[[#パッケージとグループの名前]]<sup>1</sup> |
− | *[[# |
+ | *[[#ファイルやコマンドラインの疑似変数]]<sup>m</sup> |
− | *[[#GUI/TUI |
+ | *[[#GUI/TUI テキスト]] |
− | *[[# |
+ | *[[#技術的用語]]<sup>1</sup> |
+ | *[[#強調する語・文]] |
||
− | *[[#Stressed/strong words or statements]] |
||
+ | *[[#略語の展開]] |
||
− | *[[#Acronym/abbreviation expansions]] |
||
− | === |
+ | ===太字=== |
Use the MediaWiki syntax {{ic|<nowiki>'''bold text'''</nowiki>}} instead of {{ic|<nowiki><b></nowiki>}} tags. |
Use the MediaWiki syntax {{ic|<nowiki>'''bold text'''</nowiki>}} instead of {{ic|<nowiki><b></nowiki>}} tags. |
||
− | *[[# |
+ | *[[#ファイルやコマンドラインの内容の重要な部分]]<sup>m</sup> |
+ | *[[#強調する語・文]] |
||
− | *[[#Stressed/strong words or statements]] |
||
− | *[[# |
+ | *[[#一番目の用例]] |
− | === |
+ | ===等幅=== |
− | Use [[ |
+ | Use [[テンプレート:ic]] {{ic|<nowiki>{{ic|monospace text}}</nowiki>}} instead of {{ic|<nowiki><code></nowiki>}} tags for text outside of code blocks. |
+ | *[[#ファイル名とパス]] |
||
− | *[[#File names and paths]] |
||
+ | *[[#デーモン/サービス、カーネルモジュール]] |
||
− | *[[#Daemons/services, kernel modules]] |
||
+ | *[[#設定パラメータ・変数・オプション・プロパティ等]] |
||
− | *[[#Configuration parameters, variables, options, properties...]] |
||
− | *[[# |
+ | *[[#コマンド行]] |
− | *[[# |
+ | *[[#ファイルの内容]] |
− | *[[# |
+ | *[[#キーボードキー]] |
− | === |
+ | ===引用符=== |
Use typewriter quotes {{ic|"quoted text"}} instead of single quotes {{ic|'quoted text'}} or typographic quotes {{ic|“quoted text”}}. |
Use typewriter quotes {{ic|"quoted text"}} instead of single quotes {{ic|'quoted text'}} or typographic quotes {{ic|“quoted text”}}. |
||
+ | *[[#タイトルや見出しへの参照]] |
||
− | *[[#References to titles, headings...]] |
||
+ | *[[#単なる"テキストそのもの"への参照としての単語・文字]] |
||
− | *[[#Words/letters when referenced as mere "text entities"]] |
||
+ | *[[#正しくない・疑わしい方法で使われる一般的な単語]] |
||
− | *[[#Generic words used in an improper or questionable way]] |
||
− | *[[# |
+ | *[[#引用符]] |
+ | ==特定のケース== |
||
− | ==Specific cases== |
||
− | [[# |
+ | [[#全般的なルール]] always override the following rules. |
+ | === 略語の展開=== |
||
− | === Acronym/abbreviation expansions=== |
||
Use ''italic''. |
Use ''italic''. |
||
82行目: | 82行目: | ||
* [[Wikipedia:cat_(Unix)|cat]] (''catenate'') is a standard Unix utility that concatenates and lists files. |
* [[Wikipedia:cat_(Unix)|cat]] (''catenate'') is a standard Unix utility that concatenates and lists files. |
||
− | === |
+ | ===コマンド行=== |
− | Use {{ic|monospace}}. Must be inline command examples, not simple mentions of [[# |
+ | Use {{ic|monospace}}. Must be inline command examples, not simple mentions of [[#実行ファイル/アプリケーションの名前]]. Also console output and text that may reasonably be useful to paste in a terminal. |
;Examples |
;Examples |
||
92行目: | 92行目: | ||
* Execute {{ic|pacman -Syu}} with root privileges. |
* Execute {{ic|pacman -Syu}} with root privileges. |
||
+ | === 設定パラメータ・変数・オプション・プロパティ等 === |
||
− | === Configuration parameters, variables, options, properties... === |
||
Use {{ic|monospace}}. Also affects command options, user groups, IP addresses, environment variables and variables in general. |
Use {{ic|monospace}}. Also affects command options, user groups, IP addresses, environment variables and variables in general. |
||
109行目: | 109行目: | ||
* All files should have {{ic|644}} permissions and {{ic|root:root}} ownership. |
* All files should have {{ic|644}} permissions and {{ic|root:root}} ownership. |
||
* The {{ic|-i}} switch can be omitted if you wish to install every package from the {{Grp|base}} group without prompting. |
* The {{ic|-i}} switch can be omitted if you wish to install every package from the {{Grp|base}} group without prompting. |
||
− | * Adding your user to [[ |
+ | * Adding your user to [[ユーザーとグループ|groups]] ({{ic|sys}}, {{ic|disk}}, {{ic|lp}}, {{ic|network}}, {{ic|video}}, {{ic|audio}}, {{ic|optical}}, {{ic|storage}}, {{ic|scanner}}, {{ic|power}}, etc.) is '''not''' necessary for most use cases with systemd. |
* If you are behind a proxy server, you will need to export the {{ic|http_proxy}} and {{ic|ftp_proxy}}environment variables. |
* If you are behind a proxy server, you will need to export the {{ic|http_proxy}} and {{ic|ftp_proxy}}environment variables. |
||
* To use other locales for other {{ic|LC_*}} variables, run {{ic|locale}} to see the available options and add them to ''locale.conf''. It is not recommended to set the {{ic|LC_ALL}} variable. See [[Locale#Setting the system locale]] for an advanced example. |
* To use other locales for other {{ic|LC_*}} variables, run {{ic|locale}} to see the available options and add them to ''locale.conf''. It is not recommended to set the {{ic|LC_ALL}} variable. See [[Locale#Setting the system locale]] for an advanced example. |
||
116行目: | 116行目: | ||
* By giving the {{ic|-net nic}} argument to QEMU, it will, by default, assign a virtual machine a network interface with the link-level address {{ic|52:54:00:12:34:56}}. |
* By giving the {{ic|-net nic}} argument to QEMU, it will, by default, assign a virtual machine a network interface with the link-level address {{ic|52:54:00:12:34:56}}. |
||
+ | === デーモン/サービス、カーネルモジュール === |
||
− | === Daemons/services, kernel modules === |
||
Use {{ic|monospace}}. |
Use {{ic|monospace}}. |
||
125行目: | 125行目: | ||
* Some unit names contain an {{ic|@}} sign (e.g. {{ic|name@''string''.service}}). |
* Some unit names contain an {{ic|@}} sign (e.g. {{ic|name@''string''.service}}). |
||
+ | === 実行ファイル/アプリケーションの名前=== |
||
− | === Executable/application names=== |
||
− | Use ''italic'', but only for full lower-case names. Affected by [[# |
+ | Use ''italic'', but only for full lower-case names. Affected by [[#一番目の用例]]. |
− | Note that this rule applies to executables only when they represent the application/file itself, not when used in [[# |
+ | Note that this rule applies to executables only when they represent the application/file itself, not when used in [[#コマンド行]]. In particular pay attention to executables that are usually run without any arguments. See also [[ヘルプ:スタイル#スペル]]. |
;Examples |
;Examples |
||
138行目: | 138行目: | ||
* Set a root password with {{ic|passwd}}. |
* Set a root password with {{ic|passwd}}. |
||
− | === |
+ | ===ファイルの内容=== |
Use {{ic|monospace}} for content that can be both read or written on a file or that may reasonably be useful to copy from or paste in a text editor. |
Use {{ic|monospace}} for content that can be both read or written on a file or that may reasonably be useful to copy from or paste in a text editor. |
||
145行目: | 145行目: | ||
* Remove the {{ic|#}} in front of the [http://www.greendesktiny.com/support/knowledgebase_detail.php?ref=EUH-483 locale] you want from {{ic|/etc/locale.gen}}. |
* Remove the {{ic|#}} in front of the [http://www.greendesktiny.com/support/knowledgebase_detail.php?ref=EUH-483 locale] you want from {{ic|/etc/locale.gen}}. |
||
+ | ===ファイルの拡張子=== |
||
− | ===File extensions=== |
||
Use ''italic''. |
Use ''italic''. |
||
151行目: | 151行目: | ||
* Pacman is written in the C programming language and uses the ''.pkg.tar.xz'' package format. |
* Pacman is written in the C programming language and uses the ''.pkg.tar.xz'' package format. |
||
+ | ===ファイル名とパス=== |
||
− | ===File names and paths=== |
||
− | Use {{ic|monospace}}. Also device names and names with wildcards are affected. [[# |
+ | Use {{ic|monospace}}. Also device names and names with wildcards are affected. [[#ファイルの拡張子]] are treated differently, though. |
;Examples |
;Examples |
||
162行目: | 162行目: | ||
* Each partition is identified with a number suffix. For example, {{ic|sda1}} specifies the first partition of the first drive, while {{ic|sda}} designates the entire drive. |
* Each partition is identified with a number suffix. For example, {{ic|sda1}} specifies the first partition of the first drive, while {{ic|sda}} designates the entire drive. |
||
+ | === 正しくない・疑わしい方法で使われる一般的な単語 === |
||
− | === Generic words used in an improper or questionable way === |
||
Use "typewriter quotes". |
Use "typewriter quotes". |
||
;Example |
;Example |
||
+ | * 単なる"テキストそのもの"への参照としての単語・文字. |
||
− | * Words/letters when referenced as mere "text entities". |
||
− | ===GUI/TUI |
+ | ===GUI/TUI テキスト=== |
Use ''italic''. For example for menu entries. When representing navigation in menus, use the "''>''" symbol, still in ''italic'', to separate the items. |
Use ''italic''. For example for menu entries. When representing navigation in menus, use the "''>''" symbol, still in ''italic'', to separate the items. |
||
177行目: | 177行目: | ||
* For plugins to be updated, you should check to have their update repositories enabled in ''Window > Preferences > Install/Update > Available Software Sites''. |
* For plugins to be updated, you should check to have their update repositories enabled in ''Window > Preferences > Install/Update > Available Software Sites''. |
||
+ | ===ファイルやコマンドラインの内容の重要な部分=== |
||
− | ===Important part of file/command line contents=== |
||
Use '''bold'''. Since these contents are code themselves, when referenced outside of the template, {{ic|monospace}} should be preserved. |
Use '''bold'''. Since these contents are code themselves, when referenced outside of the template, {{ic|monospace}} should be preserved. |
||
184行目: | 184行目: | ||
: You can replace '''{{ic|$(uname -r)}}''' with any kernel not currently running. |
: You can replace '''{{ic|$(uname -r)}}''' with any kernel not currently running. |
||
− | === |
+ | ===キーボードキー=== |
Use {{ic|monospace}}. |
Use {{ic|monospace}}. |
||
190行目: | 190行目: | ||
* You have to press a key (usually {{ic|Delete}}, {{ic|F1}}, {{ic|F2}}, {{ic|F11}}, or {{ic|F12}}) during the POST. |
* You have to press a key (usually {{ic|Delete}}, {{ic|F1}}, {{ic|F2}}, {{ic|F11}}, or {{ic|F12}}) during the POST. |
||
+ | ===パッケージとグループの名前=== |
||
− | ===Package and group names=== |
||
− | Use ''italic''. Affected by [[# |
+ | Use ''italic''. Affected by [[#一番目の用例]]. |
;Example |
;Example |
||
* The package ''wireless_tools'' then provides a basic set of tools for managing the wireless connection. |
* The package ''wireless_tools'' then provides a basic set of tools for managing the wireless connection. |
||
+ | === ファイルやコマンドラインの疑似変数 === |
||
− | === Pseudo-variables in file/command line contents === |
||
Use ''italic''. When mentioning a variable outside of the template, {{ic|monospace}} should be preserved. |
Use ''italic''. When mentioning a variable outside of the template, {{ic|monospace}} should be preserved. |
||
213行目: | 213行目: | ||
: Where {{ic|''interface_name''}} is the interface of your wireless chipset. |
: Where {{ic|''interface_name''}} is the interface of your wireless chipset. |
||
− | === |
+ | ===引用符=== |
For inline quotations, use "typewriter quotes". For block quotations, use indentation through a line-initial colon without any additional punctuation or formatting. |
For inline quotations, use "typewriter quotes". For block quotations, use indentation through a line-initial colon without any additional punctuation or formatting. |
||
221行目: | 221行目: | ||
: The X.Org project provides an open source implementation of the X Window System. The development work is being done in conjunction with the freedesktop.org community. The X.Org Foundation is the educational non-profit corporation whose Board serves this effort, and whose Members lead this work. |
: The X.Org project provides an open source implementation of the X Window System. The development work is being done in conjunction with the freedesktop.org community. The X.Org Foundation is the educational non-profit corporation whose Board serves this effort, and whose Members lead this work. |
||
+ | ===タイトルや見出しへの参照=== |
||
− | ===References to titles, headings...=== |
||
Use "typewriter quotes". When referencing section headings, however, use internal anchor links ({{ic|<nowiki>[[#Section]]</nowiki>}}). |
Use "typewriter quotes". When referencing section headings, however, use internal anchor links ({{ic|<nowiki>[[#Section]]</nowiki>}}). |
||
227行目: | 227行目: | ||
* The column "dm-crypt +/- LUKS" denotes features of dm-crypt for both LUKS ("+") and plain ("-") encryption modes. If a specific feature requires using LUKS, this is indicated by "(with LUKS)". Likewise "(without LUKS)" indicates usage of LUKS is counter-productive to achieve the feature and plain mode should be used. |
* The column "dm-crypt +/- LUKS" denotes features of dm-crypt for both LUKS ("+") and plain ("-") encryption modes. If a specific feature requires using LUKS, this is indicated by "(with LUKS)". Likewise "(without LUKS)" indicates usage of LUKS is counter-productive to achieve the feature and plain mode should be used. |
||
+ | ===リポジトリの名前=== |
||
− | ===Repository names=== |
||
− | Use ''italic'' for repository names. Affected by [[# |
+ | Use ''italic'' for repository names. Affected by [[#一番目の用例]]. |
;Example |
;Example |
||
234行目: | 234行目: | ||
* If you enable the ''testing'' repository, you must also enable the ''community-testing'' repository. |
* If you enable the ''testing'' repository, you must also enable the ''community-testing'' repository. |
||
+ | ===強調する語・文=== |
||
− | ===Stressed/strong words or statements=== |
||
Use ''italic'' for words whose importance in giving the meaning to a sentence would not be recognized otherwise; usually they would be pronounced in a stressed way if reading out loud. |
Use ''italic'' for words whose importance in giving the meaning to a sentence would not be recognized otherwise; usually they would be pronounced in a stressed way if reading out loud. |
||
252行目: | 252行目: | ||
* This means that partial upgrades are '''not supported'''. |
* This means that partial upgrades are '''not supported'''. |
||
− | === |
+ | ===技術的用語=== |
− | Use ''italic'', except for all-caps terms (usually acronyms). Affected by [[# |
+ | Use ''italic'', except for all-caps terms (usually acronyms). Affected by [[#一番目の用例]]. |
;Examples |
;Examples |
||
262行目: | 262行目: | ||
* You have to press a key (usually {{ic|Delete}}, {{ic|F1}}, {{ic|F2}}, {{ic|F11}} or {{ic|F12}}) during the POST (Power On Self-Test) phase. |
* You have to press a key (usually {{ic|Delete}}, {{ic|F1}}, {{ic|F2}}, {{ic|F11}} or {{ic|F12}}) during the POST (Power On Self-Test) phase. |
||
+ | === 単なる"テキストそのもの"への参照としての単語・文字 === |
||
− | === Words/letters when referenced as mere "text entities" === |
||
Use "typewriter quotes". |
Use "typewriter quotes". |
||
2020年4月19日 (日) 10:43時点における版
The following directions define how different parts of the content of an article should be highlighted through formatting or punctuation.
目次
- 1 全般的なルール
- 2 フォーマット/句読点のケース
- 3 特定のケース
- 3.1 略語の展開
- 3.2 コマンド行
- 3.3 設定パラメータ・変数・オプション・プロパティ等
- 3.4 デーモン/サービス、カーネルモジュール
- 3.5 実行ファイル/アプリケーションの名前
- 3.6 ファイルの内容
- 3.7 ファイルの拡張子
- 3.8 ファイル名とパス
- 3.9 正しくない・疑わしい方法で使われる一般的な単語
- 3.10 GUI/TUI テキスト
- 3.11 ファイルやコマンドラインの内容の重要な部分
- 3.12 キーボードキー
- 3.13 パッケージとグループの名前
- 3.14 ファイルやコマンドラインの疑似変数
- 3.15 引用符
- 3.16 タイトルや見出しへの参照
- 3.17 リポジトリの名前
- 3.18 強調する語・文
- 3.19 技術的用語
- 3.20 単なる"テキストそのもの"への参照としての単語・文字
全般的なルール
These general rules always override #特定のケース. For cases not covered in this guide, Wikipedia:Manual of Style is the authority reference.
- Do not mix more than one highlighting method except where explicitly allowed by these rules.
This rule also applies in the cases where some formatting is already set by CSS rules, for example bold in definition list terms. If the preset CSS formatting is not allowed on the affected item (e.g. bold on #ファイル名とパス), then you have to resort using a different, compatible wiki markup altogether (e.g. bullet points instead of a definition list). - Do not use different highlighting methods from the ones defined in this manual; this includes, but is not limited to, underlining, blinking, full-word capitalization, colors, asterisks, exclamation marks, emoticons, HTML tags with a
style
attribute.
一番目の用例
- The first relevant appearance of a term or name in an article (e.g. executable names) can be highlighted (see below) if regarded as worthy of particular attention, considering the topic of the article or the specific section. The first "relevant" appearance may not be the absolute first appearance of the name: its choice is left to the editor.
- The preferable way of highlighting the name is using a link to a closely related article in the wiki or to an external page, like Wikipedia; if there are no possible pertinent links, bold can be used as a fallback solution.
- Package and package group names should make use of テンプレート:Pkg, テンプレート:AUR or テンプレート:Grp.
- If the name is already introduced by the title of the article or by a section heading, its first relevant appearance in the body can only be used as a link anchor, but not simply highlighted in bold, except in the case of #名前/用語集.
- First-instance highlighting can be applied only to the #特定のケース that explicitly allow it.
リンク
- No formatting shall be applied to the anchor text of links.
名前/用語集
- It is allowed, not mandatory, to keep consistent formatting in lists of names or terms, even if normally not all of the items would require to be formatted. This can involve for example all-caps terms, which should not be italic-ized by themselves, or names in a list where most of the items are formatted according to #一番目の用例.
"List" is to be intended in a broad sense, so that for example also all the initial words of a series of subsequent paragraphs could be considered forming a list of terms.
フォーマット/句読点のケース
Cases marked by 1 are affected by #一番目の用例. Cases marked by m apply to monospaced text.
斜体
Use the MediaWiki syntax ''italic text''
instead of <i>
tags.
- #実行ファイル/アプリケーションの名前1
- #ファイルの拡張子
- #リポジトリの名前1
- #パッケージとグループの名前1
- #ファイルやコマンドラインの疑似変数m
- #GUI/TUI テキスト
- #技術的用語1
- #強調する語・文
- #略語の展開
太字
Use the MediaWiki syntax '''bold text'''
instead of <b>
tags.
等幅
Use テンプレート:ic {{ic|monospace text}}
instead of <code>
tags for text outside of code blocks.
引用符
Use typewriter quotes "quoted text"
instead of single quotes 'quoted text'
or typographic quotes “quoted text”
.
特定のケース
#全般的なルール always override the following rules.
略語の展開
Use italic.
- Examples
- Pacman is the Arch Linux package manager.
- cat (catenate) is a standard Unix utility that concatenates and lists files.
コマンド行
Use monospace
. Must be inline command examples, not simple mentions of #実行ファイル/アプリケーションの名前. Also console output and text that may reasonably be useful to paste in a terminal.
- Examples
- You are encouraged to type
man command
to read the man page of any command. - You can use the command
ip link
to discover the names of your interfaces. - If you get a
ping: unknown host
error, first check if there is an issue with your cable or wireless signal strength. - Type
yes
and choose Quit (or pressQ
) to exit without making any more changes. - Execute
pacman -Syu
with root privileges.
設定パラメータ・変数・オプション・プロパティ等
Use monospace
. Also affects command options, user groups, IP addresses, environment variables and variables in general.
When both the short and long form of a command option have to be represented, use the "/" symbol without spaces to separate them, for example -a
/--anything
.
- Examples
- By default, the keyboard layout is set to
us
. - [...] where layout can be
fr
,uk
,dvorak
,be-latin1
, etc. - As of v197, udev no longer assigns network interface names according to the
wlanX
andethX
naming scheme. - In this example, the Ethernet interface is
enp2s0f0
. - If you are unsure, your Ethernet interface is likely to start with the letter "e", and unlikely to be
lo
or start with the letter "w". - Currently, you may include a maximum of three
nameserver
lines. - You will need to create an extra BIOS Boot Partition of size 1007 KiB and
EF02
type code. - All files should have
644
permissions androot:root
ownership. - The
-i
switch can be omitted if you wish to install every package from the base group without prompting. - Adding your user to groups (
sys
,disk
,lp
,network
,video
,audio
,optical
,storage
,scanner
,power
, etc.) is not necessary for most use cases with systemd. - If you are behind a proxy server, you will need to export the
http_proxy
andftp_proxy
environment variables. - To use other locales for other
LC_*
variables, runlocale
to see the available options and add them to locale.conf. It is not recommended to set theLC_ALL
variable. See Locale#Setting the system locale for an advanced example. - [...] this roughly equates to what you included in the
DAEMONS
array. - If you are running a private network, it is safe to use IP addresses in
192.168.*.*
for your IP addresses, with a subnet mask of255.255.255.0
and a broadcast address of192.168.*.255
. The gateway is usually192.168.*.1
or192.168.*.254
. - By giving the
-net nic
argument to QEMU, it will, by default, assign a virtual machine a network interface with the link-level address52:54:00:12:34:56
.
デーモン/サービス、カーネルモジュール
Use monospace
.
- Example
- The
dhcpcd.service
starts the daemon for all network interfaces. - Some unit names contain an
@
sign (e.g.name@string.service
).
実行ファイル/アプリケーションの名前
Use italic, but only for full lower-case names. Affected by #一番目の用例.
Note that this rule applies to executables only when they represent the application/file itself, not when used in #コマンド行. In particular pay attention to executables that are usually run without any arguments. See also ヘルプ:スタイル#スペル.
- Examples
- Uncomment the selected locale in
/etc/locale.gen
and generate it with the locale-gen utility. - Uncomment the selected locale in
/etc/locale.gen
and generate it withlocale-gen
. - As of v197, udev no longer assigns network interface names according to the
wlanX
andethX
naming scheme. - The Arch Linux install media includes the following partitioning tools: fdisk, gdisk, cfdisk, cgdisk, parted.
- If pacman fails to verify your packages, check the system time with
cal
. - Set a root password with
passwd
.
ファイルの内容
Use monospace
for content that can be both read or written on a file or that may reasonably be useful to copy from or paste in a text editor.
- Examples
- At the end of the string type
nomodeset
and pressEnter
. Alternatively, tryvideo=SVIDEO-1:d
which, if it works, will not disable kernel mode setting. - Remove the
#
in front of the locale you want from/etc/locale.gen
.
ファイルの拡張子
Use italic.
- Example
- Pacman is written in the C programming language and uses the .pkg.tar.xz package format.
ファイル名とパス
Use monospace
. Also device names and names with wildcards are affected. #ファイルの拡張子 are treated differently, though.
- Examples
- To test if you have booted into UEFI mode check if directory
/sys/firmware/efi
has been created. - All files and directories appear under the root directory
/
, even if they are stored on different physical devices. - Edit
/etc/resolv.conf
, substituting your name servers' IP addresses and your local domain name. - Before installing, you may want to edit the
mirrorlist
file and place your preferred mirror first. - For kernel modules to load during boot, place a .conf file with a name based on the program that uses them in
/etc/modules-load.d/
. - Each partition is identified with a number suffix. For example,
sda1
specifies the first partition of the first drive, whilesda
designates the entire drive.
正しくない・疑わしい方法で使われる一般的な単語
Use "typewriter quotes".
- Example
- 単なる"テキストそのもの"への参照としての単語・文字.
GUI/TUI テキスト
Use italic. For example for menu entries. When representing navigation in menus, use the ">" symbol, still in italic, to separate the items.
- Examples
- Then, select Boot Arch Linux from the menu and press
Enter
in order to begin with the installation. - When using Gparted, selecting the option to create a new partition table gives an msdos partition table by default. If you are intending to follow the advice to create a GPT partition table then you need to choose Advanced and then select gpt from the drop-down menu.
- Type
yes
and choose Quit (or pressQ
) to exit without making any more changes. - For plugins to be updated, you should check to have their update repositories enabled in Window > Preferences > Install/Update > Available Software Sites.
ファイルやコマンドラインの内容の重要な部分
Use bold. Since these contents are code themselves, when referenced outside of the template, monospace
should be preserved.
- Example
# ln -s /usr/src/linux-$(uname -r)/include/generated/uapi/linux/version.h /usr/src/linux-$(uname -r)/include/linux/
- You can replace
$(uname -r)
with any kernel not currently running.
キーボードキー
Use monospace
.
- Example
- You have to press a key (usually
Delete
,F1
,F2
,F11
, orF12
) during the POST.
パッケージとグループの名前
Use italic. Affected by #一番目の用例.
- Example
- The package wireless_tools then provides a basic set of tools for managing the wireless connection.
ファイルやコマンドラインの疑似変数
Use italic. When mentioning a variable outside of the template, monospace
should be preserved.
Make sure that variables do not contain any spaces: underscores should be used in their place.
Ensure naming consistency with the rest of the article, which may already use a pseudo-variable. For example do not introduce a new keyboardlayout
variable, if keyboard_layout
is already used.
- Example
# loadkeys keyboard_layout
- [...] where
keyboard_layout
can befr
,uk
,dvorak
,be-latin1
, etc.
- Bring the interface up with
ip link set interface up
. - You can connect to the network with:
# wifi-menu interface_name
- Where
interface_name
is the interface of your wireless chipset.
引用符
For inline quotations, use "typewriter quotes". For block quotations, use indentation through a line-initial colon without any additional punctuation or formatting.
- Examples
- "All your data belongs to us" – Google
- From http://www.x.org/wiki/:
- The X.Org project provides an open source implementation of the X Window System. The development work is being done in conjunction with the freedesktop.org community. The X.Org Foundation is the educational non-profit corporation whose Board serves this effort, and whose Members lead this work.
タイトルや見出しへの参照
Use "typewriter quotes". When referencing section headings, however, use internal anchor links ([[#Section]]
).
- Example
- The column "dm-crypt +/- LUKS" denotes features of dm-crypt for both LUKS ("+") and plain ("-") encryption modes. If a specific feature requires using LUKS, this is indicated by "(with LUKS)". Likewise "(without LUKS)" indicates usage of LUKS is counter-productive to achieve the feature and plain mode should be used.
リポジトリの名前
Use italic for repository names. Affected by #一番目の用例.
- Example
- To enable the testing repository, you have to uncomment the
[testing]
section in/etc/pacman.conf
. - If you enable the testing repository, you must also enable the community-testing repository.
強調する語・文
Use italic for words whose importance in giving the meaning to a sentence would not be recognized otherwise; usually they would be pronounced in a stressed way if reading out loud.
When however particular attention is needed, words like "not", "only", "exactly", "strongly", "before"... can be highlighted in bold.
The same goes for very important statements that cannot be put in a separate Warning or Note as they are an essential part of the section itself.
- Examples
- Choose the best environment for your needs.
- This command can synchronize the repository databases and update the system's packages.
- If the screen does not go blank and the boot process gets stuck.
- [...] so please type it exactly as you see it.
- If you want, you can make it the only mirror available by getting rid of everything else.
- Partitioning can destroy data. You are strongly cautioned and advised to backup any critical data before proceeding.
- keep up to date with changes in Arch Linux that require manual intervention before upgrading your system.
- When performing a system update, it is essential that users read all information output by pacman and use common sense.
- This means that partial upgrades are not supported.
技術的用語
Use italic, except for all-caps terms (usually acronyms). Affected by #一番目の用例.
- Examples
- You are encouraged to type
man command
to read the man page of any command. - This article deals with so-called core utilities on a GNU/Linux system.
- Primary partitions can be bootable and are limited to four partitions per disk or RAID volume.
- This is already a separate partition by default, by virtue of being mounted as tmpfs by systemd.
- You have to press a key (usually
Delete
,F1
,F2
,F11
orF12
) during the POST (Power On Self-Test) phase.
単なる"テキストそのもの"への参照としての単語・文字
Use "typewriter quotes".
- Examples
- When however particular attention is needed, words like "not", "only", "exactly", "strongly", "before"... can be highlighted in bold.
- If you are unsure, your Ethernet interface is likely to start with the letter "e", and unlikely to be
lo
or start with the letter "w".