X-Git-Url: http://git.osdn.net/view?a=blobdiff_plain;f=po4a%2Fman2%2Fpo%2Fja.po;h=7741fec3c22f3b5630d47f1ad4fc3ffc9629cfe6;hb=d16cdf77a1abd0dff4998f94c24756d6d0e479ba;hp=bb7f3d7f73f44f3b177b7d67951b0769905ef778;hpb=be0cf6a256928b1a3dbd26395957b26b35a71020;p=linuxjm%2FLDP_man-pages.git

diff --git a/po4a/man2/po/ja.po b/po4a/man2/po/ja.po
index bb7f3d7f..7741fec3 100644
--- a/po4a/man2/po/ja.po
+++ b/po4a/man2/po/ja.po
@@ -6,8 +6,8 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2015-01-23 22:22+0900\n"
-"PO-Revision-Date: 2015-01-23 22:33+0900\n"
+"POT-Creation-Date: 2015-01-23 22:24+0900\n"
+"PO-Revision-Date: 2015-01-25 01:03+0900\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
 "Language: \n"
@@ -135,16 +135,8 @@ msgstr "説明"
 
 #. type: Plain text
 #: build/C/man2/arch_prctl.2:52
-msgid ""
-"The B<arch_prctl>()  function sets architecture-specific process or thread "
-"state.  I<code> selects a subfunction and passes argument I<addr> to it; "
-"I<addr> is interpreted as either an I<unsigned long> for the \"set\" "
-"operations, or as an I<unsigned long\\ *>, for the \"get\" operations."
-msgstr ""
-"B<arch_prctl>()  関数はアーキテクチャ固有のプロセス状態またはスレッド状態を設"
-"定する。 I<code> は副機能を選択し、引き数 I<addr> を副機能に渡す。 I<addr> "
-"は、\"set\" 操作では I<unsigned long> として、\"get\" 操作では I<unsigned "
-"long\\ *> として解釈される。"
+msgid "The B<arch_prctl>()  function sets architecture-specific process or thread state.  I<code> selects a subfunction and passes argument I<addr> to it; I<addr> is interpreted as either an I<unsigned long> for the \"set\" operations, or as an I<unsigned long\\ *>, for the \"get\" operations."
+msgstr "B<arch_prctl>()  関数はアーキテクチャ固有のプロセス状態またはスレッド状態を設定する。 I<code> は副機能を選択し、引き数 I<addr> を副機能に渡す。 I<addr> は、\"set\" 操作では I<unsigned long> として、\"get\" 操作では I<unsigned long\\ *> として解釈される。"
 
 #. type: Plain text
 #: build/C/man2/arch_prctl.2:54
@@ -170,12 +162,8 @@ msgstr "B<ARCH_GET_FS>"
 
 #. type: Plain text
 #: build/C/man2/arch_prctl.2:68
-msgid ""
-"Return the 64-bit base value for the I<FS> register of the current thread in "
-"the I<unsigned long> pointed to by I<addr>."
-msgstr ""
-"現在のスレッドの I<FS> レジスタの 64 ビットベース値を、 I<addr> が指す "
-"I<unsigned long> の領域に格納する。"
+msgid "Return the 64-bit base value for the I<FS> register of the current thread in the I<unsigned long> pointed to by I<addr>."
+msgstr "現在のスレッドの I<FS> レジスタの 64 ビットベース値を、 I<addr> が指す I<unsigned long> の領域に格納する。"
 
 #. type: TP
 #: build/C/man2/arch_prctl.2:68
@@ -196,12 +184,8 @@ msgstr "B<ARCH_GET_GS>"
 
 #. type: Plain text
 #: build/C/man2/arch_prctl.2:82
-msgid ""
-"Return the 64-bit base value for the I<GS> register of the current thread in "
-"the I<unsigned long> pointed to by I<addr>."
-msgstr ""
-"現在のスレッドの I<GS> レジスタの 64 ビットベース値を、 I<addr> が指す "
-"I<unsigned long> の領域に格納する。"
+msgid "Return the 64-bit base value for the I<GS> register of the current thread in the I<unsigned long> pointed to by I<addr>."
+msgstr "現在のスレッドの I<GS> レジスタの 64 ビットベース値を、 I<addr> が指す I<unsigned long> の領域に格納する。"
 
 #. type: SH
 #: build/C/man2/arch_prctl.2:82 build/C/man2/futex.2:216
@@ -221,12 +205,8 @@ msgstr "返り値"
 
 #. type: Plain text
 #: build/C/man2/arch_prctl.2:88
-msgid ""
-"On success, B<arch_prctl>()  returns 0; on error, -1 is returned, and "
-"I<errno> is set to indicate the error."
-msgstr ""
-"成功すると、 B<arch_prctl>()  は 0 を返す。エラーの場合、-1 を返し、 "
-"I<errno> をエラーを示す値に設定する。"
+msgid "On success, B<arch_prctl>()  returns 0; on error, -1 is returned, and I<errno> is set to indicate the error."
+msgstr "成功すると、 B<arch_prctl>()  は 0 を返す。エラーの場合、-1 を返し、 I<errno> をエラーを示す値に設定する。"
 
 #. type: SH
 #: build/C/man2/arch_prctl.2:88 build/C/man2/futex.2:241
@@ -256,12 +236,8 @@ msgstr "B<EFAULT>"
 
 #. type: Plain text
 #: build/C/man2/arch_prctl.2:93
-msgid ""
-"I<addr> points to an unmapped address or is outside the process address "
-"space."
-msgstr ""
-"I<addr> がアンマップされたアドレスを指しているか、プロセスのアドレス空間の外"
-"にある。"
+msgid "I<addr> points to an unmapped address or is outside the process address space."
+msgstr "I<addr> がアンマップされたアドレスを指しているか、プロセスのアドレス空間の外にある。"
 
 #. type: TP
 #: build/C/man2/arch_prctl.2:93 build/C/man2/futex.2:268
@@ -318,12 +294,8 @@ msgstr "準拠"
 
 #. type: Plain text
 #: build/C/man2/arch_prctl.2:107
-msgid ""
-"B<arch_prctl>()  is a Linux/x86-64 extension and should not be used in "
-"programs intended to be portable."
-msgstr ""
-"B<arch_prctl>()  は Linux/x86-64 拡張であり、移植性を意図したプログラムでは使"
-"うべきでない。"
+msgid "B<arch_prctl>()  is a Linux/x86-64 extension and should not be used in programs intended to be portable."
+msgstr "B<arch_prctl>()  は Linux/x86-64 拡張であり、移植性を意図したプログラムでは使うべきでない。"
 
 #. type: SH
 #: build/C/man2/arch_prctl.2:107 build/C/man2/futex.2:305
@@ -340,19 +312,13 @@ msgstr "注意"
 
 #. type: Plain text
 #: build/C/man2/arch_prctl.2:110
-msgid ""
-"B<arch_prctl>()  is supported only on Linux/x86-64 for 64-bit programs "
-"currently."
-msgstr ""
-"B<arch_prctl>()  は現在のところ Linux/x86-64 上の 64 ビットプログラムでのみサ"
-"ポートされている。"
+msgid "B<arch_prctl>()  is supported only on Linux/x86-64 for 64-bit programs currently."
+msgstr "B<arch_prctl>()  は現在のところ Linux/x86-64 上の 64 ビットプログラムでのみサポートされている。"
 
 #. type: Plain text
 #: build/C/man2/arch_prctl.2:112
 msgid "The 64-bit base changes when a new 32-bit segment selector is loaded."
-msgstr ""
-"新しい 32 ビットセグメントセレクタがロードされた場合、 64 ビットベースは変更"
-"される。"
+msgstr "新しい 32 ビットセグメントセレクタがロードされた場合、 64 ビットベースは変更される。"
 
 #. type: Plain text
 #: build/C/man2/arch_prctl.2:115
@@ -361,31 +327,13 @@ msgstr "B<ARCH_SET_GS> が無効にされているカーネルもある。"
 
 #. type: Plain text
 #: build/C/man2/arch_prctl.2:130
-msgid ""
-"Context switches for 64-bit segment bases are rather expensive.  It may be a "
-"faster alternative to set a 32-bit base using a segment selector by setting "
-"up an LDT with B<modify_ldt>(2)  or using the B<set_thread_area>(2)  system "
-"call in kernel 2.5 or later.  B<arch_prctl>()  is needed only when you want "
-"to set bases that are larger than 4GB.  Memory in the first 2GB of address "
-"space can be allocated by using B<mmap>(2)  with the B<MAP_32BIT> flag."
-msgstr ""
-"64 ビットセグメントベースのコンテキストスイッチは、やや高価である。 LDT を "
-"B<modify_ldt>(2)  で設定してセグメントセレクタを使うか、 (カーネル 2.5 以降"
-"の)  B<set_thread_area>(2)  システムコールを使うことにより、 32 ビットベース"
-"を設定するという高速な代替手段もある。 4GB より大きなベースを設定したい場合に"
-"のみ、 B<arch_prctl>()  が必要である。 アドレス空間の最初の 2GB にあるメモリ"
-"は、 B<mmap>(2)  に B<MAP_32BIT> フラグを指定して割り当てることができる。"
+msgid "Context switches for 64-bit segment bases are rather expensive.  It may be a faster alternative to set a 32-bit base using a segment selector by setting up an LDT with B<modify_ldt>(2)  or using the B<set_thread_area>(2)  system call in kernel 2.5 or later.  B<arch_prctl>()  is needed only when you want to set bases that are larger than 4GB.  Memory in the first 2GB of address space can be allocated by using B<mmap>(2)  with the B<MAP_32BIT> flag."
+msgstr "64 ビットセグメントベースのコンテキストスイッチは、やや高価である。 LDT を B<modify_ldt>(2)  で設定してセグメントセレクタを使うか、 (カーネル 2.5 以降の)  B<set_thread_area>(2)  システムコールを使うことにより、 32 ビットベースを設定するという高速な代替手段もある。 4GB より大きなベースを設定したい場合にのみ、 B<arch_prctl>()  が必要である。 アドレス空間の最初の 2GB にあるメモリは、 B<mmap>(2)  に B<MAP_32BIT> フラグを指定して割り当てることができる。"
 
 #. type: Plain text
 #: build/C/man2/arch_prctl.2:135
-msgid ""
-"As of version 2.7, glibc provides no prototype for B<arch_prctl>().  You "
-"have to declare it yourself for now.  This may be fixed in future glibc "
-"versions."
-msgstr ""
-"バージョン 2.7 時点では、glibc には B<arch_prctl>()  のプロトタイプがない。 "
-"今のところユーザは自分自身で宣言する必要がある。 これは将来の glibc のバー"
-"ジョンで修正されるかもしれない。"
+msgid "As of version 2.7, glibc provides no prototype for B<arch_prctl>().  You have to declare it yourself for now.  This may be fixed in future glibc versions."
+msgstr "バージョン 2.7 時点では、glibc には B<arch_prctl>()  のプロトタイプがない。 今のところユーザは自分自身で宣言する必要がある。 これは将来の glibc のバージョンで修正されるかもしれない。"
 
 #. type: Plain text
 #: build/C/man2/arch_prctl.2:138
@@ -445,11 +393,7 @@ msgstr "この文書について"
 #: build/C/man2/quotactl.2:520 build/C/man2/sendfile.2:211
 #: build/C/man2/set_tid_address.2:111 build/C/man2/splice.2:252
 #: build/C/man2/tee.2:225 build/C/man2/vm86.2:84 build/C/man2/vmsplice.2:175
-msgid ""
-"This page is part of release 3.78 of the Linux I<man-pages> project.  A "
-"description of the project, information about reporting bugs, and the latest "
-"version of this page, can be found at \\%http://www.kernel.org/doc/man-"
-"pages/."
+msgid "This page is part of release 3.78 of the Linux I<man-pages> project.  A description of the project, information about reporting bugs, and the latest version of this page, can be found at \\%http://www.kernel.org/doc/man-pages/."
 msgstr ""
 "この man ページは Linux I<man-pages> プロジェクトのリリース 3.78 の一部\n"
 "である。プロジェクトの説明とバグ報告に関する情報は\n"
@@ -501,66 +445,27 @@ msgstr "B<          int *>I<uaddr2>B<, int >I<val3>B<);>\n"
 #: build/C/man2/perf_event_open.2:42 build/C/man2/perfmonctl.2:39
 #: build/C/man2/pivot_root.2:18
 msgid "I<Note>: There is no glibc wrapper for this system call; see NOTES."
-msgstr ""
-"I<注>: このシステムコールには glibc のラッパー関数は存在しない。「注意」の節"
-"を参照。"
+msgstr "I<注>: このシステムコールには glibc のラッパー関数は存在しない。「注意」の節を参照。"
 
 #. type: Plain text
 #: build/C/man2/futex.2:86
-msgid ""
-"The B<futex>()  system call provides a method for a program to wait for a "
-"value at a given address to change, and a method to wake up anyone waiting "
-"on a particular address (while the addresses for the same memory in separate "
-"processes may not be equal, the kernel maps them internally so the same "
-"memory mapped in different locations will correspond for B<futex>()  "
-"calls).  This system call is typically used to implement the contended case "
-"of a lock in shared memory, as described in B<futex>(7)."
-msgstr ""
-"B<futex>()  システムコールは、 指定したアドレスの値が変更されるのをプログラム"
-"が待つ手段や 特定のアドレスに対して待機中のプロセスを wake (起床) させる手段"
-"を提供する (プロセスが異なれば同じメモリに対するアドレスも同じではないかもし"
-"れないが、 カーネルは異なる位置にマップされた同じメモリを B<futex>()  で使え"
-"るよう内部でマップする)。 通常は、このシステムコールは B<futex>(7)  に書かれ"
-"ているように、 共有メモリ中のロックが競合する場合の処理を実装するのに用いられ"
-"る。"
+msgid "The B<futex>()  system call provides a method for a program to wait for a value at a given address to change, and a method to wake up anyone waiting on a particular address (while the addresses for the same memory in separate processes may not be equal, the kernel maps them internally so the same memory mapped in different locations will correspond for B<futex>()  calls).  This system call is typically used to implement the contended case of a lock in shared memory, as described in B<futex>(7)."
+msgstr "B<futex>()  システムコールは、 指定したアドレスの値が変更されるのをプログラムが待つ手段や 特定のアドレスに対して待機中のプロセスを wake (起床) させる手段を提供する (プロセスが異なれば同じメモリに対するアドレスも同じではないかもしれないが、 カーネルは異なる位置にマップされた同じメモリを B<futex>()  で使えるよう内部でマップする)。 通常は、このシステムコールは B<futex>(7)  に書かれているように、 共有メモリ中のロックが競合する場合の処理を実装するのに用いられる。"
 
 #. type: Plain text
 #: build/C/man2/futex.2:93
-msgid ""
-"When a B<futex>(7)  operation did not finish uncontended in user space, a "
-"call needs to be made to the kernel to arbitrate.  Arbitration can either "
-"mean putting the calling process to sleep or, conversely, waking a waiting "
-"process."
-msgstr ""
-"B<futex>(7)  の操作がユーザ空間で競合なく完了しなかった場合、 カーネルに仲裁"
-"させるためにシステムコールを呼ぶ必要がある。 仲裁というのは、呼び出しプロセス"
-"を sleep (起床待ち) させたり、反対に 待ちプロセスを wake させたりすることを意"
-"味する。"
+msgid "When a B<futex>(7)  operation did not finish uncontended in user space, a call needs to be made to the kernel to arbitrate.  Arbitration can either mean putting the calling process to sleep or, conversely, waking a waiting process."
+msgstr "B<futex>(7)  の操作がユーザ空間で競合なく完了しなかった場合、 カーネルに仲裁させるためにシステムコールを呼ぶ必要がある。 仲裁というのは、呼び出しプロセスを sleep (起床待ち) させたり、反対に 待ちプロセスを wake させたりすることを意味する。"
 
 #. type: Plain text
 #: build/C/man2/futex.2:100
-msgid ""
-"Callers of this function are expected to adhere to the semantics as set out "
-"in B<futex>(7).  As these semantics involve writing nonportable assembly "
-"instructions, this in turn probably means that most users will in fact be "
-"library authors and not general application developers."
-msgstr ""
-"この関数を呼び出すプロセスは B<futex>(7)  に記述されているセマンティクスに忠"
-"実であることが要求される。 このセマンティクスには移植不可能なアセンブリ命令を"
-"書くことが含まれる。 このことは言い換えると futex のユーザのほとんどは実際は"
-"ライブラリの作者であり、 一般アプリケーションの開発者ではないということであ"
-"る。"
+msgid "Callers of this function are expected to adhere to the semantics as set out in B<futex>(7).  As these semantics involve writing nonportable assembly instructions, this in turn probably means that most users will in fact be library authors and not general application developers."
+msgstr "この関数を呼び出すプロセスは B<futex>(7)  に記述されているセマンティクスに忠実であることが要求される。 このセマンティクスには移植不可能なアセンブリ命令を書くことが含まれる。 このことは言い換えると futex のユーザのほとんどは実際はライブラリの作者であり、 一般アプリケーションの開発者ではないということである。"
 
 #. type: Plain text
 #: build/C/man2/futex.2:108
-msgid ""
-"The I<uaddr> argument needs to point to an aligned integer which stores the "
-"counter.  The operation to execute is passed via the I<op> argument, along "
-"with a value I<val>."
-msgstr ""
-"I<uaddr> 引き数は、カウンタを格納する、 アラインメントの揃った int 型変数を指"
-"している必要がある。 実行する操作は I<op> 引き数を介して、値 I<val> とともに"
-"渡される。"
+msgid "The I<uaddr> argument needs to point to an aligned integer which stores the counter.  The operation to execute is passed via the I<op> argument, along with a value I<val>."
+msgstr "I<uaddr> 引き数は、カウンタを格納する、 アラインメントの揃った int 型変数を指している必要がある。 実行する操作は I<op> 引き数を介して、値 I<val> とともに渡される。"
 
 #. type: Plain text
 #: build/C/man2/futex.2:110
@@ -575,33 +480,13 @@ msgstr "B<FUTEX_WAIT>"
 
 #. type: Plain text
 #: build/C/man2/futex.2:133
-msgid ""
-"This operation atomically verifies that the futex address I<uaddr> still "
-"contains the value I<val>, and sleeps awaiting B<FUTEX_WAKE> on this futex "
-"address.  If the I<timeout> argument is non-NULL, its contents specify the "
-"duration of the wait.  (This interval will be rounded up to the system clock "
-"granularity, and kernel scheduling delays mean that the blocking interval "
-"may overrun by a small amount.)  If I<timeout> is NULL, the call blocks "
-"indefinitely.  The arguments I<uaddr2> and I<val3> are ignored."
-msgstr ""
-"この操作は futex アドレス I<uaddr> に指定された値 I<val> がまだ格納されている"
-"かどうかを不可分操作で検証し、 sleep 状態で この futex アドレスに対して "
-"B<FUTEX_WAKE> が実行されるのを待つ。 I<timeout> 引き数が NULL でない場合、そ"
-"の内容は待ち時間の最大値を表す (この停止時間はシステムクロックの粒度に切り上"
-"げられ、 カーネルのスケジューリング遅延により少しだけ長くなる可能性がある)。 "
-"NULL の場合、 呼び出しは無限に停止する。 引き数 I<uaddr2> と I<val3> は無視さ"
-"れる。"
+msgid "This operation atomically verifies that the futex address I<uaddr> still contains the value I<val>, and sleeps awaiting B<FUTEX_WAKE> on this futex address.  If the I<timeout> argument is non-NULL, its contents specify the duration of the wait.  (This interval will be rounded up to the system clock granularity, and kernel scheduling delays mean that the blocking interval may overrun by a small amount.)  If I<timeout> is NULL, the call blocks indefinitely.  The arguments I<uaddr2> and I<val3> are ignored."
+msgstr "この操作は futex アドレス I<uaddr> に指定された値 I<val> がまだ格納されているかどうかを不可分操作で検証し、 sleep 状態で この futex アドレスに対して B<FUTEX_WAKE> が実行されるのを待つ。 I<timeout> 引き数が NULL でない場合、その内容は待ち時間の最大値を表す (この停止時間はシステムクロックの粒度に切り上げられ、 カーネルのスケジューリング遅延により少しだけ長くなる可能性がある)。 NULL の場合、 呼び出しは無限に停止する。 引き数 I<uaddr2> と I<val3> は無視される。"
 
 #. type: Plain text
 #: build/C/man2/futex.2:141
-msgid ""
-"For B<futex>(7), this call is executed if decrementing the count gave a "
-"negative value (indicating contention), and will sleep until another process "
-"releases the futex and executes the B<FUTEX_WAKE> operation."
-msgstr ""
-"B<futex>(7)  に照らし合わせると、この呼び出しは カウントのデクリメントで負の"
-"値 (競合を表す) になった場合に実行され、 別のプロセスがその futex を解放し "
-"B<FUTEX_WAKE> の操作を実行するまで sleep する。"
+msgid "For B<futex>(7), this call is executed if decrementing the count gave a negative value (indicating contention), and will sleep until another process releases the futex and executes the B<FUTEX_WAKE> operation."
+msgstr "B<futex>(7)  に照らし合わせると、この呼び出しは カウントのデクリメントで負の値 (競合を表す) になった場合に実行され、 別のプロセスがその futex を解放し B<FUTEX_WAKE> の操作を実行するまで sleep する。"
 
 #. type: TP
 #: build/C/man2/futex.2:141 build/C/man2/futex.2:229
@@ -611,25 +496,13 @@ msgstr "B<FUTEX_WAKE>"
 
 #. type: Plain text
 #: build/C/man2/futex.2:152
-msgid ""
-"This operation wakes at most I<val> processes waiting on this futex address "
-"(i.e., inside B<FUTEX_WAIT>).  The arguments I<timeout>, I<uaddr2> and "
-"I<val3> are ignored."
-msgstr ""
-"この操作では指定した futex アドレスに対して待ち状態の (すなわち "
-"B<FUTEX_WAIT> 中の) 最大 I<val> 個のプロセスを wake させる。 引き数 "
-"I<timeout>, I<uaddr2>, I<val3> は無視される。"
+msgid "This operation wakes at most I<val> processes waiting on this futex address (i.e., inside B<FUTEX_WAIT>).  The arguments I<timeout>, I<uaddr2> and I<val3> are ignored."
+msgstr "この操作では指定した futex アドレスに対して待ち状態の (すなわち B<FUTEX_WAIT> 中の) 最大 I<val> 個のプロセスを wake させる。 引き数 I<timeout>, I<uaddr2>, I<val3> は無視される。"
 
 #. type: Plain text
 #: build/C/man2/futex.2:158
-msgid ""
-"For B<futex>(7), this is executed if incrementing the count showed that "
-"there were waiters, once the futex value has been set to 1 (indicating that "
-"it is available)."
-msgstr ""
-"B<futex>(4) に照らし合わせると、 この操作は カウントのインクリメントで待ちプ"
-"ロセスがあると判明し、 futex 値が 1 に設定された (利用可能であることを表す) "
-"場合に実行される。"
+msgid "For B<futex>(7), this is executed if incrementing the count showed that there were waiters, once the futex value has been set to 1 (indicating that it is available)."
+msgstr "B<futex>(4) に照らし合わせると、 この操作は カウントのインクリメントで待ちプロセスがあると判明し、 futex 値が 1 に設定された (利用可能であることを表す) 場合に実行される。"
 
 #. type: TP
 #: build/C/man2/futex.2:158
@@ -640,36 +513,18 @@ msgstr "B<FUTEX_FD> (Linux 2.6.25 以前)"
 #.  , suitable for .BR poll (2).
 #. type: Plain text
 #: build/C/man2/futex.2:174
-msgid ""
-"To support asynchronous wakeups, this operation associates a file descriptor "
-"with a futex.  If another process executes a B<FUTEX_WAKE>, the process will "
-"receive the signal number that was passed in I<val>.  The calling process "
-"must close the returned file descriptor after use.  The arguments "
-"I<timeout>, I<uaddr2> and I<val3> are ignored."
-msgstr ""
-"非同期の wake に対応するため、この操作はファイルディスクリプタを futex に 関"
-"連づける。 別のプロセスが B<FUTEX_WAKE> を実行すると、プロセスは I<val> で渡"
-"されたシグナル番号のシグナルを受信する。 呼び出しプロセスは使用後、返された"
-"ファイルディスクリプタを クローズしなければならない。 引き数 I<timeout>, "
-"I<uaddr2>, I<val3> は無視される。"
+msgid "To support asynchronous wakeups, this operation associates a file descriptor with a futex.  If another process executes a B<FUTEX_WAKE>, the process will receive the signal number that was passed in I<val>.  The calling process must close the returned file descriptor after use.  The arguments I<timeout>, I<uaddr2> and I<val3> are ignored."
+msgstr "非同期の wake に対応するため、この操作はファイルディスクリプタを futex に 関連づける。 別のプロセスが B<FUTEX_WAKE> を実行すると、プロセスは I<val> で渡されたシグナル番号のシグナルを受信する。 呼び出しプロセスは使用後、返されたファイルディスクリプタを クローズしなければならない。 引き数 I<timeout>, I<uaddr2>, I<val3> は無視される。"
 
 #. type: Plain text
 #: build/C/man2/futex.2:179
-msgid ""
-"To prevent race conditions, the caller should test if the futex has been "
-"upped after B<FUTEX_FD> returns."
-msgstr ""
-"競合状態を防止するため、呼び出しプロセスは B<FUTEX_FD> が返ったあと futex が "
-"up されたかどうかを確認しなければならない。"
+msgid "To prevent race conditions, the caller should test if the futex has been upped after B<FUTEX_FD> returns."
+msgstr "競合状態を防止するため、呼び出しプロセスは B<FUTEX_FD> が返ったあと futex が up されたかどうかを確認しなければならない。"
 
 #. type: Plain text
 #: build/C/man2/futex.2:183
-msgid ""
-"Because it was inherently racy, B<FUTEX_FD> has been removed from Linux "
-"2.6.26 onward."
-msgstr ""
-"B<FUTEX_FD> はもともと競合が起きやすかったため、 Linux 2.6.26 以降で削除され"
-"ている。"
+msgid "Because it was inherently racy, B<FUTEX_FD> has been removed from Linux 2.6.26 onward."
+msgstr "B<FUTEX_FD> はもともと競合が起きやすかったため、 Linux 2.6.26 以降で削除されている。"
 
 #. type: TP
 #: build/C/man2/futex.2:183
@@ -679,18 +534,8 @@ msgstr "B<FUTEX_REQUEUE> (Linux 2.5.70 以降)"
 
 #. type: Plain text
 #: build/C/man2/futex.2:198
-msgid ""
-"This operation was introduced in order to avoid a \"thundering herd\" effect "
-"when B<FUTEX_WAKE> is used and all processes woken up need to acquire "
-"another futex.  This call wakes up I<val> processes, and requeues all other "
-"waiters on the futex at address I<uaddr2>.  The arguments I<timeout> and "
-"I<val3> are ignored."
-msgstr ""
-"この操作は、 B<FUTEX_WAKE> が使われていて、かつ wake されている全てのプロセス"
-"が 他の futex を取得する必要がある場合に、 「獣の群れの暴走 (thundering "
-"herd)」効果を避けるために導入された。 この呼び出しは I<val> 個のプロセスを "
-"wake し、アドレス I<uaddr2> で futex を待っている他の全てのプロセスを再度"
-"キューにいれる。 引き数 I<timeout> と I<val3> は無視される。"
+msgid "This operation was introduced in order to avoid a \"thundering herd\" effect when B<FUTEX_WAKE> is used and all processes woken up need to acquire another futex.  This call wakes up I<val> processes, and requeues all other waiters on the futex at address I<uaddr2>.  The arguments I<timeout> and I<val3> are ignored."
+msgstr "この操作は、 B<FUTEX_WAKE> が使われていて、かつ wake されている全てのプロセスが 他の futex を取得する必要がある場合に、 「獣の群れの暴走 (thundering herd)」効果を避けるために導入された。 この呼び出しは I<val> 個のプロセスを wake し、アドレス I<uaddr2> で futex を待っている他の全てのプロセスを再度キューにいれる。 引き数 I<timeout> と I<val3> は無視される。"
 
 #. type: TP
 #: build/C/man2/futex.2:198
@@ -700,37 +545,18 @@ msgstr "B<FUTEX_CMP_REQUEUE> (Linux 2.6.7 以降)"
 
 #. type: Plain text
 #: build/C/man2/futex.2:216
-msgid ""
-"There was a race in the intended use of B<FUTEX_REQUEUE>, so "
-"B<FUTEX_CMP_REQUEUE> was introduced.  This is similar to B<FUTEX_REQUEUE>, "
-"but first checks whether the location I<uaddr> still contains the value "
-"I<val3>.  If not, the operation fails with the error B<EAGAIN>.  The "
-"argument I<timeout> is ignored."
-msgstr ""
-"故意に B<FUTEX_REQUEUE> を使う場合に競合が起こるため、 B<FUTEX_CMP_REQUEUE> "
-"が導入された。これは B<FUTEX_REQUEUE> と似ているが、場所 I<uaddr> に値 "
-"I<val3> がまだ保持されているかを最初にチェックする。 保持されていない場合、操"
-"作はエラー B<EAGAIN> で失敗する。引き数 I<timeout> は無視される。"
+msgid "There was a race in the intended use of B<FUTEX_REQUEUE>, so B<FUTEX_CMP_REQUEUE> was introduced.  This is similar to B<FUTEX_REQUEUE>, but first checks whether the location I<uaddr> still contains the value I<val3>.  If not, the operation fails with the error B<EAGAIN>.  The argument I<timeout> is ignored."
+msgstr "故意に B<FUTEX_REQUEUE> を使う場合に競合が起こるため、 B<FUTEX_CMP_REQUEUE> が導入された。これは B<FUTEX_REQUEUE> と似ているが、場所 I<uaddr> に値 I<val3> がまだ保持されているかを最初にチェックする。 保持されていない場合、操作はエラー B<EAGAIN> で失敗する。引き数 I<timeout> は無視される。"
 
 #. type: Plain text
 #: build/C/man2/futex.2:223
-msgid ""
-"In the event of an error, all operations return -1, and set I<errno> to "
-"indicate the error.  The return value on success depends on the operation, "
-"as described in the following list:"
-msgstr ""
-"エラーの場合、全ての操作で -1 が返り、 I<errno> がエラーの内容を示す値に設定"
-"される。成功時の返り値は操作によって異なり、以下のリストに書かれている通りで"
-"ある。"
+msgid "In the event of an error, all operations return -1, and set I<errno> to indicate the error.  The return value on success depends on the operation, as described in the following list:"
+msgstr "エラーの場合、全ての操作で -1 が返り、 I<errno> がエラーの内容を示す値に設定される。成功時の返り値は操作によって異なり、以下のリストに書かれている通りである。"
 
 #. type: Plain text
 #: build/C/man2/futex.2:229
-msgid ""
-"Returns 0 if the process was woken by a B<FUTEX_WAKE> call.  See ERRORS for "
-"the various possible error returns."
-msgstr ""
-"そのプロセスが B<FUTEX_WAKE> により wake された場合 0 を返す。発生する可能性"
-"があるエラーについては「エラー」の節を参照。"
+msgid "Returns 0 if the process was woken by a B<FUTEX_WAKE> call.  See ERRORS for the various possible error returns."
+msgstr "そのプロセスが B<FUTEX_WAKE> により wake された場合 0 を返す。発生する可能性があるエラーについては「エラー」の節を参照。"
 
 #. type: Plain text
 #: build/C/man2/futex.2:232 build/C/man2/futex.2:238 build/C/man2/futex.2:241
@@ -782,14 +608,8 @@ msgstr "B<EAGAIN>"
 
 #. type: Plain text
 #: build/C/man2/futex.2:256
-msgid ""
-"B<FUTEX_CMP_REQUEUE> detected that the value pointed to by I<uaddr> is not "
-"equal to the expected value I<val3>.  (This probably indicates a race; use "
-"the safe B<FUTEX_WAKE> now.)"
-msgstr ""
-"B<FUTEX_CMP_REQUEUE> で、I<uaddr> が指す値が期待値 I<val3> と異なる状況が検出"
-"された。 (これは競合を示しているかもしれない。この場合は安全な B<FUTEX_WAKE> "
-"を使うこと。)"
+msgid "B<FUTEX_CMP_REQUEUE> detected that the value pointed to by I<uaddr> is not equal to the expected value I<val3>.  (This probably indicates a race; use the safe B<FUTEX_WAKE> now.)"
+msgstr "B<FUTEX_CMP_REQUEUE> で、I<uaddr> が指す値が期待値 I<val3> と異なる状況が検出された。 (これは競合を示しているかもしれない。この場合は安全な B<FUTEX_WAKE> を使うこと。)"
 
 #. type: Plain text
 #: build/C/man2/futex.2:261
@@ -804,12 +624,8 @@ msgstr "B<EINTR>"
 
 #. type: Plain text
 #: build/C/man2/futex.2:268
-msgid ""
-"A B<FUTEX_WAIT> operation was interrupted by a signal (see B<signal>(7))  or "
-"a spurious wakeup."
-msgstr ""
-"B<FUTEX_WAIT> 操作がシグナル (B<signal>(7) 参照) もしくは偽の wakeup により中"
-"断された。"
+msgid "A B<FUTEX_WAIT> operation was interrupted by a signal (see B<signal>(7))  or a spurious wakeup."
+msgstr "B<FUTEX_WAIT> 操作がシグナル (B<signal>(7) 参照) もしくは偽の wakeup により中断された。"
 
 #. type: Plain text
 #: build/C/man2/futex.2:271
@@ -859,12 +675,8 @@ msgstr "B<EWOULDBLOCK>"
 
 #. type: Plain text
 #: build/C/man2/futex.2:293
-msgid ""
-"I<op> was B<FUTEX_WAIT> and the value pointed to by I<uaddr> was not equal "
-"to the expected value I<val> at the time of the call."
-msgstr ""
-"I<op> が B<FUTEX_WAIT> で、その呼び出しにおいて I<uaddr> が指す値が期待値 "
-"I<val> と異なっていた。"
+msgid "I<op> was B<FUTEX_WAIT> and the value pointed to by I<uaddr> was not equal to the expected value I<val> at the time of the call."
+msgstr "I<op> が B<FUTEX_WAIT> で、その呼び出しにおいて I<uaddr> が指す値が期待値 I<val> と異なっていた。"
 
 #. type: SH
 #: build/C/man2/futex.2:293 build/C/man2/get_robust_list.2:116
@@ -880,18 +692,8 @@ msgstr "バージョン"
 
 #. type: Plain text
 #: build/C/man2/futex.2:303
-msgid ""
-"Initial futex support was merged in Linux 2.5.7 but with different semantics "
-"from what was described above.  A 4-argument system call with the semantics "
-"described in this page was introduced in Linux 2.5.40.  In Linux 2.5.70, one "
-"argument was added.  In Linux 2.6.7, a sixth argument was added\\(emmessy, "
-"especially on the s390 architecture."
-msgstr ""
-"最初の futex 対応は Linux 2.5.7 で組み込まれたが、 上記のセマンティクスとは異"
-"なる。 4 つの引き数のここに書かれているセマンティクスを持つ システムコール"
-"は、Linux 2.5.40 で導入された。 Linux 2.5.70 では 1 つの引き数が追加された。 "
-"Linux 2.6.7 では 6 番目の引き数が追加された。 これは汚く、s390 アーキテクチャ"
-"上の特別のものである。"
+msgid "Initial futex support was merged in Linux 2.5.7 but with different semantics from what was described above.  A 4-argument system call with the semantics described in this page was introduced in Linux 2.5.40.  In Linux 2.5.70, one argument was added.  In Linux 2.6.7, a sixth argument was added\\(emmessy, especially on the s390 architecture."
+msgstr "最初の futex 対応は Linux 2.5.7 で組み込まれたが、 上記のセマンティクスとは異なる。 4 つの引き数のここに書かれているセマンティクスを持つ システムコールは、Linux 2.5.40 で導入された。 Linux 2.5.70 では 1 つの引き数が追加された。 Linux 2.6.7 では 6 番目の引き数が追加された。 これは汚く、s390 アーキテクチャ上の特別のものである。"
 
 #. type: Plain text
 #: build/C/man2/futex.2:305 build/C/man2/kexec_load.2:147
@@ -909,16 +711,8 @@ msgstr "このシステムコールは Linux 固有である。"
 #.  This page written by bert hubert.
 #. type: Plain text
 #: build/C/man2/futex.2:319
-msgid ""
-"To reiterate, bare futexes are not intended as an easy-to-use abstraction "
-"for end-users.  (There is no wrapper function for this system call in "
-"glibc.)  Implementors are expected to be assembly literate and to have read "
-"the sources of the futex user-space library referenced below."
-msgstr ""
-"繰り返すが、裸の futex はエンドユーザが容易に使うことのできる概念として 意図"
-"されたものではない (glibc にはこのシステムコールに対するラッパー関数はな"
-"い)。 実装者は、アセンブリ言語に慣れており、以下に挙げる futex ユーザ空間ライ"
-"ブラリの ソースを読み終えていることが要求される。"
+msgid "To reiterate, bare futexes are not intended as an easy-to-use abstraction for end-users.  (There is no wrapper function for this system call in glibc.)  Implementors are expected to be assembly literate and to have read the sources of the futex user-space library referenced below."
+msgstr "繰り返すが、裸の futex はエンドユーザが容易に使うことのできる概念として 意図されたものではない (glibc にはこのシステムコールに対するラッパー関数はない)。 実装者は、アセンブリ言語に慣れており、以下に挙げる futex ユーザ空間ライブラリの ソースを読み終えていることが要求される。"
 
 #. type: Plain text
 #: build/C/man2/futex.2:322
@@ -927,21 +721,13 @@ msgstr "B<restart_syscall>(2), B<futex>(7)"
 
 #. type: Plain text
 #: build/C/man2/futex.2:325
-msgid ""
-"I<Fuss, Futexes and Furwocks: Fast Userlevel Locking in Linux> (proceedings "
-"of the Ottawa Linux Symposium 2002), online at"
-msgstr ""
-"I<Fuss, Futexes and Furwocks: Fast Userlevel Locking in Linux> (proceedings "
-"of the Ottawa Linux Symposium 2002), online at"
+msgid "I<Fuss, Futexes and Furwocks: Fast Userlevel Locking in Linux> (proceedings of the Ottawa Linux Symposium 2002), online at"
+msgstr "I<Fuss, Futexes and Furwocks: Fast Userlevel Locking in Linux> (proceedings of the Ottawa Linux Symposium 2002), online at"
 
 #. type: Plain text
 #: build/C/man2/futex.2:328
-msgid ""
-"E<.UR http://kernel.org\\:/doc\\:/ols\\:/2002\\:/ols2002-pages-479-495.pdf> "
-"E<.UE>"
-msgstr ""
-"E<.UR http://kernel.org\\:/doc\\:/ols\\:/2002\\:/ols2002-pages-479-495.pdf> "
-"E<.UE>"
+msgid "E<.UR http://kernel.org\\:/doc\\:/ols\\:/2002\\:/ols2002-pages-479-495.pdf> E<.UE>"
+msgstr "E<.UR http://kernel.org\\:/doc\\:/ols\\:/2002\\:/ols2002-pages-479-495.pdf> E<.UE>"
 
 #. type: Plain text
 #: build/C/man2/futex.2:330
@@ -950,12 +736,8 @@ msgstr "futex の使用例ライブラリ, futex-*.tar.bz2"
 
 #. type: Plain text
 #: build/C/man2/futex.2:333
-msgid ""
-"E<.UR ftp://ftp.kernel.org\\:/pub\\:/linux\\:/kernel\\:/people\\:/rusty/> E<."
-"UE>"
-msgstr ""
-"E<.UR ftp://ftp.kernel.org\\:/pub\\:/linux\\:/kernel\\:/people\\:/rusty/> E<."
-"UE>"
+msgid "E<.UR ftp://ftp.kernel.org\\:/pub\\:/linux\\:/kernel\\:/people\\:/rusty/> E<.UE>"
+msgstr "E<.UR ftp://ftp.kernel.org\\:/pub\\:/linux\\:/kernel\\:/people\\:/rusty/> E<.UE>"
 
 #. type: TH
 #: build/C/man2/get_robust_list.2:29
@@ -965,10 +747,9 @@ msgstr "GET_ROBUST_LIST"
 
 #. type: TH
 #: build/C/man2/get_robust_list.2:29 build/C/man2/ptrace.2:46
-#, fuzzy, no-wrap
-#| msgid "2015-01-10"
+#, no-wrap
 msgid "2015-01-22"
-msgstr "2015-01-10"
+msgstr "2015-01-22"
 
 #. type: TH
 #: build/C/man2/get_robust_list.2:29
@@ -1005,70 +786,46 @@ msgstr ""
 #. type: Plain text
 #: build/C/man2/get_robust_list.2:45
 msgid "I<Note>: There are no glibc wrappers for these system calls; see NOTES."
-msgstr ""
-"I<注意>: これらのシステムコールには glibc ラッパー関数は存在しない。 「注意」"
-"の節を参照。"
+msgstr "I<注意>: これらのシステムコールには glibc ラッパー関数は存在しない。 「注意」の節を参照。"
 
 #. type: Plain text
 #: build/C/man2/get_robust_list.2:50
-msgid ""
-"The robust futex implementation needs to maintain per-thread lists of robust "
-"futexes which are unlocked when the thread exits.  These lists are managed "
-"in user space; the kernel is notified about only the location of the head of "
-"the list."
+msgid "The robust futex implementation needs to maintain per-thread lists of robust futexes which are unlocked when the thread exits.  These lists are managed in user space; the kernel is notified about only the location of the head of the list."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/get_robust_list.2:66
-msgid ""
-"The B<get_robust_list>()  system call returns the head of the robust futex "
-"list of the thread whose thread ID is specified in I<pid>.  If I<pid> is 0, "
-"the head of the list for the calling thread is returned.  The list head is "
-"stored in the location pointed to by I<head_ptr>.  The size of the object "
-"pointed to by I<**head_ptr> is stored in I<len_ptr>."
+msgid "The B<get_robust_list>()  system call returns the head of the robust futex list of the thread whose thread ID is specified in I<pid>.  If I<pid> is 0, the head of the list for the calling thread is returned.  The list head is stored in the location pointed to by I<head_ptr>.  The size of the object pointed to by I<**head_ptr> is stored in I<len_ptr>."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/get_robust_list.2:78
-msgid ""
-"The B<set_robust_list>()  system call requests the kernel to record the head "
-"of the list of robust futexes owned by the calling thread.  The I<head> "
-"argument is the list head to record.  The I<len> argument should be "
-"I<sizeof(*head)>."
+msgid "The B<set_robust_list>()  system call requests the kernel to record the head of the list of robust futexes owned by the calling thread.  The I<head> argument is the list head to record.  The I<len> argument should be I<sizeof(*head)>."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/get_robust_list.2:85
-msgid ""
-"The B<set_robust_list>()  and B<get_robust_list>()  system calls return zero "
-"when the operation is successful, an error code otherwise."
+msgid "The B<set_robust_list>()  and B<get_robust_list>()  system calls return zero when the operation is successful, an error code otherwise."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/get_robust_list.2:89
-msgid ""
-"The B<set_robust_list>()  system call can fail with the following error:"
+msgid "The B<set_robust_list>()  system call can fail with the following error:"
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/get_robust_list.2:95
-msgid ""
-"I<len> does not match the size of structure B<struct robust_list_head> "
-"expected by kernel."
+msgid "I<len> does not match the size of structure B<struct robust_list_head> expected by kernel."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/get_robust_list.2:99
-msgid ""
-"The B<get_robust_list>()  system call can fail with the following errors:"
+msgid "The B<get_robust_list>()  system call can fail with the following errors:"
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/get_robust_list.2:107
-msgid ""
-"The calling process does not have permission to see the robust futex list of "
-"the thread with the thread ID I<pid>, and does not have the "
-"B<CAP_SYS_PTRACE> capability."
+msgid "The calling process does not have permission to see the robust futex list of the thread with the thread ID I<pid>, and does not have the B<CAP_SYS_PTRACE> capability."
 msgstr ""
 
 #. type: TP
@@ -1086,34 +843,22 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/get_robust_list.2:116
-msgid ""
-"The head of the robust futex list can't be stored at the location I<head>."
+msgid "The head of the robust futex list can't be stored at the location I<head>."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/get_robust_list.2:118
-#, fuzzy
-#| msgid "The B<kexec_load>()  system call first appeared in Linux 2.6.13."
 msgid "These system calls were added in Linux 2.6.17."
-msgstr "B<kexec_load>() システムコールは Linux 2.6.13 で初めて登場した。"
+msgstr "これらのシステムコールは Linux 2.6.17 で追加された。"
 
 #. type: Plain text
 #: build/C/man2/get_robust_list.2:123
-msgid ""
-"These system calls are not needed by normal applications.  No support for "
-"them is provided in glibc.  In the unlikely event that you want to call them "
-"directly, use B<syscall>(2)."
-msgstr ""
-"通常のアプリケーションでは、これらのシステムコールは必要ではない。 glibc によ"
-"るサポートは提供されていない。おそらくないと思うが、このシステムコールを直接"
-"呼び出したい場合は B<syscall>(2) を使うこと。"
+msgid "These system calls are not needed by normal applications.  No support for them is provided in glibc.  In the unlikely event that you want to call them directly, use B<syscall>(2)."
+msgstr "通常のアプリケーションでは、これらのシステムコールは必要ではない。 glibc によるサポートは提供されていない。おそらくないと思うが、このシステムコールを直接呼び出したい場合は B<syscall>(2) を使うこと。"
 
 #. type: Plain text
 #: build/C/man2/get_robust_list.2:127
-msgid ""
-"A thread can have only one robust futex list; therefore applications that "
-"wish to use this functionality should use the robust mutexes provided by "
-"glibc."
+msgid "A thread can have only one robust futex list; therefore applications that wish to use this functionality should use the robust mutexes provided by glibc."
 msgstr ""
 
 #.  .BR pthread_mutexattr_setrobust_np (3)
@@ -1125,9 +870,7 @@ msgstr "B<futex>(2)"
 #.  http://lwn.net/Articles/172149/
 #. type: Plain text
 #: build/C/man2/get_robust_list.2:136
-msgid ""
-"I<Documentation/robust-futexes.txt> and I<Documentation/robust-futex-ABI."
-"txt> in the Linux kernel source tree"
+msgid "I<Documentation/robust-futexes.txt> and I<Documentation/robust-futex-ABI.txt> in the Linux kernel source tree"
 msgstr ""
 
 #. type: TH
@@ -1170,29 +913,17 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/getunwind.2:52
-msgid ""
-"The IA-64-specific B<getunwind>()  system call copies the kernel's call "
-"frame unwind data into the buffer pointed to by I<buf> and returns the size "
-"of the unwind data; this data describes the gate page (kernel code that is "
-"mapped into user space)."
+msgid "The IA-64-specific B<getunwind>()  system call copies the kernel's call frame unwind data into the buffer pointed to by I<buf> and returns the size of the unwind data; this data describes the gate page (kernel code that is mapped into user space)."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/getunwind.2:64
-msgid ""
-"The size of the buffer I<buf> is specified in I<buf_size>.  The data is "
-"copied only if I<buf_size> is greater than or equal to the size of the "
-"unwind data and I<buf> is not NULL; otherwise, no data is copied, and the "
-"call succeeds, returning the size that would be needed to store the unwind "
-"data."
+msgid "The size of the buffer I<buf> is specified in I<buf_size>.  The data is copied only if I<buf_size> is greater than or equal to the size of the unwind data and I<buf> is not NULL; otherwise, no data is copied, and the call succeeds, returning the size that would be needed to store the unwind data."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/getunwind.2:68
-msgid ""
-"The first part of the unwind data contains an unwind table.  The rest "
-"contains the associated unwind information, in no particular order.  The "
-"unwind table contains entries of the following form:"
+msgid "The first part of the unwind data contains an unwind table.  The rest contains the associated unwind information, in no particular order.  The unwind table contains entries of the following form:"
 msgstr ""
 
 #. type: Plain text
@@ -1206,26 +937,17 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/getunwind.2:81
-msgid ""
-"An entry whose I<start> value is zero indicates the end of the table.  For "
-"more information about the format, see the I<IA-64 Software Conventions and "
-"Runtime Architecture> manual."
+msgid "An entry whose I<start> value is zero indicates the end of the table.  For more information about the format, see the I<IA-64 Software Conventions and Runtime Architecture> manual."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/getunwind.2:88
-msgid ""
-"On success, B<getunwind>()  returns the size of the unwind data.  On error, "
-"-1 is returned and I<errno> is set to indicate the error."
-msgstr ""
-"成功すると、 B<getunwind> は unwind されたデータのサイズを返す。 エラーの場"
-"合、 -1 が返り、 I<errno> にエラーを示す値が設定される。"
+msgid "On success, B<getunwind>()  returns the size of the unwind data.  On error, -1 is returned and I<errno> is set to indicate the error."
+msgstr "成功すると、 B<getunwind> は unwind されたデータのサイズを返す。 エラーの場合、 -1 が返り、 I<errno> にエラーを示す値が設定される。"
 
 #. type: Plain text
 #: build/C/man2/getunwind.2:94
-msgid ""
-"B<getunwind>()  fails with the error B<EFAULT> if the unwind info can't be "
-"stored in the space specified by I<buf>."
+msgid "B<getunwind>()  fails with the error B<EFAULT> if the unwind info can't be stored in the space specified by I<buf>."
 msgstr ""
 
 #. type: Plain text
@@ -1235,27 +957,18 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/getunwind.2:99
-msgid ""
-"This system call is Linux-specific, and is available only on the IA-64 "
-"architecture."
+msgid "This system call is Linux-specific, and is available only on the IA-64 architecture."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/getunwind.2:107
-msgid ""
-"This system call has been deprecated.  The modern way to obtain the kernel's "
-"unwind data is via the gate DSO.  The address of the ELF header for this DSO "
-"is passed to user level via B<AT_SYSINFO_EHDR> (see B<getauxval>(3))."
+msgid "This system call has been deprecated.  The modern way to obtain the kernel's unwind data is via the gate DSO.  The address of the ELF header for this DSO is passed to user level via B<AT_SYSINFO_EHDR> (see B<getauxval>(3))."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/getunwind.2:111
-msgid ""
-"Glibc does not provide a wrapper for this system call; in the unlikely event "
-"that you want to call it, use B<syscall>(2)."
-msgstr ""
-"glibc はこのシステムコールに対するラッパー関数を提供していない。おそらくない"
-"と思うが、このシステムコールを呼び出したい場合は B<syscall>(2) を使うこと。"
+msgid "Glibc does not provide a wrapper for this system call; in the unlikely event that you want to call it, use B<syscall>(2)."
+msgstr "glibc はこのシステムコールに対するラッパー関数を提供していない。おそらくないと思うが、このシステムコールを呼び出したい場合は B<syscall>(2) を使うこと。"
 
 #. type: Plain text
 #: build/C/man2/getunwind.2:113
@@ -1286,12 +999,8 @@ msgstr "B<#include E<lt>linux/kexec.hE<gt>>"
 
 #. type: Plain text
 #: build/C/man2/kexec_load.2:33
-msgid ""
-"B<long kexec_load(unsigned long >I<entry>B<, unsigned long >I<nr_segments>B<,"
-">"
-msgstr ""
-"B<long kexec_load(unsigned long >I<entry>B<, unsigned long >I<nr_segments>B<,"
-">"
+msgid "B<long kexec_load(unsigned long >I<entry>B<, unsigned long >I<nr_segments>B<,>"
+msgstr "B<long kexec_load(unsigned long >I<entry>B<, unsigned long >I<nr_segments>B<,>"
 
 #. type: Plain text
 #: build/C/man2/kexec_load.2:36
@@ -1300,21 +1009,15 @@ msgstr "B< struct kexec_segment *>I<segments>B<, unsigned long >I<flags>B<);>"
 
 #. type: Plain text
 #: build/C/man2/kexec_load.2:44
-msgid ""
-"The B<kexec_load>()  system call loads a new kernel that can be executed "
-"later by B<reboot>(2)."
+msgid "The B<kexec_load>()  system call loads a new kernel that can be executed later by B<reboot>(2)."
 msgstr ""
 "B<kexec_load>() システムコールは、新しいカーネルをロードし、\n"
 "その後の B<reboot>(2) で実行できるようにする。"
 
 #. type: Plain text
 #: build/C/man2/kexec_load.2:50
-msgid ""
-"The I<flags> argument is a bit mask that controls the operation of the "
-"call.  The following values can be specified in I<flags>:"
-msgstr ""
-"I<flags> 引き数は、システムコールの呼び出しの動作を制御するマスクビットであ"
-"る。 I<flags> には以下の値を指定できる。"
+msgid "The I<flags> argument is a bit mask that controls the operation of the call.  The following values can be specified in I<flags>:"
+msgstr "I<flags> 引き数は、システムコールの呼び出しの動作を制御するマスクビットである。 I<flags> には以下の値を指定できる。"
 
 #. type: TP
 #: build/C/man2/kexec_load.2:50
@@ -1336,11 +1039,7 @@ msgstr "B<KEXEC_PRESERVE_CONTEXT> (Linux 2.6.27 以降)"
 
 #. type: Plain text
 #: build/C/man2/kexec_load.2:64
-msgid ""
-"Preserve the system hardware and software states before executing the new "
-"kernel.  This could be used for system suspend.  This flag is available only "
-"if the kernel was configured with B<CONFIG_KEXEC_JUMP>, and is effective "
-"only if I<nr_segments> is greater than 0."
+msgid "Preserve the system hardware and software states before executing the new kernel.  This could be used for system suspend.  This flag is available only if the kernel was configured with B<CONFIG_KEXEC_JUMP>, and is effective only if I<nr_segments> is greater than 0."
 msgstr ""
 "新しいカーネルを実行する前に、\n"
 "システムのハードウェアとソフトウェアの状態を保存する。\n"
@@ -1350,21 +1049,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/kexec_load.2:85
-msgid ""
-"The high-order bits (corresponding to the mask 0xffff0000) of I<flags> "
-"contain the architecture of the to-be-executed kernel.  Specify (OR) the "
-"constant B<KEXEC_ARCH_DEFAULT> to use the current architecture, or one of "
-"the following architecture constants B<KEXEC_ARCH_386>, B<KEXEC_ARCH_68K>, "
-"B<KEXEC_ARCH_X86_64>, B<KEXEC_ARCH_PPC>, B<KEXEC_ARCH_PPC64>, "
-"B<KEXEC_ARCH_IA_64>, B<KEXEC_ARCH_ARM>, B<KEXEC_ARCH_S390>, "
-"B<KEXEC_ARCH_SH>, B<KEXEC_ARCH_MIPS>, and B<KEXEC_ARCH_MIPS_LE>.  The "
-"architecture must be executable on the CPU of the system."
+msgid "The high-order bits (corresponding to the mask 0xffff0000) of I<flags> contain the architecture of the to-be-executed kernel.  Specify (OR) the constant B<KEXEC_ARCH_DEFAULT> to use the current architecture, or one of the following architecture constants B<KEXEC_ARCH_386>, B<KEXEC_ARCH_68K>, B<KEXEC_ARCH_X86_64>, B<KEXEC_ARCH_PPC>, B<KEXEC_ARCH_PPC64>, B<KEXEC_ARCH_IA_64>, B<KEXEC_ARCH_ARM>, B<KEXEC_ARCH_S390>, B<KEXEC_ARCH_SH>, B<KEXEC_ARCH_MIPS>, and B<KEXEC_ARCH_MIPS_LE>.  The architecture must be executable on the CPU of the system."
 msgstr ""
 "I<flags> の上位ビット (マスク 0xffff0000 に対応) には、\n"
 "実行されるカーネルのアーキテクチャが入る。\n"
 "現在のアーキテクチャを使うことを意味する定数 B<KEXEC_ARCH_DEFAULT> か、\n"
-"アーキテクチャ定数 B<KEXEC_ARCH_386>, B<KEXEC_ARCH_68K>, "
-"B<KEXEC_ARCH_X86_64>,\n"
+"アーキテクチャ定数 B<KEXEC_ARCH_386>, B<KEXEC_ARCH_68K>, B<KEXEC_ARCH_X86_64>,\n"
 "B<KEXEC_ARCH_PPC>, B<KEXEC_ARCH_PPC64>, B<KEXEC_ARCH_IA_64>,\n"
 "B<KEXEC_ARCH_ARM>, B<KEXEC_ARCH_S390>, B<KEXEC_ARCH_SH>,\n"
 "B<KEXEC_ARCH_MIPS>, B<KEXEC_ARCH_MIPS_LE> の\n"
@@ -1373,18 +1063,8 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/kexec_load.2:100
-msgid ""
-"The I<entry> argument is the physical entry address in the kernel image.  "
-"The I<nr_segments> argument is the number of segments pointed to by the "
-"I<segments> pointer; the kernel imposes an (arbitrary) limit of 16 on the "
-"number of segments.  The I<segments> argument is an array of "
-"I<kexec_segment> structures which define the kernel layout:"
-msgstr ""
-"I<entry> 引き数は、カーネルイメージの物理エントリーアドレスである。 "
-"I<nr_segments> 引き数は、 I<segments> ポインタが指すセグメントの数である。 な"
-"お、セグメント数には、カーネルにより 16 という (強制的な) 上限が課される。 "
-"I<segments> 引き数は I<kexec_segment> 構造体の配列で、 この構造体によりカーネ"
-"ルの配置が定義される。"
+msgid "The I<entry> argument is the physical entry address in the kernel image.  The I<nr_segments> argument is the number of segments pointed to by the I<segments> pointer; the kernel imposes an (arbitrary) limit of 16 on the number of segments.  The I<segments> argument is an array of I<kexec_segment> structures which define the kernel layout:"
+msgstr "I<entry> 引き数は、カーネルイメージの物理エントリーアドレスである。 I<nr_segments> 引き数は、 I<segments> ポインタが指すセグメントの数である。 なお、セグメント数には、カーネルにより 16 という (強制的な) 上限が課される。 I<segments> 引き数は I<kexec_segment> 構造体の配列で、 この構造体によりカーネルの配置が定義される。"
 
 #. type: Plain text
 #: build/C/man2/kexec_load.2:109
@@ -1408,18 +1088,14 @@ msgstr ""
 #.  is copied from the calling process into previously reserved memory.
 #. type: Plain text
 #: build/C/man2/kexec_load.2:117
-msgid ""
-"The kernel image defined by I<segments> is copied from the calling process "
-"into previously reserved memory."
+msgid "The kernel image defined by I<segments> is copied from the calling process into previously reserved memory."
 msgstr ""
 "I<segments> で定義されたカーネルイメージは、\n"
 "呼び出したプロセスから予約済みメモリにコピーされる。"
 
 #. type: Plain text
 #: build/C/man2/kexec_load.2:124
-msgid ""
-"On success, B<kexec_load>()  returns 0.  On error, -1 is returned and "
-"I<errno> is set to indicate the error."
+msgid "On success, B<kexec_load>()  returns 0.  On error, -1 is returned and I<errno> is set to indicate the error."
 msgstr ""
 "成功すると、 B<kexec_load> は 0 を返す。\n"
 "エラーの場合、 -1 が返り、 I<errno> にエラーを示す値が設定される。"
@@ -1433,9 +1109,7 @@ msgstr "B<EBUSY>"
 
 #. type: Plain text
 #: build/C/man2/kexec_load.2:129
-msgid ""
-"Another crash kernel is already being loaded or a crash kernel is already in "
-"use."
+msgid "Another crash kernel is already being loaded or a crash kernel is already in use."
 msgstr ""
 "別のクラッシュカーネルがすでにロードされているか、\n"
 "クラッシュカーネルがすでに使用されている。"
@@ -1458,9 +1132,7 @@ msgstr "B<kexec_load>() システムコールは Linux 2.6.13 で初めて登場
 
 #. type: Plain text
 #: build/C/man2/kexec_load.2:152
-msgid ""
-"Currently, there is no glibc support for B<kexec_load>().  Call it using "
-"B<syscall>(2)."
+msgid "Currently, there is no glibc support for B<kexec_load>().  Call it using B<syscall>(2)."
 msgstr ""
 "現在のところ、 B<kexec_load>() は glibc ではサポートされていない。\n"
 "B<syscall>(2) を使って呼び出すこと。"
@@ -1469,21 +1141,15 @@ msgstr ""
 #.  Check if it got accepted later.
 #. type: Plain text
 #: build/C/man2/kexec_load.2:159
-msgid ""
-"The required constants are in the Linux kernel source file I<linux/kexec.h>, "
-"which is not currently exported to glibc.  Therefore, these constants must "
-"be defined manually."
+msgid "The required constants are in the Linux kernel source file I<linux/kexec.h>, which is not currently exported to glibc.  Therefore, these constants must be defined manually."
 msgstr ""
-"必要な定数は Linux カーネルのソースファイル I<linux/kexec.h> で定義されてい"
-"る\n"
+"必要な定数は Linux カーネルのソースファイル I<linux/kexec.h> で定義されている\n"
 "が、現在のところ glibc には公開されていない。\n"
 "そのため、これらの定数は手動で定義しなければならない。"
 
 #. type: Plain text
 #: build/C/man2/kexec_load.2:162
-msgid ""
-"This system call is available only if the kernel was configured with "
-"B<CONFIG_KEXEC>."
+msgid "This system call is available only if the kernel was configured with B<CONFIG_KEXEC>."
 msgstr ""
 "このシステムコールは、カーネルの設定で B<CONFIG_KEXEC> が有効になって\n"
 "いる場合にのみ利用できる。"
@@ -1512,44 +1178,23 @@ msgstr "lookup_dcookie - ディレクトリ・エントリのパス名を返す"
 
 #. type: Plain text
 #: build/C/man2/lookup_dcookie.2:32
-msgid ""
-"B<int lookup_dcookie(u64 >I<cookie>B<, char *>I<buffer>B<, size_t >I<len>B<);"
-">"
-msgstr ""
-"B<int lookup_dcookie(u64 >I<cookie>B<, char *>I<buffer>B<, size_t >I<len>B<);"
-">"
+msgid "B<int lookup_dcookie(u64 >I<cookie>B<, char *>I<buffer>B<, size_t >I<len>B<);>"
+msgstr "B<int lookup_dcookie(u64 >I<cookie>B<, char *>I<buffer>B<, size_t >I<len>B<);>"
 
 #. type: Plain text
 #: build/C/man2/lookup_dcookie.2:38
-msgid ""
-"Look up the full path of the directory entry specified by the value "
-"I<cookie>.  The cookie is an opaque identifier uniquely identifying a "
-"particular directory entry.  The buffer given is filled in with the full "
-"path of the directory entry."
-msgstr ""
-"I<cookie> 値で指定されたディレクトリ・エントリのフルパス名を検索する。 "
-"cookie は、個々のディレクトリ・エントリを区別する内部識別子 (opaque "
-"identifier) である。引き数で指定されたバッファに、ディレクトリ・エントリの フ"
-"ルパス名が格納される。"
+msgid "Look up the full path of the directory entry specified by the value I<cookie>.  The cookie is an opaque identifier uniquely identifying a particular directory entry.  The buffer given is filled in with the full path of the directory entry."
+msgstr "I<cookie> 値で指定されたディレクトリ・エントリのフルパス名を検索する。 cookie は、個々のディレクトリ・エントリを区別する内部識別子 (opaque identifier) である。引き数で指定されたバッファに、ディレクトリ・エントリの フルパス名が格納される。"
 
 #. type: Plain text
 #: build/C/man2/lookup_dcookie.2:43
-msgid ""
-"For B<lookup_dcookie>()  to return successfully, the kernel must still hold "
-"a cookie reference to the directory entry."
-msgstr ""
-"B<lookup_dcookie>()  が正常に値を返すためには、カーネルがディレクトリ・エント"
-"リへの cookie 参照を 保持していなければならない。"
+msgid "For B<lookup_dcookie>()  to return successfully, the kernel must still hold a cookie reference to the directory entry."
+msgstr "B<lookup_dcookie>()  が正常に値を返すためには、カーネルがディレクトリ・エントリへの cookie 参照を 保持していなければならない。"
 
 #. type: Plain text
 #: build/C/man2/lookup_dcookie.2:50
-msgid ""
-"On success, B<lookup_dcookie>()  returns the length of the path string "
-"copied into the buffer.  On error, -1 is returned, and I<errno> is set "
-"appropriately."
-msgstr ""
-"成功した場合、 B<lookup_dcookie>()  はバッファにコピーしたパス文字列の長さを"
-"返す。 エラーの場合は -1 を返し、 I<errno> に適切な値を設定する。"
+msgid "On success, B<lookup_dcookie>()  returns the length of the path string copied into the buffer.  On error, -1 is returned, and I<errno> is set appropriately."
+msgstr "成功した場合、 B<lookup_dcookie>()  はバッファにコピーしたパス文字列の長さを返す。 エラーの場合は -1 を返し、 I<errno> に適切な値を設定する。"
 
 #. type: Plain text
 #: build/C/man2/lookup_dcookie.2:54
@@ -1558,13 +1203,8 @@ msgstr "バッファが有効でなかった。"
 
 #. type: Plain text
 #: build/C/man2/lookup_dcookie.2:58
-msgid ""
-"The kernel has no registered cookie/directory entry mappings at the time of "
-"lookup, or the cookie does not refer to a valid directory entry."
-msgstr ""
-"検索が行われた時、cookie とディレクトリ・エントリのマッピングがカーネルに 登"
-"録されていなかったか、または cookie が有効なディレクトリ・エントリを 参照して"
-"いない。"
+msgid "The kernel has no registered cookie/directory entry mappings at the time of lookup, or the cookie does not refer to a valid directory entry."
+msgstr "検索が行われた時、cookie とディレクトリ・エントリのマッピングがカーネルに 登録されていなかったか、または cookie が有効なディレクトリ・エントリを 参照していない。"
 
 #. type: TP
 #: build/C/man2/lookup_dcookie.2:58
@@ -1587,21 +1227,13 @@ msgstr "B<ENOMEM>"
 
 #. type: Plain text
 #: build/C/man2/lookup_dcookie.2:65
-msgid ""
-"The kernel could not allocate memory for the temporary buffer holding the "
-"path."
-msgstr ""
-"カーネルが、パス名を保持する一時バッファ用のメモリを割り当てることが できな"
-"かった。"
+msgid "The kernel could not allocate memory for the temporary buffer holding the path."
+msgstr "カーネルが、パス名を保持する一時バッファ用のメモリを割り当てることが できなかった。"
 
 #. type: Plain text
 #: build/C/man2/lookup_dcookie.2:70
-msgid ""
-"The process does not have the capability B<CAP_SYS_ADMIN> required to look "
-"up cookie values."
-msgstr ""
-"プロセスが cookie 値を検索するのに必要なケーパビリティ B<CAP_SYS_ADMIN> を"
-"持っていない。"
+msgid "The process does not have the capability B<CAP_SYS_ADMIN> required to look up cookie values."
+msgstr "プロセスが cookie 値を検索するのに必要なケーパビリティ B<CAP_SYS_ADMIN> を持っていない。"
 
 #. type: TP
 #: build/C/man2/lookup_dcookie.2:70 build/C/man2/quotactl.2:474
@@ -1611,20 +1243,13 @@ msgstr "B<ERANGE>"
 
 #. type: Plain text
 #: build/C/man2/lookup_dcookie.2:73
-msgid ""
-"The buffer was not large enough to hold the path of the directory entry."
-msgstr ""
-"バッファが、ディレクトリ・エントリのパス名を収容するのに 十分な大きさではな"
-"かった。"
+msgid "The buffer was not large enough to hold the path of the directory entry."
+msgstr "バッファが、ディレクトリ・エントリのパス名を収容するのに 十分な大きさではなかった。"
 
 #. type: Plain text
 #: build/C/man2/lookup_dcookie.2:78
-msgid ""
-"Available since Linux 2.5.43.  The B<ENAMETOOLONG> error return was added in "
-"2.5.70."
-msgstr ""
-"Linux 2.5.43 以降で利用できる。 エラー B<ENAMETOOLONG> を返す仕様は 2.5.70 で"
-"追加された。"
+msgid "Available since Linux 2.5.43.  The B<ENAMETOOLONG> error return was added in 2.5.70."
+msgstr "Linux 2.5.43 以降で利用できる。 エラー B<ENAMETOOLONG> を返す仕様は 2.5.70 で追加された。"
 
 #. type: Plain text
 #: build/C/man2/lookup_dcookie.2:81
@@ -1633,22 +1258,13 @@ msgstr "B<lookup_dcookie>()  は Linux 独自の関数である。"
 
 #. type: Plain text
 #: build/C/man2/lookup_dcookie.2:85
-msgid ""
-"B<lookup_dcookie>()  is a special-purpose system call, currently used only "
-"by the oprofile profiler.  It relies on a kernel driver to register cookies "
-"for directory entries."
-msgstr ""
-"B<lookup_dcookie>()  は特殊な用途に使われるシステムコールで、現在のところ "
-"oprofile profiler で 使われているだけである。"
+msgid "B<lookup_dcookie>()  is a special-purpose system call, currently used only by the oprofile profiler.  It relies on a kernel driver to register cookies for directory entries."
+msgstr "B<lookup_dcookie>()  は特殊な用途に使われるシステムコールで、現在のところ oprofile profiler で 使われているだけである。"
 
 #. type: Plain text
 #: build/C/man2/lookup_dcookie.2:88
-msgid ""
-"The path returned may be suffixed by the string \" (deleted)\" if the "
-"directory entry has been removed."
-msgstr ""
-"指定されたディレクトリ・エントリが削除されていた場合、返されるパス名の最後に "
-"\" (deleted)\" という文字列が付加されることがある。"
+msgid "The path returned may be suffixed by the string \" (deleted)\" if the directory entry has been removed."
+msgstr "指定されたディレクトリ・エントリが削除されていた場合、返されるパス名の最後に \" (deleted)\" という文字列が付加されることがある。"
 
 #. type: TH
 #: build/C/man2/modify_ldt.2:24
@@ -1681,27 +1297,13 @@ msgstr "B<int modify_ldt(int >I<func>B<, void *>I<ptr>B<, unsigned long >I<bytec
 
 #. type: Plain text
 #: build/C/man2/modify_ldt.2:41
-msgid ""
-"B<modify_ldt>()  reads or writes the local descriptor table (ldt) for a "
-"process.  The ldt is a per-process memory management table used by the i386 "
-"processor.  For more information on this table, see an Intel 386 processor "
-"handbook."
-msgstr ""
-"B<modify_ldt>()  はプロセスのローカル・ディスクリプタ・テーブル (local "
-"descriptor table; ldt)  を読み書きする。 ldt は i386 プロセッサで使用されるプ"
-"ロセスごとのメモリ管理テーブルである。 このテーブルに関してのより詳しい情報"
-"は Intel 386 processor handbook を 参照すること。"
+msgid "B<modify_ldt>()  reads or writes the local descriptor table (ldt) for a process.  The ldt is a per-process memory management table used by the i386 processor.  For more information on this table, see an Intel 386 processor handbook."
+msgstr "B<modify_ldt>()  はプロセスのローカル・ディスクリプタ・テーブル (local descriptor table; ldt)  を読み書きする。 ldt は i386 プロセッサで使用されるプロセスごとのメモリ管理テーブルである。 このテーブルに関してのより詳しい情報は Intel 386 processor handbook を 参照すること。"
 
 #. type: Plain text
 #: build/C/man2/modify_ldt.2:51
-msgid ""
-"When I<func> is 0, B<modify_ldt>()  reads the ldt into the memory pointed to "
-"by I<ptr>.  The number of bytes read is the smaller of I<bytecount> and the "
-"actual size of the ldt."
-msgstr ""
-"I<func> が 0 ならば、 B<modify_ldt>()  は ldt を I<ptr> が指しているメモリに"
-"読み込む。 読み込むバイト数は実際の ldt のサイズか I<bytecount> より小さい方"
-"である。"
+msgid "When I<func> is 0, B<modify_ldt>()  reads the ldt into the memory pointed to by I<ptr>.  The number of bytes read is the smaller of I<bytecount> and the actual size of the ldt."
+msgstr "I<func> が 0 ならば、 B<modify_ldt>()  は ldt を I<ptr> が指しているメモリに読み込む。 読み込むバイト数は実際の ldt のサイズか I<bytecount> より小さい方である。"
 
 #.  FIXME Should this page say something about func == 2 and func == 0x11?
 #.  In Linux 2.4, func == 2 returned "the default ldt"
@@ -1709,20 +1311,13 @@ msgstr ""
 #.  Linux 2.4 and 2.6 implement an operation for func == 0x11
 #. type: Plain text
 #: build/C/man2/modify_ldt.2:69
-msgid ""
-"When I<func> is 1, B<modify_ldt>()  modifies one ldt entry.  I<ptr> points "
-"to a I<user_desc> structure and I<bytecount> must equal the size of this "
-"structure."
-msgstr ""
-"I<func> が 1 ならば、 B<modify_ldt>()  は ldt エントリの一つを変更する。 "
-"I<ptr> は I<user_desc> 構造体を指し、 I<bytecount> はこの構造体の大きさに等し"
-"くなければならない。"
+msgid "When I<func> is 1, B<modify_ldt>()  modifies one ldt entry.  I<ptr> points to a I<user_desc> structure and I<bytecount> must equal the size of this structure."
+msgstr "I<func> が 1 ならば、 B<modify_ldt>()  は ldt エントリの一つを変更する。 I<ptr> は I<user_desc> 構造体を指し、 I<bytecount> はこの構造体の大きさに等しくなければならない。"
 
 #. type: Plain text
 #: build/C/man2/modify_ldt.2:73
 msgid "The I<user_desc> structure is defined in I<E<lt>asm/ldt.hE<gt>> as:"
-msgstr ""
-"I<user_desc> 構造体は I<E<lt>asm/ldt.hE<gt>> で以下のように定義されている:"
+msgstr "I<user_desc> 構造体は I<E<lt>asm/ldt.hE<gt>> で以下のように定義されている:"
 
 #. type: Plain text
 #: build/C/man2/modify_ldt.2:87
@@ -1761,19 +1356,12 @@ msgstr ""
 #. type: Plain text
 #: build/C/man2/modify_ldt.2:98
 msgid "In Linux 2.4 and earlier, this structure was named I<modify_ldt_ldt_s>."
-msgstr ""
-"Linux 2.4 以前では、この構造体は I<modify_ldt_ldt_s> という名前であった。"
+msgstr "Linux 2.4 以前では、この構造体は I<modify_ldt_ldt_s> という名前であった。"
 
 #. type: Plain text
 #: build/C/man2/modify_ldt.2:108
-msgid ""
-"On success, B<modify_ldt>()  returns either the actual number of bytes read "
-"(for reading)  or 0 (for writing).  On failure, B<modify_ldt>()  returns -1 "
-"and sets I<errno> to indicate the error."
-msgstr ""
-"成功した場合は、 B<modify_ldt>()  は (読み込みの場合は) 実際に読み込んだバイ"
-"ト数、 または (書き込みの場合は) 0 を返す。 失敗した場合は B<modify_ldt>()  "
-"は -1 を返し、 I<errno> をエラーを示す値に設定する。"
+msgid "On success, B<modify_ldt>()  returns either the actual number of bytes read (for reading)  or 0 (for writing).  On failure, B<modify_ldt>()  returns -1 and sets I<errno> to indicate the error."
+msgstr "成功した場合は、 B<modify_ldt>()  は (読み込みの場合は) 実際に読み込んだバイト数、 または (書き込みの場合は) 0 を返す。 失敗した場合は B<modify_ldt>()  は -1 を返し、 I<errno> をエラーを示す値に設定する。"
 
 #. type: Plain text
 #: build/C/man2/modify_ldt.2:113
@@ -1782,14 +1370,8 @@ msgstr "I<ptr> がアドレス空間の外を指している。"
 
 #. type: Plain text
 #: build/C/man2/modify_ldt.2:126
-msgid ""
-"I<ptr> is 0, or I<func> is 1 and I<bytecount> is not equal to the size of "
-"the structure I<modify_ldt_ldt_s>, or I<func> is 1 and the new ldt entry has "
-"invalid values."
-msgstr ""
-"I<ptr> が 0 である、 または I<func> が 1 で I<bytecount> が "
-"I<modify_ldt_ldt_s> 構造体のサイズと等しくないか、 I<func> が 1 で新しい ldt "
-"エントリが無効な値である。"
+msgid "I<ptr> is 0, or I<func> is 1 and I<bytecount> is not equal to the size of the structure I<modify_ldt_ldt_s>, or I<func> is 1 and the new ldt entry has invalid values."
+msgstr "I<ptr> が 0 である、 または I<func> が 1 で I<bytecount> が I<modify_ldt_ldt_s> 構造体のサイズと等しくないか、 I<func> が 1 で新しい ldt エントリが無効な値である。"
 
 #. type: Plain text
 #: build/C/man2/modify_ldt.2:130
@@ -1798,22 +1380,14 @@ msgstr "I<func> が 0 でも 1 でもない。"
 
 #. type: Plain text
 #: build/C/man2/modify_ldt.2:133
-msgid ""
-"This call is Linux-specific and should not be used in programs intended to "
-"be portable."
-msgstr ""
-"このコールは Linux 特有であり、移植を意図したプログラムでは 使用してはいけな"
-"い。"
+msgid "This call is Linux-specific and should not be used in programs intended to be portable."
+msgstr "このコールは Linux 特有であり、移植を意図したプログラムでは 使用してはいけない。"
 
 #. type: Plain text
 #: build/C/man2/modify_ldt.2:136 build/C/man2/perfmonctl.2:205
 #: build/C/man2/pivot_root.2:134
-msgid ""
-"Glibc does not provide a wrapper for this system call; call it using "
-"B<syscall>(2)."
-msgstr ""
-"glibc はこのシステムコールに対するラッパー関数を提供していない。 "
-"B<syscall>(2)  を使って呼び出すこと。"
+msgid "Glibc does not provide a wrapper for this system call; call it using B<syscall>(2)."
+msgstr "glibc はこのシステムコールに対するラッパー関数を提供していない。 B<syscall>(2)  を使って呼び出すこと。"
 
 #. type: Plain text
 #: build/C/man2/modify_ldt.2:138
@@ -1933,12 +1507,8 @@ msgstr ""
 #. type: Plain text
 #: build/C/man2/nfsservctl.2:58 build/C/man2/pivot_root.2:105
 #: build/C/man2/vm86.2:59
-msgid ""
-"On success, zero is returned.  On error, -1 is returned, and I<errno> is set "
-"appropriately."
-msgstr ""
-"成功した場合は 0 が返される。エラーの場合は -1 が返され、 I<errno> が適切に設"
-"定される。"
+msgid "On success, zero is returned.  On error, -1 is returned, and I<errno> is set appropriately."
+msgstr "成功した場合は 0 が返される。エラーの場合は -1 が返され、 I<errno> が適切に設定される。"
 
 #. type: Plain text
 #: build/C/man2/nfsservctl.2:60
@@ -1959,12 +1529,8 @@ msgstr "2012-12-31"
 
 #. type: Plain text
 #: build/C/man2/outb.2:31
-msgid ""
-"outb, outw, outl, outsb, outsw, outsl, inb, inw, inl, insb, insw, insl, "
-"outb_p, outw_p, outl_p, inb_p, inw_p, inl_p - port I/O"
-msgstr ""
-"outb, outw, outl, outsb, outsw, outsl, inb, inw, inl, insb, insw, insl, "
-"outb_p, outw_p, outl_p, inb_p, inw_p, inl_p - ポート入出力"
+msgid "outb, outw, outl, outsb, outsw, outsl, inb, inw, inl, insb, insw, insl, outb_p, outw_p, outl_p, inb_p, inw_p, inl_p - port I/O"
+msgstr "outb, outw, outl, outsb, outsw, outsl, inb, inw, inl, insb, insw, insl, outb_p, outw_p, outl_p, inb_p, inw_p, inl_p - ポート入出力"
 
 #. type: Plain text
 #: build/C/man2/outb.2:34
@@ -2040,63 +1606,31 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/outb.2:67
-msgid ""
-"This family of functions is used to do low-level port input and output.  The "
-"out* functions do port output, the in* functions do port input; the b-suffix "
-"functions are byte-width and the w-suffix functions word-width; the _p-"
-"suffix functions pause until the I/O completes."
-msgstr ""
-"この一連の関数はポートに対する低レベルの入出力に使用する。 out* 関数はポート"
-"出力、in* 関数はポート入力を行う。 語尾に b がついている関数はバイト単位、w "
-"がついている関数はワード単位である。 _p がついている関数は I/O が終了するまで"
-"待つ。"
+msgid "This family of functions is used to do low-level port input and output.  The out* functions do port output, the in* functions do port input; the b-suffix functions are byte-width and the w-suffix functions word-width; the _p-suffix functions pause until the I/O completes."
+msgstr "この一連の関数はポートに対する低レベルの入出力に使用する。 out* 関数はポート出力、in* 関数はポート入力を行う。 語尾に b がついている関数はバイト単位、w がついている関数はワード単位である。 _p がついている関数は I/O が終了するまで待つ。"
 
 #.  , given the following information
 #.  in addition to that given in
 #.  .BR outb (9).
 #. type: Plain text
 #: build/C/man2/outb.2:73
-msgid ""
-"They are primarily designed for internal kernel use, but can be used from "
-"user space."
-msgstr ""
-"これらの関数はもともとカーネル内部での使用を想定して設計されているが、 ユー"
-"ザー空間からでも使用できる。"
+msgid "They are primarily designed for internal kernel use, but can be used from user space."
+msgstr "これらの関数はもともとカーネル内部での使用を想定して設計されているが、 ユーザー空間からでも使用できる。"
 
 #. type: Plain text
 #: build/C/man2/outb.2:78
-msgid ""
-"You must compile with B<-O> or B<-O2> or similar.  The functions are defined "
-"as inline macros, and will not be substituted in without optimization "
-"enabled, causing unresolved references at link time."
-msgstr ""
-"B<-O> や B<-O2> などを指定してコンパイルしなければならない。 これらの関数はイ"
-"ンライン・マクロとして定義されており、 最適化を行わないと関数の展開が行われ"
-"ず、 リンクの時に「解決できない参照(unresolved reference)」が発生する。"
+msgid "You must compile with B<-O> or B<-O2> or similar.  The functions are defined as inline macros, and will not be substituted in without optimization enabled, causing unresolved references at link time."
+msgstr "B<-O> や B<-O2> などを指定してコンパイルしなければならない。 これらの関数はインライン・マクロとして定義されており、 最適化を行わないと関数の展開が行われず、 リンクの時に「解決できない参照(unresolved reference)」が発生する。"
 
 #. type: Plain text
 #: build/C/man2/outb.2:87
-msgid ""
-"You use B<ioperm>(2)  or alternatively B<iopl>(2)  to tell the kernel to "
-"allow the user space application to access the I/O ports in question.  "
-"Failure to do this will cause the application to receive a segmentation "
-"fault."
-msgstr ""
-"ユーザー空間のアプリケーションが I/O ポートにアクセスすることを カーネルに教"
-"えるために B<ioperm>(2)  もしくは B<iopl>(2)  を使用すること。これを忘れると"
-"アプリケーションはセグメンテーション違反 (segmentation fault) を受けとること"
-"になる。"
+msgid "You use B<ioperm>(2)  or alternatively B<iopl>(2)  to tell the kernel to allow the user space application to access the I/O ports in question.  Failure to do this will cause the application to receive a segmentation fault."
+msgstr "ユーザー空間のアプリケーションが I/O ポートにアクセスすることを カーネルに教えるために B<ioperm>(2)  もしくは B<iopl>(2)  を使用すること。これを忘れるとアプリケーションはセグメンテーション違反 (segmentation fault) を受けとることになる。"
 
 #. type: Plain text
 #: build/C/man2/outb.2:96
-msgid ""
-"B<outb>()  and friends are hardware-specific.  The I<value> argument is "
-"passed first and the I<port> argument is passed second, which is the "
-"opposite order from most DOS implementations."
-msgstr ""
-"B<outb>()  とその仲間はハードウェア特有である。 I<value> 引数が最初に渡さ"
-"れ、 I<port> 引数が二番目に渡される。 この順序はほとんどの DOS での実装とは逆"
-"である。"
+msgid "B<outb>()  and friends are hardware-specific.  The I<value> argument is passed first and the I<port> argument is passed second, which is the opposite order from most DOS implementations."
+msgstr "B<outb>()  とその仲間はハードウェア特有である。 I<value> 引数が最初に渡され、 I<port> 引数が二番目に渡される。 この順序はほとんどの DOS での実装とは逆である。"
 
 #. type: Plain text
 #: build/C/man2/outb.2:99
@@ -2117,11 +1651,8 @@ msgstr "2003-07-14"
 
 #. type: Plain text
 #: build/C/man2/pciconfig_read.2:11
-msgid ""
-"pciconfig_read, pciconfig_write, pciconfig_iobase - pci device information "
-"handling"
-msgstr ""
-"pciconfig_read, pciconfig_write, pciconfig_iobase - pci デバイス情報を扱う"
+msgid "pciconfig_read, pciconfig_write, pciconfig_iobase - pci device information handling"
+msgstr "pciconfig_read, pciconfig_write, pciconfig_iobase - pci デバイス情報を扱う"
 
 #. type: Plain text
 #: build/C/man2/pciconfig_read.2:14
@@ -2149,13 +1680,8 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/pciconfig_read.2:27
-msgid ""
-"Most of the interaction with PCI devices is already handled by the kernel "
-"PCI layer, and thus these calls should not normally need to be accessed from "
-"user space."
-msgstr ""
-"PCI デバイスとのやり取り (interaction) は カーネル PCI レイヤですでに処理され"
-"ているので、 通常はこららの関数をユーザ空間からアクセスする必要はない。"
+msgid "Most of the interaction with PCI devices is already handled by the kernel PCI layer, and thus these calls should not normally need to be accessed from user space."
+msgstr "PCI デバイスとのやり取り (interaction) は カーネル PCI レイヤですでに処理されているので、 通常はこららの関数をユーザ空間からアクセスする必要はない。"
 
 #. type: TP
 #: build/C/man2/pciconfig_read.2:27 build/C/man2/pciconfig_read.2:51
@@ -2187,42 +1713,23 @@ msgstr "B<pciconfig_iobase>()"
 
 #. type: Plain text
 #: build/C/man2/pciconfig_read.2:50
-msgid ""
-"You pass it a bus/devfn pair and get a physical address for either the "
-"memory offset (for things like prep, this is 0xc0000000), the IO base for "
-"PIO cycles, or the ISA holes if any."
-msgstr ""
-"bus/devfn ペアをこの関数に渡し、 メモリオフセット (prep のようなものでは、こ"
-"の値は 0xc0000000 である) と PIO サイクルの IO ベースの物理アドレスを取得す"
-"る。 また、もしあるならば ISA hole の物理アドレスを取得する。"
+msgid "You pass it a bus/devfn pair and get a physical address for either the memory offset (for things like prep, this is 0xc0000000), the IO base for PIO cycles, or the ISA holes if any."
+msgstr "bus/devfn ペアをこの関数に渡し、 メモリオフセット (prep のようなものでは、この値は 0xc0000000 である) と PIO サイクルの IO ベースの物理アドレスを取得する。 また、もしあるならば ISA hole の物理アドレスを取得する。"
 
 #. type: Plain text
 #: build/C/man2/pciconfig_read.2:57 build/C/man2/pciconfig_read.2:63
-msgid ""
-"On success zero is returned.  On error, -1 is returned and I<errno> is set "
-"appropriately."
-msgstr ""
-"成功した場合、0 が返される。 エラーの場合、-1 が返され、 I<errno> が適切に設"
-"定される。"
+msgid "On success zero is returned.  On error, -1 is returned and I<errno> is set appropriately."
+msgstr "成功した場合、0 が返される。 エラーの場合、-1 が返され、 I<errno> が適切に設定される。"
 
 #. type: Plain text
 #: build/C/man2/pciconfig_read.2:77
-msgid ""
-"Returns information on locations of various I/O regions in physical memory "
-"according to the I<which> value.  Values for I<which> are: "
-"B<IOBASE_BRIDGE_NUMBER>, B<IOBASE_MEMORY>, B<IOBASE_IO>, B<IOBASE_ISA_IO>, "
-"B<IOBASE_ISA_MEM>."
-msgstr ""
-"I<which> の値に基づいて、物理メモリ内の様々な I/O 領域の位置情報が返される。 "
-"I<which> の値は、 B<IOBASE_BRIDGE_NUMBER>, B<IOBASE_MEMORY>, B<IOBASE_IO>, "
-"B<IOBASE_ISA_IO>, B<IOBASE_ISA_MEM> である。"
+msgid "Returns information on locations of various I/O regions in physical memory according to the I<which> value.  Values for I<which> are: B<IOBASE_BRIDGE_NUMBER>, B<IOBASE_MEMORY>, B<IOBASE_IO>, B<IOBASE_ISA_IO>, B<IOBASE_ISA_MEM>."
+msgstr "I<which> の値に基づいて、物理メモリ内の様々な I/O 領域の位置情報が返される。 I<which> の値は、 B<IOBASE_BRIDGE_NUMBER>, B<IOBASE_MEMORY>, B<IOBASE_IO>, B<IOBASE_ISA_IO>, B<IOBASE_ISA_MEM> である。"
 
 #. type: Plain text
 #: build/C/man2/pciconfig_read.2:84
 msgid "I<len> value is invalid.  This does not apply to B<pciconfig_iobase>()."
-msgstr ""
-"I<len> の値が無効である。 このエラーは B<pciconfig_iobase>()  には適用されな"
-"い。"
+msgstr "I<len> の値が無効である。 このエラーは B<pciconfig_iobase>()  には適用されない。"
 
 #. type: TP
 #: build/C/man2/pciconfig_read.2:84 build/C/man2/ptrace.2:1929
@@ -2244,19 +1751,13 @@ msgstr "B<ENODEV>"
 
 #. type: Plain text
 #: build/C/man2/pciconfig_read.2:93
-msgid ""
-"For B<pciconfig_iobase>(), \"hose\" value is NULL.  For the other calls, "
-"could not find a slot."
-msgstr ""
-"B<pciconfig_iobase>()  の場合、でホース (hose) の値が NULL である。 他の呼び"
-"出しの場合、スロット (slot) が見つからない。"
+msgid "For B<pciconfig_iobase>(), \"hose\" value is NULL.  For the other calls, could not find a slot."
+msgstr "B<pciconfig_iobase>()  の場合、でホース (hose) の値が NULL である。 他の呼び出しの場合、スロット (slot) が見つからない。"
 
 #. type: Plain text
 #: build/C/man2/pciconfig_read.2:98
 msgid "The system has not implemented these calls (B<CONFIG_PCI> not defined)."
-msgstr ""
-"このシステムはこれらの呼び出しを実装していない。 (B<CONFIG_PCI> が定義されて"
-"いない)。"
+msgstr "このシステムはこれらの呼び出しを実装していない。 (B<CONFIG_PCI> が定義されていない)。"
 
 #. type: TP
 #: build/C/man2/pciconfig_read.2:98 build/C/man2/perf_event_open.2:2668
@@ -2266,28 +1767,18 @@ msgstr "B<EOPNOTSUPP>"
 
 #. type: Plain text
 #: build/C/man2/pciconfig_read.2:105
-msgid ""
-"This return value is valid only for B<pciconfig_iobase>().  It is returned "
-"if the value for I<which> is invalid."
-msgstr ""
-"この返り値は B<pciconfig_iobase>()  でのみ有効である。 このエラーは I<which> "
-"の値が無効であるときに返される。"
+msgid "This return value is valid only for B<pciconfig_iobase>().  It is returned if the value for I<which> is invalid."
+msgstr "この返り値は B<pciconfig_iobase>()  でのみ有効である。 このエラーは I<which> の値が無効であるときに返される。"
 
 #. type: Plain text
 #: build/C/man2/pciconfig_read.2:112
-msgid ""
-"User does not have the B<CAP_SYS_ADMIN> capability.  This does not apply to "
-"B<pciconfig_iobase>()."
-msgstr ""
-"ユーザが B<CAP_SYS_ADMIN> 権限を持っていない。 このエラーは "
-"B<pciconfig_iobase>()  には適用されない。"
+msgid "User does not have the B<CAP_SYS_ADMIN> capability.  This does not apply to B<pciconfig_iobase>()."
+msgstr "ユーザが B<CAP_SYS_ADMIN> 権限を持っていない。 このエラーは B<pciconfig_iobase>()  には適用されない。"
 
 #. type: Plain text
 #: build/C/man2/pciconfig_read.2:114
 msgid "These calls are Linux-specific, available since Linux 2.0.26/2.1.11."
-msgstr ""
-"これらの呼び出しは Linux 特有のものであり、 Linux 2.0.26/2.1.11 から使用可能"
-"である。"
+msgstr "これらの呼び出しは Linux 特有のものであり、 Linux 2.0.26/2.1.11 から使用可能である。"
 
 #. type: Plain text
 #: build/C/man2/pciconfig_read.2:116
@@ -2335,37 +1826,22 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:47
-msgid ""
-"Given a list of parameters, B<perf_event_open>()  returns a file descriptor, "
-"for use in subsequent system calls (B<read>(2), B<mmap>(2), B<prctl>(2), "
-"B<fcntl>(2), etc.)."
+msgid "Given a list of parameters, B<perf_event_open>()  returns a file descriptor, for use in subsequent system calls (B<read>(2), B<mmap>(2), B<prctl>(2), B<fcntl>(2), etc.)."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:55
-msgid ""
-"A call to B<perf_event_open>()  creates a file descriptor that allows "
-"measuring performance information.  Each file descriptor corresponds to one "
-"event that is measured; these can be grouped together to measure multiple "
-"events simultaneously."
+msgid "A call to B<perf_event_open>()  creates a file descriptor that allows measuring performance information.  Each file descriptor corresponds to one event that is measured; these can be grouped together to measure multiple events simultaneously."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:62
-msgid ""
-"Events can be enabled and disabled in two ways: via B<ioctl>(2)  and via "
-"B<prctl>(2).  When an event is disabled it does not count or generate "
-"overflows but does continue to exist and maintain its count value."
+msgid "Events can be enabled and disabled in two ways: via B<ioctl>(2)  and via B<prctl>(2).  When an event is disabled it does not count or generate overflows but does continue to exist and maintain its count value."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:76
-msgid ""
-"Events come in two flavors: counting and sampled.  A I<counting> event is "
-"one that is used for counting the aggregate number of events that occur.  In "
-"general, counting event results are gathered with a B<read>(2)  call.  A "
-"I<sampling> event periodically writes measurements to a buffer that can then "
-"be accessed via B<mmap>(2)."
+msgid "Events come in two flavors: counting and sampled.  A I<counting> event is one that is used for counting the aggregate number of events that occur.  In general, counting event results are gathered with a B<read>(2)  call.  A I<sampling> event periodically writes measurements to a buffer that can then be accessed via B<mmap>(2)."
 msgstr ""
 
 #. type: SS
@@ -2376,9 +1852,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:83
-msgid ""
-"The I<pid> and I<cpu> arguments allow specifying which process and CPU to "
-"monitor:"
+msgid "The I<pid> and I<cpu> arguments allow specifying which process and CPU to monitor:"
 msgstr ""
 
 #. type: TP
@@ -2400,9 +1874,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:90
-msgid ""
-"This measures the calling process/thread only when running on the specified "
-"CPU."
+msgid "This measures the calling process/thread only when running on the specified CPU."
 msgstr ""
 
 #. type: TP
@@ -2424,9 +1896,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:97
-msgid ""
-"This measures the specified process/thread only when running on the "
-"specified CPU."
+msgid "This measures the specified process/thread only when running on the specified CPU."
 msgstr ""
 
 #. type: TP
@@ -2437,10 +1907,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:105
-msgid ""
-"This measures all processes/threads on the specified CPU.  This requires "
-"B<CAP_SYS_ADMIN> capability or a I</proc/sys/kernel/perf_event_paranoid> "
-"value of less than 1."
+msgid "This measures all processes/threads on the specified CPU.  This requires B<CAP_SYS_ADMIN> capability or a I</proc/sys/kernel/perf_event_paranoid> value of less than 1."
 msgstr ""
 
 #. type: TP
@@ -2456,45 +1923,24 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:130
-msgid ""
-"The I<group_fd> argument allows event groups to be created.  An event group "
-"has one event which is the group leader.  The leader is created first, with "
-"I<group_fd> = -1.  The rest of the group members are created with subsequent "
-"B<perf_event_open>()  calls with I<group_fd> being set to the file "
-"descriptor of the group leader.  (A single event on its own is created with "
-"I<group_fd> = -1 and is considered to be a group with only 1 member.)  An "
-"event group is scheduled onto the CPU as a unit: it will be put onto the CPU "
-"only if all of the events in the group can be put onto the CPU.  This means "
-"that the values of the member events can be meaningfully compared\\(emadded, "
-"divided (to get ratios), and so on\\(emwith each other, since they have "
-"counted events for the same set of executed instructions."
+msgid "The I<group_fd> argument allows event groups to be created.  An event group has one event which is the group leader.  The leader is created first, with I<group_fd> = -1.  The rest of the group members are created with subsequent B<perf_event_open>()  calls with I<group_fd> being set to the file descriptor of the group leader.  (A single event on its own is created with I<group_fd> = -1 and is considered to be a group with only 1 member.)  An event group is scheduled onto the CPU as a unit: it will be put onto the CPU only if all of the events in the group can be put onto the CPU.  This means that the values of the member events can be meaningfully compared\\(emadded, divided (to get ratios), and so on\\(emwith each other, since they have counted events for the same set of executed instructions."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:134
-msgid ""
-"The I<flags> argument is formed by ORing together zero or more of the "
-"following values:"
-msgstr ""
-"I<flags> 引き数には、以下の値の 0 個以上をビット毎の論理和の形で指定する。"
+msgid "The I<flags> argument is formed by ORing together zero or more of the following values:"
+msgstr "I<flags> 引き数には、以下の値の 0 個以上をビット毎の論理和の形で指定する。"
 
 #. type: TP
 #: build/C/man2/perf_event_open.2:134
-#, fuzzy, no-wrap
-#| msgid "B<PERF_FLAG_FD_CLOEXEC> (since Linux 3.14)."
+#, no-wrap
 msgid "B<PERF_FLAG_FD_CLOEXEC> (since Linux 3.14)"
-msgstr "B<PERF_FLAG_FD_CLOEXEC> (Linux 3.14 以降)."
+msgstr "B<PERF_FLAG_FD_CLOEXEC> (Linux 3.14 以降)"
 
 #.  commit a21b0b354d4ac39be691f51c53562e2c24443d9e
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:151
-msgid ""
-"This flag enables the close-on-exec flag for the created event file "
-"descriptor, so that the file descriptor is automatically closed on "
-"B<execve>(2).  Setting the close-on-exec flags at creation time, rather than "
-"later with B<fcntl>(2), avoids potential race conditions where the calling "
-"thread invokes B<perf_event_open>()  and B<fcntl>(2)  at the same time as "
-"another thread calls B<fork>(2)  then B<execve>(2)."
+msgid "This flag enables the close-on-exec flag for the created event file descriptor, so that the file descriptor is automatically closed on B<execve>(2).  Setting the close-on-exec flags at creation time, rather than later with B<fcntl>(2), avoids potential race conditions where the calling thread invokes B<perf_event_open>()  and B<fcntl>(2)  at the same time as another thread calls B<fork>(2)  then B<execve>(2)."
 msgstr ""
 
 #. type: TP
@@ -2505,54 +1951,35 @@ msgstr "B<PERF_FLAG_FD_NO_GROUP>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:159
-msgid ""
-"This flag tells the event to ignore the I<group_fd> parameter except for the "
-"purpose of setting up output redirection using the B<PERF_FLAG_FD_OUTPUT> "
-"flag."
+msgid "This flag tells the event to ignore the I<group_fd> parameter except for the purpose of setting up output redirection using the B<PERF_FLAG_FD_OUTPUT> flag."
 msgstr ""
 
 #. type: TP
 #: build/C/man2/perf_event_open.2:159
-#, fuzzy, no-wrap
-#| msgid "B<PERF_FLAG_PID_CGROUP> (since Linux 2.6.39)."
+#, no-wrap
 msgid "B<PERF_FLAG_FD_OUTPUT> (broken since Linux 2.6.35)"
-msgstr "B<PERF_FLAG_PID_CGROUP> (Linux 2.6.39 以降)."
+msgstr "B<PERF_FLAG_FD_OUTPUT> (Linux 2.6.35 以降では正しく動作しない)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:164
-msgid ""
-"This flag re-routes the event's sampled output to instead be included in the "
-"mmap buffer of the event specified by I<group_fd>."
+msgid "This flag re-routes the event's sampled output to instead be included in the mmap buffer of the event specified by I<group_fd>."
 msgstr ""
 
 #. type: TP
 #: build/C/man2/perf_event_open.2:164
-#, fuzzy, no-wrap
-#| msgid "B<PERF_FLAG_PID_CGROUP> (since Linux 2.6.39)."
+#, no-wrap
 msgid "B<PERF_FLAG_PID_CGROUP> (since Linux 2.6.39)"
-msgstr "B<PERF_FLAG_PID_CGROUP> (Linux 2.6.39 以降)."
+msgstr "B<PERF_FLAG_PID_CGROUP> (Linux 2.6.39 以降)"
 
 #.  commit e5d1367f17ba6a6fed5fd8b74e4d5720923e0c25
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:188
-msgid ""
-"This flag activates per-container system-wide monitoring.  A container is an "
-"abstraction that isolates a set of resources for finer-grained control "
-"(CPUs, memory, etc.).  In this mode, the event is measured only if the "
-"thread running on the monitored CPU belongs to the designated container "
-"(cgroup).  The cgroup is identified by passing a file descriptor opened on "
-"its directory in the cgroupfs filesystem.  For instance, if the cgroup to "
-"monitor is called I<test>, then a file descriptor opened on I</dev/cgroup/"
-"test> (assuming cgroupfs is mounted on I</dev/cgroup>)  must be passed as "
-"the I<pid> parameter.  cgroup monitoring is available only for system-wide "
-"events and may therefore require extra permissions."
+msgid "This flag activates per-container system-wide monitoring.  A container is an abstraction that isolates a set of resources for finer-grained control (CPUs, memory, etc.).  In this mode, the event is measured only if the thread running on the monitored CPU belongs to the designated container (cgroup).  The cgroup is identified by passing a file descriptor opened on its directory in the cgroupfs filesystem.  For instance, if the cgroup to monitor is called I<test>, then a file descriptor opened on I</dev/cgroup/test> (assuming cgroupfs is mounted on I</dev/cgroup>)  must be passed as the I<pid> parameter.  cgroup monitoring is available only for system-wide events and may therefore require extra permissions."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:193
-msgid ""
-"The I<perf_event_attr> structure provides detailed configuration information "
-"for the event being created."
+msgid "The I<perf_event_attr> structure provides detailed configuration information for the event being created."
 msgstr ""
 
 #. type: Plain text
@@ -2719,9 +2146,7 @@ msgstr "};\n"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:266
-msgid ""
-"The fields of the I<perf_event_attr> structure are described in more detail "
-"below:"
+msgid "The fields of the I<perf_event_attr> structure are described in more detail below:"
 msgstr ""
 
 #. type: TP
@@ -2732,9 +2157,7 @@ msgstr "I<type>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:270
-msgid ""
-"This field specifies the overall event type.  It has one of the following "
-"values:"
+msgid "This field specifies the overall event type.  It has one of the following values:"
 msgstr ""
 
 #. type: TP
@@ -2745,9 +2168,7 @@ msgstr "B<PERF_TYPE_HARDWARE>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:278
-msgid ""
-"This indicates one of the \"generalized\" hardware events provided by the "
-"kernel.  See the I<config> field definition for more details."
+msgid "This indicates one of the \"generalized\" hardware events provided by the kernel.  See the I<config> field definition for more details."
 msgstr ""
 
 #. type: TP
@@ -2758,9 +2179,7 @@ msgstr "B<PERF_TYPE_SOFTWARE>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:282
-msgid ""
-"This indicates one of the software-defined events provided by the kernel "
-"(even if no hardware support is available)."
+msgid "This indicates one of the software-defined events provided by the kernel (even if no hardware support is available)."
 msgstr ""
 
 #. type: TP
@@ -2771,8 +2190,7 @@ msgstr "B<PERF_TYPE_TRACEPOINT>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:286
-msgid ""
-"This indicates a tracepoint provided by the kernel tracepoint infrastructure."
+msgid "This indicates a tracepoint provided by the kernel tracepoint infrastructure."
 msgstr ""
 
 #. type: TP
@@ -2783,9 +2201,7 @@ msgstr "B<PERF_TYPE_HW_CACHE>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:292
-msgid ""
-"This indicates a hardware cache event.  This has a special encoding, "
-"described in the I<config> field definition."
+msgid "This indicates a hardware cache event.  This has a special encoding, described in the I<config> field definition."
 msgstr ""
 
 #. type: TP
@@ -2796,9 +2212,7 @@ msgstr "B<PERF_TYPE_RAW>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:296
-msgid ""
-"This indicates a \"raw\" implementation-specific event in the I<config> "
-"field."
+msgid "This indicates a \"raw\" implementation-specific event in the I<config> field."
 msgstr ""
 
 #. type: TP
@@ -2810,10 +2224,7 @@ msgstr "B<PERF_TYPE_BREAKPOINT> (Linux 2.6.33 以降)"
 #.  commit 24f1e32c60c45c89a997c73395b69c8af6f0a84e
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:302
-msgid ""
-"This indicates a hardware breakpoint as provided by the CPU.  Breakpoints "
-"can be read/write accesses to an address as well as execution of an "
-"instruction address."
+msgid "This indicates a hardware breakpoint as provided by the CPU.  Breakpoints can be read/write accesses to an address as well as execution of an instruction address."
 msgstr ""
 
 #. type: TP
@@ -2824,15 +2235,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:321
-msgid ""
-"Since Linux 2.6.39, B<perf_event_open>()  can support multiple PMUs.  To "
-"enable this, a value exported by the kernel can be used in the I<type> field "
-"to indicate which PMU to use.  The value to use can be found in the sysfs "
-"filesystem: there is a subdirectory per PMU instance under I</sys/bus/"
-"event_source/devices>.  In each subdirectory there is a I<type> file whose "
-"content is an integer that can be used in the I<type> field.  For instance, "
-"I</sys/bus/event_source/devices/cpu/type> contains the value for the core "
-"CPU PMU, which is usually 4."
+msgid "Since Linux 2.6.39, B<perf_event_open>()  can support multiple PMUs.  To enable this, a value exported by the kernel can be used in the I<type> field to indicate which PMU to use.  The value to use can be found in the sysfs filesystem: there is a subdirectory per PMU instance under I</sys/bus/event_source/devices>.  In each subdirectory there is a I<type> file whose content is an integer that can be used in the I<type> field.  For instance, I</sys/bus/event_source/devices/cpu/type> contains the value for the core CPU PMU, which is usually 4."
 msgstr ""
 
 #. type: TP
@@ -2843,21 +2246,12 @@ msgstr "I<size>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:331
-msgid ""
-"The size of the I<perf_event_attr> structure for forward/backward "
-"compatibility.  Set this using I<sizeof(struct perf_event_attr)> to allow "
-"the kernel to see the struct size at the time of compilation."
+msgid "The size of the I<perf_event_attr> structure for forward/backward compatibility.  Set this using I<sizeof(struct perf_event_attr)> to allow the kernel to see the struct size at the time of compilation."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:346
-msgid ""
-"The related define B<PERF_ATTR_SIZE_VER0> is set to 64; this was the size of "
-"the first published struct.  B<PERF_ATTR_SIZE_VER1> is 72, corresponding to "
-"the addition of breakpoints in Linux 2.6.33.  B<PERF_ATTR_SIZE_VER2> is 80 "
-"corresponding to the addition of branch sampling in Linux 3.4.  "
-"B<PERF_ATTR_SIZE_VER3> is 96 corresponding to the addition of "
-"I<sample_regs_user> and I<sample_stack_user> in Linux 3.7."
+msgid "The related define B<PERF_ATTR_SIZE_VER0> is set to 64; this was the size of the first published struct.  B<PERF_ATTR_SIZE_VER1> is 72, corresponding to the addition of breakpoints in Linux 2.6.33.  B<PERF_ATTR_SIZE_VER2> is 80 corresponding to the addition of branch sampling in Linux 3.4.  B<PERF_ATTR_SIZE_VER3> is 96 corresponding to the addition of I<sample_regs_user> and I<sample_stack_user> in Linux 3.7."
 msgstr ""
 
 #. type: TP
@@ -2868,27 +2262,17 @@ msgstr "I<config>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:357
-msgid ""
-"This specifies which event you want, in conjunction with the I<type> field.  "
-"The I<config1> and I<config2> fields are also taken into account in cases "
-"where 64 bits is not enough to fully specify the event.  The encoding of "
-"these fields are event dependent."
+msgid "This specifies which event you want, in conjunction with the I<type> field.  The I<config1> and I<config2> fields are also taken into account in cases where 64 bits is not enough to fully specify the event.  The encoding of these fields are event dependent."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:368
-msgid ""
-"There are various ways to set the I<config> field that are dependent on the "
-"value of the previously described I<type> field.  What follows are various "
-"possible settings for I<config> separated out by I<type>."
+msgid "There are various ways to set the I<config> field that are dependent on the value of the previously described I<type> field.  What follows are various possible settings for I<config> separated out by I<type>."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:378
-msgid ""
-"If I<type> is B<PERF_TYPE_HARDWARE>, we are measuring one of the generalized "
-"hardware CPU events.  Not all of these are available on all platforms.  Set "
-"I<config> to one of the following:"
+msgid "If I<type> is B<PERF_TYPE_HARDWARE>, we are measuring one of the generalized hardware CPU events.  Not all of these are available on all platforms.  Set I<config> to one of the following:"
 msgstr ""
 
 #. type: TP
@@ -2910,9 +2294,7 @@ msgstr "B<PERF_COUNT_HW_INSTRUCTIONS>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:388
-msgid ""
-"Retired instructions.  Be careful, these can be affected by various issues, "
-"most notably hardware interrupt counts."
+msgid "Retired instructions.  Be careful, these can be affected by various issues, most notably hardware interrupt counts."
 msgstr ""
 
 #. type: TP
@@ -2923,10 +2305,7 @@ msgstr "B<PERF_COUNT_HW_CACHE_REFERENCES>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:395
-msgid ""
-"Cache accesses.  Usually this indicates Last Level Cache accesses but this "
-"may vary depending on your CPU.  This may include prefetches and coherency "
-"messages; again this depends on the design of your CPU."
+msgid "Cache accesses.  Usually this indicates Last Level Cache accesses but this may vary depending on your CPU.  This may include prefetches and coherency messages; again this depends on the design of your CPU."
 msgstr ""
 
 #. type: TP
@@ -2937,10 +2316,7 @@ msgstr "B<PERF_COUNT_HW_CACHE_MISSES>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:402
-msgid ""
-"Cache misses.  Usually this indicates Last Level Cache misses; this is "
-"intended to be used in conjunction with the "
-"B<PERF_COUNT_HW_CACHE_REFERENCES> event to calculate cache miss rates."
+msgid "Cache misses.  Usually this indicates Last Level Cache misses; this is intended to be used in conjunction with the B<PERF_COUNT_HW_CACHE_REFERENCES> event to calculate cache miss rates."
 msgstr ""
 
 #. type: TP
@@ -2951,9 +2327,7 @@ msgstr "B<PERF_COUNT_HW_BRANCH_INSTRUCTIONS>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:407
-msgid ""
-"Retired branch instructions.  Prior to Linux 2.6.34, this used the wrong "
-"event on AMD processors."
+msgid "Retired branch instructions.  Prior to Linux 2.6.34, this used the wrong event on AMD processors."
 msgstr ""
 
 #. type: TP
@@ -3014,9 +2388,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:433
-msgid ""
-"If I<type> is B<PERF_TYPE_SOFTWARE>, we are measuring software events "
-"provided by the kernel.  Set I<config> to one of the following:"
+msgid "If I<type> is B<PERF_TYPE_SOFTWARE>, we are measuring software events provided by the kernel.  Set I<config> to one of the following:"
 msgstr ""
 
 #. type: TP
@@ -3060,10 +2432,7 @@ msgstr "B<PERF_COUNT_SW_CONTEXT_SWITCHES>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:448
-msgid ""
-"This counts context switches.  Until Linux 2.6.34, these were all reported "
-"as user-space events, after that they are reported as happening in the "
-"kernel."
+msgid "This counts context switches.  Until Linux 2.6.34, these were all reported as user-space events, after that they are reported as happening in the kernel."
 msgstr ""
 
 #. type: TP
@@ -3085,9 +2454,7 @@ msgstr "B<PERF_COUNT_SW_PAGE_FAULTS_MIN>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:456
-msgid ""
-"This counts the number of minor page faults.  These did not require disk I/O "
-"to handle."
+msgid "This counts the number of minor page faults.  These did not require disk I/O to handle."
 msgstr ""
 
 #. type: TP
@@ -3098,9 +2465,7 @@ msgstr "B<PERF_COUNT_SW_PAGE_FAULTS_MAJ>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:460
-msgid ""
-"This counts the number of major page faults.  These required disk I/O to "
-"handle."
+msgid "This counts the number of major page faults.  These required disk I/O to handle."
 msgstr ""
 
 #. type: TP
@@ -3112,10 +2477,7 @@ msgstr "B<PERF_COUNT_SW_ALIGNMENT_FAULTS> (Linux 2.6.33 以降)"
 #.  commit f7d7986060b2890fc26db6ab5203efbd33aa2497
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:467
-msgid ""
-"This counts the number of alignment faults.  These happen when unaligned "
-"memory accesses happen; the kernel can handle these but it reduces "
-"performance.  This happens only on some architectures (never on x86)."
+msgid "This counts the number of alignment faults.  These happen when unaligned memory accesses happen; the kernel can handle these but it reduces performance.  This happens only on some architectures (never on x86)."
 msgstr ""
 
 #. type: TP
@@ -3127,10 +2489,7 @@ msgstr "B<PERF_COUNT_SW_EMULATION_FAULTS> (Linux 2.6.33 以降)"
 #.  commit f7d7986060b2890fc26db6ab5203efbd33aa2497
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:474
-msgid ""
-"This counts the number of emulation faults.  The kernel sometimes traps on "
-"unimplemented instructions and emulates them for user space.  This can "
-"negatively impact performance."
+msgid "This counts the number of emulation faults.  The kernel sometimes traps on unimplemented instructions and emulates them for user space.  This can negatively impact performance."
 msgstr ""
 
 #. type: TP
@@ -3142,27 +2501,17 @@ msgstr "B<PERF_COUNT_SW_DUMMY> (Linux 3.12 以降)"
 #.  commit fa0097ee690693006ab1aea6c01ad3c851b65c77
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:482
-msgid ""
-"This is a placeholder event that counts nothing.  Informational sample "
-"record types such as mmap or comm must be associated with an active event.  "
-"This dummy event allows gathering such records without requiring a counting "
-"event."
+msgid "This is a placeholder event that counts nothing.  Informational sample record types such as mmap or comm must be associated with an active event.  This dummy event allows gathering such records without requiring a counting event."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:495
-msgid ""
-"If I<type> is B<PERF_TYPE_TRACEPOINT>, then we are measuring kernel "
-"tracepoints.  The value to use in I<config> can be obtained from under "
-"debugfs I<tracing/events/*/*/id> if ftrace is enabled in the kernel."
+msgid "If I<type> is B<PERF_TYPE_TRACEPOINT>, then we are measuring kernel tracepoints.  The value to use in I<config> can be obtained from under debugfs I<tracing/events/*/*/id> if ftrace is enabled in the kernel."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:506
-msgid ""
-"If I<type> is B<PERF_TYPE_HW_CACHE>, then we are measuring a hardware CPU "
-"cache event.  To calculate the appropriate I<config> value use the following "
-"equation:"
+msgid "If I<type> is B<PERF_TYPE_HW_CACHE>, then we are measuring a hardware CPU cache event.  To calculate the appropriate I<config> value use the following equation:"
 msgstr ""
 
 #. type: Plain text
@@ -3248,10 +2597,9 @@ msgstr ""
 
 #. type: TP
 #: build/C/man2/perf_event_open.2:535
-#, fuzzy, no-wrap
-#| msgid "B<PERF_COUNT_HW_CACHE_NODE> (since Linux 3.0)"
+#, no-wrap
 msgid "B<PERF_COUNT_HW_CACHE_NODE> (since Linux 3.1)"
-msgstr "B<PERF_COUNT_HW_CACHE_NODE> (Linux 3.0 以降)"
+msgstr "B<PERF_COUNT_HW_CACHE_NODE> (Linux 3.1 以降)"
 
 #.  commit 89d6c0b5bdbb1927775584dcf532d98b3efe1477
 #. type: Plain text
@@ -3326,21 +2674,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:584
-msgid ""
-"If I<type> is B<PERF_TYPE_RAW>, then a custom \"raw\" I<config> value is "
-"needed.  Most CPUs support events that are not covered by the \"generalized"
-"\" events.  These are implementation defined; see your CPU manual (for "
-"example the Intel Volume 3B documentation or the AMD BIOS and Kernel "
-"Developer Guide).  The libpfm4 library can be used to translate from the "
-"name in the architectural manuals to the raw hex value B<perf_event_open>()  "
-"expects in this field."
+msgid "If I<type> is B<PERF_TYPE_RAW>, then a custom \"raw\" I<config> value is needed.  Most CPUs support events that are not covered by the \"generalized\" events.  These are implementation defined; see your CPU manual (for example the Intel Volume 3B documentation or the AMD BIOS and Kernel Developer Guide).  The libpfm4 library can be used to translate from the name in the architectural manuals to the raw hex value B<perf_event_open>()  expects in this field."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:593
-msgid ""
-"If I<type> is B<PERF_TYPE_BREAKPOINT>, then leave I<config> set to zero.  "
-"Its parameters are set in other places."
+msgid "If I<type> is B<PERF_TYPE_BREAKPOINT>, then leave I<config> set to zero.  Its parameters are set in other places."
 msgstr ""
 
 #. type: TP
@@ -3351,21 +2690,12 @@ msgstr "I<sample_period>, I<sample_freq>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:606
-msgid ""
-"A \"sampling\" event is one that generates an overflow notification every N "
-"events, where N is given by I<sample_period>.  A sampling event has "
-"I<sample_period> E<gt> 0.  When an overflow occurs, requested data is "
-"recorded in the mmap buffer.  The I<sample_type> field controls what data is "
-"recorded on each overflow."
+msgid "A \"sampling\" event is one that generates an overflow notification every N events, where N is given by I<sample_period>.  A sampling event has I<sample_period> E<gt> 0.  When an overflow occurs, requested data is recorded in the mmap buffer.  The I<sample_type> field controls what data is recorded on each overflow."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:616
-msgid ""
-"I<sample_freq> can be used if you wish to use frequency rather than period.  "
-"In this case, you set the I<freq> flag.  The kernel will adjust the sampling "
-"period to try and achieve the desired rate.  The rate of adjustment is a "
-"timer tick."
+msgid "I<sample_freq> can be used if you wish to use frequency rather than period.  In this case, you set the I<freq> flag.  The kernel will adjust the sampling period to try and achieve the desired rate.  The rate of adjustment is a timer tick."
 msgstr ""
 
 #. type: TP
@@ -3376,12 +2706,7 @@ msgstr "I<sample_type>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:628
-msgid ""
-"The various bits in this field specify which values to include in the "
-"sample.  They will be recorded in a ring-buffer, which is available to user "
-"space using B<mmap>(2).  The order in which the values are saved in the "
-"sample are documented in the MMAP Layout subsection below; it is not the "
-"I<enum perf_event_sample_format> order."
+msgid "The various bits in this field specify which values to include in the sample.  They will be recorded in a ring-buffer, which is available to user space using B<mmap>(2).  The order in which the values are saved in the sample are documented in the MMAP Layout subsection below; it is not the I<enum perf_event_sample_format> order."
 msgstr ""
 
 #. type: TP
@@ -3436,8 +2761,7 @@ msgstr "B<PERF_SAMPLE_READ>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:644
-msgid ""
-"Record counter values for all events in a group, not just the group leader."
+msgid "Record counter values for all events in a group, not just the group leader."
 msgstr ""
 
 #. type: TP
@@ -3492,10 +2816,7 @@ msgstr "B<PERF_SAMPLE_STREAM_ID>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:664
-msgid ""
-"Records a unique ID for the opened event.  Unlike B<PERF_SAMPLE_ID> the "
-"actual ID is returned, not the group leader.  This ID is the same as the one "
-"returned by B<PERF_FORMAT_ID>."
+msgid "Records a unique ID for the opened event.  Unlike B<PERF_SAMPLE_ID> the actual ID is returned, not the group leader.  This ID is the same as the one returned by B<PERF_FORMAT_ID>."
 msgstr ""
 
 #. type: TP
@@ -3506,9 +2827,7 @@ msgstr "B<PERF_SAMPLE_RAW>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:668
-msgid ""
-"Records additional data, if applicable.  Usually returned by tracepoint "
-"events."
+msgid "Records additional data, if applicable.  Usually returned by tracepoint events."
 msgstr ""
 
 #. type: TP
@@ -3520,17 +2839,12 @@ msgstr "B<PERF_SAMPLE_BRANCH_STACK> (Linux 3.4 以降)"
 #.  commit bce38cd53e5ddba9cb6d708c4ef3d04a4016ec7e
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:674
-msgid ""
-"This provides a record of recent branches, as provided by CPU branch "
-"sampling hardware (such as Intel Last Branch Record).  Not all hardware "
-"supports this feature."
+msgid "This provides a record of recent branches, as provided by CPU branch sampling hardware (such as Intel Last Branch Record).  Not all hardware supports this feature."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:678
-msgid ""
-"See the I<branch_sample_type> field for how to filter which branches are "
-"reported."
+msgid "See the I<branch_sample_type> field for how to filter which branches are reported."
 msgstr ""
 
 #. type: TP
@@ -3542,9 +2856,7 @@ msgstr "B<PERF_SAMPLE_REGS_USER> (Linux 3.7 以降)"
 #.  commit 4018994f3d8785275ef0e7391b75c3462c029e56
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:683
-msgid ""
-"Records the current user-level CPU register state (the values in the process "
-"before the kernel was called)."
+msgid "Records the current user-level CPU register state (the values in the process before the kernel was called)."
 msgstr ""
 
 #. type: TP
@@ -3568,10 +2880,7 @@ msgstr "B<PERF_SAMPLE_WEIGHT> (Linux 3.10 以降)"
 #.  commit c3feedf2aaf9ac8bad6f19f5d21e4ee0b4b87e9c
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:694
-msgid ""
-"Records a hardware provided weight value that expresses how costly the "
-"sampled event was.  This allows the hardware to highlight expensive events "
-"in a profile."
+msgid "Records a hardware provided weight value that expresses how costly the sampled event was.  This allows the hardware to highlight expensive events in a profile."
 msgstr ""
 
 #. type: TP
@@ -3583,10 +2892,7 @@ msgstr "B<PERF_SAMPLE_DATA_SRC> (Linux 3.10 以降)"
 #.  commit d6be9ad6c960f43800a6f118932bc8a5a4eadcd1
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:701
-msgid ""
-"Records the data source: where in the memory hierarchy the data associated "
-"with the sampled instruction came from.  This is only available if the "
-"underlying hardware supports this feature."
+msgid "Records the data source: where in the memory hierarchy the data associated with the sampled instruction came from.  This is only available if the underlying hardware supports this feature."
 msgstr ""
 
 #. type: TP
@@ -3598,51 +2904,34 @@ msgstr "B<PERF_SAMPLE_IDENTIFIER> (Linux 3.12 以降)"
 #.  commit ff3d527cebc1fa3707c617bfe9e74f53fcfb0955
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:709
-msgid ""
-"Places the B<SAMPLE_ID> value in a fixed position in the record, either at "
-"the beginning (for sample events) or at the end (if a non-sample event)."
+msgid "Places the B<SAMPLE_ID> value in a fixed position in the record, either at the beginning (for sample events) or at the end (if a non-sample event)."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:721
-msgid ""
-"This was necessary because a sample stream may have records from various "
-"different event sources with different I<sample_type> settings.  Parsing the "
-"event stream properly was not possible because the format of the record was "
-"needed to find B<SAMPLE_ID>, but the format could not be found without "
-"knowing what event the sample belonged to (causing a circular dependency)."
+msgid "This was necessary because a sample stream may have records from various different event sources with different I<sample_type> settings.  Parsing the event stream properly was not possible because the format of the record was needed to find B<SAMPLE_ID>, but the format could not be found without knowing what event the sample belonged to (causing a circular dependency)."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:731
-msgid ""
-"The B<PERF_SAMPLE_IDENTIFIER> setting makes the event stream always parsable "
-"by putting B<SAMPLE_ID> in a fixed location, even though it means having "
-"duplicate B<SAMPLE_ID> values in records."
+msgid "The B<PERF_SAMPLE_IDENTIFIER> setting makes the event stream always parsable by putting B<SAMPLE_ID> in a fixed location, even though it means having duplicate B<SAMPLE_ID> values in records."
 msgstr ""
 
 #. type: TP
 #: build/C/man2/perf_event_open.2:731
-#, fuzzy, no-wrap
-#| msgid "B<PERF_SAMPLE_TRANSACTION> (Since Linux 3.13)"
+#, no-wrap
 msgid "B<PERF_SAMPLE_TRANSACTION> (since Linux 3.13)"
 msgstr "B<PERF_SAMPLE_TRANSACTION> (Linux 3.13 以降)"
 
 #.  commit fdfbbd07e91f8fe387140776f3fd94605f0c89e5
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:736
-msgid ""
-"Records reasons for transactional memory abort events (for example, from "
-"Intel TSX transactional memory support)."
+msgid "Records reasons for transactional memory abort events (for example, from Intel TSX transactional memory support)."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:744
-msgid ""
-"The I<precise_ip> setting must be greater than 0 and a transactional memory "
-"abort event must be measured or no values will be recorded.  Also note that "
-"some perf_event measurements, such as sampled cycle counting, may cause "
-"extraneous aborts (by causing an interrupt during a transaction)."
+msgid "The I<precise_ip> setting must be greater than 0 and a transactional memory abort event must be measured or no values will be recorded.  Also note that some perf_event measurements, such as sampled cycle counting, may cause extraneous aborts (by causing an interrupt during a transaction)."
 msgstr ""
 
 #. type: TP
@@ -3653,9 +2942,7 @@ msgstr "I<read_format>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:752
-msgid ""
-"This field specifies the format of the data returned by B<read>(2)  on a "
-"B<perf_event_open>()  file descriptor."
+msgid "This field specifies the format of the data returned by B<read>(2)  on a B<perf_event_open>()  file descriptor."
 msgstr ""
 
 #. type: TP
@@ -3666,9 +2953,7 @@ msgstr "B<PERF_FORMAT_TOTAL_TIME_ENABLED>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:760
-msgid ""
-"Adds the 64-bit I<time_enabled> field.  This can be used to calculate "
-"estimated totals if the PMU is overcommitted and multiplexing is happening."
+msgid "Adds the 64-bit I<time_enabled> field.  This can be used to calculate estimated totals if the PMU is overcommitted and multiplexing is happening."
 msgstr ""
 
 #. type: TP
@@ -3679,9 +2964,7 @@ msgstr "B<PERF_FORMAT_TOTAL_TIME_RUNNING>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:767
-msgid ""
-"Adds the 64-bit I<time_running> field.  This can be used to calculate "
-"estimated totals if the PMU is overcommitted and multiplexing is happening."
+msgid "Adds the 64-bit I<time_running> field.  This can be used to calculate estimated totals if the PMU is overcommitted and multiplexing is happening."
 msgstr ""
 
 #. type: TP
@@ -3714,19 +2997,12 @@ msgstr "I<disabled>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:784
-msgid ""
-"The I<disabled> bit specifies whether the counter starts out disabled or "
-"enabled.  If disabled, the event can later be enabled by B<ioctl>(2), "
-"B<prctl>(2), or I<enable_on_exec>."
+msgid "The I<disabled> bit specifies whether the counter starts out disabled or enabled.  If disabled, the event can later be enabled by B<ioctl>(2), B<prctl>(2), or I<enable_on_exec>."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:795
-msgid ""
-"When creating an event group, typically the group leader is initialized with "
-"I<disabled> set to 1 and any child events are initialized with I<disabled> "
-"set to 0.  Despite I<disabled> being 0, the child events will not start "
-"until the group leader is enabled."
+msgid "When creating an event group, typically the group leader is initialized with I<disabled> set to 1 and any child events are initialized with I<disabled> set to 0.  Despite I<disabled> being 0, the child events will not start until the group leader is enabled."
 msgstr ""
 
 #. type: TP
@@ -3737,18 +3013,12 @@ msgstr "I<inherit>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:804
-msgid ""
-"The I<inherit> bit specifies that this counter should count events of child "
-"tasks as well as the task specified.  This applies only to new children, not "
-"to any existing children at the time the counter is created (nor to any new "
-"children of existing children)."
+msgid "The I<inherit> bit specifies that this counter should count events of child tasks as well as the task specified.  This applies only to new children, not to any existing children at the time the counter is created (nor to any new children of existing children)."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:809
-msgid ""
-"Inherit does not work for some combinations of I<read_format>s, such as "
-"B<PERF_FORMAT_GROUP>."
+msgid "Inherit does not work for some combinations of I<read_format>s, such as B<PERF_FORMAT_GROUP>."
 msgstr ""
 
 #. type: TP
@@ -3759,14 +3029,7 @@ msgstr "I<pinned>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:822
-msgid ""
-"The I<pinned> bit specifies that the counter should always be on the CPU if "
-"at all possible.  It applies only to hardware counters and only to group "
-"leaders.  If a pinned counter cannot be put onto the CPU (e.g., because "
-"there are not enough hardware counters or because of a conflict with some "
-"other event), then the counter goes into an 'error' state, where reads "
-"return end-of-file (i.e., B<read>(2)  returns 0) until the counter is "
-"subsequently enabled or disabled."
+msgid "The I<pinned> bit specifies that the counter should always be on the CPU if at all possible.  It applies only to hardware counters and only to group leaders.  If a pinned counter cannot be put onto the CPU (e.g., because there are not enough hardware counters or because of a conflict with some other event), then the counter goes into an 'error' state, where reads return end-of-file (i.e., B<read>(2)  returns 0) until the counter is subsequently enabled or disabled."
 msgstr ""
 
 #. type: TP
@@ -3777,20 +3040,12 @@ msgstr "I<exclusive>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:831
-msgid ""
-"The I<exclusive> bit specifies that when this counter's group is on the CPU, "
-"it should be the only group using the CPU's counters.  In the future this "
-"may allow monitoring programs to support PMU features that need to run alone "
-"so that they do not disrupt other hardware counters."
+msgid "The I<exclusive> bit specifies that when this counter's group is on the CPU, it should be the only group using the CPU's counters.  In the future this may allow monitoring programs to support PMU features that need to run alone so that they do not disrupt other hardware counters."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:838
-msgid ""
-"Note that many unexpected situations may prevent events with the "
-"I<exclusive> bit set from ever running.  This includes any users running a "
-"system-wide measurement as well as any kernel use of the performance "
-"counters (including the commonly enabled NMI Watchdog Timer interface)."
+msgid "Note that many unexpected situations may prevent events with the I<exclusive> bit set from ever running.  This includes any users running a system-wide measurement as well as any kernel use of the performance counters (including the commonly enabled NMI Watchdog Timer interface)."
 msgstr ""
 
 #. type: TP
@@ -3801,8 +3056,7 @@ msgstr "I<exclude_user>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:841
-msgid ""
-"If this bit is set, the count excludes events that happen in user space."
+msgid "If this bit is set, the count excludes events that happen in user space."
 msgstr ""
 
 #. type: TP
@@ -3813,8 +3067,7 @@ msgstr "I<exclude_kernel>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:844
-msgid ""
-"If this bit is set, the count excludes events that happen in kernel-space."
+msgid "If this bit is set, the count excludes events that happen in kernel-space."
 msgstr ""
 
 #. type: TP
@@ -3825,11 +3078,7 @@ msgstr "I<exclude_hv>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:852
-msgid ""
-"If this bit is set, the count excludes events that happen in the "
-"hypervisor.  This is mainly for PMUs that have built-in support for handling "
-"this (such as POWER).  Extra support is needed for handling hypervisor "
-"measurements on most machines."
+msgid "If this bit is set, the count excludes events that happen in the hypervisor.  This is mainly for PMUs that have built-in support for handling this (such as POWER).  Extra support is needed for handling hypervisor measurements on most machines."
 msgstr ""
 
 #. type: TP
@@ -3851,11 +3100,7 @@ msgstr "I<mmap>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:869
-msgid ""
-"The I<mmap> bit enables generation of B<PERF_RECORD_MMAP> samples for every "
-"B<mmap>(2)  call that has B<PROT_EXEC> set.  This allows tools to notice new "
-"executable code being mapped into a program (dynamic shared libraries for "
-"example)  so that addresses can be mapped back to the original code."
+msgid "The I<mmap> bit enables generation of B<PERF_RECORD_MMAP> samples for every B<mmap>(2)  call that has B<PROT_EXEC> set.  This allows tools to notice new executable code being mapped into a program (dynamic shared libraries for example)  so that addresses can be mapped back to the original code."
 msgstr ""
 
 #. type: TP
@@ -3866,13 +3111,7 @@ msgstr "I<comm>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:887
-msgid ""
-"The I<comm> bit enables tracking of process command name as modified by the "
-"B<exec>(2)  and B<prctl>(PR_SET_NAME)  system calls as well as writing to I</"
-"proc/self/comm>.  If the I<comm_exec> flag is also successfully set "
-"(possible since Linux 3.16), then the misc flag "
-"B<PERF_RECORD_MISC_COMM_EXEC> can be used to differentiate the B<exec>(2)  "
-"case from the others."
+msgid "The I<comm> bit enables tracking of process command name as modified by the B<exec>(2)  and B<prctl>(PR_SET_NAME)  system calls as well as writing to I</proc/self/comm>.  If the I<comm_exec> flag is also successfully set (possible since Linux 3.16), then the misc flag B<PERF_RECORD_MISC_COMM_EXEC> can be used to differentiate the B<exec>(2)  case from the others."
 msgstr ""
 
 #. type: TP
@@ -3883,9 +3122,7 @@ msgstr "I<freq>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:894
-msgid ""
-"If this bit is set, then I<sample_frequency> not I<sample_period> is used "
-"when setting up the sampling interval."
+msgid "If this bit is set, then I<sample_frequency> not I<sample_period> is used when setting up the sampling interval."
 msgstr ""
 
 #. type: TP
@@ -3896,9 +3133,7 @@ msgstr "I<inherit_stat>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:901
-msgid ""
-"This bit enables saving of event counts on context switch for inherited "
-"tasks.  This is meaningful only if the I<inherit> field is set."
+msgid "This bit enables saving of event counts on context switch for inherited tasks.  This is meaningful only if the I<inherit> field is set."
 msgstr ""
 
 #. type: TP
@@ -3909,9 +3144,7 @@ msgstr "I<enable_on_exec>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:906
-msgid ""
-"If this bit is set, a counter is automatically enabled after a call to "
-"B<exec>(2)."
+msgid "If this bit is set, a counter is automatically enabled after a call to B<exec>(2)."
 msgstr ""
 
 #. type: TP
@@ -3922,9 +3155,7 @@ msgstr "I<task>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:910
-msgid ""
-"If this bit is set, then fork/exit notifications are included in the ring "
-"buffer."
+msgid "If this bit is set, then fork/exit notifications are included in the ring buffer."
 msgstr ""
 
 #. type: TP
@@ -3935,10 +3166,7 @@ msgstr "I<watermark>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:918
-msgid ""
-"If set, have an overflow notification happen when we cross the "
-"I<wakeup_watermark> boundary.  Otherwise, overflow notifications happen "
-"after I<wakeup_events> samples."
+msgid "If set, have an overflow notification happen when we cross the I<wakeup_watermark> boundary.  Otherwise, overflow notifications happen after I<wakeup_events> samples."
 msgstr ""
 
 #. type: TP
@@ -3949,12 +3177,7 @@ msgstr "I<precise_ip> (Linux 2.6.35 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:928
-msgid ""
-"This controls the amount of skid.  Skid is how many instructions execute "
-"between an event of interest happening and the kernel being able to stop and "
-"record the event.  Smaller skid is better and allows more accurate reporting "
-"of which events correspond to which instructions, but hardware is often "
-"limited with how small this can be."
+msgid "This controls the amount of skid.  Skid is how many instructions execute between an event of interest happening and the kernel being able to stop and record the event.  Smaller skid is better and allows more accurate reporting of which events correspond to which instructions, but hardware is often limited with how small this can be."
 msgstr ""
 
 #. type: Plain text
@@ -4014,10 +3237,7 @@ msgstr "I<mmap_data> (Linux 2.6.36 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:962
-msgid ""
-"The counterpart of the I<mmap> field.  This enables generation of "
-"B<PERF_RECORD_MMAP> samples for B<mmap>(2)  calls that do not have "
-"B<PROT_EXEC> set (for example data and SysV shared memory)."
+msgid "The counterpart of the I<mmap> field.  This enables generation of B<PERF_RECORD_MMAP> samples for B<mmap>(2)  calls that do not have B<PROT_EXEC> set (for example data and SysV shared memory)."
 msgstr ""
 
 #. type: TP
@@ -4028,18 +3248,12 @@ msgstr "I<sample_id_all> (Linux 2.6.38 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:970
-msgid ""
-"If set, then TID, TIME, ID, STREAM_ID, and CPU can additionally be included "
-"in non-B<PERF_RECORD_SAMPLE>s if the corresponding I<sample_type> is "
-"selected."
+msgid "If set, then TID, TIME, ID, STREAM_ID, and CPU can additionally be included in non-B<PERF_RECORD_SAMPLE>s if the corresponding I<sample_type> is selected."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:978
-msgid ""
-"If B<PERF_SAMPLE_IDENTIFIER> is specified, then an additional ID value is "
-"included as the last value to ease parsing the record stream.  This may lead "
-"to the I<id> value appearing twice."
+msgid "If B<PERF_SAMPLE_IDENTIFIER> is specified, then an additional ID value is included as the last value to ease parsing the record stream.  This may lead to the I<id> value appearing twice."
 msgstr ""
 
 #. type: Plain text
@@ -4121,10 +3335,7 @@ msgstr "I<mmap2> (Linux 3.16 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1010
-msgid ""
-"Generate an extended executable mmap record that contains enough additional "
-"information to uniquely identify shared mappings.  The I<mmap> flag must "
-"also be set for this to work."
+msgid "Generate an extended executable mmap record that contains enough additional information to uniquely identify shared mappings.  The I<mmap> flag must also be set for this to work."
 msgstr ""
 
 #. type: TP
@@ -4135,13 +3346,7 @@ msgstr "I<comm_exec> (Linux 3.16 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1025
-msgid ""
-"This is purely a feature-detection flag, it does not change kernel "
-"behavior.  If this flag can successfully be set, then, when I<comm> is "
-"enabled, the B<PERF_RECORD_MISC_COMM_EXEC> flag will be set in the I<misc> "
-"field of a comm record header if the rename event being reported was caused "
-"by a call to B<exec>(2).  This allows tools to distinguish between the "
-"various types of process renaming."
+msgid "This is purely a feature-detection flag, it does not change kernel behavior.  If this flag can successfully be set, then, when I<comm> is enabled, the B<PERF_RECORD_MISC_COMM_EXEC> flag will be set in the I<misc> field of a comm record header if the rename event being reported was caused by a call to B<exec>(2).  This allows tools to distinguish between the various types of process renaming."
 msgstr ""
 
 #. type: TP
@@ -4152,25 +3357,17 @@ msgstr "I<wakeup_events>, I<wakeup_watermark>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1035
-msgid ""
-"This union sets how many samples (I<wakeup_events>)  or bytes "
-"(I<wakeup_watermark>)  happen before an overflow notification happens.  "
-"Which one is used is selected by the I<watermark> bit flag."
+msgid "This union sets how many samples (I<wakeup_events>)  or bytes (I<wakeup_watermark>)  happen before an overflow notification happens.  Which one is used is selected by the I<watermark> bit flag."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1045
-msgid ""
-"I<wakeup_events> only counts B<PERF_RECORD_SAMPLE> record types.  To receive "
-"overflow notification for all B<PERF_RECORD> types choose watermark and set "
-"I<wakeup_watermark> to 1."
+msgid "I<wakeup_events> only counts B<PERF_RECORD_SAMPLE> record types.  To receive overflow notification for all B<PERF_RECORD> types choose watermark and set I<wakeup_watermark> to 1."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1050
-msgid ""
-"Prior to Linux 3.0 setting I<wakeup_events> to 0 resulted in no overflow "
-"notifications; more recent kernels treat 0 the same as 1."
+msgid "Prior to Linux 3.0 setting I<wakeup_events> to 0 resulted in no overflow notifications; more recent kernels treat 0 the same as 1."
 msgstr ""
 
 #. type: TP
@@ -4241,10 +3438,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1079
-msgid ""
-"The values can be combined via a bitwise or, but the combination of "
-"B<HW_BREAKPOINT_R> or B<HW_BREAKPOINT_W> with B<HW_BREAKPOINT_X> is not "
-"allowed."
+msgid "The values can be combined via a bitwise or, but the combination of B<HW_BREAKPOINT_R> or B<HW_BREAKPOINT_W> with B<HW_BREAKPOINT_X> is not allowed."
 msgstr ""
 
 #. type: TP
@@ -4255,10 +3449,7 @@ msgstr "I<bp_addr> (Linux 2.6.33 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1087
-msgid ""
-"I<bp_addr> address of the breakpoint.  For execution breakpoints this is the "
-"memory address of the instruction of interest; for read and write "
-"breakpoints it is the memory address of the memory location of interest."
+msgid "I<bp_addr> address of the breakpoint.  For execution breakpoints this is the memory address of the instruction of interest; for read and write breakpoints it is the memory address of the memory location of interest."
 msgstr ""
 
 #. type: TP
@@ -4269,10 +3460,7 @@ msgstr "I<config1> (Linux 2.6.39 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1094
-msgid ""
-"I<config1> is used for setting events that need an extra register or "
-"otherwise do not fit in the regular config field.  Raw OFFCORE_EVENTS on "
-"Nehalem/Westmere/SandyBridge use this field on 3.3 and later kernels."
+msgid "I<config1> is used for setting events that need an extra register or otherwise do not fit in the regular config field.  Raw OFFCORE_EVENTS on Nehalem/Westmere/SandyBridge use this field on 3.3 and later kernels."
 msgstr ""
 
 #. type: TP
@@ -4283,11 +3471,7 @@ msgstr "I<bp_len> (Linux 2.6.33 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1108
-msgid ""
-"I<bp_len> is the length of the breakpoint being measured if I<type> is "
-"B<PERF_TYPE_BREAKPOINT>.  Options are B<HW_BREAKPOINT_LEN_1>, "
-"B<HW_BREAKPOINT_LEN_2>, B<HW_BREAKPOINT_LEN_4>, B<HW_BREAKPOINT_LEN_8>.  For "
-"an execution breakpoint, set this to I<sizeof(long)>."
+msgid "I<bp_len> is the length of the breakpoint being measured if I<type> is B<PERF_TYPE_BREAKPOINT>.  Options are B<HW_BREAKPOINT_LEN_1>, B<HW_BREAKPOINT_LEN_2>, B<HW_BREAKPOINT_LEN_4>, B<HW_BREAKPOINT_LEN_8>.  For an execution breakpoint, set this to I<sizeof(long)>."
 msgstr ""
 
 #. type: TP
@@ -4309,18 +3493,12 @@ msgstr "I<branch_sample_type> (Linux 3.4 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1121
-msgid ""
-"If B<PERF_SAMPLE_BRANCH_STACK> is enabled, then this specifies what branches "
-"to include in the branch record."
+msgid "If B<PERF_SAMPLE_BRANCH_STACK> is enabled, then this specifies what branches to include in the branch record."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1127
-msgid ""
-"The first part of the value is the privilege level, which is a combination "
-"of one of the following values.  If the user does not set privilege level "
-"explicitly, the kernel will use the event's privilege level.  Event and "
-"branch privilege levels do not have to match."
+msgid "The first part of the value is the privilege level, which is a combination of one of the following values.  If the user does not set privilege level explicitly, the kernel will use the event's privilege level.  Event and branch privilege levels do not have to match."
 msgstr ""
 
 #. type: TP
@@ -4369,9 +3547,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1144
-msgid ""
-"In addition to the privilege value, at least one or more of the following "
-"bits must be set."
+msgid "In addition to the privilege value, at least one or more of the following bits must be set."
 msgstr ""
 
 #. type: TP
@@ -4474,10 +3650,7 @@ msgstr "I<sample_regs_user> (Linux 3.7 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1181
-msgid ""
-"This bit mask defines the set of user CPU registers to dump on samples.  The "
-"layout of the register mask is architecture-specific and described in the "
-"kernel header I<arch/ARCH/include/uapi/asm/perf_regs.h>."
+msgid "This bit mask defines the set of user CPU registers to dump on samples.  The layout of the register mask is architecture-specific and described in the kernel header I<arch/ARCH/include/uapi/asm/perf_regs.h>."
 msgstr ""
 
 #. type: TP
@@ -4488,9 +3661,7 @@ msgstr "I<sample_stack_user> (Linux 3.7 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1186
-msgid ""
-"This defines the size of the user stack to dump if B<PERF_SAMPLE_STACK_USER> "
-"is specified."
+msgid "This defines the size of the user stack to dump if B<PERF_SAMPLE_STACK_USER> is specified."
 msgstr ""
 
 #. type: SS
@@ -4501,18 +3672,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1196
-msgid ""
-"Once a B<perf_event_open>()  file descriptor has been opened, the values of "
-"the events can be read from the file descriptor.  The values that are there "
-"are specified by the I<read_format> field in the I<attr> structure at open "
-"time."
+msgid "Once a B<perf_event_open>()  file descriptor has been opened, the values of the events can be read from the file descriptor.  The values that are there are specified by the I<read_format> field in the I<attr> structure at open time."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1201
-msgid ""
-"If you attempt to read into a buffer that is not big enough to hold the data "
-"B<ENOSPC> is returned"
+msgid "If you attempt to read into a buffer that is not big enough to hold the data B<ENOSPC> is returned"
 msgstr ""
 
 #. type: Plain text
@@ -4532,9 +3697,7 @@ msgstr "*"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1207
-msgid ""
-"If B<PERF_FORMAT_GROUP> was specified to allow reading all events in a group "
-"at once:"
+msgid "If B<PERF_FORMAT_GROUP> was specified to allow reading all events in a group at once:"
 msgstr ""
 
 #. type: Plain text
@@ -4582,9 +3745,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1246
-msgid ""
-"The number of events in this file descriptor.  Only available if "
-"B<PERF_FORMAT_GROUP> was specified."
+msgid "The number of events in this file descriptor.  Only available if B<PERF_FORMAT_GROUP> was specified."
 msgstr ""
 
 #. type: TP
@@ -4595,12 +3756,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1258
-msgid ""
-"Total time the event was enabled and running.  Normally these are the same.  "
-"If more events are started, then available counter slots on the PMU, then "
-"multiplexing happens and events run only part of the time.  In that case, "
-"the I<time_enabled> and I<time running> values can be used to scale an "
-"estimated value for the count."
+msgid "Total time the event was enabled and running.  Normally these are the same.  If more events are started, then available counter slots on the PMU, then multiplexing happens and events run only part of the time.  In that case, the I<time_enabled> and I<time running> values can be used to scale an estimated value for the count."
 msgstr ""
 
 #. type: TP
@@ -4623,9 +3779,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1267
-msgid ""
-"A globally unique value for this particular event, only there if "
-"B<PERF_FORMAT_ID> was specified in I<read_format>."
+msgid "A globally unique value for this particular event, only there if B<PERF_FORMAT_ID> was specified in I<read_format>."
 msgstr ""
 
 #. type: SS
@@ -4636,25 +3790,17 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1277
-msgid ""
-"When using B<perf_event_open>()  in sampled mode, asynchronous events (like "
-"counter overflow or B<PROT_EXEC> mmap tracking)  are logged into a ring-"
-"buffer.  This ring-buffer is created and accessed through B<mmap>(2)."
+msgid "When using B<perf_event_open>()  in sampled mode, asynchronous events (like counter overflow or B<PROT_EXEC> mmap tracking)  are logged into a ring-buffer.  This ring-buffer is created and accessed through B<mmap>(2)."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1283
-msgid ""
-"The mmap size should be 1+2^n pages, where the first page is a metadata page "
-"(I<struct perf_event_mmap_page>)  that contains various bits of information "
-"such as where the ring-buffer head is."
+msgid "The mmap size should be 1+2^n pages, where the first page is a metadata page (I<struct perf_event_mmap_page>)  that contains various bits of information such as where the ring-buffer head is."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1286
-msgid ""
-"Before kernel 2.6.39, there is a bug that means you must allocate a mmap "
-"ring buffer when sampling even if you do not plan to access it."
+msgid "Before kernel 2.6.39, there is a bug that means you must allocate a mmap ring buffer when sampling even if you do not plan to access it."
 msgstr ""
 
 #. type: Plain text
@@ -4696,9 +3842,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1323
-msgid ""
-"The following list describes the fields in the I<perf_event_mmap_page> "
-"structure in more detail:"
+msgid "The following list describes the fields in the I<perf_event_mmap_page> structure in more detail:"
 msgstr ""
 
 #. type: TP
@@ -4753,9 +3897,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1340
-msgid ""
-"When using rdpmc for reads this offset value must be added to the one "
-"returned by rdpmc to get the current total event count."
+msgid "When using rdpmc for reads this offset value must be added to the one returned by rdpmc to get the current total event count."
 msgstr ""
 
 #. type: TP
@@ -4788,18 +3930,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1359
-msgid ""
-"There was a bug in the definition of I<cap_usr_time> and I<cap_usr_rdpmc> "
-"from Linux 3.4 until Linux 3.11.  Both bits were defined to point to the "
-"same location, so it was impossible to know if I<cap_usr_time> or "
-"I<cap_usr_rdpmc> were actually set."
+msgid "There was a bug in the definition of I<cap_usr_time> and I<cap_usr_rdpmc> from Linux 3.4 until Linux 3.11.  Both bits were defined to point to the same location, so it was impossible to know if I<cap_usr_time> or I<cap_usr_rdpmc> were actually set."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1367
-msgid ""
-"Starting with Linux 3.12, these are renamed to I<cap_bit0> and you should "
-"use the I<cap_user_time> and I<cap_user_rdpmc> fields instead."
+msgid "Starting with Linux 3.12, these are renamed to I<cap_bit0> and you should use the I<cap_user_time> and I<cap_user_rdpmc> fields instead."
 msgstr ""
 
 #. type: TP
@@ -4810,17 +3946,12 @@ msgstr "I<cap_bit0_is_deprecated> (Linux 3.12 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1376
-msgid ""
-"If set, this bit indicates that the kernel supports the properly separated "
-"I<cap_user_time> and I<cap_user_rdpmc> bits."
+msgid "If set, this bit indicates that the kernel supports the properly separated I<cap_user_time> and I<cap_user_rdpmc> bits."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1383
-msgid ""
-"If not-set, it indicates an older kernel where I<cap_usr_time> and "
-"I<cap_usr_rdpmc> map to the same bit and thus both features should be used "
-"with caution."
+msgid "If not-set, it indicates an older kernel where I<cap_usr_time> and I<cap_usr_rdpmc> map to the same bit and thus both features should be used with caution."
 msgstr ""
 
 #. type: TP
@@ -4831,10 +3962,7 @@ msgstr "I<cap_user_rdpmc> (Linux 3.12 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1389
-msgid ""
-"If the hardware supports user-space read of performance counters without "
-"syscall (this is the \"rdpmc\" instruction on x86), then the following code "
-"can be used to do a read:"
+msgid "If the hardware supports user-space read of performance counters without syscall (this is the \"rdpmc\" instruction on x86), then the following code can be used to do a read:"
 msgstr ""
 
 #. type: Plain text
@@ -4919,16 +4047,13 @@ msgstr ""
 
 #. type: TP
 #: build/C/man2/perf_event_open.2:1421
-#, fuzzy, no-wrap
-#| msgid "I<cap_user_time  (since Linux 3.12)>"
+#, no-wrap
 msgid "I<cap_user_time> (since Linux 3.12)"
-msgstr "I<cap_user_time  (Linux 3.12 以降)>"
+msgstr "I<cap_user_time> (Linux 3.12 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1425
-msgid ""
-"This bit indicates the hardware has a constant, nonstop timestamp counter "
-"(TSC on x86)."
+msgid "This bit indicates the hardware has a constant, nonstop timestamp counter (TSC on x86)."
 msgstr ""
 
 #. type: TP
@@ -4939,9 +4064,7 @@ msgstr "I<cap_user_time_zero> (Linux 3.12 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1431
-msgid ""
-"Indicates the presence of I<time_zero> which allows mapping timestamp values "
-"to the hardware clock."
+msgid "Indicates the presence of I<time_zero> which allows mapping timestamp values to the hardware clock."
 msgstr ""
 
 #. type: TP
@@ -4952,10 +4075,7 @@ msgstr "I<pmc_width>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1438
-msgid ""
-"If I<cap_usr_rdpmc>, this field provides the bit-width of the value read "
-"using the rdpmc or equivalent instruction.  This can be used to sign extend "
-"the result like:"
+msgid "If I<cap_usr_rdpmc>, this field provides the bit-width of the value read using the rdpmc or equivalent instruction.  This can be used to sign extend the result like:"
 msgstr ""
 
 #. type: Plain text
@@ -4978,9 +4098,7 @@ msgstr "I<time_shift>, I<time_mult>, I<time_offset>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1453
-msgid ""
-"If I<cap_usr_time>, these fields can be used to compute the time delta since "
-"time_enabled (in nanoseconds) using rdtsc or similar."
+msgid "If I<cap_usr_time>, these fields can be used to compute the time delta since time_enabled (in nanoseconds) using rdtsc or similar."
 msgstr ""
 
 #. type: Plain text
@@ -5003,10 +4121,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1473
-msgid ""
-"Where I<time_offset>, I<time_mult>, I<time_shift>, and I<cyc> are read in "
-"the seqcount loop described above.  This delta can then be added to enabled "
-"and possible running (if idx), improving the scaling:"
+msgid "Where I<time_offset>, I<time_mult>, I<time_shift>, and I<cyc> are read in the seqcount loop described above.  This delta can then be added to enabled and possible running (if idx), improving the scaling:"
 msgstr ""
 
 #. type: Plain text
@@ -5035,10 +4150,7 @@ msgstr "I<time_zero> (Linux 3.12 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1490
-msgid ""
-"If I<cap_usr_time_zero> is set, then the hardware clock (the TSC timestamp "
-"counter on x86)  can be calculated from the I<time_zero>, I<time_mult>, and "
-"I<time_shift> values:"
+msgid "If I<cap_usr_time_zero> is set, then the hardware clock (the TSC timestamp counter on x86)  can be calculated from the I<time_zero>, I<time_mult>, and I<time_shift> values:"
 msgstr ""
 
 #. type: Plain text
@@ -5082,17 +4194,12 @@ msgstr "I<data_head>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1512
-msgid ""
-"This points to the head of the data section.  The value continuously "
-"increases, it does not wrap.  The value needs to be manually wrapped by the "
-"size of the mmap buffer before accessing the samples."
+msgid "This points to the head of the data section.  The value continuously increases, it does not wrap.  The value needs to be manually wrapped by the size of the mmap buffer before accessing the samples."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1517
-msgid ""
-"On SMP-capable platforms, after reading the I<data_head> value, user space "
-"should issue an rmb()."
+msgid "On SMP-capable platforms, after reading the I<data_head> value, user space should issue an rmb()."
 msgstr ""
 
 #. type: TP
@@ -5103,10 +4210,7 @@ msgstr "I<data_tail>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1525
-msgid ""
-"When the mapping is B<PROT_WRITE>, the I<data_tail> value should be written "
-"by user space to reflect the last read data.  In this case, the kernel will "
-"not overwrite unread data."
+msgid "When the mapping is B<PROT_WRITE>, the I<data_tail> value should be written by user space to reflect the last read data.  In this case, the kernel will not overwrite unread data."
 msgstr ""
 
 #. type: Plain text
@@ -5116,14 +4220,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1541
-msgid ""
-"If I<perf_event_attr.sample_id_all> is set, then all event types will have "
-"the sample_type selected fields related to where/when (identity)  an event "
-"took place (TID, TIME, ID, CPU, STREAM_ID) described in "
-"B<PERF_RECORD_SAMPLE> below, it will be stashed just after the "
-"I<perf_event_header> and the fields already present for the existing fields, "
-"that is, at the end of the payload.  That way a newer perf.data file will be "
-"supported by older perf tools, with these new optional fields being ignored."
+msgid "If I<perf_event_attr.sample_id_all> is set, then all event types will have the sample_type selected fields related to where/when (identity)  an event took place (TID, TIME, ID, CPU, STREAM_ID) described in B<PERF_RECORD_SAMPLE> below, it will be stashed just after the I<perf_event_header> and the fields already present for the existing fields, that is, at the end of the payload.  That way a newer perf.data file will be supported by older perf tools, with these new optional fields being ignored."
 msgstr ""
 
 #. type: Plain text
@@ -5149,9 +4246,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1559
-msgid ""
-"Below, we describe the I<perf_event_header> fields in more detail.  For ease "
-"of reading, the fields with shorter descriptions are presented first."
+msgid "Below, we describe the I<perf_event_header> fields in more detail.  For ease of reading, the fields with shorter descriptions are presented first."
 msgstr ""
 
 #. type: Plain text
@@ -5172,10 +4267,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1572
-msgid ""
-"The CPU mode can be determined from this value by masking with "
-"B<PERF_RECORD_MISC_CPUMODE_MASK> and looking for one of the following (note "
-"these are not bit masks, only one can be set at a time):"
+msgid "The CPU mode can be determined from this value by masking with B<PERF_RECORD_MISC_CPUMODE_MASK> and looking for one of the following (note these are not bit masks, only one can be set at a time):"
 msgstr ""
 
 #. type: TP
@@ -5224,10 +4316,9 @@ msgstr ""
 
 #. type: TP
 #: build/C/man2/perf_event_open.2:1585
-#, fuzzy, no-wrap
-#| msgid "B<PERF_RECORD_MISC_GUEST_KERNEL>"
+#, no-wrap
 msgid "B<PERF_RECORD_MISC_GUEST_KERNEL> (since Linux2.6.35)"
-msgstr "B<PERF_RECORD_MISC_GUEST_KERNEL>"
+msgstr "B<PERF_RECORD_MISC_GUEST_KERNEL> (Linux 2.6.35 以降)"
 
 #.  commit 39447b386c846bbf1c56f6403c5282837486200f
 #. type: Plain text
@@ -5237,10 +4328,9 @@ msgstr ""
 
 #. type: TP
 #: build/C/man2/perf_event_open.2:1589
-#, fuzzy, no-wrap
-#| msgid "B<PERF_RECORD_MISC_GUEST_USER>"
+#, no-wrap
 msgid "B<PERF_RECORD_MISC_GUEST_USER  (since Linux2.6.35)>"
-msgstr "B<PERF_RECORD_MISC_GUEST_USER>"
+msgstr "B<PERF_RECORD_MISC_GUEST_USER  (Linux 2.6.35 以降)>"
 
 #.  commit 39447b386c846bbf1c56f6403c5282837486200f
 #. type: Plain text
@@ -5255,34 +4345,26 @@ msgstr ""
 
 #. type: TP
 #: build/C/man2/perf_event_open.2:1597
-#, fuzzy, no-wrap
-#| msgid "B<PERF_SAMPLE_DATA_SRC> (since Linux 3.10)"
+#, no-wrap
 msgid "B<PERF_RECORD_MISC_MMAP_DATA> (since Linux 3.10)"
-msgstr "B<PERF_SAMPLE_DATA_SRC> (Linux 3.10 以降)"
+msgstr "B<PERF_RECORD_MISC_MMAP_DATA> (Linux 3.10 以降)"
 
 #.  commit 2fe85427e3bf65d791700d065132772fc26e4d75
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1602
-msgid ""
-"This is set when the mapping is not executable; otherwise the mapping is "
-"executable."
+msgid "This is set when the mapping is not executable; otherwise the mapping is executable."
 msgstr ""
 
 #. type: TP
 #: build/C/man2/perf_event_open.2:1602
-#, fuzzy, no-wrap
-#| msgid "B<PERF_RECORD_MISC_COMM_EXEC>"
+#, no-wrap
 msgid "B<PERF_RECORD_MISC_COMM_EXEC> (since Linux 3.16)"
-msgstr "B<PERF_RECORD_MISC_COMM_EXEC>"
+msgstr "B<PERF_RECORD_MISC_COMM_EXEC> (Linux 3.16 以降)"
 
 #.  commit 82b897782d10fcc4930c9d4a15b175348fdd2871
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1614
-msgid ""
-"This is set for a B<PERF_RECORD_COMM> record on kernels more recent than "
-"Linux 3.16 if a process name change was caused by an B<exec>(2)  system "
-"call.  It is an alias for B<PERF_RECORD_MISC_MMAP_DATA> since the two values "
-"would not be set in the same record."
+msgid "This is set for a B<PERF_RECORD_COMM> record on kernels more recent than Linux 3.16 if a process name change was caused by an B<exec>(2)  system call.  It is an alias for B<PERF_RECORD_MISC_MMAP_DATA> since the two values would not be set in the same record."
 msgstr ""
 
 #. type: TP
@@ -5293,18 +4375,14 @@ msgstr "B<PERF_RECORD_MISC_EXACT_IP>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1622
-msgid ""
-"This indicates that the content of B<PERF_SAMPLE_IP> points to the actual "
-"instruction that triggered the event.  See also I<perf_event_attr."
-"precise_ip>."
+msgid "This indicates that the content of B<PERF_SAMPLE_IP> points to the actual instruction that triggered the event.  See also I<perf_event_attr.precise_ip>."
 msgstr ""
 
 #. type: TP
 #: build/C/man2/perf_event_open.2:1622
-#, fuzzy, no-wrap
-#| msgid "B<PERF_RECORD_MISC_EXT_RESERVED>"
+#, no-wrap
 msgid "B<PERF_RECORD_MISC_EXT_RESERVED> (since Linux 2.6.35)"
-msgstr "B<PERF_RECORD_MISC_EXT_RESERVED>"
+msgstr "B<PERF_RECORD_MISC_EXT_RESERVED> (Linux 2.6.35 以降)"
 
 #.  commit 1676b8a077c352085d52578fb4f29350b58b6e74
 #. type: Plain text
@@ -5314,9 +4392,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1636
-msgid ""
-"The I<type> value is one of the below.  The values in the corresponding "
-"record (that follows the header)  depend on the I<type> selected as shown."
+msgid "The I<type> value is one of the below.  The values in the corresponding record (that follows the header)  depend on the I<type> selected as shown."
 msgstr ""
 
 #. type: TP
@@ -5327,9 +4403,7 @@ msgstr "B<PERF_RECORD_MMAP>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1645
-msgid ""
-"The MMAP events record the B<PROT_EXEC> mappings so that we can correlate "
-"user-space IPs to code.  They have the following structure:"
+msgid "The MMAP events record the B<PROT_EXEC> mappings so that we can correlate user-space IPs to code.  They have the following structure:"
 msgstr ""
 
 #. type: Plain text
@@ -5389,10 +4463,7 @@ msgstr "I<addr>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1674
-msgid ""
-"is the address of the allocated memory.  I<len> is the length of the "
-"allocated memory.  I<pgoff> is the page offset of the allocated memory.  "
-"I<filename> is a string describing the backing of the allocated memory."
+msgid "is the address of the allocated memory.  I<len> is the length of the allocated memory.  I<pgoff> is the page offset of the allocated memory.  I<filename> is a string describing the backing of the allocated memory."
 msgstr ""
 
 #. type: TP
@@ -5661,10 +4732,7 @@ msgstr "I<sample_id>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1829
-msgid ""
-"If B<PERF_SAMPLE_IDENTIFIER> is enabled, a 64-bit unique ID is included.  "
-"This is a duplication of the B<PERF_SAMPLE_ID> I<id> value, but included at "
-"the beginning of the sample so parsers can easily obtain the value."
+msgid "If B<PERF_SAMPLE_IDENTIFIER> is enabled, a 64-bit unique ID is included.  This is a duplication of the B<PERF_SAMPLE_ID> I<id> value, but included at the beginning of the sample so parsers can easily obtain the value."
 msgstr ""
 
 #. type: TP
@@ -5675,9 +4743,7 @@ msgstr "I<ip>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1835
-msgid ""
-"If B<PERF_SAMPLE_IP> is enabled, then a 64-bit instruction pointer value is "
-"included."
+msgid "If B<PERF_SAMPLE_IP> is enabled, then a 64-bit instruction pointer value is included."
 msgstr ""
 
 #. type: TP
@@ -5688,9 +4754,7 @@ msgstr "I<pid>, I<tid>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1841
-msgid ""
-"If B<PERF_SAMPLE_TID> is enabled, then a 32-bit process ID and 32-bit thread "
-"ID are included."
+msgid "If B<PERF_SAMPLE_TID> is enabled, then a 32-bit process ID and 32-bit thread ID are included."
 msgstr ""
 
 #. type: TP
@@ -5701,26 +4765,17 @@ msgstr "I<time>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1849
-msgid ""
-"If B<PERF_SAMPLE_TIME> is enabled, then a 64-bit timestamp is included.  "
-"This is obtained via local_clock() which is a hardware timestamp if "
-"available and the jiffies value if not."
+msgid "If B<PERF_SAMPLE_TIME> is enabled, then a 64-bit timestamp is included.  This is obtained via local_clock() which is a hardware timestamp if available and the jiffies value if not."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1856
-msgid ""
-"If B<PERF_SAMPLE_ADDR> is enabled, then a 64-bit address is included.  This "
-"is usually the address of a tracepoint, breakpoint, or software event; "
-"otherwise the value is 0."
+msgid "If B<PERF_SAMPLE_ADDR> is enabled, then a 64-bit address is included.  This is usually the address of a tracepoint, breakpoint, or software event; otherwise the value is 0."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1864
-msgid ""
-"If B<PERF_SAMPLE_ID> is enabled, a 64-bit unique ID is included.  If the "
-"event is a member of an event group, the group leader ID is returned.  This "
-"ID is the same as the one returned by B<PERF_FORMAT_ID>."
+msgid "If B<PERF_SAMPLE_ID> is enabled, a 64-bit unique ID is included.  If the event is a member of an event group, the group leader ID is returned.  This ID is the same as the one returned by B<PERF_FORMAT_ID>."
 msgstr ""
 
 #. type: TP
@@ -5731,10 +4786,7 @@ msgstr "I<stream_id>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1874
-msgid ""
-"If B<PERF_SAMPLE_STREAM_ID> is enabled, a 64-bit unique ID is included.  "
-"Unlike B<PERF_SAMPLE_ID> the actual ID is returned, not the group leader.  "
-"This ID is the same as the one returned by B<PERF_FORMAT_ID>."
+msgid "If B<PERF_SAMPLE_STREAM_ID> is enabled, a 64-bit unique ID is included.  Unlike B<PERF_SAMPLE_ID> the actual ID is returned, not the group leader.  This ID is the same as the one returned by B<PERF_FORMAT_ID>."
 msgstr ""
 
 #. type: TP
@@ -5745,9 +4797,7 @@ msgstr "I<cpu>, I<res>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1881
-msgid ""
-"If B<PERF_SAMPLE_CPU> is enabled, this is a 32-bit value indicating which "
-"CPU was being used, in addition to a reserved (unused)  32-bit value."
+msgid "If B<PERF_SAMPLE_CPU> is enabled, this is a 32-bit value indicating which CPU was being used, in addition to a reserved (unused)  32-bit value."
 msgstr ""
 
 #. type: TP
@@ -5758,9 +4808,7 @@ msgstr "I<period>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1887
-msgid ""
-"If B<PERF_SAMPLE_PERIOD> is enabled, a 64-bit value indicating the current "
-"sampling period is written."
+msgid "If B<PERF_SAMPLE_PERIOD> is enabled, a 64-bit value indicating the current sampling period is written."
 msgstr ""
 
 #. type: TP
@@ -5771,11 +4819,7 @@ msgstr "I<v>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1898
-msgid ""
-"If B<PERF_SAMPLE_READ> is enabled, a structure of type read_format is "
-"included which has values for all events in the event group.  The values "
-"included depend on the I<read_format> value used at B<perf_event_open>()  "
-"time."
+msgid "If B<PERF_SAMPLE_READ> is enabled, a structure of type read_format is included which has values for all events in the event group.  The values included depend on the I<read_format> value used at B<perf_event_open>()  time."
 msgstr ""
 
 #. type: TP
@@ -5786,10 +4830,7 @@ msgstr "I<nr>, I<ips[nr]>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1906
-msgid ""
-"If B<PERF_SAMPLE_CALLCHAIN> is enabled, then a 64-bit number is included "
-"which indicates how many following 64-bit instruction pointers will follow.  "
-"This is the current callchain."
+msgid "If B<PERF_SAMPLE_CALLCHAIN> is enabled, then a 64-bit number is included which indicates how many following 64-bit instruction pointers will follow.  This is the current callchain."
 msgstr ""
 
 #. type: TP
@@ -5800,18 +4841,12 @@ msgstr "I<size>, I<data[size]>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1913
-msgid ""
-"If B<PERF_SAMPLE_RAW> is enabled, then a 32-bit value indicating size is "
-"included followed by an array of 8-bit values of length size.  The values "
-"are padded with 0 to have 64-bit alignment."
+msgid "If B<PERF_SAMPLE_RAW> is enabled, then a 32-bit value indicating size is included followed by an array of 8-bit values of length size.  The values are padded with 0 to have 64-bit alignment."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1918
-msgid ""
-"This RAW record data is opaque with respect to the ABI.  The ABI doesn't "
-"make any promises with respect to the stability of its content, it may vary "
-"depending on event, hardware, and kernel version."
+msgid "This RAW record data is opaque with respect to the ABI.  The ABI doesn't make any promises with respect to the stability of its content, it may vary depending on event, hardware, and kernel version."
 msgstr ""
 
 #. type: TP
@@ -5822,10 +4857,7 @@ msgstr "I<bnr>, I<lbr[bnr]>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1927
-msgid ""
-"If B<PERF_SAMPLE_BRANCH_STACK> is enabled, then a 64-bit value indicating "
-"the number of records is included, followed by I<bnr> I<perf_branch_entry> "
-"structures which each include the fields:"
+msgid "If B<PERF_SAMPLE_BRANCH_STACK> is enabled, then a 64-bit value indicating the number of records is included, followed by I<bnr> I<perf_branch_entry> structures which each include the fields:"
 msgstr ""
 
 #. type: TP
@@ -5896,23 +4928,17 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1950
-msgid ""
-"The entries are from most to least recent, so the first entry has the most "
-"recent branch."
+msgid "The entries are from most to least recent, so the first entry has the most recent branch."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1957
-msgid ""
-"Support for I<mispred> and I<predicted> is optional; if not supported, both "
-"values will be 0."
+msgid "Support for I<mispred> and I<predicted> is optional; if not supported, both values will be 0."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1961
-msgid ""
-"The type of branches recorded is specified by the I<branch_sample_type> "
-"field."
+msgid "The type of branches recorded is specified by the I<branch_sample_type> field."
 msgstr ""
 
 #. type: TP
@@ -5923,24 +4949,17 @@ msgstr "I<abi>, I<regs[weight(mask)]>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1968
-msgid ""
-"If B<PERF_SAMPLE_REGS_USER> is enabled, then the user CPU registers are "
-"recorded."
+msgid "If B<PERF_SAMPLE_REGS_USER> is enabled, then the user CPU registers are recorded."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1974
-msgid ""
-"The I<abi> field is one of B<PERF_SAMPLE_REGS_ABI_NONE>, "
-"B<PERF_SAMPLE_REGS_ABI_32> or B<PERF_SAMPLE_REGS_ABI_64>."
+msgid "The I<abi> field is one of B<PERF_SAMPLE_REGS_ABI_NONE>, B<PERF_SAMPLE_REGS_ABI_32> or B<PERF_SAMPLE_REGS_ABI_64>."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:1984
-msgid ""
-"The I<regs> field is an array of the CPU registers that were specified by "
-"the I<sample_regs_user> attr field.  The number of values is the number of "
-"bits set in the I<sample_regs_user> bit mask."
+msgid "The I<regs> field is an array of the CPU registers that were specified by the I<sample_regs_user> attr field.  The number of values is the number of bits set in the I<sample_regs_user> bit mask."
 msgstr ""
 
 #. type: TP
@@ -5951,13 +4970,7 @@ msgstr "I<size>, I<data[size]>, I<dyn_size>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2000
-msgid ""
-"If B<PERF_SAMPLE_STACK_USER> is enabled, then the user stack is recorded.  "
-"This can be used to generate stack backtraces.  I<size> is the size "
-"requested by the user in I<sample_stack_user> or else the maximum record "
-"size.  I<data> is the stack data (a raw dump of the memory pointed to by the "
-"stack pointer at the time of sampling).  I<dyn_size> is the amount of data "
-"actually dumped (can be less than I<size>)."
+msgid "If B<PERF_SAMPLE_STACK_USER> is enabled, then the user stack is recorded.  This can be used to generate stack backtraces.  I<size> is the size requested by the user in I<sample_stack_user> or else the maximum record size.  I<data> is the stack data (a raw dump of the memory pointed to by the stack pointer at the time of sampling).  I<dyn_size> is the amount of data actually dumped (can be less than I<size>)."
 msgstr ""
 
 #. type: TP
@@ -5968,10 +4981,7 @@ msgstr "I<weight>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2008
-msgid ""
-"If B<PERF_SAMPLE_WEIGHT> is enabled, then a 64-bit value provided by the "
-"hardware is recorded that indicates how costly the event was.  This allows "
-"expensive events to stand out more clearly in profiles."
+msgid "If B<PERF_SAMPLE_WEIGHT> is enabled, then a 64-bit value provided by the hardware is recorded that indicates how costly the event was.  This allows expensive events to stand out more clearly in profiles."
 msgstr ""
 
 #. type: TP
@@ -5982,9 +4992,7 @@ msgstr "I<data_src>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2014
-msgid ""
-"If B<PERF_SAMPLE_DATA_SRC> is enabled, then a 64-bit value is recorded that "
-"is made up of the following fields:"
+msgid "If B<PERF_SAMPLE_DATA_SRC> is enabled, then a 64-bit value is recorded that is made up of the following fields:"
 msgstr ""
 
 #. type: TP
@@ -6063,9 +5071,7 @@ msgstr "I<mem_lvl>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2043
-msgid ""
-"Memory hierarchy level hit or miss, a bitwise combination of the following, "
-"shifted left by B<PERF_MEM_LVL_SHIFT>:"
+msgid "Memory hierarchy level hit or miss, a bitwise combination of the following, shifted left by B<PERF_MEM_LVL_SHIFT>:"
 msgstr ""
 
 #. type: TP
@@ -6225,9 +5231,7 @@ msgstr "I<mem_snoop>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2094
-msgid ""
-"Snoop mode, a bitwise combination of the following, shifted left by "
-"B<PERF_MEM_SNOOP_SHIFT>:"
+msgid "Snoop mode, a bitwise combination of the following, shifted left by B<PERF_MEM_SNOOP_SHIFT>:"
 msgstr ""
 
 #. type: TP
@@ -6288,9 +5292,7 @@ msgstr "I<mem_lock>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2118
-msgid ""
-"Lock instruction, a bitwise combination of the following, shifted left by "
-"B<PERF_MEM_LOCK_SHIFT>:"
+msgid "Lock instruction, a bitwise combination of the following, shifted left by B<PERF_MEM_LOCK_SHIFT>:"
 msgstr ""
 
 #. type: TP
@@ -6318,9 +5320,7 @@ msgstr "I<mem_dtlb>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2134
-msgid ""
-"TLB access hit or miss, a bitwise combination of the following, shifted left "
-"by B<PERF_MEM_TLB_SHIFT>:"
+msgid "TLB access hit or miss, a bitwise combination of the following, shifted left by B<PERF_MEM_TLB_SHIFT>:"
 msgstr ""
 
 #. type: TP
@@ -6393,9 +5393,7 @@ msgstr "I<transaction>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2167
-msgid ""
-"If the B<PERF_SAMPLE_TRANSACTION> flag is set, then a 64-bit field is "
-"recorded describing the sources of any transactional memory aborts."
+msgid "If the B<PERF_SAMPLE_TRANSACTION> flag is set, then a 64-bit field is recorded describing the sources of any transactional memory aborts."
 msgstr ""
 
 #. type: Plain text
@@ -6493,10 +5491,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2201
-msgid ""
-"In addition, a user-specified abort code can be obtained from the high 32 "
-"bits of the field by shifting right by B<PERF_TXN_ABORT_SHIFT> and masking "
-"with B<PERF_TXN_ABORT_MASK>."
+msgid "In addition, a user-specified abort code can be obtained from the high 32 bits of the field by shifting right by B<PERF_TXN_ABORT_SHIFT> and masking with B<PERF_TXN_ABORT_MASK>."
 msgstr ""
 
 #. type: TP
@@ -6507,11 +5502,7 @@ msgstr "B<PERF_RECORD_MMAP2>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2211
-msgid ""
-"This record includes extended information on B<mmap>(2)  calls returning "
-"executable mappings.  The format is similar to that of the "
-"B<PERF_RECORD_MMAP> record, but includes extra values that allow uniquely "
-"identifying shared mappings."
+msgid "This record includes extended information on B<mmap>(2)  calls returning executable mappings.  The format is similar to that of the B<PERF_RECORD_MMAP> record, but includes extra values that allow uniquely identifying shared mappings."
 msgstr ""
 
 #. type: Plain text
@@ -6664,19 +5655,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2283
-msgid ""
-"Events can be set to notify when a threshold is crossed, indicating an "
-"overflow.  Overflow conditions can be captured by monitoring the event file "
-"descriptor with B<poll>(2), B<select>(2), or B<epoll>(2).  Alternately, a "
-"SIGIO signal handler can be created and the event configured with "
-"B<fcntl>(2)  to generate SIGIO signals."
+msgid "Events can be set to notify when a threshold is crossed, indicating an overflow.  Overflow conditions can be captured by monitoring the event file descriptor with B<poll>(2), B<select>(2), or B<epoll>(2).  Alternately, a SIGIO signal handler can be created and the event configured with B<fcntl>(2)  to generate SIGIO signals."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2287
-msgid ""
-"Overflows are only generated by sampling events (I<sample_period> must have "
-"a nonzero value)."
+msgid "Overflows are only generated by sampling events (I<sample_period> must have a nonzero value)."
 msgstr ""
 
 #. type: Plain text
@@ -6686,26 +5670,17 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2299
-msgid ""
-"The first is to set a I<wakeup_events> or I<wakeup_watermark> value that "
-"will trigger if a certain number of samples or bytes have been written to "
-"the mmap ring buffer.  In this case B<POLL_IN> is indicated."
+msgid "The first is to set a I<wakeup_events> or I<wakeup_watermark> value that will trigger if a certain number of samples or bytes have been written to the mmap ring buffer.  In this case B<POLL_IN> is indicated."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2311
-msgid ""
-"The other way is by use of the B<PERF_EVENT_IOC_REFRESH> ioctl.  This ioctl "
-"adds to a counter that decrements each time the event overflows.  When "
-"nonzero, B<POLL_IN> is indicated, but once the counter reaches 0 B<POLL_HUP> "
-"is indicated and the underlying event is disabled."
+msgid "The other way is by use of the B<PERF_EVENT_IOC_REFRESH> ioctl.  This ioctl adds to a counter that decrements each time the event overflows.  When nonzero, B<POLL_IN> is indicated, but once the counter reaches 0 B<POLL_HUP> is indicated and the underlying event is disabled."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2316
-msgid ""
-"Starting with Linux 3.18, B<POLL_HUP> is indicated if the event being "
-"monitored is attached to a different process and that process exits."
+msgid "Starting with Linux 3.18, B<POLL_HUP> is indicated if the event being monitored is attached to a different process and that process exits."
 msgstr ""
 
 #. type: SS
@@ -6716,19 +5691,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2323
-msgid ""
-"Starting with Linux 3.4 on x86, you can use the I<rdpmc> instruction to get "
-"low-latency reads without having to enter the kernel.  Note that using "
-"I<rdpmc> is not necessarily faster than other methods for reading event "
-"values."
+msgid "Starting with Linux 3.4 on x86, you can use the I<rdpmc> instruction to get low-latency reads without having to enter the kernel.  Note that using I<rdpmc> is not necessarily faster than other methods for reading event values."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2328
-msgid ""
-"Support for this can be detected with the I<cap_usr_rdpmc> field in the mmap "
-"page; documentation on how to calculate event values can be found in that "
-"section."
+msgid "Support for this can be detected with the I<cap_usr_rdpmc> field in the mmap page; documentation on how to calculate event values can be found in that section."
 msgstr ""
 
 #. type: SS
@@ -6750,17 +5718,12 @@ msgstr "B<PERF_EVENT_IOC_ENABLE>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2337
-msgid ""
-"This enables the individual event or event group specified by the file "
-"descriptor argument."
+msgid "This enables the individual event or event group specified by the file descriptor argument."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2343
-msgid ""
-"If the B<PERF_IOC_FLAG_GROUP> bit is set in the ioctl argument, then all "
-"events in a group are enabled, even if the event specified is not the group "
-"leader (but see BUGS)."
+msgid "If the B<PERF_IOC_FLAG_GROUP> bit is set in the ioctl argument, then all events in a group are enabled, even if the event specified is not the group leader (but see BUGS)."
 msgstr ""
 
 #. type: TP
@@ -6771,27 +5734,17 @@ msgstr "B<PERF_EVENT_IOC_DISABLE>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2347
-msgid ""
-"This disables the individual counter or event group specified by the file "
-"descriptor argument."
+msgid "This disables the individual counter or event group specified by the file descriptor argument."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2354
-msgid ""
-"Enabling or disabling the leader of a group enables or disables the entire "
-"group; that is, while the group leader is disabled, none of the counters in "
-"the group will count.  Enabling or disabling a member of a group other than "
-"the leader affects only that counter; disabling a non-leader stops that "
-"counter from counting but doesn't affect any other counter."
+msgid "Enabling or disabling the leader of a group enables or disables the entire group; that is, while the group leader is disabled, none of the counters in the group will count.  Enabling or disabling a member of a group other than the leader affects only that counter; disabling a non-leader stops that counter from counting but doesn't affect any other counter."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2360
-msgid ""
-"If the B<PERF_IOC_FLAG_GROUP> bit is set in the ioctl argument, then all "
-"events in a group are disabled, even if the event specified is not the group "
-"leader (but see BUGS)."
+msgid "If the B<PERF_IOC_FLAG_GROUP> bit is set in the ioctl argument, then all events in a group are disabled, even if the event specified is not the group leader (but see BUGS)."
 msgstr ""
 
 #. type: TP
@@ -6802,14 +5755,7 @@ msgstr "B<PERF_EVENT_IOC_REFRESH>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2374
-msgid ""
-"Non-inherited overflow counters can use this to enable a counter for a "
-"number of overflows specified by the argument, after which it is disabled.  "
-"Subsequent calls of this ioctl add the argument value to the current count.  "
-"An overflow notification with B<POLL_IN> set will happen on each overflow "
-"until the count reaches 0; when that happens a notification with B<POLL_HUP> "
-"set is sent and the event is disabled.  Using an argument of 0 is considered "
-"undefined behavior."
+msgid "Non-inherited overflow counters can use this to enable a counter for a number of overflows specified by the argument, after which it is disabled.  Subsequent calls of this ioctl add the argument value to the current count.  An overflow notification with B<POLL_IN> set will happen on each overflow until the count reaches 0; when that happens a notification with B<POLL_HUP> set is sent and the event is disabled.  Using an argument of 0 is considered undefined behavior."
 msgstr ""
 
 #. type: TP
@@ -6820,18 +5766,12 @@ msgstr "B<PERF_EVENT_IOC_RESET>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2384
-msgid ""
-"Reset the event count specified by the file descriptor argument to zero.  "
-"This resets only the counts; there is no way to reset the multiplexing "
-"I<time_enabled> or I<time_running> values."
+msgid "Reset the event count specified by the file descriptor argument to zero.  This resets only the counts; there is no way to reset the multiplexing I<time_enabled> or I<time_running> values."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2390
-msgid ""
-"If the B<PERF_IOC_FLAG_GROUP> bit is set in the ioctl argument, then all "
-"events in a group are reset, even if the event specified is not the group "
-"leader (but see BUGS)."
+msgid "If the B<PERF_IOC_FLAG_GROUP> bit is set in the ioctl argument, then all events in a group are reset, even if the event specified is not the group leader (but see BUGS)."
 msgstr ""
 
 #. type: TP
@@ -6847,23 +5787,17 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2398
-msgid ""
-"Since Linux 3.7 (on ARM) and Linux 3.14 (all other architectures), the new "
-"period takes effect immediately.  On older kernels, the new period did not "
-"take effect until after the next overflow."
+msgid "Since Linux 3.7 (on ARM) and Linux 3.14 (all other architectures), the new period takes effect immediately.  On older kernels, the new period did not take effect until after the next overflow."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2401
-msgid ""
-"The argument is a pointer to a 64-bit value containing the desired new "
-"period."
+msgid "The argument is a pointer to a 64-bit value containing the desired new period."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2404
-msgid ""
-"Prior to Linux 2.6.36 this ioctl always failed due to a bug in the kernel."
+msgid "Prior to Linux 2.6.36 this ioctl always failed due to a bug in the kernel."
 msgstr ""
 
 #. type: TP
@@ -6874,17 +5808,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2410
-msgid ""
-"This tells the kernel to report event notifications to the specified file "
-"descriptor rather than the default one.  The file descriptors must all be on "
-"the same CPU."
+msgid "This tells the kernel to report event notifications to the specified file descriptor rather than the default one.  The file descriptors must all be on the same CPU."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2413
-msgid ""
-"The argument specifies the desired file descriptor, or -1 if output should "
-"be ignored."
+msgid "The argument specifies the desired file descriptor, or -1 if output should be ignored."
 msgstr ""
 
 #. type: TP
@@ -6918,8 +5847,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2426
-msgid ""
-"The argument is a pointer to a 64-bit unsigned integer to hold the result."
+msgid "The argument is a pointer to a 64-bit unsigned integer to hold the result."
 msgstr ""
 
 #. type: SS
@@ -6930,14 +5858,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2439
-msgid ""
-"A process can enable or disable all the event groups that are attached to it "
-"using the B<prctl>(2)  B<PR_TASK_PERF_EVENTS_ENABLE> and "
-"B<PR_TASK_PERF_EVENTS_DISABLE> operations.  This applies to all counters on "
-"the calling process, whether created by this process or by another, and does "
-"not affect any counters that this process has created on other processes.  "
-"It enables or disables only the group leaders, not any other members in the "
-"groups."
+msgid "A process can enable or disable all the event groups that are attached to it using the B<prctl>(2)  B<PR_TASK_PERF_EVENTS_ENABLE> and B<PR_TASK_PERF_EVENTS_DISABLE> operations.  This applies to all counters on the calling process, whether created by this process or by another, and does not affect any counters that this process has created on other processes.  It enables or disables only the group leaders, not any other members in the groups."
 msgstr ""
 
 #. type: SS
@@ -6959,9 +5880,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2449
-msgid ""
-"The I<perf_event_paranoid> file can be set to restrict access to the "
-"performance counters."
+msgid "The I<perf_event_paranoid> file can be set to restrict access to the performance counters."
 msgstr ""
 
 #. type: IP
@@ -7010,9 +5929,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2464
-msgid ""
-"The existence of the I<perf_event_paranoid> file is the official method for "
-"determining if a kernel supports B<perf_event_open>()."
+msgid "The existence of the I<perf_event_paranoid> file is the official method for determining if a kernel supports B<perf_event_open>()."
 msgstr ""
 
 #. type: TP
@@ -7023,10 +5940,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2473
-msgid ""
-"This sets the maximum sample rate.  Setting this too high can allow users to "
-"sample at a rate that impacts overall machine performance and potentially "
-"lock up the machine.  The default value is 100000 (samples per second)."
+msgid "This sets the maximum sample rate.  Setting this too high can allow users to sample at a rate that impacts overall machine performance and potentially lock up the machine.  The default value is 100000 (samples per second)."
 msgstr ""
 
 #. type: TP
@@ -7037,9 +5951,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2479
-msgid ""
-"Maximum number of pages an unprivileged user can B<mlock>(2).  The default "
-"is 516 (kB)."
+msgid "Maximum number of pages an unprivileged user can B<mlock>(2).  The default is 516 (kB)."
 msgstr ""
 
 #. type: Plain text
@@ -7049,11 +5961,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2489
-msgid ""
-"Since Linux 2.6.34, the kernel supports having multiple PMUs available for "
-"monitoring.  Information on how to program these PMUs can be found under I</"
-"sys/bus/event_source/devices/>.  Each subdirectory corresponds to a "
-"different PMU."
+msgid "Since Linux 2.6.34, the kernel supports having multiple PMUs available for monitoring.  Information on how to program these PMUs can be found under I</sys/bus/event_source/devices/>.  Each subdirectory corresponds to a different PMU."
 msgstr ""
 
 #. type: TP
@@ -7064,9 +5972,7 @@ msgstr "I</sys/bus/event_source/devices/*/type> (Linux 2.6.38 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2496
-msgid ""
-"This contains an integer that can be used in the I<type> field of "
-"I<perf_event_attr> to indicate that you wish to use this PMU."
+msgid "This contains an integer that can be used in the I<type> field of I<perf_event_attr> to indicate that you wish to use this PMU."
 msgstr ""
 
 #. type: TP
@@ -7077,10 +5983,7 @@ msgstr "I</sys/bus/event_source/devices/*/rdpmc> (Linux 3.4 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2501
-msgid ""
-"If this file is 1, then direct user-space access to the performance counter "
-"registers is allowed via the rdpmc instruction.  This can be disabled by "
-"echoing 0 to the file."
+msgid "If this file is 1, then direct user-space access to the performance counter registers is allowed via the rdpmc instruction.  This can be disabled by echoing 0 to the file."
 msgstr ""
 
 #. type: TP
@@ -7091,20 +5994,12 @@ msgstr "I</sys/bus/event_source/devices/*/format/> (Linux 3.4 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2509
-msgid ""
-"This subdirectory contains information on the architecture-specific "
-"subfields available for programming the various I<config> fields in the "
-"I<perf_event_attr> struct."
+msgid "This subdirectory contains information on the architecture-specific subfields available for programming the various I<config> fields in the I<perf_event_attr> struct."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2520
-msgid ""
-"The content of each file is the name of the config field, followed by a "
-"colon, followed by a series of integer bit ranges separated by commas.  For "
-"example, the file I<event> may contain the value I<config1:1,6-10,44> which "
-"indicates that event is an attribute that occupies bits 1,6-10, and 44 of "
-"I<perf_event_attr::config1>."
+msgid "The content of each file is the name of the config field, followed by a colon, followed by a series of integer bit ranges separated by commas.  For example, the file I<event> may contain the value I<config1:1,6-10,44> which indicates that event is an attribute that occupies bits 1,6-10, and 44 of I<perf_event_attr::config1>."
 msgstr ""
 
 #. type: TP
@@ -7115,21 +6010,12 @@ msgstr "I</sys/bus/event_source/devices/*/events/> (Linux 3.4 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2529
-msgid ""
-"This subdirectory contains files with predefined events.  The contents are "
-"strings describing the event settings expressed in terms of the fields found "
-"in the previously mentioned I<./format/> directory.  These are not "
-"necessarily complete lists of all events supported by a PMU, but usually a "
-"subset of events deemed useful or interesting."
+msgid "This subdirectory contains files with predefined events.  The contents are strings describing the event settings expressed in terms of the fields found in the previously mentioned I<./format/> directory.  These are not necessarily complete lists of all events supported by a PMU, but usually a subset of events deemed useful or interesting."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2537
-msgid ""
-"The content of each file is a list of attribute names separated by commas.  "
-"Each entry has an optional value (either hex or decimal).  If no value is "
-"specified, then it is assumed to be a single-bit field with a value of 1.  "
-"An example entry may look like this: I<event=0x2,inv,ldlat=3>."
+msgid "The content of each file is a list of attribute names separated by commas.  Each entry has an optional value (either hex or decimal).  If no value is specified, then it is assumed to be a single-bit field with a value of 1.  An example entry may look like this: I<event=0x2,inv,ldlat=3>."
 msgstr ""
 
 #. type: TP
@@ -7140,9 +6026,7 @@ msgstr "I</sys/bus/event_source/devices/*/uevent>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2541
-msgid ""
-"This file is the standard kernel device interface for injecting hotplug "
-"events."
+msgid "This file is the standard kernel device interface for injecting hotplug events."
 msgstr ""
 
 #. type: TP
@@ -7153,25 +6037,17 @@ msgstr "I</sys/bus/event_source/devices/*/cpumask> (Linux 3.7 以降)"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2550
-msgid ""
-"The I<cpumask> file contains a comma-separated list of integers that "
-"indicate a representative CPU number for each socket (package)  on the "
-"motherboard.  This is needed when setting up uncore or northbridge events, "
-"as those PMUs present socket-wide events."
+msgid "The I<cpumask> file contains a comma-separated list of integers that indicate a representative CPU number for each socket (package)  on the motherboard.  This is needed when setting up uncore or northbridge events, as those PMUs present socket-wide events."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2557
-msgid ""
-"B<perf_event_open>()  returns the new file descriptor, or -1 if an error "
-"occurred (in which case, I<errno> is set appropriately)."
+msgid "B<perf_event_open>()  returns the new file descriptor, or -1 if an error occurred (in which case, I<errno> is set appropriately)."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2562
-msgid ""
-"The errors returned by B<perf_event_open>()  can be inconsistent, and may "
-"vary across processor architectures and performance monitoring units."
+msgid "The errors returned by B<perf_event_open>()  can be inconsistent, and may vary across processor architectures and performance monitoring units."
 msgstr ""
 
 #. type: TP
@@ -7182,23 +6058,12 @@ msgstr "B<E2BIG>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2579
-msgid ""
-"Returned if the I<perf_event_attr> I<size> value is too small (smaller than "
-"B<PERF_ATTR_SIZE_VER0>), too big (larger than the page size), or larger than "
-"the kernel supports and the extra bytes are not zero.  When B<E2BIG> is "
-"returned, the I<perf_event_attr> I<size> field is overwritten by the kernel "
-"to be the size of the structure it was expecting."
+msgid "Returned if the I<perf_event_attr> I<size> value is too small (smaller than B<PERF_ATTR_SIZE_VER0>), too big (larger than the page size), or larger than the kernel supports and the extra bytes are not zero.  When B<E2BIG> is returned, the I<perf_event_attr> I<size> field is overwritten by the kernel to be the size of the structure it was expecting."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2593
-msgid ""
-"Returned when the requested event requires B<CAP_SYS_ADMIN> permissions (or "
-"a more permissive perf_event paranoid setting).  Some common cases where an "
-"unprivileged process may encounter this error: attaching to a process owned "
-"by a different user; monitoring all processes on a given CPU (i.e., "
-"specifying the I<pid> argument as -1); and not setting I<exclude_kernel> "
-"when the paranoid setting requires it."
+msgid "Returned when the requested event requires B<CAP_SYS_ADMIN> permissions (or a more permissive perf_event paranoid setting).  Some common cases where an unprivileged process may encounter this error: attaching to a process owned by a different user; monitoring all processes on a given CPU (i.e., specifying the I<pid> argument as -1); and not setting I<exclude_kernel> when the paranoid setting requires it."
 msgstr ""
 
 #. type: TP
@@ -7210,10 +6075,7 @@ msgstr "B<EBADF>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2603
-msgid ""
-"Returned if the I<group_fd> file descriptor is not valid, or, if "
-"B<PERF_FLAG_PID_CGROUP> is set, the cgroup file descriptor in I<pid> is not "
-"valid."
+msgid "Returned if the I<group_fd> file descriptor is not valid, or, if B<PERF_FLAG_PID_CGROUP> is set, the cgroup file descriptor in I<pid> is not valid."
 msgstr ""
 
 #. type: Plain text
@@ -7223,15 +6085,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2634
-msgid ""
-"Returned if the specified event is invalid.  There are many possible reasons "
-"for this.  A not-exhaustive list: I<sample_freq> is higher than the maximum "
-"setting; the I<cpu> to monitor does not exist; I<read_format> is out of "
-"range; I<sample_type> is out of range; the I<flags> value is out of range; "
-"I<exclusive> or I<pinned> set and the event is not a group leader; the event "
-"I<config> values are out of range or set reserved bits; the generic event "
-"selected is not supported; or there is not enough room to add the selected "
-"event."
+msgid "Returned if the specified event is invalid.  There are many possible reasons for this.  A not-exhaustive list: I<sample_freq> is higher than the maximum setting; the I<cpu> to monitor does not exist; I<read_format> is out of range; I<sample_type> is out of range; the I<flags> value is out of range; I<exclusive> or I<pinned> set and the event is not a group leader; the event I<config> values are out of range or set reserved bits; the generic event selected is not supported; or there is not enough room to add the selected event."
 msgstr ""
 
 #. type: TP
@@ -7242,16 +6096,12 @@ msgstr "B<EMFILE>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2640
-msgid ""
-"Each opened event uses one file descriptor.  If a large number of events are "
-"opened the per-user file descriptor limit (often 1024) will be hit and no "
-"more events can be created."
+msgid "Each opened event uses one file descriptor.  If a large number of events are opened the per-user file descriptor limit (often 1024) will be hit and no more events can be created."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2644
-msgid ""
-"Returned when the event involves a feature not supported by the current CPU."
+msgid "Returned when the event involves a feature not supported by the current CPU."
 msgstr ""
 
 #. type: TP
@@ -7262,9 +6112,7 @@ msgstr "B<ENOENT>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2651
-msgid ""
-"Returned if the I<type> setting is not valid.  This error is also returned "
-"for some unsupported generic events."
+msgid "Returned if the I<type> setting is not valid.  This error is also returned for some unsupported generic events."
 msgstr ""
 
 #. type: TP
@@ -7275,44 +6123,27 @@ msgstr "B<ENOSPC>"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2661
-msgid ""
-"Prior to Linux 3.3, if there was not enough room for the event, B<ENOSPC> "
-"was returned.  In Linux 3.3, this was changed to B<EINVAL>.  B<ENOSPC> is "
-"still returned if you try to add more breakpoint events than supported by "
-"the hardware."
+msgid "Prior to Linux 3.3, if there was not enough room for the event, B<ENOSPC> was returned.  In Linux 3.3, this was changed to B<EINVAL>.  B<ENOSPC> is still returned if you try to add more breakpoint events than supported by the hardware."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2668
-msgid ""
-"Returned if B<PERF_SAMPLE_STACK_USER> is set in I<sample_type> and it is not "
-"supported by hardware."
+msgid "Returned if B<PERF_SAMPLE_STACK_USER> is set in I<sample_type> and it is not supported by hardware."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2675
-msgid ""
-"Returned if an event requiring a specific hardware feature is requested but "
-"there is no hardware support.  This includes requesting low-skid events if "
-"not supported, branch tracing if it is not available, sampling if no PMU "
-"interrupt is available, and branch stacks for software events."
+msgid "Returned if an event requiring a specific hardware feature is requested but there is no hardware support.  This includes requesting low-skid events if not supported, branch tracing if it is not available, sampling if no PMU interrupt is available, and branch stacks for software events."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2680
-msgid ""
-"Returned on many (but not all) architectures when an unsupported "
-"I<exclude_hv>, I<exclude_idle>, I<exclude_user>, or I<exclude_kernel> "
-"setting is specified."
+msgid "Returned on many (but not all) architectures when an unsupported I<exclude_hv>, I<exclude_idle>, I<exclude_user>, or I<exclude_kernel> setting is specified."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2688
-msgid ""
-"It can also happen, as with B<EACCES>, when the requested event requires "
-"B<CAP_SYS_ADMIN> permissions (or a more permissive perf_event paranoid "
-"setting).  This includes setting a breakpoint on a kernel address, and "
-"(since Linux 3.13) setting a kernel function-trace tracepoint."
+msgid "It can also happen, as with B<EACCES>, when the requested event requires B<CAP_SYS_ADMIN> permissions (or a more permissive perf_event paranoid setting).  This includes setting a breakpoint on a kernel address, and (since Linux 3.13) setting a kernel function-trace tracepoint."
 msgstr ""
 
 #. type: Plain text
@@ -7328,35 +6159,22 @@ msgstr "バージョン"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2696
-msgid ""
-"B<perf_event_open>()  was introduced in Linux 2.6.31 but was called "
-"B<perf_counter_open>().  It was renamed in Linux 2.6.32."
+msgid "B<perf_event_open>()  was introduced in Linux 2.6.31 but was called B<perf_counter_open>().  It was renamed in Linux 2.6.32."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2701
-msgid ""
-"This B<perf_event_open>()  system call Linux- specific and should not be "
-"used in programs intended to be portable."
-msgstr ""
-"B<perf_event_open>() システムコールは Linux 固有であり、 移植を意図したプログ"
-"ラムで使用すべきではない。"
+msgid "This B<perf_event_open>()  system call Linux- specific and should not be used in programs intended to be portable."
+msgstr "B<perf_event_open>() システムコールは Linux 固有であり、 移植を意図したプログラムで使用すべきではない。"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2705
-msgid ""
-"Glibc does not provide a wrapper for this system call; call it using "
-"B<syscall>(2).  See the example below."
-msgstr ""
-"glibc はこのシステムコールに対するラッパー関数を提供していない。 "
-"B<syscall>(2)  を使って呼び出すこと。 以下の例を参照。"
+msgid "Glibc does not provide a wrapper for this system call; call it using B<syscall>(2).  See the example below."
+msgstr "glibc はこのシステムコールに対するラッパー関数を提供していない。 B<syscall>(2)  を使って呼び出すこと。 以下の例を参照。"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2711
-msgid ""
-"The official way of knowing if B<perf_event_open>()  support is enabled is "
-"checking for the existence of the file I</proc/sys/kernel/"
-"perf_event_paranoid>."
+msgid "The official way of knowing if B<perf_event_open>()  support is enabled is checking for the existence of the file I</proc/sys/kernel/perf_event_paranoid>."
 msgstr ""
 
 #. type: SH
@@ -7368,88 +6186,57 @@ msgstr "バグ"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2718
-msgid ""
-"The B<F_SETOWN_EX> option to B<fcntl>(2)  is needed to properly get overflow "
-"signals in threads.  This was introduced in Linux 2.6.32."
+msgid "The B<F_SETOWN_EX> option to B<fcntl>(2)  is needed to properly get overflow signals in threads.  This was introduced in Linux 2.6.32."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2726
-msgid ""
-"Prior to Linux 2.6.33 (at least for x86), the kernel did not check if events "
-"could be scheduled together until read time.  The same happens on all known "
-"kernels if the NMI watchdog is enabled.  This means to see if a given set of "
-"events works you have to B<perf_event_open>(), start, then read before you "
-"know for sure you can get valid measurements."
+msgid "Prior to Linux 2.6.33 (at least for x86), the kernel did not check if events could be scheduled together until read time.  The same happens on all known kernels if the NMI watchdog is enabled.  This means to see if a given set of events works you have to B<perf_event_open>(), start, then read before you know for sure you can get valid measurements."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2730
-msgid ""
-"Prior to Linux 2.6.34, event constraints were not enforced by the kernel.  "
-"In that case, some events would silently return \"0\" if the kernel "
-"scheduled them in an improper counter slot."
+msgid "Prior to Linux 2.6.34, event constraints were not enforced by the kernel.  In that case, some events would silently return \"0\" if the kernel scheduled them in an improper counter slot."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2733
-msgid ""
-"Prior to Linux 2.6.34, there was a bug when multiplexing where the wrong "
-"results could be returned."
+msgid "Prior to Linux 2.6.34, there was a bug when multiplexing where the wrong results could be returned."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2736
-msgid ""
-"Kernels from Linux 2.6.35 to Linux 2.6.39 can quickly crash the kernel if "
-"\"inherit\" is enabled and many threads are started."
+msgid "Kernels from Linux 2.6.35 to Linux 2.6.39 can quickly crash the kernel if \"inherit\" is enabled and many threads are started."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2740
-msgid ""
-"Prior to Linux 2.6.35, B<PERF_FORMAT_GROUP> did not work with attached "
-"processes."
+msgid "Prior to Linux 2.6.35, B<PERF_FORMAT_GROUP> did not work with attached processes."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2745
-msgid ""
-"In older Linux 2.6 versions, refreshing an event group leader refreshed all "
-"siblings, and refreshing with a parameter of 0 enabled infinite refresh.  "
-"This behavior is unsupported and should not be relied on."
+msgid "In older Linux 2.6 versions, refreshing an event group leader refreshed all siblings, and refreshing with a parameter of 0 enabled infinite refresh.  This behavior is unsupported and should not be relied on."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2751
-msgid ""
-"There is a bug in the kernel code between Linux 2.6.36 and Linux 3.0 that "
-"ignores the \"watermark\" field and acts as if a wakeup_event was chosen if "
-"the union has a nonzero value in it."
+msgid "There is a bug in the kernel code between Linux 2.6.36 and Linux 3.0 that ignores the \"watermark\" field and acts as if a wakeup_event was chosen if the union has a nonzero value in it."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2757
-msgid ""
-"From Linux 2.6.31 to Linux 3.4, the B<PERF_IOC_FLAG_GROUP> ioctl argument "
-"was broken and would repeatedly operate on the event specified rather than "
-"iterating across all sibling events in a group."
+msgid "From Linux 2.6.31 to Linux 3.4, the B<PERF_IOC_FLAG_GROUP> ioctl argument was broken and would repeatedly operate on the event specified rather than iterating across all sibling events in a group."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2768
-msgid ""
-"From Linux 3.4 to Linux 3.11, the mmap I<cap_usr_rdpmc> and I<cap_usr_time> "
-"bits mapped to the same location.  Code should migrate to the new "
-"I<cap_user_rdpmc> and I<cap_user_time> fields instead."
+msgid "From Linux 3.4 to Linux 3.11, the mmap I<cap_usr_rdpmc> and I<cap_usr_time> bits mapped to the same location.  Code should migrate to the new I<cap_user_rdpmc> and I<cap_user_time> fields instead."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2773
-msgid ""
-"Always double-check your results! Various generalized events have had wrong "
-"values.  For example, retired branches measured the wrong thing on AMD "
-"machines until Linux 2.6.35."
+msgid "Always double-check your results! Various generalized events have had wrong values.  For example, retired branches measured the wrong thing on AMD machines until Linux 2.6.35."
 msgstr ""
 
 #. type: SH
@@ -7461,9 +6248,7 @@ msgstr "例"
 
 #. type: Plain text
 #: build/C/man2/perf_event_open.2:2777
-msgid ""
-"The following is a short example that measures the total instruction count "
-"of a call to B<printf>(3)."
+msgid "The following is a short example that measures the total instruction count of a call to B<printf>(3)."
 msgstr ""
 
 #. type: Plain text
@@ -7652,19 +6437,12 @@ msgstr "B<long perfmonctl(int >I<fd>B<, int >I<cmd>B<, void *>I<arg>B<, int >I<n
 
 #. type: Plain text
 #: build/C/man2/perfmonctl.2:47
-msgid ""
-"The IA-64-specific B<perfmonctl>()  system call provides an interface to the "
-"PMU (performance monitoring unit).  The PMU consists of PMD (performance "
-"monitoring data) registers and PMC (performance monitoring control) "
-"registers, which gather hardware statistics."
+msgid "The IA-64-specific B<perfmonctl>()  system call provides an interface to the PMU (performance monitoring unit).  The PMU consists of PMD (performance monitoring data) registers and PMC (performance monitoring control) registers, which gather hardware statistics."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perfmonctl.2:57
-msgid ""
-"B<perfmonctl>()  applies the operation I<cmd> to the input arguments "
-"specified by I<arg>.  The number of arguments is defined by I<narg>.  The "
-"I<fd> argument specifies the perfmon context to operate on."
+msgid "B<perfmonctl>()  applies the operation I<cmd> to the input arguments specified by I<arg>.  The number of arguments is defined by I<narg>.  The I<fd> argument specifies the perfmon context to operate on."
 msgstr ""
 
 #. type: Plain text
@@ -7691,25 +6469,17 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perfmonctl.2:74
-msgid ""
-"The I<fd> parameter is ignored.  A new perfmon context is created as "
-"specified in I<ctxt> and its file descriptor is returned in I<ctxt-"
-"E<gt>ctx_fd>."
+msgid "The I<fd> parameter is ignored.  A new perfmon context is created as specified in I<ctxt> and its file descriptor is returned in I<ctxt-E<gt>ctx_fd>."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perfmonctl.2:86
-msgid ""
-"The file descriptor can be used in subsequent calls to B<perfmonctl>()  and "
-"can be used to read event notifications (type I<pfm_msg_t>)  using "
-"B<read>(2).  The file descriptor is pollable using B<select>(2), B<poll>(2), "
-"and B<epoll>(7)."
+msgid "The file descriptor can be used in subsequent calls to B<perfmonctl>()  and can be used to read event notifications (type I<pfm_msg_t>)  using B<read>(2).  The file descriptor is pollable using B<select>(2), B<poll>(2), and B<epoll>(7)."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perfmonctl.2:90
-msgid ""
-"The context can be destroyed by calling B<close>(2)  on the file descriptor."
+msgid "The context can be destroyed by calling B<close>(2)  on the file descriptor."
 msgstr ""
 
 #. type: TP
@@ -7919,9 +6689,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perfmonctl.2:196
-msgid ""
-"B<perfmonctl>()  returns zero when the operation is successful.  On error, "
-"-1 is returned and I<errno> is set to indicate the cause of the error."
+msgid "B<perfmonctl>()  returns zero when the operation is successful.  On error, -1 is returned and I<errno> is set to indicate the cause of the error."
 msgstr ""
 
 #. type: Plain text
@@ -7931,9 +6699,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/perfmonctl.2:202
-msgid ""
-"B<perfmonctl>()  is Linux-specific and is available only on the IA-64 "
-"architecture."
+msgid "B<perfmonctl>()  is Linux-specific and is available only on the IA-64 architecture."
 msgstr ""
 
 #. type: Plain text
@@ -7975,47 +6741,23 @@ msgstr "B<int personality(unsigned long >I<persona>B<);>"
 
 #. type: Plain text
 #: build/C/man2/personality.2:47
-msgid ""
-"Linux supports different execution domains, or personalities, for each "
-"process.  Among other things, execution domains tell Linux how to map signal "
-"numbers into signal actions.  The execution domain system allows Linux to "
-"provide limited support for binaries compiled under other UNIX-like "
-"operating systems."
-msgstr ""
-"Linux は、プロセス毎の異なる実行ドメイン、すなわち パーソナリティ "
-"(personality) をサポートしている。 実行ドメインは Linux にシグナル番号にどの"
-"シグナルを割り付けるかを 教えたりする。また、実行ドメイン・システムにより、 "
-"Linux は、 他の UNIX 風のオペレーティングシステムでコンパイルされたバイナリに"
-"対する限定的なサポートを提供している。"
+msgid "Linux supports different execution domains, or personalities, for each process.  Among other things, execution domains tell Linux how to map signal numbers into signal actions.  The execution domain system allows Linux to provide limited support for binaries compiled under other UNIX-like operating systems."
+msgstr "Linux は、プロセス毎の異なる実行ドメイン、すなわち パーソナリティ (personality) をサポートしている。 実行ドメインは Linux にシグナル番号にどのシグナルを割り付けるかを 教えたりする。また、実行ドメイン・システムにより、 Linux は、 他の UNIX 風のオペレーティングシステムでコンパイルされたバイナリに対する限定的なサポートを提供している。"
 
 #. type: Plain text
 #: build/C/man2/personality.2:59
-msgid ""
-"If I<persona> is not 0xffffffff, then B<personality>()  sets the caller's "
-"execution domain to the value specified by I<persona>.  Specifying "
-"I<persona> as 0xffffffff provides a way of retrieving the current persona "
-"without changing it."
-msgstr ""
-"I<persona> が 0xffffffff 以外の場合、 B<personality>() は呼び出し元の実行ドメ"
-"インを I<persona> で指定された値に設定する。 I<persona> に 0xffffffff を指定"
-"すると、変更を行わず、現在の persona 値を取得できる。"
+msgid "If I<persona> is not 0xffffffff, then B<personality>()  sets the caller's execution domain to the value specified by I<persona>.  Specifying I<persona> as 0xffffffff provides a way of retrieving the current persona without changing it."
+msgstr "I<persona> が 0xffffffff 以外の場合、 B<personality>() は呼び出し元の実行ドメインを I<persona> で指定された値に設定する。 I<persona> に 0xffffffff を指定すると、変更を行わず、現在の persona 値を取得できる。"
 
 #. type: Plain text
 #: build/C/man2/personality.2:62
-msgid ""
-"A list of the available execution domains can be found in I<E<lt>sys/"
-"personality.hE<gt>>."
-msgstr ""
-"利用可能な実行ドメインのリストは I<E<lt>sys/personality.hE<gt>> にある。"
+msgid "A list of the available execution domains can be found in I<E<lt>sys/personality.hE<gt>>."
+msgstr "利用可能な実行ドメインのリストは I<E<lt>sys/personality.hE<gt>> にある。"
 
 #. type: Plain text
 #: build/C/man2/personality.2:69
-msgid ""
-"On success, the previous I<persona> is returned.  On error, -1 is returned, "
-"and I<errno> is set appropriately."
-msgstr ""
-"成功した場合、以前の I<persona> が返される。エラーの場合は、-1 が返され、 "
-"I<errno> が適切に設定される。"
+msgid "On success, the previous I<persona> is returned.  On error, -1 is returned, and I<errno> is set appropriately."
+msgstr "成功した場合、以前の I<persona> が返される。エラーの場合は、-1 が返され、 I<errno> が適切に設定される。"
 
 #. type: Plain text
 #: build/C/man2/personality.2:73
@@ -8024,12 +6766,8 @@ msgstr "カーネルがパーソナリティを変更できなかった。"
 
 #. type: Plain text
 #: build/C/man2/personality.2:77
-msgid ""
-"B<personality>()  is Linux-specific and should not be used in programs "
-"intended to be portable."
-msgstr ""
-"B<personality>()  は Linux 固有であり、移植を意図したプログラムで使用すべきで"
-"はない。"
+msgid "B<personality>()  is Linux-specific and should not be used in programs intended to be portable."
+msgstr "B<personality>()  は Linux 固有であり、移植を意図したプログラムで使用すべきではない。"
 
 #. type: TH
 #: build/C/man2/pivot_root.2:10
@@ -8044,91 +6782,36 @@ msgstr "pivot_root - root ファイルシステムを変更する"
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:15
-msgid ""
-"B<int pivot_root(const char *>I<new_root>B<, const char *>I<put_old>B<);>"
-msgstr ""
-"B<int pivot_root(const char *>I<new_root>B<, const char *>I<put_old>B<);>"
+msgid "B<int pivot_root(const char *>I<new_root>B<, const char *>I<put_old>B<);>"
+msgstr "B<int pivot_root(const char *>I<new_root>B<, const char *>I<put_old>B<);>"
 
 #.  The
 #.  .B CAP_SYS_ADMIN
 #.  capability is required.
 #. type: Plain text
 #: build/C/man2/pivot_root.2:27
-msgid ""
-"B<pivot_root>()  moves the root filesystem of the calling process to the "
-"directory I<put_old> and makes I<new_root> the new root filesystem of the "
-"calling process."
-msgstr ""
-"B<pivot_root>()  は呼び出し元のプロセスの root ファイルシステムを I<put_old> "
-"ディレクトリに移動し、 I<new_root> を呼び出し元のプロセスの新しい root ファイ"
-"ルシステムにする。"
+msgid "B<pivot_root>()  moves the root filesystem of the calling process to the directory I<put_old> and makes I<new_root> the new root filesystem of the calling process."
+msgstr "B<pivot_root>()  は呼び出し元のプロセスの root ファイルシステムを I<put_old> ディレクトリに移動し、 I<new_root> を呼び出し元のプロセスの新しい root ファイルシステムにする。"
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:34
-msgid ""
-"The typical use of B<pivot_root>()  is during system startup, when the "
-"system mounts a temporary root filesystem (e.g., an B<initrd>), then mounts "
-"the real root filesystem, and eventually turns the latter into the current "
-"root of all relevant processes or threads."
-msgstr ""
-"B<pivot_root>()  の典型的な利用法は、システムの起動中にシステムが一時的な "
-"root ファイルシステム (例えば B<initrd>)  をマウントし、これに続いて本当の "
-"root ファイルシステムをマウントし、 後者を必要な全てのプロセス・スレッドの カ"
-"レント root に変更するような場合である。"
+msgid "The typical use of B<pivot_root>()  is during system startup, when the system mounts a temporary root filesystem (e.g., an B<initrd>), then mounts the real root filesystem, and eventually turns the latter into the current root of all relevant processes or threads."
+msgstr "B<pivot_root>()  の典型的な利用法は、システムの起動中にシステムが一時的な root ファイルシステム (例えば B<initrd>)  をマウントし、これに続いて本当の root ファイルシステムをマウントし、 後者を必要な全てのプロセス・スレッドの カレント root に変更するような場合である。"
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:46
-msgid ""
-"B<pivot_root>()  may or may not change the current root and the current "
-"working directory of any processes or threads which use the old root "
-"directory.  The caller of B<pivot_root>()  must ensure that processes with "
-"root or current working directory at the old root operate correctly in "
-"either case.  An easy way to ensure this is to change their root and current "
-"working directory to I<new_root> before invoking B<pivot_root>()."
-msgstr ""
-"古い root ディレクトリを使っていた全てのプロセスやスレッドの カレント root と"
-"カレントワーキングディレクトリを、 B<pivot_root>()  が変更するかどうかはわか"
-"らない。 B<pivot_root>()  の呼びだしプロセスは、古い root やカレントワーキン"
-"グディレクトリを使っていた プロセスが、いずれの場合でも正しく動作することを保"
-"証しなければならない。 これを簡単に行うには、それらのプロセスの root と カレ"
-"ントワーキングディレクトリを B<pivot_root>()  を呼び出す前に I<new_root> に変"
-"更しておくことである。"
+msgid "B<pivot_root>()  may or may not change the current root and the current working directory of any processes or threads which use the old root directory.  The caller of B<pivot_root>()  must ensure that processes with root or current working directory at the old root operate correctly in either case.  An easy way to ensure this is to change their root and current working directory to I<new_root> before invoking B<pivot_root>()."
+msgstr "古い root ディレクトリを使っていた全てのプロセスやスレッドの カレント root とカレントワーキングディレクトリを、 B<pivot_root>()  が変更するかどうかはわからない。 B<pivot_root>()  の呼びだしプロセスは、古い root やカレントワーキングディレクトリを使っていた プロセスが、いずれの場合でも正しく動作することを保証しなければならない。 これを簡単に行うには、それらのプロセスの root と カレントワーキングディレクトリを B<pivot_root>()  を呼び出す前に I<new_root> に変更しておくことである。"
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:64
-msgid ""
-"The paragraph above is intentionally vague because the implementation of "
-"B<pivot_root>()  may change in the future.  At the time of writing, "
-"B<pivot_root>()  changes root and current working directory of each process "
-"or thread to I<new_root> if they point to the old root directory.  This is "
-"necessary in order to prevent kernel threads from keeping the old root "
-"directory busy with their root and current working directory, even if they "
-"never access the filesystem in any way.  In the future, there may be a "
-"mechanism for kernel threads to explicitly relinquish any access to the "
-"filesystem, such that this fairly intrusive mechanism can be removed from "
-"B<pivot_root>()."
-msgstr ""
-"上記の段落は、将来 B<pivot_root>()  が変更されるかも知れないことを鑑みて、わ"
-"ざと曖昧に書いてある。 本ページを記述している時点では、 B<pivot_root>()  は古"
-"い root ディレクトリを用いている全てのプロセス・スレッドの root と カレント"
-"ワーキングディレクトリを I<new_root> に変更する。これはカーネルのスレッドが古"
-"い root ディレクトリを busy 状態にしないために必要である。これらのスレッドが "
-"古いディレクトリを root やカレントワーキングディレクトリとしていると、 ファイ"
-"ルシステムに一切アクセスしない場合でも 古い root が busy になってしまうからで"
-"ある。 将来は、カーネルスレッドがあらゆるファイルシステムへのアクセスを 明示"
-"的に放棄するメカニズムができ、このでしゃばりな機能は B<pivot_root>()  から削"
-"除されるかもしれない。"
+msgid "The paragraph above is intentionally vague because the implementation of B<pivot_root>()  may change in the future.  At the time of writing, B<pivot_root>()  changes root and current working directory of each process or thread to I<new_root> if they point to the old root directory.  This is necessary in order to prevent kernel threads from keeping the old root directory busy with their root and current working directory, even if they never access the filesystem in any way.  In the future, there may be a mechanism for kernel threads to explicitly relinquish any access to the filesystem, such that this fairly intrusive mechanism can be removed from B<pivot_root>()."
+msgstr "上記の段落は、将来 B<pivot_root>()  が変更されるかも知れないことを鑑みて、わざと曖昧に書いてある。 本ページを記述している時点では、 B<pivot_root>()  は古い root ディレクトリを用いている全てのプロセス・スレッドの root と カレントワーキングディレクトリを I<new_root> に変更する。これはカーネルのスレッドが古い root ディレクトリを busy 状態にしないために必要である。これらのスレッドが 古いディレクトリを root やカレントワーキングディレクトリとしていると、 ファイルシステムに一切アクセスしない場合でも 古い root が busy になってしまうからである。 将来は、カーネルスレッドがあらゆるファイルシステムへのアクセスを 明示的に放棄するメカニズムができ、このでしゃばりな機能は B<pivot_root>()  から削除されるかもしれない。"
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:72
-msgid ""
-"Note that this also applies to the calling process: B<pivot_root>()  may or "
-"may not affect its current working directory.  It is therefore recommended "
-"to call B<chdir(\"/\")> immediately after B<pivot_root>()."
-msgstr ""
-"これは呼び出し元のプロセスについても当てはまることに注意。 B<pivot_root>()  "
-"がカレントプロセスのカレントワーキングディレクトリに影響するかどうかは 分から"
-"ない。したがって B<pivot_root>()  の直後に B<chdir(\"/\")> を呼び出すとよい。"
+msgid "Note that this also applies to the calling process: B<pivot_root>()  may or may not affect its current working directory.  It is therefore recommended to call B<chdir(\"/\")> immediately after B<pivot_root>()."
+msgstr "これは呼び出し元のプロセスについても当てはまることに注意。 B<pivot_root>()  がカレントプロセスのカレントワーキングディレクトリに影響するかどうかは 分からない。したがって B<pivot_root>()  の直後に B<chdir(\"/\")> を呼び出すとよい。"
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:74
@@ -8149,23 +6832,13 @@ msgstr "ディレクトリでなければならない。"
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:79
-msgid ""
-"I<new_root> and I<put_old> must not be on the same filesystem as the current "
-"root."
-msgstr ""
-"I<new_root> と I<put_old> は現在の root と同じファイルシステムにあってはなら"
-"ない。"
+msgid "I<new_root> and I<put_old> must not be on the same filesystem as the current root."
+msgstr "I<new_root> と I<put_old> は現在の root と同じファイルシステムにあってはならない。"
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:83
-msgid ""
-"I<put_old> must be underneath I<new_root>, that is, adding a nonzero number "
-"of I</..> to the string pointed to by I<put_old> must yield the same "
-"directory as I<new_root>."
-msgstr ""
-"I<put_old> は I<new_root> 以下になければならない。すなわち I<put_old> を差す"
-"文字列に 1 個以上の I<../> を付けることによって I<new_root> と同じディレクト"
-"リが得られなければならない。"
+msgid "I<put_old> must be underneath I<new_root>, that is, adding a nonzero number of I</..> to the string pointed to by I<put_old> must yield the same directory as I<new_root>."
+msgstr "I<put_old> は I<new_root> 以下になければならない。すなわち I<put_old> を差す文字列に 1 個以上の I<../> を付けることによって I<new_root> と同じディレクトリが得られなければならない。"
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:85
@@ -8179,43 +6852,23 @@ msgstr "利用例については B<pivot_root>(8)  を参照のこと。"
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:96
-msgid ""
-"If the current root is not a mount point (e.g., after B<chroot>(2)  or "
-"B<pivot_root>(), see also below), not the old root directory, but the mount "
-"point of that filesystem is mounted on I<put_old>."
-msgstr ""
-"現在の root がマウントポイントではない (B<chroot>(2)  や B<pivot_root>()  の"
-"後など。以下も参照) 場合、 古い root ディレクトリではなく、 そのファイルシス"
-"テムのマウントポイントが I<put_old> にマウントされる。"
+msgid "If the current root is not a mount point (e.g., after B<chroot>(2)  or B<pivot_root>(), see also below), not the old root directory, but the mount point of that filesystem is mounted on I<put_old>."
+msgstr "現在の root がマウントポイントではない (B<chroot>(2)  や B<pivot_root>()  の後など。以下も参照) 場合、 古い root ディレクトリではなく、 そのファイルシステムのマウントポイントが I<put_old> にマウントされる。"
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:101
-msgid ""
-"I<new_root> does not have to be a mount point.  In this case, I</proc/"
-"mounts> will show the mount point of the filesystem containing I<new_root> "
-"as root (I</>)."
-msgstr ""
-"I<new_root> はマウントポイントでなくてもよい。 この場合 I</proc/mounts> は、 "
-"I<new_root> を root (I</>)  とするファイルシステムのマウントポイントを表示す"
-"る。"
+msgid "I<new_root> does not have to be a mount point.  In this case, I</proc/mounts> will show the mount point of the filesystem containing I<new_root> as root (I</>)."
+msgstr "I<new_root> はマウントポイントでなくてもよい。 この場合 I</proc/mounts> は、 I<new_root> を root (I</>)  とするファイルシステムのマウントポイントを表示する。"
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:110
-msgid ""
-"B<pivot_root>()  may return (in I<errno>) any of the errors returned by "
-"B<stat>(2).  Additionally, it may return:"
-msgstr ""
-"B<pivot_root>()  は B<stat>(2)  の返すあらゆるエラーを (I<errno> に) 返す可能"
-"性がある。さらに以下を返すことがある:"
+msgid "B<pivot_root>()  may return (in I<errno>) any of the errors returned by B<stat>(2).  Additionally, it may return:"
+msgstr "B<pivot_root>()  は B<stat>(2)  の返すあらゆるエラーを (I<errno> に) 返す可能性がある。さらに以下を返すことがある:"
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:114
-msgid ""
-"I<new_root> or I<put_old> are on the current root filesystem, or a "
-"filesystem is already mounted on I<put_old>."
-msgstr ""
-"I<new_root> または I<put_old> が、現在の root ファイルシステム上にあるか、既"
-"に I<put_old> になんらかのファイルシステムがマウントされている。"
+msgid "I<new_root> or I<put_old> are on the current root filesystem, or a filesystem is already mounted on I<put_old>."
+msgstr "I<new_root> または I<put_old> が、現在の root ファイルシステム上にあるか、既に I<put_old> になんらかのファイルシステムがマウントされている。"
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:117
@@ -8250,21 +6903,13 @@ msgstr "B<pivot_root>()  は Linux に固有のものなので、移植性はな
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:138
-msgid ""
-"B<pivot_root>()  should not have to change root and current working "
-"directory of all other processes in the system."
-msgstr ""
-"B<pivot_root>()  はシステムの他のプロセス全ての root と カレントワーキング"
-"ディレクトリとを変更しなくてもよいはずである。"
+msgid "B<pivot_root>()  should not have to change root and current working directory of all other processes in the system."
+msgstr "B<pivot_root>()  はシステムの他のプロセス全ての root と カレントワーキングディレクトリとを変更しなくてもよいはずである。"
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:143
-msgid ""
-"Some of the more obscure uses of B<pivot_root>()  may quickly lead to "
-"insanity."
-msgstr ""
-"B<pivot_root>()  の使い方がもうちょっと曖昧になると、 あっという間にわけのわ"
-"からない状態になってしまうだろう"
+msgid "Some of the more obscure uses of B<pivot_root>()  may quickly lead to insanity."
+msgstr "B<pivot_root>()  の使い方がもうちょっと曖昧になると、 あっという間にわけのわからない状態になってしまうだろう"
 
 #. type: Plain text
 #: build/C/man2/pivot_root.2:149
@@ -8279,12 +6924,8 @@ msgstr "PROCESS_VM_READV"
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:32
-msgid ""
-"process_vm_readv, process_vm_writev - transfer data between process address "
-"spaces"
-msgstr ""
-"process_vm_readv, process_vm_writev - プロセスのアドレス空間間でデータを転送"
-"する"
+msgid "process_vm_readv, process_vm_writev - transfer data between process address spaces"
+msgstr "process_vm_readv, process_vm_writev - プロセスのアドレス空間間でデータを転送する"
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:35
@@ -8330,8 +6971,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:54
-msgid ""
-"Feature Test Macro Requirements for glibc (see B<feature_test_macros>(7)):"
+msgid "Feature Test Macro Requirements for glibc (see B<feature_test_macros>(7)):"
 msgstr ""
 
 #. type: Plain text
@@ -8346,41 +6986,22 @@ msgstr "B<_GNU_SOURCE>"
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:73
-msgid ""
-"These system calls transfer data between the address space of the calling "
-"process (\"the local process\") and the process identified by I<pid> (\"the "
-"remote process\").  The data moves directly between the address spaces of "
-"the two processes, without passing through kernel space."
+msgid "These system calls transfer data between the address space of the calling process (\"the local process\") and the process identified by I<pid> (\"the remote process\").  The data moves directly between the address spaces of the two processes, without passing through kernel space."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:98
-msgid ""
-"The B<process_vm_readv>()  system call transfers data from the remote "
-"process to the local process.  The data to be transferred is identified by "
-"I<remote_iov> and I<riovcnt>: I<remote_iov> is a pointer to an array "
-"describing address ranges in the process I<pid>, and I<riovcnt> specifies "
-"the number of elements in I<remote_iov>.  The data is transferred to the "
-"locations specified by I<local_iov> and I<liovcnt>: I<local_iov> is a "
-"pointer to an array describing address ranges in the calling process, and "
-"I<liovcnt> specifies the number of elements in I<local_iov>."
+msgid "The B<process_vm_readv>()  system call transfers data from the remote process to the local process.  The data to be transferred is identified by I<remote_iov> and I<riovcnt>: I<remote_iov> is a pointer to an array describing address ranges in the process I<pid>, and I<riovcnt> specifies the number of elements in I<remote_iov>.  The data is transferred to the locations specified by I<local_iov> and I<liovcnt>: I<local_iov> is a pointer to an array describing address ranges in the calling process, and I<liovcnt> specifies the number of elements in I<local_iov>."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:112
-msgid ""
-"The B<process_vm_writev>()  system call is the converse of "
-"B<process_vm_readv>()\\(emit transfers data from the local process to the "
-"remote process.  Other than the direction of the transfer, the arguments "
-"I<liovcnt>, I<local_iov>, I<riovcnt>, and I<remote_iov> have the same "
-"meaning as for B<process_vm_readv>()."
+msgid "The B<process_vm_writev>()  system call is the converse of B<process_vm_readv>()\\(emit transfers data from the local process to the remote process.  Other than the direction of the transfer, the arguments I<liovcnt>, I<local_iov>, I<riovcnt>, and I<remote_iov> have the same meaning as for B<process_vm_readv>()."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:122
-msgid ""
-"The I<local_iov> and I<remote_iov> arguments point to an array of I<iovec> "
-"structures, defined in I<E<lt>sys/uio.hE<gt>> as:"
+msgid "The I<local_iov> and I<remote_iov> arguments point to an array of I<iovec> structures, defined in I<E<lt>sys/uio.hE<gt>> as:"
 msgstr ""
 "引き数 I<local_iov> と I<remote_iov> は I<iovec> 構造体の配列へのポイン\n"
 "タである。 I<iovec> 構造体は I<E<lt>sys/uio.hE<gt>> で以下のように定義\n"
@@ -8402,11 +7023,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:145
-msgid ""
-"Buffers are processed in array order.  This means that "
-"B<process_vm_readv>()  completely fills I<local_iov[0]> before proceeding to "
-"I<local_iov[1]>, and so on.  Likewise, I<remote_iov[0]> is completely read "
-"before proceeding to I<remote_iov[1]>, and so on."
+msgid "Buffers are processed in array order.  This means that B<process_vm_readv>()  completely fills I<local_iov[0]> before proceeding to I<local_iov[1]>, and so on.  Likewise, I<remote_iov[0]> is completely read before proceeding to I<remote_iov[1]>, and so on."
 msgstr ""
 "バッファは配列の順序で処理される。これは、 B<process_vm_readv>() が\n"
 "I<local_iov>[0] が完全に一杯になるまでデータを詰めてから、\n"
@@ -8416,18 +7033,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:156
-msgid ""
-"Similarly, B<process_vm_writev>()  writes out the entire contents of "
-"I<local_iov[0]> before proceeding to I<local_iov[1]>, and it completely "
-"fills I<remote_iov[0]> before proceeding to I<remote_iov[1]>."
+msgid "Similarly, B<process_vm_writev>()  writes out the entire contents of I<local_iov[0]> before proceeding to I<local_iov[1]>, and it completely fills I<remote_iov[0]> before proceeding to I<remote_iov[1]>."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:164
-msgid ""
-"The lengths of I<remote_iov[i].iov_len> and I<local_iov[i].iov_len> do not "
-"have to be the same.  Thus, it is possible to split a single local buffer "
-"into multiple remote buffers, or vice versa."
+msgid "The lengths of I<remote_iov[i].iov_len> and I<local_iov[i].iov_len> do not have to be the same.  Thus, it is possible to split a single local buffer into multiple remote buffers, or vice versa."
 msgstr ""
 
 #. type: Plain text
@@ -8439,60 +7050,27 @@ msgstr "I<flags> 引き数は現在使用されておらず、 0 を設定しな
 #.  as is done for readv()/writev()
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:181
-msgid ""
-"The values specified in the I<liovcnt> and I<riovcnt> arguments must be less "
-"than or equal to B<IOV_MAX> (defined in I<E<lt>limits.hE<gt>> or accessible "
-"via the call I<sysconf(_SC_IOV_MAX)>)."
+msgid "The values specified in the I<liovcnt> and I<riovcnt> arguments must be less than or equal to B<IOV_MAX> (defined in I<E<lt>limits.hE<gt>> or accessible via the call I<sysconf(_SC_IOV_MAX)>)."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:191
-msgid ""
-"The count arguments and I<local_iov> are checked before doing any "
-"transfers.  If the counts are too big, or I<local_iov> is invalid, or the "
-"addresses refer to regions that are inaccessible to the local process, none "
-"of the vectors will be processed and an error will be returned immediately."
+msgid "The count arguments and I<local_iov> are checked before doing any transfers.  If the counts are too big, or I<local_iov> is invalid, or the addresses refer to regions that are inaccessible to the local process, none of the vectors will be processed and an error will be returned immediately."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:211
-msgid ""
-"Note, however, that these system calls do not check the memory regions in "
-"the remote process until just before doing the read/write.  Consequently, a "
-"partial read/write (see RETURN VALUE)  may result if one of the "
-"I<remote_iov> elements points to an invalid memory region in the remote "
-"process.  No further reads/writes will be attempted beyond that point.  Keep "
-"this in mind when attempting to read data of unknown length (such as C "
-"strings that are null-terminated) from a remote process, by avoiding "
-"spanning memory pages (typically 4KiB) in a single remote I<iovec> element.  "
-"(Instead, split the remote read into two I<remote_iov> elements and have "
-"them merge back into a single write I<local_iov> entry.  The first read "
-"entry goes up to the page boundary, while the second starts on the next page "
-"boundary.)"
+msgid "Note, however, that these system calls do not check the memory regions in the remote process until just before doing the read/write.  Consequently, a partial read/write (see RETURN VALUE)  may result if one of the I<remote_iov> elements points to an invalid memory region in the remote process.  No further reads/writes will be attempted beyond that point.  Keep this in mind when attempting to read data of unknown length (such as C strings that are null-terminated) from a remote process, by avoiding spanning memory pages (typically 4KiB) in a single remote I<iovec> element.  (Instead, split the remote read into two I<remote_iov> elements and have them merge back into a single write I<local_iov> entry.  The first read entry goes up to the page boundary, while the second starts on the next page boundary.)"
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:225
-msgid ""
-"In order to read from or write to another process, either the caller must "
-"have the capability B<CAP_SYS_PTRACE>, or the real user ID, effective user "
-"ID, and saved set-user-ID of the remote process must match the real user ID "
-"of the caller I<and> the real group ID, effective group ID, and saved set-"
-"group-ID of the remote process must match the real group ID of the caller.  "
-"(The permission required is exactly the same as that required to perform a "
-"B<ptrace>(2)  B<PTRACE_ATTACH> on the remote process.)"
+msgid "In order to read from or write to another process, either the caller must have the capability B<CAP_SYS_PTRACE>, or the real user ID, effective user ID, and saved set-user-ID of the remote process must match the real user ID of the caller I<and> the real group ID, effective group ID, and saved set-group-ID of the remote process must match the real group ID of the caller.  (The permission required is exactly the same as that required to perform a B<ptrace>(2)  B<PTRACE_ATTACH> on the remote process.)"
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:241
-msgid ""
-"On success, B<process_vm_readv>()  returns the number of bytes read and "
-"B<process_vm_writev>()  returns the number of bytes written.  This return "
-"value may be less than the total number of requested bytes, if a partial "
-"read/write occurred.  (Partial transfers apply at the granularity of "
-"I<iovec> elements.  These system calls won't perform a partial transfer that "
-"splits a single I<iovec> element.)  The caller should check the return value "
-"to determine whether a partial read/write occurred."
+msgid "On success, B<process_vm_readv>()  returns the number of bytes read and B<process_vm_writev>()  returns the number of bytes written.  This return value may be less than the total number of requested bytes, if a partial read/write occurred.  (Partial transfers apply at the granularity of I<iovec> elements.  These system calls won't perform a partial transfer that splits a single I<iovec> element.)  The caller should check the return value to determine whether a partial read/write occurred."
 msgstr ""
 
 #. type: Plain text
@@ -8502,9 +7080,7 @@ msgstr "エラーの場合は -1 が返され、 I<errno> が適切に設定さ
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:257
-msgid ""
-"The sum of the I<iov_len> values of either I<local_iov> or I<remote_iov> "
-"overflows a I<ssize_t> value."
+msgid "The sum of the I<iov_len> values of either I<local_iov> or I<remote_iov> overflows a I<ssize_t> value."
 msgstr ""
 
 #. type: Plain text
@@ -8519,31 +7095,24 @@ msgstr "I<liovcnt> か I<riovcnt> が大きすぎる。"
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:272
-msgid ""
-"The memory described by I<local_iov> is outside the caller's accessible "
-"address space."
+msgid "The memory described by I<local_iov> is outside the caller's accessible address space."
 msgstr ""
 "I<local_iov> が示すメモリが呼び出し側がアクセス可能な\n"
 "アドレス空間の外にある。"
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:278
-msgid ""
-"The memory described by I<remote_iov> is outside the accessible address "
-"space of the process I<pid>."
+msgid "The memory described by I<remote_iov> is outside the accessible address space of the process I<pid>."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:283
-msgid ""
-"Could not allocate memory for internal copies of the I<iovec> structures."
+msgid "Could not allocate memory for internal copies of the I<iovec> structures."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:287
-msgid ""
-"The caller does not have permission to access the address space of the "
-"process I<pid>."
+msgid "The caller does not have permission to access the address space of the process I<pid>."
 msgstr ""
 "呼び出し側がプロセス I<pid> のアドレス空間に対するアクセス許可を\n"
 "持っていない。"
@@ -8555,9 +7124,7 @@ msgstr "ID が I<pid> のプロセスが存在しない。"
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:295
-msgid ""
-"These system calls were added in Linux 3.2.  Support is provided in glibc "
-"since version 2.15."
+msgid "These system calls were added in Linux 3.2.  Support is provided in glibc since version 2.15."
 msgstr ""
 "これらのシステムコールは Linux 3.2 で追加された。ライブラリによる\n"
 "サポートは glibc バージョン 2.15 以降で提供されている。"
@@ -8569,9 +7136,7 @@ msgstr "これらのシステムコールは非標準で Linux による拡張
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:303
-msgid ""
-"The data transfers performed by B<process_vm_readv>()  and "
-"B<process_vm_writev>()  are not guaranteed to be atomic in any way."
+msgid "The data transfers performed by B<process_vm_readv>()  and B<process_vm_writev>()  are not guaranteed to be atomic in any way."
 msgstr ""
 
 #.  Original user is MPI, http://www.mcs.anl.gov/research/projects/mpi/
@@ -8579,19 +7144,12 @@ msgstr ""
 #.  and http://marc.info/?l=linux-mm&m=130105930902915&w=2
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:311
-msgid ""
-"These system calls were designed to permit fast message passing by allowing "
-"messages to be exchanged with a single copy operation (rather than the "
-"double copy that would be required when using, for example, shared memory or "
-"pipes)."
+msgid "These system calls were designed to permit fast message passing by allowing messages to be exchanged with a single copy operation (rather than the double copy that would be required when using, for example, shared memory or pipes)."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/process_vm_readv.2:319
-msgid ""
-"The following code sample demonstrates the use of B<process_vm_readv>().  It "
-"reads 20 bytes at the address 0x10000 from the process with PID 10 and "
-"writes the first 10 bytes into I<buf1> and the second 10 bytes into I<buf2>."
+msgid "The following code sample demonstrates the use of B<process_vm_readv>().  It reads 20 bytes at the address 0x10000 from the process with PID 10 and writes the first 10 bytes into I<buf1> and the second 10 bytes into I<buf2>."
 msgstr ""
 
 #. type: Plain text
@@ -8695,31 +7253,13 @@ msgstr ""
 #. type: Plain text
 #: build/C/man2/ptrace.2:64
 #, fuzzy
-#| msgid ""
-#| "The B<ptrace>()  system call provides a means by which a parent process "
-#| "may observe and control the execution of another process, and examine and "
-#| "change its core image and registers.  It is primarily used to implement "
-#| "breakpoint debugging and system call tracing."
-msgid ""
-"The B<ptrace>()  system call provides a means by which one process (the "
-"\"tracer\")  may observe and control the execution of another process (the "
-"\"tracee\"), and examine and change the tracee's memory and registers.  It "
-"is primarily used to implement breakpoint debugging and system call tracing."
-msgstr ""
-"B<ptrace>()  システムコールは、親プロセスが、別のプロセスの実行の監視/制御を "
-"行ったり、コアイメージ (core image) やレジスタの調査/変更を 行ったりする手段"
-"を提供する。 B<ptrace>()  は、主にブレークポイントによるデバッグやシステム"
-"コールのトレースを 実装するのに用いられる。"
+#| msgid "The B<ptrace>()  system call provides a means by which a parent process may observe and control the execution of another process, and examine and change its core image and registers.  It is primarily used to implement breakpoint debugging and system call tracing."
+msgid "The B<ptrace>()  system call provides a means by which one process (the \"tracer\")  may observe and control the execution of another process (the \"tracee\"), and examine and change the tracee's memory and registers.  It is primarily used to implement breakpoint debugging and system call tracing."
+msgstr "B<ptrace>()  システムコールは、親プロセスが、別のプロセスの実行の監視/制御を 行ったり、コアイメージ (core image) やレジスタの調査/変更を 行ったりする手段を提供する。 B<ptrace>()  は、主にブレークポイントによるデバッグやシステムコールのトレースを 実装するのに用いられる。"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:75
-msgid ""
-"A tracee first needs to be attached to the tracer.  Attachment and "
-"subsequent commands are per thread: in a multithreaded process, every thread "
-"can be individually attached to a (potentially different) tracer, or left "
-"not attached and thus not debugged.  Therefore, \"tracee\" always means "
-"\"(one) thread\", never \"a (possibly multithreaded) process\".  Ptrace "
-"commands are always sent to a specific tracee using a call of the form"
+msgid "A tracee first needs to be attached to the tracer.  Attachment and subsequent commands are per thread: in a multithreaded process, every thread can be individually attached to a (potentially different) tracer, or left not attached and thus not debugged.  Therefore, \"tracee\" always means \"(one) thread\", never \"a (possibly multithreaded) process\".  Ptrace commands are always sent to a specific tracee using a call of the form"
 msgstr ""
 
 #. type: Plain text
@@ -8735,82 +7275,34 @@ msgstr "ここで I<pid> は対応する Linux スレッドのスレッド ID 
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:87
-msgid ""
-"(Note that in this page, a \"multithreaded process\" means a thread group "
-"consisting of threads created using the B<clone>(2)  B<CLONE_THREAD> flag.)"
+msgid "(Note that in this page, a \"multithreaded process\" means a thread group consisting of threads created using the B<clone>(2)  B<CLONE_THREAD> flag.)"
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:98
 #, fuzzy
-#| msgid ""
-#| "The parent can initiate a trace by calling B<fork>(2)  and having the "
-#| "resulting child do a B<PTRACE_TRACEME>, followed (typically) by an "
-#| "B<exec>(3).  Alternatively, the parent may commence trace of an existing "
-#| "process using B<PTRACE_ATTACH>."
-msgid ""
-"A process can initiate a trace by calling B<fork>(2)  and having the "
-"resulting child do a B<PTRACE_TRACEME>, followed (typically) by an "
-"B<execve>(2).  Alternatively, one process may commence tracing another "
-"process using B<PTRACE_ATTACH> or B<PTRACE_SEIZE>."
-msgstr ""
-"トレースを開始するには、まず親プロセスで B<fork>(2)  を呼び出す。生成された子"
-"プロセスで B<PTRACE_TRACEME> を行い、続いて (典型的には)  B<exec>(3)  を行な"
-"う。 別の方法としては、 親プロセスが既存のプロセスに対して B<PTRACE_ATTACH> "
-"を使用し、トレースを開始する。"
+#| msgid "The parent can initiate a trace by calling B<fork>(2)  and having the resulting child do a B<PTRACE_TRACEME>, followed (typically) by an B<exec>(3).  Alternatively, the parent may commence trace of an existing process using B<PTRACE_ATTACH>."
+msgid "A process can initiate a trace by calling B<fork>(2)  and having the resulting child do a B<PTRACE_TRACEME>, followed (typically) by an B<execve>(2).  Alternatively, one process may commence tracing another process using B<PTRACE_ATTACH> or B<PTRACE_SEIZE>."
+msgstr "トレースを開始するには、まず親プロセスで B<fork>(2)  を呼び出す。生成された子プロセスで B<PTRACE_TRACEME> を行い、続いて (典型的には)  B<exec>(3)  を行なう。 別の方法としては、 親プロセスが既存のプロセスに対して B<PTRACE_ATTACH> を使用し、トレースを開始する。"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:115
 #, fuzzy
-#| msgid ""
-#| "While being traced, the child will stop each time a signal is delivered, "
-#| "even if the signal is being ignored.  (The exception is B<SIGKILL>, which "
-#| "has its usual effect.)  The parent will be notified at its next "
-#| "B<wait>(2)  and may inspect and modify the child process while it is "
-#| "stopped.  The parent then causes the child to continue, optionally "
-#| "ignoring the delivered signal (or even delivering a different signal "
-#| "instead)."
-msgid ""
-"While being traced, the tracee will stop each time a signal is delivered, "
-"even if the signal is being ignored.  (An exception is B<SIGKILL>, which has "
-"its usual effect.)  The tracer will be notified at its next call to "
-"B<waitpid>(2)  (or one of the related \"wait\" system calls); that call will "
-"return a I<status> value containing information that indicates the cause of "
-"the stop in the tracee.  While the tracee is stopped, the tracer can use "
-"various ptrace requests to inspect and modify the tracee.  The tracer then "
-"causes the tracee to continue, optionally ignoring the delivered signal (or "
-"even delivering a different signal instead)."
-msgstr ""
-"トレースの実行中、子プロセスはシグナルが配送されるたびに、 たとえそのシグナル"
-"が無視すべきものであっても停止する (B<SIGKILL> は例外で、通常どおりの効果をも"
-"たらす)。 親プロセスには次の B<wait>(2)  で通知され、停止している間に子プロセ"
-"スを調べたり修正したりすることができる。 そして親プロセスは子プロセスの実行を"
-"再開させるが、配送された シグナルを無視することもできる (あるいは代わりに別の"
-"シグナルを 配送することもできる) 。"
+#| msgid "While being traced, the child will stop each time a signal is delivered, even if the signal is being ignored.  (The exception is B<SIGKILL>, which has its usual effect.)  The parent will be notified at its next B<wait>(2)  and may inspect and modify the child process while it is stopped.  The parent then causes the child to continue, optionally ignoring the delivered signal (or even delivering a different signal instead)."
+msgid "While being traced, the tracee will stop each time a signal is delivered, even if the signal is being ignored.  (An exception is B<SIGKILL>, which has its usual effect.)  The tracer will be notified at its next call to B<waitpid>(2)  (or one of the related \"wait\" system calls); that call will return a I<status> value containing information that indicates the cause of the stop in the tracee.  While the tracee is stopped, the tracer can use various ptrace requests to inspect and modify the tracee.  The tracer then causes the tracee to continue, optionally ignoring the delivered signal (or even delivering a different signal instead)."
+msgstr "トレースの実行中、子プロセスはシグナルが配送されるたびに、 たとえそのシグナルが無視すべきものであっても停止する (B<SIGKILL> は例外で、通常どおりの効果をもたらす)。 親プロセスには次の B<wait>(2)  で通知され、停止している間に子プロセスを調べたり修正したりすることができる。 そして親プロセスは子プロセスの実行を再開させるが、配送された シグナルを無視することもできる (あるいは代わりに別のシグナルを 配送することもできる) 。"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:125
-msgid ""
-"If the B<PTRACE_O_TRACEEXEC> option is not in effect, all successful calls "
-"to B<execve>(2)  by the traced process will cause it to be sent a B<SIGTRAP> "
-"signal, giving the parent a chance to gain control before the new program "
-"begins execution."
+msgid "If the B<PTRACE_O_TRACEEXEC> option is not in effect, all successful calls to B<execve>(2)  by the traced process will cause it to be sent a B<SIGTRAP> signal, giving the parent a chance to gain control before the new program begins execution."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:129
 #, fuzzy
-#| msgid ""
-#| "When the parent is finished tracing, it can terminate the child with "
-#| "B<PTRACE_KILL> or cause it to continue executing in a normal, untraced "
-#| "mode via B<PTRACE_DETACH>."
-msgid ""
-"When the tracer is finished tracing, it can cause the tracee to continue "
-"executing in a normal, untraced mode via B<PTRACE_DETACH>."
-msgstr ""
-"親プロセスがトレースを終了する際には、 B<PTRACE_KILL> を使用して子プロセスを"
-"終了させることもできるし、 B<PTRACE_DETACH> を用いて通常のトレースなしのモー"
-"ドにして、 実行を継続させることもできる。"
+#| msgid "When the parent is finished tracing, it can terminate the child with B<PTRACE_KILL> or cause it to continue executing in a normal, untraced mode via B<PTRACE_DETACH>."
+msgid "When the tracer is finished tracing, it can cause the tracee to continue executing in a normal, untraced mode via B<PTRACE_DETACH>."
+msgstr "親プロセスがトレースを終了する際には、 B<PTRACE_KILL> を使用して子プロセスを終了させることもできるし、 B<PTRACE_DETACH> を用いて通常のトレースなしのモードにして、 実行を継続させることもできる。"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:133
@@ -8825,34 +7317,15 @@ msgstr "B<PTRACE_TRACEME>"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:143
-msgid ""
-"Indicate that this process is to be traced by its parent.  A process "
-"probably shouldn't make this request if its parent isn't expecting to trace "
-"it.  (I<pid>, I<addr>, and I<data> are ignored.)"
-msgstr ""
-"このプロセスが親プロセスによってトレースされることを表す。親プロセスが自プロ"
-"セスをトレースするつもりがない場合には、 おそらくこのプロセスは本要求を行うべ"
-"きではないだろう。 (I<pid>, I<addr>, I<data> は無視される。)"
+msgid "Indicate that this process is to be traced by its parent.  A process probably shouldn't make this request if its parent isn't expecting to trace it.  (I<pid>, I<addr>, and I<data> are ignored.)"
+msgstr "このプロセスが親プロセスによってトレースされることを表す。親プロセスが自プロセスをトレースするつもりがない場合には、 おそらくこのプロセスは本要求を行うべきではないだろう。 (I<pid>, I<addr>, I<data> は無視される。)"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:158
 #, fuzzy
-#| msgid ""
-#| "The above request is used only by the child process; the rest are used "
-#| "only by the parent.  In the following requests, I<pid> specifies the "
-#| "child process to be acted on.  For requests other than B<PTRACE_KILL>, "
-#| "the child process must be stopped."
-msgid ""
-"The B<PTRACE_TRACEME> request is used only by the tracee; the remaining "
-"requests are used only by the tracer.  In the following requests, I<pid> "
-"specifies the thread ID of the tracee to be acted on.  For requests other "
-"than B<PTRACE_ATTACH>, B<PTRACE_SEIZE>, B<PTRACE_INTERRUPT>, and "
-"B<PTRACE_KILL>, the tracee must be stopped."
-msgstr ""
-"上記の要求は子プロセスだけが行なうものである。 残りは親プロセスだけが行なうも"
-"のである。 以下の要求では、I<pid> で操作の対象となる 子プロセスを指定する。 "
-"B<PTRACE_KILL> を除き、要求を行なうためには 子プロセスは停止していなければな"
-"らない。"
+#| msgid "The above request is used only by the child process; the rest are used only by the parent.  In the following requests, I<pid> specifies the child process to be acted on.  For requests other than B<PTRACE_KILL>, the child process must be stopped."
+msgid "The B<PTRACE_TRACEME> request is used only by the tracee; the remaining requests are used only by the tracer.  In the following requests, I<pid> specifies the thread ID of the tracee to be acted on.  For requests other than B<PTRACE_ATTACH>, B<PTRACE_SEIZE>, B<PTRACE_INTERRUPT>, and B<PTRACE_KILL>, the tracee must be stopped."
+msgstr "上記の要求は子プロセスだけが行なうものである。 残りは親プロセスだけが行なうものである。 以下の要求では、I<pid> で操作の対象となる 子プロセスを指定する。 B<PTRACE_KILL> を除き、要求を行なうためには 子プロセスは停止していなければならない。"
 
 #. type: TP
 #: build/C/man2/ptrace.2:158
@@ -8863,21 +7336,9 @@ msgstr "B<PTRACE_PEEKTEXT>, B<PTRACE_PEEKDATA>"
 #. type: Plain text
 #: build/C/man2/ptrace.2:169
 #, fuzzy
-#| msgid ""
-#| "Reads a word at the location I<addr> in the child's memory, returning the "
-#| "word as the result of the B<ptrace>()  call.  Linux does not have "
-#| "separate text and data address spaces, so the two requests are currently "
-#| "equivalent.  (The argument I<data> is ignored.)"
-msgid ""
-"Read a word at the address I<addr> in the tracee's memory, returning the "
-"word as the result of the B<ptrace>()  call.  Linux does not have separate "
-"text and data address spaces, so these two requests are currently "
-"equivalent.  (I<data> is ignored; but see NOTES.)"
-msgstr ""
-"子プロセスのメモリの I<addr> の位置から 1 ワードを読み出す。読み出したワード"
-"は B<ptrace>()  の返り値として返される。 Linux ではテキスト (text) とデータ "
-"(data) で 同じアドレス空間を使用するため、この 2 つの要求は現在のところ 同じ"
-"ものである。 (引き数 I<data> は無視される。)"
+#| msgid "Reads a word at the location I<addr> in the child's memory, returning the word as the result of the B<ptrace>()  call.  Linux does not have separate text and data address spaces, so the two requests are currently equivalent.  (The argument I<data> is ignored.)"
+msgid "Read a word at the address I<addr> in the tracee's memory, returning the word as the result of the B<ptrace>()  call.  Linux does not have separate text and data address spaces, so these two requests are currently equivalent.  (I<data> is ignored; but see NOTES.)"
+msgstr "子プロセスのメモリの I<addr> の位置から 1 ワードを読み出す。読み出したワードは B<ptrace>()  の返り値として返される。 Linux ではテキスト (text) とデータ (data) で 同じアドレス空間を使用するため、この 2 つの要求は現在のところ 同じものである。 (引き数 I<data> は無視される。)"
 
 #. type: TP
 #: build/C/man2/ptrace.2:169
@@ -8890,25 +7351,9 @@ msgstr "B<PTRACE_PEEKUSER>"
 #. type: Plain text
 #: build/C/man2/ptrace.2:187
 #, fuzzy
-#| msgid ""
-#| "Reads a word at offset I<addr> in the child's USER area, which holds the "
-#| "registers and other information about the process (see I<E<lt>sys/user."
-#| "hE<gt>>).  The word is returned as the result of the B<ptrace>()  call.  "
-#| "Typically the offset must be word-aligned, though this might vary by "
-#| "architecture.  See NOTES.  (I<data> is ignored.)"
-msgid ""
-"Read a word at offset I<addr> in the tracee's USER area, which holds the "
-"registers and other information about the process (see I<E<lt>sys/user."
-"hE<gt>>).  The word is returned as the result of the B<ptrace>()  call.  "
-"Typically, the offset must be word-aligned, though this might vary by "
-"architecture.  See NOTES.  (I<data> is ignored; but see NOTES.)"
-msgstr ""
-"子プロセスの USER 領域のオフセット I<addr> の位置から 1 ワードを読み込む。"
-"USER 領域にはそのプロセスの レジスタ (registers) などの情報が保持されている "
-"(I<E<lt>sys/user.hE<gt>> を参照)。読み込んだワードは B<ptrace>()  コールの結"
-"果として返される。 たいていはオフセットはワード境界になければならないが、 "
-"アーキテクチャによってはその必要はない。 「注意」の節を参照。 (I<data> は無視"
-"される。 )"
+#| msgid "Reads a word at offset I<addr> in the child's USER area, which holds the registers and other information about the process (see I<E<lt>sys/user.hE<gt>>).  The word is returned as the result of the B<ptrace>()  call.  Typically the offset must be word-aligned, though this might vary by architecture.  See NOTES.  (I<data> is ignored.)"
+msgid "Read a word at offset I<addr> in the tracee's USER area, which holds the registers and other information about the process (see I<E<lt>sys/user.hE<gt>>).  The word is returned as the result of the B<ptrace>()  call.  Typically, the offset must be word-aligned, though this might vary by architecture.  See NOTES.  (I<data> is ignored; but see NOTES.)"
+msgstr "子プロセスの USER 領域のオフセット I<addr> の位置から 1 ワードを読み込む。USER 領域にはそのプロセスの レジスタ (registers) などの情報が保持されている (I<E<lt>sys/user.hE<gt>> を参照)。読み込んだワードは B<ptrace>()  コールの結果として返される。 たいていはオフセットはワード境界になければならないが、 アーキテクチャによってはその必要はない。 「注意」の節を参照。 (I<data> は無視される。 )"
 
 #. type: TP
 #: build/C/man2/ptrace.2:187
@@ -8919,16 +7364,9 @@ msgstr "B<PTRACE_POKETEXT>, B<PTRACE_POKEDATA>"
 #. type: Plain text
 #: build/C/man2/ptrace.2:199
 #, fuzzy
-#| msgid ""
-#| "Copies the word I<data> to location I<addr> in the child's memory.  As "
-#| "above, the two requests are currently equivalent."
-msgid ""
-"Copy the word I<data> to the address I<addr> in the tracee's memory.  As for "
-"B<PTRACE_PEEKTEXT> and B<PTRACE_PEEKDATA>, these two requests are currently "
-"equivalent."
-msgstr ""
-"ワード I<data> を子プロセスのメモリの I<addr> の位置へコピーする。上と同様"
-"に、現在のところ二つの 要求は同じものである。"
+#| msgid "Copies the word I<data> to location I<addr> in the child's memory.  As above, the two requests are currently equivalent."
+msgid "Copy the word I<data> to the address I<addr> in the tracee's memory.  As for B<PTRACE_PEEKTEXT> and B<PTRACE_PEEKDATA>, these two requests are currently equivalent."
+msgstr "ワード I<data> を子プロセスのメモリの I<addr> の位置へコピーする。上と同様に、現在のところ二つの 要求は同じものである。"
 
 #. type: TP
 #: build/C/man2/ptrace.2:199
@@ -8943,21 +7381,9 @@ msgstr "B<PTRACE_POKEUSER>"
 #. type: Plain text
 #: build/C/man2/ptrace.2:215
 #, fuzzy
-#| msgid ""
-#| "Copies the word I<data> to offset I<addr> in the child's USER area.  As "
-#| "above, the offset must typically be word-aligned.  In order to maintain "
-#| "the integrity of the kernel, some modifications to the USER area are "
-#| "disallowed."
-msgid ""
-"Copy the word I<data> to offset I<addr> in the tracee's USER area.  As for "
-"B<PTRACE_PEEKUSER>, the offset must typically be word-aligned.  In order to "
-"maintain the integrity of the kernel, some modifications to the USER area "
-"are disallowed."
-msgstr ""
-"ワード I<data> を子プロセスの USER 領域のオフセット I<addr> の位置にコピーす"
-"る。 上と同様に、通常、オフセットはワード境界になければならない。 カーネルの"
-"完全性 (integrity) を維持するため、 変更内容によっては USER 領域の変更は禁止"
-"されている。"
+#| msgid "Copies the word I<data> to offset I<addr> in the child's USER area.  As above, the offset must typically be word-aligned.  In order to maintain the integrity of the kernel, some modifications to the USER area are disallowed."
+msgid "Copy the word I<data> to offset I<addr> in the tracee's USER area.  As for B<PTRACE_PEEKUSER>, the offset must typically be word-aligned.  In order to maintain the integrity of the kernel, some modifications to the USER area are disallowed."
+msgstr "ワード I<data> を子プロセスの USER 領域のオフセット I<addr> の位置にコピーする。 上と同様に、通常、オフセットはワード境界になければならない。 カーネルの完全性 (integrity) を維持するため、 変更内容によっては USER 領域の変更は禁止されている。"
 
 #. type: TP
 #: build/C/man2/ptrace.2:215
@@ -8968,22 +7394,9 @@ msgstr "B<PTRACE_GETREGS>, B<PTRACE_GETFPREGS>"
 #. type: Plain text
 #: build/C/man2/ptrace.2:238
 #, fuzzy
-#| msgid ""
-#| "Copies the child's general purpose or floating-point registers, "
-#| "respectively, to location I<data> in the parent.  See I<E<lt>sys/user."
-#| "hE<gt>> for information on the format of this data.  (I<addr> is ignored.)"
-msgid ""
-"Copy the tracee's general-purpose or floating-point registers, respectively, "
-"to the address I<data> in the tracer.  See I<E<lt>sys/user.hE<gt>> for "
-"information on the format of this data.  (I<addr> is ignored.)  Note that "
-"SPARC systems have the meaning of I<data> and I<addr> reversed; that is, "
-"I<data> is ignored and the registers are copied to the address I<addr>.  "
-"B<PTRACE_GETREGS> and B<PTRACE_GETFPREGS> are not present on all "
-"architectures."
-msgstr ""
-"それぞれ、子プロセスの汎用レジスタ、浮動小数点レジスタを親プロセスの I<data> "
-"の位置にコピーする。この data の書式に関しては I<E<lt>sys/user.hE<gt>> を参照"
-"すること。(I<addr> は無視される。)"
+#| msgid "Copies the child's general purpose or floating-point registers, respectively, to location I<data> in the parent.  See I<E<lt>sys/user.hE<gt>> for information on the format of this data.  (I<addr> is ignored.)"
+msgid "Copy the tracee's general-purpose or floating-point registers, respectively, to the address I<data> in the tracer.  See I<E<lt>sys/user.hE<gt>> for information on the format of this data.  (I<addr> is ignored.)  Note that SPARC systems have the meaning of I<data> and I<addr> reversed; that is, I<data> is ignored and the registers are copied to the address I<addr>.  B<PTRACE_GETREGS> and B<PTRACE_GETFPREGS> are not present on all architectures."
+msgstr "それぞれ、子プロセスの汎用レジスタ、浮動小数点レジスタを親プロセスの I<data> の位置にコピーする。この data の書式に関しては I<E<lt>sys/user.hE<gt>> を参照すること。(I<addr> は無視される。)"
 
 #. type: TP
 #: build/C/man2/ptrace.2:238
@@ -8993,15 +7406,7 @@ msgstr " B<PTRACE_GETREGSET> (since Linux 2.6.34)"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:259
-msgid ""
-"Read the tracee's registers.  I<addr> specifies, in an architecture-"
-"dependent way, the type of registers to be read.  B<NT_PRSTATUS> (with "
-"numerical value 1)  usually results in reading of general-purpose "
-"registers.  If the CPU has, for example, floating-point and/or vector "
-"registers, they can be retrieved by setting I<addr> to the corresponding "
-"B<NT_foo> constant.  I<data> points to a B<struct iovec>, which describes "
-"the destination buffer's location and length.  On return, the kernel "
-"modifies B<iov.len> to indicate the actual number of bytes returned."
+msgid "Read the tracee's registers.  I<addr> specifies, in an architecture-dependent way, the type of registers to be read.  B<NT_PRSTATUS> (with numerical value 1)  usually results in reading of general-purpose registers.  If the CPU has, for example, floating-point and/or vector registers, they can be retrieved by setting I<addr> to the corresponding B<NT_foo> constant.  I<data> points to a B<struct iovec>, which describes the destination buffer's location and length.  On return, the kernel modifies B<iov.len> to indicate the actual number of bytes returned."
 msgstr ""
 
 #. type: TP
@@ -9015,23 +7420,9 @@ msgstr "B<PTRACE_SETREGS>, B<PTRACE_SETFPREGS>"
 #. type: Plain text
 #: build/C/man2/ptrace.2:284
 #, fuzzy
-#| msgid ""
-#| "Copies the child's general purpose or floating-point registers, "
-#| "respectively, from location I<data> in the parent.  As for "
-#| "B<PTRACE_POKEUSER>, some general purpose register modifications may be "
-#| "disallowed.  (I<addr> is ignored.)"
-msgid ""
-"Modify the tracee's general-purpose or floating-point registers, "
-"respectively, from the address I<data> in the tracer.  As for "
-"B<PTRACE_POKEUSER>, some general-purpose register modifications may be "
-"disallowed.  (I<addr> is ignored.)  Note that SPARC systems have the meaning "
-"of I<data> and I<addr> reversed; that is, I<data> is ignored and the "
-"registers are copied from the address I<addr>.  B<PTRACE_SETREGS> and "
-"B<PTRACE_SETFPREGS> are not present on all architectures."
-msgstr ""
-"それぞれ、子プロセスの汎用レジスタ、浮動小数点レジスタに 親プロセスの "
-"I<date> の位置からコピーする。 B<PTRACE_POKEUSER> と同様に、汎用レジスタに"
-"よっては 変更が禁止されている場合がある。 (I<addr> は無視される。)"
+#| msgid "Copies the child's general purpose or floating-point registers, respectively, from location I<data> in the parent.  As for B<PTRACE_POKEUSER>, some general purpose register modifications may be disallowed.  (I<addr> is ignored.)"
+msgid "Modify the tracee's general-purpose or floating-point registers, respectively, from the address I<data> in the tracer.  As for B<PTRACE_POKEUSER>, some general-purpose register modifications may be disallowed.  (I<addr> is ignored.)  Note that SPARC systems have the meaning of I<data> and I<addr> reversed; that is, I<data> is ignored and the registers are copied from the address I<addr>.  B<PTRACE_SETREGS> and B<PTRACE_SETFPREGS> are not present on all architectures."
+msgstr "それぞれ、子プロセスの汎用レジスタ、浮動小数点レジスタに 親プロセスの I<date> の位置からコピーする。 B<PTRACE_POKEUSER> と同様に、汎用レジスタによっては 変更が禁止されている場合がある。 (I<addr> は無視される。)"
 
 #. type: TP
 #: build/C/man2/ptrace.2:284
@@ -9041,9 +7432,7 @@ msgstr " B<PTRACE_SETREGSET> (since Linux 2.6.34)"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:293
-msgid ""
-"Modify the tracee's registers.  The meaning of I<addr> and I<data> is "
-"analogous to B<PTRACE_GETREGSET>."
+msgid "Modify the tracee's registers.  The meaning of I<addr> and I<data> is analogous to B<PTRACE_GETREGSET>."
 msgstr ""
 
 #. type: TP
@@ -9055,18 +7444,9 @@ msgstr "B<PTRACE_GETSIGINFO> (Linux 2.3.99-pre6 以降)"
 #. type: Plain text
 #: build/C/man2/ptrace.2:305
 #, fuzzy
-#| msgid ""
-#| "Retrieve information about the signal that caused the stop.  Copies a "
-#| "I<siginfo_t> structure (see B<sigaction>(2))  from the child to location "
-#| "I<data> in the parent.  (I<addr> is ignored.)"
-msgid ""
-"Retrieve information about the signal that caused the stop.  Copy a "
-"I<siginfo_t> structure (see B<sigaction>(2))  from the tracee to the address "
-"I<data> in the tracer.  (I<addr> is ignored.)"
-msgstr ""
-"停止の原因となったシグナルに関する情報を取得する。 I<siginfo_t> 構造体 "
-"(B<sigaction>(2)  参照) を子プロセスから親プロセスの I<data> の位置にコピーす"
-"る。 (I<addr> は無視される。)"
+#| msgid "Retrieve information about the signal that caused the stop.  Copies a I<siginfo_t> structure (see B<sigaction>(2))  from the child to location I<data> in the parent.  (I<addr> is ignored.)"
+msgid "Retrieve information about the signal that caused the stop.  Copy a I<siginfo_t> structure (see B<sigaction>(2))  from the tracee to the address I<data> in the tracer.  (I<addr> is ignored.)"
+msgstr "停止の原因となったシグナルに関する情報を取得する。 I<siginfo_t> 構造体 (B<sigaction>(2)  参照) を子プロセスから親プロセスの I<data> の位置にコピーする。 (I<addr> は無視される。)"
 
 #. type: TP
 #: build/C/man2/ptrace.2:305
@@ -9077,24 +7457,9 @@ msgstr "B<PTRACE_SETSIGINFO> (Linux 2.3.99-pre6 以降)"
 #. type: Plain text
 #: build/C/man2/ptrace.2:321
 #, fuzzy
-#| msgid ""
-#| "Set signal information.  Copies a I<siginfo_t> structure from location "
-#| "I<data> in the parent to the child.  This will only affect signals that "
-#| "would normally be delivered to the child and were caught by the tracer.  "
-#| "It may be difficult to tell these normal signals from synthetic signals "
-#| "generated by B<ptrace>()  itself.  (I<addr> is ignored.)"
-msgid ""
-"Set signal information: copy a I<siginfo_t> structure from the address "
-"I<data> in the tracer to the tracee.  This will affect only signals that "
-"would normally be delivered to the tracee and were caught by the tracer.  It "
-"may be difficult to tell these normal signals from synthetic signals "
-"generated by B<ptrace>()  itself.  (I<addr> is ignored.)"
-msgstr ""
-"シグナル情報を設定する。 I<siginfo_t> 構造体を親プロセスのデータ I<data> の位"
-"置から 子プロセスにコピーする。 この処理を行うことができるのは、子プロセスに"
-"通常は配送されるはずで トレーサに捕捉されたシグナルについてだけである。 これ"
-"らの通常のシグナルと B<ptrace>()  自身が発生するシグナルを見分けるのは難しい"
-"かもしれない。 (I<addr> は無視される。)"
+#| msgid "Set signal information.  Copies a I<siginfo_t> structure from location I<data> in the parent to the child.  This will only affect signals that would normally be delivered to the child and were caught by the tracer.  It may be difficult to tell these normal signals from synthetic signals generated by B<ptrace>()  itself.  (I<addr> is ignored.)"
+msgid "Set signal information: copy a I<siginfo_t> structure from the address I<data> in the tracer to the tracee.  This will affect only signals that would normally be delivered to the tracee and were caught by the tracer.  It may be difficult to tell these normal signals from synthetic signals generated by B<ptrace>()  itself.  (I<addr> is ignored.)"
+msgstr "シグナル情報を設定する。 I<siginfo_t> 構造体を親プロセスのデータ I<data> の位置から 子プロセスにコピーする。 この処理を行うことができるのは、子プロセスに通常は配送されるはずで トレーサに捕捉されたシグナルについてだけである。 これらの通常のシグナルと B<ptrace>()  自身が発生するシグナルを見分けるのは難しいかもしれない。 (I<addr> は無視される。)"
 
 #. type: TP
 #: build/C/man2/ptrace.2:321
@@ -9105,16 +7470,7 @@ msgstr "B<PTRACE_PEEKSIGINFO> (Linux 3.10 以降)"
 #.  commit 84c751bd4aebbaae995fe32279d3dba48327bad4
 #. type: Plain text
 #: build/C/man2/ptrace.2:347
-msgid ""
-"Retrieve I<siginfo_t> structures without removing signals from a queue.  "
-"I<addr> points to a I<ptrace_peeksiginfo_args> structure that specifies the "
-"ordinal position from which copying of signals should start, and the number "
-"of signals to copy.  I<siginfo_t> structures are copied into the buffer "
-"pointed to by I<data>.  The return value contains the number of copied "
-"signals (zero indicates that there is no signal corresponding to the "
-"specified ordinal position).  Within the returned I<siginfo> structures, the "
-"I<si_code> field includes information (B<__SI_CHLD>, B<__SI_FAULT>, etc.) "
-"that are not otherwise exposed to user space."
+msgid "Retrieve I<siginfo_t> structures without removing signals from a queue.  I<addr> points to a I<ptrace_peeksiginfo_args> structure that specifies the ordinal position from which copying of signals should start, and the number of signals to copy.  I<siginfo_t> structures are copied into the buffer pointed to by I<data>.  The return value contains the number of copied signals (zero indicates that there is no signal corresponding to the specified ordinal position).  Within the returned I<siginfo> structures, the I<si_code> field includes information (B<__SI_CHLD>, B<__SI_FAULT>, etc.) that are not otherwise exposed to user space."
 msgstr ""
 
 #. type: Plain text
@@ -9131,10 +7487,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:363
-msgid ""
-"Currently, there is only one flag, B<PTRACE_PEEKSIGINFO_SHARED>, for dumping "
-"signals from the process-wide signal queue.  If this flag is not set, "
-"signals are read from the per-thread queue of the specified thread."
+msgid "Currently, there is only one flag, B<PTRACE_PEEKSIGINFO_SHARED>, for dumping signals from the process-wide signal queue.  If this flag is not set, signals are read from the per-thread queue of the specified thread."
 msgstr ""
 
 #. type: TP
@@ -9146,11 +7499,7 @@ msgstr "B<PTRACE_GETSIGMASK> (Linux 3.11 以降)"
 #.  commit 29000caecbe87b6b66f144f72111f0d02fbbf0c1
 #. type: Plain text
 #: build/C/man2/ptrace.2:380
-msgid ""
-"Place a copy of the mask of blocked signals (see B<sigprocmask>(2))  in the "
-"buffer pointed to by I<data>, which should be a pointer to a buffer of type "
-"I<sigset_t>.  The I<addr> argument contains the size of the buffer pointed "
-"to by I<data> (i.e., I<sizeof(sigset_t)>)."
+msgid "Place a copy of the mask of blocked signals (see B<sigprocmask>(2))  in the buffer pointed to by I<data>, which should be a pointer to a buffer of type I<sigset_t>.  The I<addr> argument contains the size of the buffer pointed to by I<data> (i.e., I<sizeof(sigset_t)>)."
 msgstr ""
 
 #. type: TP
@@ -9161,11 +7510,7 @@ msgstr "B<PTRACE_SETSIGMASK> (Linux 3.11 以降)"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:394
-msgid ""
-"Change the mask of blocked signals (see B<sigprocmask>(2))  to the value "
-"specified in the buffer pointed to by I<data>, which should be a pointer to "
-"a buffer of type I<sigset_t>.  The I<addr> argument contains the size of the "
-"buffer pointed to by I<data> (i.e., I<sizeof(sigset_t)>)."
+msgid "Change the mask of blocked signals (see B<sigprocmask>(2))  to the value specified in the buffer pointed to by I<data>, which should be a pointer to a buffer of type I<sigset_t>.  The I<addr> argument contains the size of the buffer pointed to by I<data> (i.e., I<sizeof(sigset_t)>)."
 msgstr ""
 
 #. type: TP
@@ -9176,14 +7521,8 @@ msgstr "B<PTRACE_SETOPTIONS> (Linux 2.4.6 以降; バグの章にある警告も
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:403
-msgid ""
-"Set ptrace options from I<data>.  (I<addr> is ignored.)  I<data> is "
-"interpreted as a bit mask of options, which are specified by the following "
-"flags:"
-msgstr ""
-"I<data> に基づいて ptrace のオプションを設定する (I<addr> は無視される)。 "
-"I<data> はオプションのビットマスクとして解釈され、 オプションには以下のフラグ"
-"を指定できる:"
+msgid "Set ptrace options from I<data>.  (I<addr> is ignored.)  I<data> is interpreted as a bit mask of options, which are specified by the following flags:"
+msgstr "I<data> に基づいて ptrace のオプションを設定する (I<addr> は無視される)。 I<data> はオプションのビットマスクとして解釈され、 オプションには以下のフラグを指定できる:"
 
 #. type: TP
 #: build/C/man2/ptrace.2:404
@@ -9194,10 +7533,7 @@ msgstr " B<PTRACE_O_EXITKILL> (since Linux 3.8)"
 #.  commit 992fb6e170639b0849bace8e49bf31bd37c4123
 #. type: Plain text
 #: build/C/man2/ptrace.2:412
-msgid ""
-"If a tracer sets this flag, a B<SIGKILL> signal will be sent to every tracee "
-"if the tracer exits.  This option is useful for ptrace jailers that want to "
-"ensure that tracees can never escape the tracer's control."
+msgid "If a tracer sets this flag, a B<SIGKILL> signal will be sent to every tracee if the tracer exits.  This option is useful for ptrace jailers that want to ensure that tracees can never escape the tracer's control."
 msgstr ""
 
 #. type: TP
@@ -9209,21 +7545,9 @@ msgstr "B<PTRACE_O_TRACECLONE> (Linux 2.5.46 以降)"
 #. type: Plain text
 #: build/C/man2/ptrace.2:429
 #, fuzzy
-#| msgid ""
-#| "Stop the child at the next B<fork>(2)  call with I<SIGTRAP | "
-#| "PTRACE_EVENT_FORK\\ E<lt>E<lt>\\ 8> and automatically start tracing the "
-#| "newly forked process, which will start with a B<SIGSTOP>.  The PID for "
-#| "the new process can be retrieved with B<PTRACE_GETEVENTMSG>."
-msgid ""
-"Stop the tracee at the next B<clone>(2)  and automatically start tracing the "
-"newly cloned process, which will start with a B<SIGSTOP>, or "
-"B<PTRACE_EVENT_STOP> if B<PTRACE_SEIZE> was used.  A B<waitpid>(2)  by the "
-"tracer will return a I<status> value such that"
-msgstr ""
-"次の B<fork>(2)  呼び出し時に I<SIGTRAP | PTRACE_EVENT_FORK\\ E<lt>E<lt>\\ "
-"8> で 子プロセスの動作を停止させ、 新たに fork されたプロセスのトレースを自動"
-"的に開始し、 B<SIGSTOP> でそのプロセスの実行を開始する。 新しいプロセスの "
-"PID は B<PTRACE_GETEVENTMSG> で取得できる。"
+#| msgid "Stop the child at the next B<fork>(2)  call with I<SIGTRAP | PTRACE_EVENT_FORK\\ E<lt>E<lt>\\ 8> and automatically start tracing the newly forked process, which will start with a B<SIGSTOP>.  The PID for the new process can be retrieved with B<PTRACE_GETEVENTMSG>."
+msgid "Stop the tracee at the next B<clone>(2)  and automatically start tracing the newly cloned process, which will start with a B<SIGSTOP>, or B<PTRACE_EVENT_STOP> if B<PTRACE_SEIZE> was used.  A B<waitpid>(2)  by the tracer will return a I<status> value such that"
+msgstr "次の B<fork>(2)  呼び出し時に I<SIGTRAP | PTRACE_EVENT_FORK\\ E<lt>E<lt>\\ 8> で 子プロセスの動作を停止させ、 新たに fork されたプロセスのトレースを自動的に開始し、 B<SIGSTOP> でそのプロセスの実行を開始する。 新しいプロセスの PID は B<PTRACE_GETEVENTMSG> で取得できる。"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:432
@@ -9240,32 +7564,9 @@ msgstr "新規のプロセスの PID は B<PTRACE_GETEVENTMSG> で取得でき
 #. type: Plain text
 #: build/C/man2/ptrace.2:457
 #, fuzzy
-#| msgid ""
-#| "Stop the child at the next B<clone>(2)  call with I<SIGTRAP | "
-#| "PTRACE_EVENT_CLONE\\ E<lt>E<lt>\\ 8> and automatically start tracing the "
-#| "newly cloned process, which will start with a B<SIGSTOP>.  The PID for "
-#| "the new process can be retrieved with B<PTRACE_GETEVENTMSG>.  This option "
-#| "may not catch B<clone>(2)  calls in all cases.  If the child calls "
-#| "B<clone>(2)  with the B<CLONE_VFORK> flag, B<PTRACE_EVENT_VFORK> will be "
-#| "delivered instead if B<PTRACE_O_TRACEVFORK> is set; otherwise if the "
-#| "child calls B<clone>(2)  with the exit signal set to B<SIGCHLD>, "
-#| "B<PTRACE_EVENT_FORK> will be delivered if B<PTRACE_O_TRACEFORK> is set."
-msgid ""
-"This option may not catch B<clone>(2)  calls in all cases.  If the tracee "
-"calls B<clone>(2)  with the B<CLONE_VFORK> flag, B<PTRACE_EVENT_VFORK> will "
-"be delivered instead if B<PTRACE_O_TRACEVFORK> is set; otherwise if the "
-"tracee calls B<clone>(2)  with the exit signal set to B<SIGCHLD>, "
-"B<PTRACE_EVENT_FORK> will be delivered if B<PTRACE_O_TRACEFORK> is set."
-msgstr ""
-"次の B<clone>(2)  呼び出し時に I<SIGTRAP | PTRACE_EVENT_CLONE\\ E<lt>E<lt> "
-"\\8> で 子プロセスの動作を停止させ、 新たに clone で作成されたプロセスのト"
-"レースを自動的に開始し、 B<SIGSTOP> でプロセスの実行を開始する。 新しいプロセ"
-"スの PID は B<PTRACE_GETEVENTMSG> で取得できる。 このオプションで全ての "
-"B<clone>(2)  コールを捕まえられるわけではない。 子プロセスが B<CLONE_VFORK> "
-"フラグ付きで B<clone>(2)  を呼び出した場合、 B<PTRACE_O_TRACEVFORK> が設定さ"
-"れていれば代わりに B<PTRACE_EVENT_VFORK> が配送される。 また、子プロセスが終"
-"了シグナルを B<SIGCHLD> に設定して B<clone>(2)  を呼び出した場合は、 "
-"B<PTRACE_O_TRACEFORK> が設定されていれば B<PTRACE_EVENT_FORK> が配送される。"
+#| msgid "Stop the child at the next B<clone>(2)  call with I<SIGTRAP | PTRACE_EVENT_CLONE\\ E<lt>E<lt>\\ 8> and automatically start tracing the newly cloned process, which will start with a B<SIGSTOP>.  The PID for the new process can be retrieved with B<PTRACE_GETEVENTMSG>.  This option may not catch B<clone>(2)  calls in all cases.  If the child calls B<clone>(2)  with the B<CLONE_VFORK> flag, B<PTRACE_EVENT_VFORK> will be delivered instead if B<PTRACE_O_TRACEVFORK> is set; otherwise if the child calls B<clone>(2)  with the exit signal set to B<SIGCHLD>, B<PTRACE_EVENT_FORK> will be delivered if B<PTRACE_O_TRACEFORK> is set."
+msgid "This option may not catch B<clone>(2)  calls in all cases.  If the tracee calls B<clone>(2)  with the B<CLONE_VFORK> flag, B<PTRACE_EVENT_VFORK> will be delivered instead if B<PTRACE_O_TRACEVFORK> is set; otherwise if the tracee calls B<clone>(2)  with the exit signal set to B<SIGCHLD>, B<PTRACE_EVENT_FORK> will be delivered if B<PTRACE_O_TRACEFORK> is set."
+msgstr "次の B<clone>(2)  呼び出し時に I<SIGTRAP | PTRACE_EVENT_CLONE\\ E<lt>E<lt> \\8> で 子プロセスの動作を停止させ、 新たに clone で作成されたプロセスのトレースを自動的に開始し、 B<SIGSTOP> でプロセスの実行を開始する。 新しいプロセスの PID は B<PTRACE_GETEVENTMSG> で取得できる。 このオプションで全ての B<clone>(2)  コールを捕まえられるわけではない。 子プロセスが B<CLONE_VFORK> フラグ付きで B<clone>(2)  を呼び出した場合、 B<PTRACE_O_TRACEVFORK> が設定されていれば代わりに B<PTRACE_EVENT_VFORK> が配送される。 また、子プロセスが終了シグナルを B<SIGCHLD> に設定して B<clone>(2)  を呼び出した場合は、 B<PTRACE_O_TRACEFORK> が設定されていれば B<PTRACE_EVENT_FORK> が配送される。"
 
 #. type: TP
 #: build/C/man2/ptrace.2:457
@@ -9275,9 +7576,7 @@ msgstr "B<PTRACE_O_TRACEEXEC> (Linux 2.5.46 以降)"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:466
-msgid ""
-"Stop the tracee at the next B<execve>(2).  A B<waitpid>(2)  by the tracer "
-"will return a I<status> value such that"
+msgid "Stop the tracee at the next B<execve>(2).  A B<waitpid>(2)  by the tracer will return a I<status> value such that"
 msgstr ""
 
 #. type: Plain text
@@ -9288,10 +7587,7 @@ msgstr "  statusE<gt>E<gt>8 == (SIGTRAP | (PTRACE_EVENT_EXECE<lt>E<lt>8))\n"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:475
-msgid ""
-"If the execing thread is not a thread group leader, the thread ID is reset "
-"to thread group leader's ID before this stop.  Since Linux 3.0, the former "
-"thread ID can be retrieved with B<PTRACE_GETEVENTMSG>."
+msgid "If the execing thread is not a thread group leader, the thread ID is reset to thread group leader's ID before this stop.  Since Linux 3.0, the former thread ID can be retrieved with B<PTRACE_GETEVENTMSG>."
 msgstr ""
 
 #. type: TP
@@ -9302,9 +7598,7 @@ msgstr "B<PTRACE_O_TRACEEXIT> (Linux 2.5.60 以降)"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:483
-msgid ""
-"Stop the tracee at exit.  A B<waitpid>(2)  by the tracer will return a "
-"I<status> value such that"
+msgid "Stop the tracee at exit.  A B<waitpid>(2)  by the tracer will return a I<status> value such that"
 msgstr ""
 
 #. type: Plain text
@@ -9321,28 +7615,9 @@ msgstr ""
 #. type: Plain text
 #: build/C/man2/ptrace.2:498
 #, fuzzy
-#| msgid ""
-#| "Stop the child at exit with I<SIGTRAP | PTRACE_EVENT_EXIT\\ E<lt>E<lt>\\ "
-#| "8>.  The child's exit status can be retrieved with "
-#| "B<PTRACE_GETEVENTMSG>.  This stop will be done early during process exit "
-#| "when registers are still available, allowing the tracer to see where the "
-#| "exit occurred, whereas the normal exit notification is done after the "
-#| "process is finished exiting.  Even though context is available, the "
-#| "tracer cannot prevent the exit from happening at this point."
-msgid ""
-"The tracee is stopped early during process exit, when registers are still "
-"available, allowing the tracer to see where the exit occurred, whereas the "
-"normal exit notification is done after the process is finished exiting.  "
-"Even though context is available, the tracer cannot prevent the exit from "
-"happening at this point."
-msgstr ""
-"終了 (exit) 時に I<SIGTRAP | PTRACE_EVENT_EXIT\\ E<lt>E<lt>\\ 8> で子プロセス"
-"の動作を停止させる。子プロセスの終了ステータスは B<PTRACE_GETEVENTMSG> で取得"
-"できる。 この停止はレジスタがまだ参照可能であるプロセス終了処理の初期に行わ"
-"れ、 トレーサはどこで終了が発生したかを知ることができる。 通常の終了通知 "
-"(exit notification) はプロセスの終了処理が完了した後に 行われる。コンテキスト"
-"を参照することはできるにも関わらず、 トレーサはこの時点から終了を止めることは"
-"できない。"
+#| msgid "Stop the child at exit with I<SIGTRAP | PTRACE_EVENT_EXIT\\ E<lt>E<lt>\\ 8>.  The child's exit status can be retrieved with B<PTRACE_GETEVENTMSG>.  This stop will be done early during process exit when registers are still available, allowing the tracer to see where the exit occurred, whereas the normal exit notification is done after the process is finished exiting.  Even though context is available, the tracer cannot prevent the exit from happening at this point."
+msgid "The tracee is stopped early during process exit, when registers are still available, allowing the tracer to see where the exit occurred, whereas the normal exit notification is done after the process is finished exiting.  Even though context is available, the tracer cannot prevent the exit from happening at this point."
+msgstr "終了 (exit) 時に I<SIGTRAP | PTRACE_EVENT_EXIT\\ E<lt>E<lt>\\ 8> で子プロセスの動作を停止させる。子プロセスの終了ステータスは B<PTRACE_GETEVENTMSG> で取得できる。 この停止はレジスタがまだ参照可能であるプロセス終了処理の初期に行われ、 トレーサはどこで終了が発生したかを知ることができる。 通常の終了通知 (exit notification) はプロセスの終了処理が完了した後に 行われる。コンテキストを参照することはできるにも関わらず、 トレーサはこの時点から終了を止めることはできない。"
 
 #. type: TP
 #: build/C/man2/ptrace.2:498
@@ -9353,21 +7628,9 @@ msgstr "B<PTRACE_O_TRACEFORK> (Linux 2.5.46 以降)"
 #. type: Plain text
 #: build/C/man2/ptrace.2:515
 #, fuzzy
-#| msgid ""
-#| "Stop the child at the next B<fork>(2)  call with I<SIGTRAP | "
-#| "PTRACE_EVENT_FORK\\ E<lt>E<lt>\\ 8> and automatically start tracing the "
-#| "newly forked process, which will start with a B<SIGSTOP>.  The PID for "
-#| "the new process can be retrieved with B<PTRACE_GETEVENTMSG>."
-msgid ""
-"Stop the tracee at the next B<fork>(2)  and automatically start tracing the "
-"newly forked process, which will start with a B<SIGSTOP>, or "
-"B<PTRACE_EVENT_STOP> if B<PTRACE_SEIZE> was used.  A B<waitpid>(2)  by the "
-"tracer will return a I<status> value such that"
-msgstr ""
-"次の B<fork>(2)  呼び出し時に I<SIGTRAP | PTRACE_EVENT_FORK\\ E<lt>E<lt>\\ "
-"8> で 子プロセスの動作を停止させ、 新たに fork されたプロセスのトレースを自動"
-"的に開始し、 B<SIGSTOP> でそのプロセスの実行を開始する。 新しいプロセスの "
-"PID は B<PTRACE_GETEVENTMSG> で取得できる。"
+#| msgid "Stop the child at the next B<fork>(2)  call with I<SIGTRAP | PTRACE_EVENT_FORK\\ E<lt>E<lt>\\ 8> and automatically start tracing the newly forked process, which will start with a B<SIGSTOP>.  The PID for the new process can be retrieved with B<PTRACE_GETEVENTMSG>."
+msgid "Stop the tracee at the next B<fork>(2)  and automatically start tracing the newly forked process, which will start with a B<SIGSTOP>, or B<PTRACE_EVENT_STOP> if B<PTRACE_SEIZE> was used.  A B<waitpid>(2)  by the tracer will return a I<status> value such that"
+msgstr "次の B<fork>(2)  呼び出し時に I<SIGTRAP | PTRACE_EVENT_FORK\\ E<lt>E<lt>\\ 8> で 子プロセスの動作を停止させ、 新たに fork されたプロセスのトレースを自動的に開始し、 B<SIGSTOP> でそのプロセスの実行を開始する。 新しいプロセスの PID は B<PTRACE_GETEVENTMSG> で取得できる。"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:518
@@ -9384,21 +7647,9 @@ msgstr "B<PTRACE_O_TRACESYSGOOD> (Linux 2.4.6 以降)"
 #. type: Plain text
 #: build/C/man2/ptrace.2:531
 #, fuzzy
-#| msgid ""
-#| "When delivering syscall traps, set bit 7 in the signal number (i.e., "
-#| "deliver I<SIGTRAP | 0x80>).  This makes it easy for the tracer to tell "
-#| "the difference between normal traps and those caused by a syscall.  "
-#| "(B<PTRACE_O_TRACESYSGOOD> may not work on all architectures.)"
-msgid ""
-"When delivering system call traps, set bit 7 in the signal number (i.e., "
-"deliver I<SIGTRAP|0x80>).  This makes it easy for the tracer to distinguish "
-"normal traps from those caused by a system call.  (B<PTRACE_O_TRACESYSGOOD> "
-"may not work on all architectures.)"
-msgstr ""
-"システムコールのトラップが配送されたときに、シグナル番号のビット 7 を設定す"
-"る (すなわち、I<SIGTRAP | 0x80> を配送する)。 これにより、トレーサが通常のト"
-"ラップとシステムコールによるトラップを 区別しやすくなる。 "
-"(B<PTRACE_O_TRACESYSGOOD> はどのアーキテクチャでも動作しない可能性がある。)"
+#| msgid "When delivering syscall traps, set bit 7 in the signal number (i.e., deliver I<SIGTRAP | 0x80>).  This makes it easy for the tracer to tell the difference between normal traps and those caused by a syscall.  (B<PTRACE_O_TRACESYSGOOD> may not work on all architectures.)"
+msgid "When delivering system call traps, set bit 7 in the signal number (i.e., deliver I<SIGTRAP|0x80>).  This makes it easy for the tracer to distinguish normal traps from those caused by a system call.  (B<PTRACE_O_TRACESYSGOOD> may not work on all architectures.)"
+msgstr "システムコールのトラップが配送されたときに、シグナル番号のビット 7 を設定する (すなわち、I<SIGTRAP | 0x80> を配送する)。 これにより、トレーサが通常のトラップとシステムコールによるトラップを 区別しやすくなる。 (B<PTRACE_O_TRACESYSGOOD> はどのアーキテクチャでも動作しない可能性がある。)"
 
 #. type: TP
 #: build/C/man2/ptrace.2:531
@@ -9409,21 +7660,9 @@ msgstr "B<PTRACE_O_TRACEVFORK> (Linux 2.5.46 以降)"
 #. type: Plain text
 #: build/C/man2/ptrace.2:548
 #, fuzzy
-#| msgid ""
-#| "Stop the child at the next B<vfork>(2)  call with I<SIGTRAP | "
-#| "PTRACE_EVENT_VFORK\\ E<lt>E<lt>\\ 8> and automatically start tracing the "
-#| "newly vforked process, which will start with a B<SIGSTOP>.  The PID for "
-#| "the new process can be retrieved with B<PTRACE_GETEVENTMSG>."
-msgid ""
-"Stop the tracee at the next B<vfork>(2)  and automatically start tracing the "
-"newly vforked process, which will start with a B<SIGSTOP>, or "
-"B<PTRACE_EVENT_STOP> if B<PTRACE_SEIZE> was used.  A B<waitpid>(2)  by the "
-"tracer will return a I<status> value such that"
-msgstr ""
-"次の B<vfork>(2)  呼び出し時に I<SIGTRAP | PTRACE_EVENT_VFORK\\ E<lt>E<lt>\\ "
-"8> で 子プロセスの動作を停止させ、 新たに vfork されたプロセスのトレースを自"
-"動的に開始し、 B<SIGSTOP> でそのプロセスの実行を開始する。 新しいプロセスの "
-"PID は B<PTRACE_GETEVENTMSG> で取得できる。"
+#| msgid "Stop the child at the next B<vfork>(2)  call with I<SIGTRAP | PTRACE_EVENT_VFORK\\ E<lt>E<lt>\\ 8> and automatically start tracing the newly vforked process, which will start with a B<SIGSTOP>.  The PID for the new process can be retrieved with B<PTRACE_GETEVENTMSG>."
+msgid "Stop the tracee at the next B<vfork>(2)  and automatically start tracing the newly vforked process, which will start with a B<SIGSTOP>, or B<PTRACE_EVENT_STOP> if B<PTRACE_SEIZE> was used.  A B<waitpid>(2)  by the tracer will return a I<status> value such that"
+msgstr "次の B<vfork>(2)  呼び出し時に I<SIGTRAP | PTRACE_EVENT_VFORK\\ E<lt>E<lt>\\ 8> で 子プロセスの動作を停止させ、 新たに vfork されたプロセスのトレースを自動的に開始し、 B<SIGSTOP> でそのプロセスの実行を開始する。 新しいプロセスの PID は B<PTRACE_GETEVENTMSG> で取得できる。"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:551
@@ -9439,9 +7678,7 @@ msgstr "B<PTRACE_O_TRACEVFORKDONE> (Linux 2.5.60 以降)"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:564
-msgid ""
-"Stop the tracee at the completion of the next B<vfork>(2).  A B<waitpid>(2)  "
-"by the tracer will return a I<status> value such that"
+msgid "Stop the tracee at the completion of the next B<vfork>(2).  A B<waitpid>(2)  by the tracer will return a I<status> value such that"
 msgstr ""
 
 #. type: Plain text
@@ -9452,51 +7689,31 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:571
-msgid ""
-"The PID of the new process can (since Linux 2.6.18) be retrieved with "
-"B<PTRACE_GETEVENTMSG>."
+msgid "The PID of the new process can (since Linux 2.6.18) be retrieved with B<PTRACE_GETEVENTMSG>."
 msgstr ""
 
 #. type: TP
 #: build/C/man2/ptrace.2:571
-#, fuzzy, no-wrap
-#| msgid "B<PTRACE_O_TRACEEXEC> (since Linux 2.5.46)"
+#, no-wrap
 msgid "B<PTRACE_O_TRACESECCOMP> (since Linux 3.5)"
-msgstr "B<PTRACE_O_TRACEEXEC> (Linux 2.5.46 以降)"
+msgstr "B<PTRACE_O_TRACESECCOMP> (Linux 3.5 以降)"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:582
 #, fuzzy
-#| msgid ""
-#| "Stop the child at the next B<fork>(2)  call with I<SIGTRAP | "
-#| "PTRACE_EVENT_FORK\\ E<lt>E<lt>\\ 8> and automatically start tracing the "
-#| "newly forked process, which will start with a B<SIGSTOP>.  The PID for "
-#| "the new process can be retrieved with B<PTRACE_GETEVENTMSG>."
-msgid ""
-"Stop the tracee when a B<seccomp>(2)  B<SECCOMP_RET_TRACE> rule is "
-"triggered.  A B<waitpid>(2)  by the tracer will return a I<status> value "
-"such that"
-msgstr ""
-"次の B<fork>(2)  呼び出し時に I<SIGTRAP | PTRACE_EVENT_FORK\\ E<lt>E<lt>\\ "
-"8> で 子プロセスの動作を停止させ、 新たに fork されたプロセスのトレースを自動"
-"的に開始し、 B<SIGSTOP> でそのプロセスの実行を開始する。 新しいプロセスの "
-"PID は B<PTRACE_GETEVENTMSG> で取得できる。"
+#| msgid "Stop the child at the next B<fork>(2)  call with I<SIGTRAP | PTRACE_EVENT_FORK\\ E<lt>E<lt>\\ 8> and automatically start tracing the newly forked process, which will start with a B<SIGSTOP>.  The PID for the new process can be retrieved with B<PTRACE_GETEVENTMSG>."
+msgid "Stop the tracee when a B<seccomp>(2)  B<SECCOMP_RET_TRACE> rule is triggered.  A B<waitpid>(2)  by the tracer will return a I<status> value such that"
+msgstr "次の B<fork>(2)  呼び出し時に I<SIGTRAP | PTRACE_EVENT_FORK\\ E<lt>E<lt>\\ 8> で 子プロセスの動作を停止させ、 新たに fork されたプロセスのトレースを自動的に開始し、 B<SIGSTOP> でそのプロセスの実行を開始する。 新しいプロセスの PID は B<PTRACE_GETEVENTMSG> で取得できる。"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:585
-#, fuzzy, no-wrap
-#| msgid "  statusE<gt>E<gt>8 == (SIGTRAP | (PTRACE_EVENT_EXECE<lt>E<lt>8))\n"
+#, no-wrap
 msgid "  statusE<gt>E<gt>8 == (SIGTRAP | (PTRACE_EVENT_SECCOMPE<lt>E<lt>8))\n"
-msgstr "  statusE<gt>E<gt>8 == (SIGTRAP | (PTRACE_EVENT_EXECE<lt>E<lt>8))\n"
+msgstr "  statusE<gt>E<gt>8 == (SIGTRAP | (PTRACE_EVENT_SECCOMPE<lt>E<lt>8))\n"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:595
-msgid ""
-"While this triggers a B<PTRACE_EVENT> stop, it is similar to a syscall-enter-"
-"stop, in that the tracee has not yet entered the syscall that seccomp "
-"triggered on.  The seccomp event message data (from the B<SECCOMP_RET_DATA> "
-"portion of the seccomp filter rule) can be retrieved with "
-"B<PTRACE_GETEVENTMSG>."
+msgid "While this triggers a B<PTRACE_EVENT> stop, it is similar to a syscall-enter-stop, in that the tracee has not yet entered the syscall that seccomp triggered on.  The seccomp event message data (from the B<SECCOMP_RET_DATA> portion of the seccomp filter rule) can be retrieved with B<PTRACE_GETEVENTMSG>."
 msgstr ""
 
 #. type: TP
@@ -9508,30 +7725,9 @@ msgstr "B<PTRACE_GETEVENTMSG> (Linux 2.5.46 以降)"
 #. type: Plain text
 #: build/C/man2/ptrace.2:623
 #, fuzzy
-#| msgid ""
-#| "Retrieve a message (as an I<unsigned long>)  about the ptrace event that "
-#| "just happened, placing it in the location I<data> in the parent.  For "
-#| "B<PTRACE_EVENT_EXIT> this is the child's exit status.  For "
-#| "B<PTRACE_EVENT_FORK>, B<PTRACE_EVENT_VFORK> and B<PTRACE_EVENT_CLONE> "
-#| "this is the PID of the new process.  Since Linux 2.6.18, the PID of the "
-#| "new process is also available for B<PTRACE_EVENT_VFORK_DONE>.  (I<addr> "
-#| "is ignored.)"
-msgid ""
-"Retrieve a message (as an I<unsigned long>)  about the ptrace event that "
-"just happened, placing it at the address I<data> in the tracer.  For "
-"B<PTRACE_EVENT_EXIT>, this is the tracee's exit status.  For "
-"B<PTRACE_EVENT_FORK>, B<PTRACE_EVENT_VFORK>, B<PTRACE_EVENT_VFORK_DONE>, and "
-"B<PTRACE_EVENT_CLONE>, this is the PID of the new process.  For "
-"B<PTRACE_EVENT_SECCOMP>, this is the B<seccomp>(2)  filter's "
-"B<SECCOMP_RET_DATA> associated with the triggered rule.  (I<addr> is "
-"ignored.)"
-msgstr ""
-"発生したばかりの ptrace イベントに関するメッセージを (I<unsigned long> 型で) "
-"取得する。 取得したメッセージは親プロセスの I<data> の位置に格納される。 得ら"
-"れる内容は、 B<PTRACE_EVENT_EXIT> の場合は子プロセスの終了ステータスであり、 "
-"B<PTRACE_EVENT_FORK>, B<PTRACE_EVENT_VFORK>, B<PTRACE_EVENT_CLONE> の場合は新"
-"しいプロセスの PID である。 Linux 2.6.18 以降では、新しいプロセスの PID は "
-"B<PTRACE_EVENT_VFORK_DONE> で入手できる。 (I<addr> は無視される。)"
+#| msgid "Retrieve a message (as an I<unsigned long>)  about the ptrace event that just happened, placing it in the location I<data> in the parent.  For B<PTRACE_EVENT_EXIT> this is the child's exit status.  For B<PTRACE_EVENT_FORK>, B<PTRACE_EVENT_VFORK> and B<PTRACE_EVENT_CLONE> this is the PID of the new process.  Since Linux 2.6.18, the PID of the new process is also available for B<PTRACE_EVENT_VFORK_DONE>.  (I<addr> is ignored.)"
+msgid "Retrieve a message (as an I<unsigned long>)  about the ptrace event that just happened, placing it at the address I<data> in the tracer.  For B<PTRACE_EVENT_EXIT>, this is the tracee's exit status.  For B<PTRACE_EVENT_FORK>, B<PTRACE_EVENT_VFORK>, B<PTRACE_EVENT_VFORK_DONE>, and B<PTRACE_EVENT_CLONE>, this is the PID of the new process.  For B<PTRACE_EVENT_SECCOMP>, this is the B<seccomp>(2)  filter's B<SECCOMP_RET_DATA> associated with the triggered rule.  (I<addr> is ignored.)"
+msgstr "発生したばかりの ptrace イベントに関するメッセージを (I<unsigned long> 型で) 取得する。 取得したメッセージは親プロセスの I<data> の位置に格納される。 得られる内容は、 B<PTRACE_EVENT_EXIT> の場合は子プロセスの終了ステータスであり、 B<PTRACE_EVENT_FORK>, B<PTRACE_EVENT_VFORK>, B<PTRACE_EVENT_CLONE> の場合は新しいプロセスの PID である。 Linux 2.6.18 以降では、新しいプロセスの PID は B<PTRACE_EVENT_VFORK_DONE> で入手できる。 (I<addr> は無視される。)"
 
 #. type: TP
 #: build/C/man2/ptrace.2:623
@@ -9542,24 +7738,9 @@ msgstr "B<PTRACE_CONT>"
 #. type: Plain text
 #: build/C/man2/ptrace.2:635
 #, fuzzy
-#| msgid ""
-#| "Restarts the stopped child process.  If I<data> is nonzero and not "
-#| "B<SIGSTOP>, it is interpreted as a signal to be delivered to the child; "
-#| "otherwise, no signal is delivered.  Thus, for example, the parent can "
-#| "control whether a signal sent to the child is delivered or not.  (I<addr> "
-#| "is ignored.)"
-msgid ""
-"Restart the stopped tracee process.  If I<data> is nonzero, it is "
-"interpreted as the number of a signal to be delivered to the tracee; "
-"otherwise, no signal is delivered.  Thus, for example, the tracer can "
-"control whether a signal sent to the tracee is delivered or not.  (I<addr> "
-"is ignored.)"
-msgstr ""
-"停止した子プロセスの実行を再開させる。 I<data> がゼロでなく、 B<SIGSTOP> でも"
-"なければ、 子プロセスに配送されるシグナルと解釈される。 ゼロや B<SIGSTOP> の"
-"場合はシグナルは配送されない。 これを使うと、例えば、親プロセスは 子プロセス"
-"に送られたシグナルを実際に配送するかどうかを 制御することができる。(I<addr> "
-"は無視される。)"
+#| msgid "Restarts the stopped child process.  If I<data> is nonzero and not B<SIGSTOP>, it is interpreted as a signal to be delivered to the child; otherwise, no signal is delivered.  Thus, for example, the parent can control whether a signal sent to the child is delivered or not.  (I<addr> is ignored.)"
+msgid "Restart the stopped tracee process.  If I<data> is nonzero, it is interpreted as the number of a signal to be delivered to the tracee; otherwise, no signal is delivered.  Thus, for example, the tracer can control whether a signal sent to the tracee is delivered or not.  (I<addr> is ignored.)"
+msgstr "停止した子プロセスの実行を再開させる。 I<data> がゼロでなく、 B<SIGSTOP> でもなければ、 子プロセスに配送されるシグナルと解釈される。 ゼロや B<SIGSTOP> の場合はシグナルは配送されない。 これを使うと、例えば、親プロセスは 子プロセスに送られたシグナルを実際に配送するかどうかを 制御することができる。(I<addr> は無視される。)"
 
 #. type: TP
 #: build/C/man2/ptrace.2:635
@@ -9570,37 +7751,9 @@ msgstr "B<PTRACE_SYSCALL>, B<PTRACE_SINGLESTEP>"
 #. type: Plain text
 #: build/C/man2/ptrace.2:659
 #, fuzzy
-#| msgid ""
-#| "Restarts the stopped child as for B<PTRACE_CONT>, but arranges for the "
-#| "child to be stopped at the next entry to or exit from a system call, or "
-#| "after execution of a single instruction, respectively.  (The child will "
-#| "also, as usual, be stopped upon receipt of a signal.)  From the parent's "
-#| "perspective, the child will appear to have been stopped by receipt of a "
-#| "B<SIGTRAP>.  So, for B<PTRACE_SYSCALL>, for example, the idea is to "
-#| "inspect the arguments to the system call at the first stop, then do "
-#| "another B<PTRACE_SYSCALL> and inspect the return value of the system call "
-#| "at the second stop.  The I<data> argument is treated as for "
-#| "B<PTRACE_CONT>.  (I<addr> is ignored.)"
-msgid ""
-"Restart the stopped tracee as for B<PTRACE_CONT>, but arrange for the tracee "
-"to be stopped at the next entry to or exit from a system call, or after "
-"execution of a single instruction, respectively.  (The tracee will also, as "
-"usual, be stopped upon receipt of a signal.)  From the tracer's perspective, "
-"the tracee will appear to have been stopped by receipt of a B<SIGTRAP>.  So, "
-"for B<PTRACE_SYSCALL>, for example, the idea is to inspect the arguments to "
-"the system call at the first stop, then do another B<PTRACE_SYSCALL> and "
-"inspect the return value of the system call at the second stop.  The I<data> "
-"argument is treated as for B<PTRACE_CONT>.  (I<addr> is ignored.)"
-msgstr ""
-"B<PTRACE_CONT> と同様に停止した子プロセスを再開する。ただし、 "
-"B<PTRACE_SYSCALL> の場合は子プロセスが 次にシステムコールに入るかシステムコー"
-"ルから抜けるかする時に、 B<PTRACE_SINGLESTEP> の場合は 1 命令 (instruction) "
-"実行した後に停止させる (通常どおり、子プロセスはシグナルを受け取った場合にも"
-"停止する)。 親プロセスから見ると、子プロセスは B<SIGTRAP> を受信して停止した"
-"ように見える。そのため、例えば B<PTRACE_SYSCALL> を使うと、1回目の停止で引き"
-"数を調べて B<PTRACE_SYSCALL> を実行し、 2回目の停止でシステムコールの返り値を"
-"調べる、 というようなことができる。 引き数 I<data> は B<PTRACE_CONT> の場合と"
-"同じ様に解釈される。 (I<addr> は無視される。)"
+#| msgid "Restarts the stopped child as for B<PTRACE_CONT>, but arranges for the child to be stopped at the next entry to or exit from a system call, or after execution of a single instruction, respectively.  (The child will also, as usual, be stopped upon receipt of a signal.)  From the parent's perspective, the child will appear to have been stopped by receipt of a B<SIGTRAP>.  So, for B<PTRACE_SYSCALL>, for example, the idea is to inspect the arguments to the system call at the first stop, then do another B<PTRACE_SYSCALL> and inspect the return value of the system call at the second stop.  The I<data> argument is treated as for B<PTRACE_CONT>.  (I<addr> is ignored.)"
+msgid "Restart the stopped tracee as for B<PTRACE_CONT>, but arrange for the tracee to be stopped at the next entry to or exit from a system call, or after execution of a single instruction, respectively.  (The tracee will also, as usual, be stopped upon receipt of a signal.)  From the tracer's perspective, the tracee will appear to have been stopped by receipt of a B<SIGTRAP>.  So, for B<PTRACE_SYSCALL>, for example, the idea is to inspect the arguments to the system call at the first stop, then do another B<PTRACE_SYSCALL> and inspect the return value of the system call at the second stop.  The I<data> argument is treated as for B<PTRACE_CONT>.  (I<addr> is ignored.)"
+msgstr "B<PTRACE_CONT> と同様に停止した子プロセスを再開する。ただし、 B<PTRACE_SYSCALL> の場合は子プロセスが 次にシステムコールに入るかシステムコールから抜けるかする時に、 B<PTRACE_SINGLESTEP> の場合は 1 命令 (instruction) 実行した後に停止させる (通常どおり、子プロセスはシグナルを受け取った場合にも停止する)。 親プロセスから見ると、子プロセスは B<SIGTRAP> を受信して停止したように見える。そのため、例えば B<PTRACE_SYSCALL> を使うと、1回目の停止で引き数を調べて B<PTRACE_SYSCALL> を実行し、 2回目の停止でシステムコールの返り値を調べる、 というようなことができる。 引き数 I<data> は B<PTRACE_CONT> の場合と同じ様に解釈される。 (I<addr> は無視される。)"
 
 #. type: TP
 #: build/C/man2/ptrace.2:659
@@ -9612,28 +7765,9 @@ msgstr "B<PTRACE_SYSEMU>, B<PTRACE_SYSEMU_SINGLESTEP> (Linux 2.6.14 以降)"
 #. type: Plain text
 #: build/C/man2/ptrace.2:680
 #, fuzzy
-#| msgid ""
-#| "For B<PTRACE_SYSEMU>, continue and stop on entry to the next syscall, "
-#| "which will not be executed.  For B<PTRACE_SYSEMU_SINGLESTEP>, do the same "
-#| "but also singlestep if not a syscall.  This call is used by programs like "
-#| "User Mode Linux that want to emulate all the child's system calls.  The "
-#| "I<data> argument is treated as for B<PTRACE_CONT>.  (I<addr> is ignored; "
-#| "not supported on all architectures.)"
-msgid ""
-"For B<PTRACE_SYSEMU>, continue and stop on entry to the next system call, "
-"which will not be executed.  For B<PTRACE_SYSEMU_SINGLESTEP>, do the same "
-"but also singlestep if not a system call.  This call is used by programs "
-"like User Mode Linux that want to emulate all the tracee's system calls.  "
-"The I<data> argument is treated as for B<PTRACE_CONT>.  The I<addr> argument "
-"is ignored.  These requests are currently supported only on x86."
-msgstr ""
-"B<PTRACE_SYSEMU> は、実行を再開し、次のシステムコールに入る時に停止させる。 "
-"システムコールは実行されない。 B<PTRACE_SYSEMU_SINGLESTEP> も同様だが、システ"
-"ムコールでない場合には 1 命令 (singlestep) だけ実行した時点でも停止させる。 "
-"このコールは User Mode Linux のように子プロセスのシステムコールを全て エミュ"
-"レートしようとするプログラムで使用される。 引き数 I<data> は B<PTRACE_CONT> "
-"の場合と同じ様に解釈される。 (I<addr> は無視される。 全てのアーキテクチャでサ"
-"ポートされているわけではない。)"
+#| msgid "For B<PTRACE_SYSEMU>, continue and stop on entry to the next syscall, which will not be executed.  For B<PTRACE_SYSEMU_SINGLESTEP>, do the same but also singlestep if not a syscall.  This call is used by programs like User Mode Linux that want to emulate all the child's system calls.  The I<data> argument is treated as for B<PTRACE_CONT>.  (I<addr> is ignored; not supported on all architectures.)"
+msgid "For B<PTRACE_SYSEMU>, continue and stop on entry to the next system call, which will not be executed.  For B<PTRACE_SYSEMU_SINGLESTEP>, do the same but also singlestep if not a system call.  This call is used by programs like User Mode Linux that want to emulate all the tracee's system calls.  The I<data> argument is treated as for B<PTRACE_CONT>.  The I<addr> argument is ignored.  These requests are currently supported only on x86."
+msgstr "B<PTRACE_SYSEMU> は、実行を再開し、次のシステムコールに入る時に停止させる。 システムコールは実行されない。 B<PTRACE_SYSEMU_SINGLESTEP> も同様だが、システムコールでない場合には 1 命令 (singlestep) だけ実行した時点でも停止させる。 このコールは User Mode Linux のように子プロセスのシステムコールを全て エミュレートしようとするプログラムで使用される。 引き数 I<data> は B<PTRACE_CONT> の場合と同じ様に解釈される。 (I<addr> は無視される。 全てのアーキテクチャでサポートされているわけではない。)"
 
 #. type: TP
 #: build/C/man2/ptrace.2:680
@@ -9643,12 +7777,7 @@ msgstr " B<PTRACE_LISTEN> (since Linux 3.4)"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:691
-msgid ""
-"Restart the stopped tracee, but prevent it from executing.  The resulting "
-"state of the tracee is similar to a process which has been stopped by a "
-"B<SIGSTOP> (or other stopping signal).  See the \"group-stop\" subsection "
-"for additional information.  B<PTRACE_LISTEN> works only on tracees attached "
-"by B<PTRACE_SEIZE>."
+msgid "Restart the stopped tracee, but prevent it from executing.  The resulting state of the tracee is similar to a process which has been stopped by a B<SIGSTOP> (or other stopping signal).  See the \"group-stop\" subsection for additional information.  B<PTRACE_LISTEN> works only on tracees attached by B<PTRACE_SEIZE>."
 msgstr ""
 
 #. type: TP
@@ -9660,26 +7789,16 @@ msgstr "B<PTRACE_KILL>"
 #. type: Plain text
 #: build/C/man2/ptrace.2:700
 #, fuzzy
-#| msgid ""
-#| "Sends the child a B<SIGKILL> to terminate it.  (I<addr> and I<data> are "
-#| "ignored.)"
-msgid ""
-"Send the tracee a B<SIGKILL> to terminate it.  (I<addr> and I<data> are "
-"ignored.)"
-msgstr ""
-"子プロセスに B<SIGKILL> を送り終了させる。(I<addr> と I<data> は無視される。)"
+#| msgid "Sends the child a B<SIGKILL> to terminate it.  (I<addr> and I<data> are ignored.)"
+msgid "Send the tracee a B<SIGKILL> to terminate it.  (I<addr> and I<data> are ignored.)"
+msgstr "子プロセスに B<SIGKILL> を送り終了させる。(I<addr> と I<data> は無視される。)"
 
 #.  [Note from Denys Vlasenko:
 #.      deprecation suggested by Oleg Nesterov. He prefers to deprecate it
 #.      instead of describing (and needing to support) PTRACE_KILL's quirks.]
 #. type: Plain text
 #: build/C/man2/ptrace.2:719
-msgid ""
-"I<This operation is deprecated; do not use it!> Instead, send a B<SIGKILL> "
-"directly using B<kill>(2)  or B<tgkill>(2).  The problem with B<PTRACE_KILL> "
-"is that it requires the tracee to be in signal-delivery-stop, otherwise it "
-"may not work (i.e., may complete successfully but won't kill the tracee).  "
-"By contrast, sending a B<SIGKILL> directly has no such limitation."
+msgid "I<This operation is deprecated; do not use it!> Instead, send a B<SIGKILL> directly using B<kill>(2)  or B<tgkill>(2).  The problem with B<PTRACE_KILL> is that it requires the tracee to be in signal-delivery-stop, otherwise it may not work (i.e., may complete successfully but won't kill the tracee).  By contrast, sending a B<SIGKILL> directly has no such limitation."
 msgstr ""
 
 #. type: TP
@@ -9690,18 +7809,7 @@ msgstr " B<PTRACE_INTERRUPT> (since Linux 3.4)"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:747
-msgid ""
-"Stop a tracee.  If the tracee is running or sleeping in kernel space and "
-"B<PTRACE_SYSCALL> is in effect, the system call is interrupted and syscall-"
-"exit-stop is reported.  (The interrupted system call is restarted when the "
-"tracee is restarted.)  If the tracee was already stopped by a signal and "
-"B<PTRACE_LISTEN> was sent to it, the tracee stops with B<PTRACE_EVENT_STOP> "
-"and I<WSTOPSIG(status)> returns the stop signal.  If any other ptrace-stop "
-"is generated at the same time (for example, if a signal is sent to the "
-"tracee), this ptrace-stop happens.  If none of the above applies (for "
-"example, if the tracee is running in user space), it stops with "
-"B<PTRACE_EVENT_STOP> with I<WSTOPSIG(status)> == B<SIGTRAP>.  "
-"B<PTRACE_INTERRUPT> only works on tracees attached by B<PTRACE_SEIZE>."
+msgid "Stop a tracee.  If the tracee is running or sleeping in kernel space and B<PTRACE_SYSCALL> is in effect, the system call is interrupted and syscall-exit-stop is reported.  (The interrupted system call is restarted when the tracee is restarted.)  If the tracee was already stopped by a signal and B<PTRACE_LISTEN> was sent to it, the tracee stops with B<PTRACE_EVENT_STOP> and I<WSTOPSIG(status)> returns the stop signal.  If any other ptrace-stop is generated at the same time (for example, if a signal is sent to the tracee), this ptrace-stop happens.  If none of the above applies (for example, if the tracee is running in user space), it stops with B<PTRACE_EVENT_STOP> with I<WSTOPSIG(status)> == B<SIGTRAP>.  B<PTRACE_INTERRUPT> only works on tracees attached by B<PTRACE_SEIZE>."
 msgstr ""
 
 #. type: TP
@@ -9724,12 +7832,7 @@ msgstr "B<PTRACE_ATTACH>"
 #.  by the tracee will still return the PID of the original parent.
 #. type: Plain text
 #: build/C/man2/ptrace.2:775
-msgid ""
-"Attach to the process specified in I<pid>, making it a tracee of the calling "
-"process.  The tracee is sent a B<SIGSTOP>, but will not necessarily have "
-"stopped by the completion of this call; use B<waitpid>(2)  to wait for the "
-"tracee to stop.  See the \"Attaching and detaching\" subsection for "
-"additional information.  (I<addr> and I<data> are ignored.)"
+msgid "Attach to the process specified in I<pid>, making it a tracee of the calling process.  The tracee is sent a B<SIGSTOP>, but will not necessarily have stopped by the completion of this call; use B<waitpid>(2)  to wait for the tracee to stop.  See the \"Attaching and detaching\" subsection for additional information.  (I<addr> and I<data> are ignored.)"
 msgstr ""
 
 #. type: TP
@@ -9740,12 +7843,7 @@ msgstr " B<PTRACE_SEIZE> (since Linux 3.4)"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:795
-msgid ""
-"Attach to the process specified in I<pid>, making it a tracee of the calling "
-"process.  Unlike B<PTRACE_ATTACH>, B<PTRACE_SEIZE> does not stop the "
-"process.  Only a B<PTRACE_SEIZE>d process can accept B<PTRACE_INTERRUPT> and "
-"B<PTRACE_LISTEN> commands.  I<addr> must be zero.  I<data> contains a bit "
-"mask of ptrace options to activate immediately."
+msgid "Attach to the process specified in I<pid>, making it a tracee of the calling process.  Unlike B<PTRACE_ATTACH>, B<PTRACE_SEIZE> does not stop the process.  Only a B<PTRACE_SEIZE>d process can accept B<PTRACE_INTERRUPT> and B<PTRACE_LISTEN> commands.  I<addr> must be zero.  I<data> contains a bit mask of ptrace options to activate immediately."
 msgstr ""
 
 #. type: TP
@@ -9757,22 +7855,9 @@ msgstr "B<PTRACE_DETACH>"
 #. type: Plain text
 #: build/C/man2/ptrace.2:804
 #, fuzzy
-#| msgid ""
-#| "Restarts the stopped child as for B<PTRACE_CONT>, but first detaches from "
-#| "the process, undoing the reparenting effect of B<PTRACE_ATTACH>, and the "
-#| "effects of B<PTRACE_TRACEME>.  Although perhaps not intended, under Linux "
-#| "a traced child can be detached in this way regardless of which method was "
-#| "used to initiate tracing.  (I<addr> is ignored.)"
-msgid ""
-"Restart the stopped tracee as for B<PTRACE_CONT>, but first detach from it.  "
-"Under Linux, a tracee can be detached in this way regardless of which method "
-"was used to initiate tracing.  (I<addr> is ignored.)"
-msgstr ""
-"B<PTRACE_CONT> と同様に停止した子プロセスを再開する。ただし まずそのプロセス"
-"からの分離 (detach) を行い、 B<PTRACE_ATTACH> での親の切り換えによる効果と "
-"B<PTRACE_TRACEME> の効果を取り消す。意図したものではないだろうが、 Linux で"
-"は、トレースされている子プロセスはどのような方法でトレースを 開始されたとして"
-"も、この方法で分離 (detach) することができる。 (I<addr> は無視される。)"
+#| msgid "Restarts the stopped child as for B<PTRACE_CONT>, but first detaches from the process, undoing the reparenting effect of B<PTRACE_ATTACH>, and the effects of B<PTRACE_TRACEME>.  Although perhaps not intended, under Linux a traced child can be detached in this way regardless of which method was used to initiate tracing.  (I<addr> is ignored.)"
+msgid "Restart the stopped tracee as for B<PTRACE_CONT>, but first detach from it.  Under Linux, a tracee can be detached in this way regardless of which method was used to initiate tracing.  (I<addr> is ignored.)"
+msgstr "B<PTRACE_CONT> と同様に停止した子プロセスを再開する。ただし まずそのプロセスからの分離 (detach) を行い、 B<PTRACE_ATTACH> での親の切り換えによる効果と B<PTRACE_TRACEME> の効果を取り消す。意図したものではないだろうが、 Linux では、トレースされている子プロセスはどのような方法でトレースを 開始されたとしても、この方法で分離 (detach) することができる。 (I<addr> は無視される。)"
 
 #. type: SS
 #: build/C/man2/ptrace.2:804
@@ -9782,83 +7867,42 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:813
-msgid ""
-"When a (possibly multithreaded) process receives a killing signal (one whose "
-"disposition is set to B<SIG_DFL> and whose default action is to kill the "
-"process), all threads exit.  Tracees report their death to their tracer(s).  "
-"Notification of this event is delivered via B<waitpid>(2)."
+msgid "When a (possibly multithreaded) process receives a killing signal (one whose disposition is set to B<SIG_DFL> and whose default action is to kill the process), all threads exit.  Tracees report their death to their tracer(s).  Notification of this event is delivered via B<waitpid>(2)."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:822
-msgid ""
-"Note that the killing signal will first cause signal-delivery-stop (on one "
-"tracee only), and only after it is injected by the tracer (or after it was "
-"dispatched to a thread which isn't traced), will death from the signal "
-"happen on I<all> tracees within a multithreaded process.  (The term \"signal-"
-"delivery-stop\" is explained below.)"
+msgid "Note that the killing signal will first cause signal-delivery-stop (on one tracee only), and only after it is injected by the tracer (or after it was dispatched to a thread which isn't traced), will death from the signal happen on I<all> tracees within a multithreaded process.  (The term \"signal-delivery-stop\" is explained below.)"
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:834
-msgid ""
-"B<SIGKILL> does not generate signal-delivery-stop and therefore the tracer "
-"can't suppress it.  B<SIGKILL> kills even within system calls (syscall-exit-"
-"stop is not generated prior to death by B<SIGKILL>).  The net effect is that "
-"B<SIGKILL> always kills the process (all its threads), even if some threads "
-"of the process are ptraced."
+msgid "B<SIGKILL> does not generate signal-delivery-stop and therefore the tracer can't suppress it.  B<SIGKILL> kills even within system calls (syscall-exit-stop is not generated prior to death by B<SIGKILL>).  The net effect is that B<SIGKILL> always kills the process (all its threads), even if some threads of the process are ptraced."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:839
-msgid ""
-"When the tracee calls B<_exit>(2), it reports its death to its tracer.  "
-"Other threads are not affected."
+msgid "When the tracee calls B<_exit>(2), it reports its death to its tracer.  Other threads are not affected."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:843
-msgid ""
-"When any thread executes B<exit_group>(2), every tracee in its thread group "
-"reports its death to its tracer."
+msgid "When any thread executes B<exit_group>(2), every tracee in its thread group reports its death to its tracer."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:857
-msgid ""
-"If the B<PTRACE_O_TRACEEXIT> option is on, B<PTRACE_EVENT_EXIT> will happen "
-"before actual death.  This applies to exits via B<exit>(2), "
-"B<exit_group>(2), and signal deaths (except B<SIGKILL>), and when threads "
-"are torn down on B<execve>(2)  in a multithreaded process."
+msgid "If the B<PTRACE_O_TRACEEXIT> option is on, B<PTRACE_EVENT_EXIT> will happen before actual death.  This applies to exits via B<exit>(2), B<exit_group>(2), and signal deaths (except B<SIGKILL>), and when threads are torn down on B<execve>(2)  in a multithreaded process."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:882
-msgid ""
-"The tracer cannot assume that the ptrace-stopped tracee exists.  There are "
-"many scenarios when the tracee may die while stopped (such as B<SIGKILL>).  "
-"Therefore, the tracer must be prepared to handle an B<ESRCH> error on any "
-"ptrace operation.  Unfortunately, the same error is returned if the tracee "
-"exists but is not ptrace-stopped (for commands which require a stopped "
-"tracee), or if it is not traced by the process which issued the ptrace "
-"call.  The tracer needs to keep track of the stopped/running state of the "
-"tracee, and interpret B<ESRCH> as \"tracee died unexpectedly\" only if it "
-"knows that the tracee has been observed to enter ptrace-stop.  Note that "
-"there is no guarantee that I<waitpid(WNOHANG)> will reliably report the "
-"tracee's death status if a ptrace operation returned B<ESRCH>.  "
-"I<waitpid(WNOHANG)> may return 0 instead.  In other words, the tracee may be "
-"\"not yet fully dead\", but already refusing ptrace requests."
+msgid "The tracer cannot assume that the ptrace-stopped tracee exists.  There are many scenarios when the tracee may die while stopped (such as B<SIGKILL>).  Therefore, the tracer must be prepared to handle an B<ESRCH> error on any ptrace operation.  Unfortunately, the same error is returned if the tracee exists but is not ptrace-stopped (for commands which require a stopped tracee), or if it is not traced by the process which issued the ptrace call.  The tracer needs to keep track of the stopped/running state of the tracee, and interpret B<ESRCH> as \"tracee died unexpectedly\" only if it knows that the tracee has been observed to enter ptrace-stop.  Note that there is no guarantee that I<waitpid(WNOHANG)> will reliably report the tracee's death status if a ptrace operation returned B<ESRCH>.  I<waitpid(WNOHANG)> may return 0 instead.  In other words, the tracee may be \"not yet fully dead\", but already refusing ptrace requests."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:896
-msgid ""
-"The tracer can't assume that the tracee I<always> ends its life by reporting "
-"I<WIFEXITED(status)> or I<WIFSIGNALED(status)>; there are cases where this "
-"does not occur.  For example, if a thread other than thread group leader "
-"does an B<execve>(2), it disappears; its PID will never be seen again, and "
-"any subsequent ptrace stops will be reported under the thread group leader's "
-"PID."
+msgid "The tracer can't assume that the tracee I<always> ends its life by reporting I<WIFEXITED(status)> or I<WIFSIGNALED(status)>; there are cases where this does not occur.  For example, if a thread other than thread group leader does an B<execve>(2), it disappears; its PID will never be seen again, and any subsequent ptrace stops will be reported under the thread group leader's PID."
 msgstr ""
 
 #. type: SS
@@ -9869,43 +7913,22 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:918
-msgid ""
-"A tracee can be in two states: running or stopped.  For the purposes of "
-"ptrace, a tracee which is blocked in a system call (such as B<read>(2), "
-"B<pause>(2), etc.)  is nevertheless considered to be running, even if the "
-"tracee is blocked for a long time.  The state of the tracee after "
-"B<PTRACE_LISTEN> is somewhat of a gray area: it is not in any ptrace-stop "
-"(ptrace commands won't work on it, and it will deliver B<waitpid>(2)  "
-"notifications), but it also may be considered \"stopped\" because it is not "
-"executing instructions (is not scheduled), and if it was in group-stop "
-"before B<PTRACE_LISTEN>, it will not respond to signals until B<SIGCONT> is "
-"received."
+msgid "A tracee can be in two states: running or stopped.  For the purposes of ptrace, a tracee which is blocked in a system call (such as B<read>(2), B<pause>(2), etc.)  is nevertheless considered to be running, even if the tracee is blocked for a long time.  The state of the tracee after B<PTRACE_LISTEN> is somewhat of a gray area: it is not in any ptrace-stop (ptrace commands won't work on it, and it will deliver B<waitpid>(2)  notifications), but it also may be considered \"stopped\" because it is not executing instructions (is not scheduled), and if it was in group-stop before B<PTRACE_LISTEN>, it will not respond to signals until B<SIGCONT> is received."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:922
-msgid ""
-"There are many kinds of states when the tracee is stopped, and in ptrace "
-"discussions they are often conflated.  Therefore, it is important to use "
-"precise terms."
+msgid "There are many kinds of states when the tracee is stopped, and in ptrace discussions they are often conflated.  Therefore, it is important to use precise terms."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:933
-msgid ""
-"In this manual page, any stopped state in which the tracee is ready to "
-"accept ptrace commands from the tracer is called I<ptrace-stop>.  Ptrace-"
-"stops can be further subdivided into I<signal-delivery-stop>, I<group-stop>, "
-"I<syscall-stop>, and so on.  These stopped states are described in detail "
-"below."
+msgid "In this manual page, any stopped state in which the tracee is ready to accept ptrace commands from the tracer is called I<ptrace-stop>.  Ptrace-stops can be further subdivided into I<signal-delivery-stop>, I<group-stop>, I<syscall-stop>, and so on.  These stopped states are described in detail below."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:938
-msgid ""
-"When the running tracee enters ptrace-stop, it notifies its tracer using "
-"B<waitpid>(2)  (or one of the other \"wait\" system calls).  Most of this "
-"manual page assumes that the tracer waits with:"
+msgid "When the running tracee enters ptrace-stop, it notifies its tracer using B<waitpid>(2)  (or one of the other \"wait\" system calls).  Most of this manual page assumes that the tracer waits with:"
 msgstr ""
 
 #. type: Plain text
@@ -9921,32 +7944,22 @@ msgstr ""
 #.      WEXITED?
 #. type: Plain text
 #: build/C/man2/ptrace.2:952
-msgid ""
-"Ptrace-stopped tracees are reported as returns with I<pid> greater than 0 "
-"and I<WIFSTOPPED(status)> true."
+msgid "Ptrace-stopped tracees are reported as returns with I<pid> greater than 0 and I<WIFSTOPPED(status)> true."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:960
-msgid ""
-"The B<__WALL> flag does not include the B<WSTOPPED> and B<WEXITED> flags, "
-"but implies their functionality."
+msgid "The B<__WALL> flag does not include the B<WSTOPPED> and B<WEXITED> flags, but implies their functionality."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:967
-msgid ""
-"Setting the B<WCONTINUED> flag when calling B<waitpid>(2)  is not "
-"recommended: the \"continued\" state is per-process and consuming it can "
-"confuse the real parent of the tracee."
+msgid "Setting the B<WCONTINUED> flag when calling B<waitpid>(2)  is not recommended: the \"continued\" state is per-process and consuming it can confuse the real parent of the tracee."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:975
-msgid ""
-"Use of the B<WNOHANG> flag may cause B<waitpid>(2)  to return 0 (\"no wait "
-"results available yet\")  even if the tracer knows there should be a "
-"notification.  Example:"
+msgid "Use of the B<WNOHANG> flag may cause B<waitpid>(2)  to return 0 (\"no wait results available yet\")  even if the tracer knows there should be a notification.  Example:"
 msgstr ""
 
 #. type: Plain text
@@ -9964,14 +7977,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1007
-msgid ""
-"The following kinds of ptrace-stops exist: signal-delivery-stops, group-"
-"stops, B<PTRACE_EVENT> stops, syscall-stops.  They all are reported by "
-"B<waitpid>(2)  with I<WIFSTOPPED(status)> true.  They may be differentiated "
-"by examining the value I<statusE<gt>E<gt>8>, and if there is ambiguity in "
-"that value, by querying B<PTRACE_GETSIGINFO>.  (Note: the "
-"I<WSTOPSIG(status)> macro can't be used to perform this examination, because "
-"it returns the value I<(statusE<gt>E<gt>8)\\ &\\ 0xff>.)"
+msgid "The following kinds of ptrace-stops exist: signal-delivery-stops, group-stops, B<PTRACE_EVENT> stops, syscall-stops.  They all are reported by B<waitpid>(2)  with I<WIFSTOPPED(status)> true.  They may be differentiated by examining the value I<statusE<gt>E<gt>8>, and if there is ambiguity in that value, by querying B<PTRACE_GETSIGINFO>.  (Note: the I<WSTOPSIG(status)> macro can't be used to perform this examination, because it returns the value I<(statusE<gt>E<gt>8)\\ &\\ 0xff>.)"
 msgstr ""
 
 #. type: SS
@@ -9982,29 +7988,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1027
-msgid ""
-"When a (possibly multithreaded) process receives any signal except "
-"B<SIGKILL>, the kernel selects an arbitrary thread which handles the "
-"signal.  (If the signal is generated with B<tgkill>(2), the target thread "
-"can be explicitly selected by the caller.)  If the selected thread is "
-"traced, it enters signal-delivery-stop.  At this point, the signal is not "
-"yet delivered to the process, and can be suppressed by the tracer.  If the "
-"tracer doesn't suppress the signal, it passes the signal to the tracee in "
-"the next ptrace restart request.  This second step of signal delivery is "
-"called I<signal injection> in this manual page.  Note that if the signal is "
-"blocked, signal-delivery-stop doesn't happen until the signal is unblocked, "
-"with the usual exception that B<SIGSTOP> can't be blocked."
+msgid "When a (possibly multithreaded) process receives any signal except B<SIGKILL>, the kernel selects an arbitrary thread which handles the signal.  (If the signal is generated with B<tgkill>(2), the target thread can be explicitly selected by the caller.)  If the selected thread is traced, it enters signal-delivery-stop.  At this point, the signal is not yet delivered to the process, and can be suppressed by the tracer.  If the tracer doesn't suppress the signal, it passes the signal to the tracee in the next ptrace restart request.  This second step of signal delivery is called I<signal injection> in this manual page.  Note that if the signal is blocked, signal-delivery-stop doesn't happen until the signal is unblocked, with the usual exception that B<SIGSTOP> can't be blocked."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1041
-msgid ""
-"Signal-delivery-stop is observed by the tracer as B<waitpid>(2)  returning "
-"with I<WIFSTOPPED(status)> true, with the signal returned by "
-"I<WSTOPSIG(status)>.  If the signal is B<SIGTRAP>, this may be a different "
-"kind of ptrace-stop; see the \"Syscall-stops\" and \"execve\" sections below "
-"for details.  If I<WSTOPSIG(status)> returns a stopping signal, this may be "
-"a group-stop; see below."
+msgid "Signal-delivery-stop is observed by the tracer as B<waitpid>(2)  returning with I<WIFSTOPPED(status)> true, with the signal returned by I<WSTOPSIG(status)>.  If the signal is B<SIGTRAP>, this may be a different kind of ptrace-stop; see the \"Syscall-stops\" and \"execve\" sections below for details.  If I<WSTOPSIG(status)> returns a stopping signal, this may be a group-stop; see below."
 msgstr ""
 
 #. type: SS
@@ -10015,9 +8004,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1044
-msgid ""
-"After signal-delivery-stop is observed by the tracer, the tracer should "
-"restart the tracee with the call"
+msgid "After signal-delivery-stop is observed by the tracer, the tracer should restart the tracee with the call"
 msgstr ""
 
 #. type: Plain text
@@ -10028,52 +8015,27 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1059
-msgid ""
-"where B<PTRACE_restart> is one of the restarting ptrace requests.  If I<sig> "
-"is 0, then a signal is not delivered.  Otherwise, the signal I<sig> is "
-"delivered.  This operation is called I<signal injection> in this manual "
-"page, to distinguish it from signal-delivery-stop."
+msgid "where B<PTRACE_restart> is one of the restarting ptrace requests.  If I<sig> is 0, then a signal is not delivered.  Otherwise, the signal I<sig> is delivered.  This operation is called I<signal injection> in this manual page, to distinguish it from signal-delivery-stop."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1065
-msgid ""
-"The I<sig> value may be different from the I<WSTOPSIG(status)> value: the "
-"tracer can cause a different signal to be injected."
+msgid "The I<sig> value may be different from the I<WSTOPSIG(status)> value: the tracer can cause a different signal to be injected."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1081
-msgid ""
-"Note that a suppressed signal still causes system calls to return "
-"prematurely.  In this case, system calls will be restarted: the tracer will "
-"observe the tracee to reexecute the interrupted system call (or "
-"B<restart_syscall>(2)  system call for a few system calls which use a "
-"different mechanism for restarting) if the tracer uses B<PTRACE_SYSCALL>.  "
-"Even system calls (such as B<poll>(2))  which are not restartable after "
-"signal are restarted after signal is suppressed; however, kernel bugs exist "
-"which cause some system calls to fail with B<EINTR> even though no "
-"observable signal is injected to the tracee."
+msgid "Note that a suppressed signal still causes system calls to return prematurely.  In this case, system calls will be restarted: the tracer will observe the tracee to reexecute the interrupted system call (or B<restart_syscall>(2)  system call for a few system calls which use a different mechanism for restarting) if the tracer uses B<PTRACE_SYSCALL>.  Even system calls (such as B<poll>(2))  which are not restartable after signal are restarted after signal is suppressed; however, kernel bugs exist which cause some system calls to fail with B<EINTR> even though no observable signal is injected to the tracee."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1092
-msgid ""
-"Restarting ptrace commands issued in ptrace-stops other than signal-delivery-"
-"stop are not guaranteed to inject a signal, even if I<sig> is nonzero.  No "
-"error is reported; a nonzero I<sig> may simply be ignored.  Ptrace users "
-"should not try to \"create a new signal\" this way: use B<tgkill>(2)  "
-"instead."
+msgid "Restarting ptrace commands issued in ptrace-stops other than signal-delivery-stop are not guaranteed to inject a signal, even if I<sig> is nonzero.  No error is reported; a nonzero I<sig> may simply be ignored.  Ptrace users should not try to \"create a new signal\" this way: use B<tgkill>(2)  instead."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1099
-msgid ""
-"The fact that signal injection requests may be ignored when restarting the "
-"tracee after ptrace stops that are not signal-delivery-stops is a cause of "
-"confusion among ptrace users.  One typical scenario is that the tracer "
-"observes group-stop, mistakes it for signal-delivery-stop, restarts the "
-"tracee with"
+msgid "The fact that signal injection requests may be ignored when restarting the tracee after ptrace stops that are not signal-delivery-stops is a cause of confusion among ptrace users.  One typical scenario is that the tracer observes group-stop, mistakes it for signal-delivery-stop, restarts the tracee with"
 msgstr ""
 
 #. type: Plain text
@@ -10084,31 +8046,17 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1107
-msgid ""
-"with the intention of injecting I<stopsig>, but I<stopsig> gets ignored and "
-"the tracee continues to run."
+msgid "with the intention of injecting I<stopsig>, but I<stopsig> gets ignored and the tracee continues to run."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1127
-msgid ""
-"The B<SIGCONT> signal has a side effect of waking up (all threads of)  a "
-"group-stopped process.  This side effect happens before signal-delivery-"
-"stop.  The tracer can't suppress this side effect (it can only suppress "
-"signal injection, which only causes the B<SIGCONT> handler to not be "
-"executed in the tracee, if such a handler is installed).  In fact, waking up "
-"from group-stop may be followed by signal-delivery-stop for signal(s)  "
-"I<other than> B<SIGCONT>, if they were pending when B<SIGCONT> was "
-"delivered.  In other words, B<SIGCONT> may be not the first signal observed "
-"by the tracee after it was sent."
+msgid "The B<SIGCONT> signal has a side effect of waking up (all threads of)  a group-stopped process.  This side effect happens before signal-delivery-stop.  The tracer can't suppress this side effect (it can only suppress signal injection, which only causes the B<SIGCONT> handler to not be executed in the tracee, if such a handler is installed).  In fact, waking up from group-stop may be followed by signal-delivery-stop for signal(s)  I<other than> B<SIGCONT>, if they were pending when B<SIGCONT> was delivered.  In other words, B<SIGCONT> may be not the first signal observed by the tracee after it was sent."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1131
-msgid ""
-"Stopping signals cause (all threads of) a process to enter group-stop.  This "
-"side effect happens after signal injection, and therefore can be suppressed "
-"by the tracer."
+msgid "Stopping signals cause (all threads of) a process to enter group-stop.  This side effect happens after signal injection, and therefore can be suppressed by the tracer."
 msgstr ""
 
 #
@@ -10124,12 +8072,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1158
-msgid ""
-"B<PTRACE_GETSIGINFO> can be used to retrieve a I<siginfo_t> structure which "
-"corresponds to the delivered signal.  B<PTRACE_SETSIGINFO> may be used to "
-"modify it.  If B<PTRACE_SETSIGINFO> has been used to alter I<siginfo_t>, the "
-"I<si_signo> field and the I<sig> parameter in the restarting command must "
-"match, otherwise the result is undefined."
+msgid "B<PTRACE_GETSIGINFO> can be used to retrieve a I<siginfo_t> structure which corresponds to the delivered signal.  B<PTRACE_SETSIGINFO> may be used to modify it.  If B<PTRACE_SETSIGINFO> has been used to alter I<siginfo_t>, the I<si_signo> field and the I<sig> parameter in the restarting command must match, otherwise the result is undefined."
 msgstr ""
 
 #. type: SS
@@ -10140,23 +8083,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1170
-msgid ""
-"When a (possibly multithreaded) process receives a stopping signal, all "
-"threads stop.  If some threads are traced, they enter a group-stop.  Note "
-"that the stopping signal will first cause signal-delivery-stop (on one "
-"tracee only), and only after it is injected by the tracer (or after it was "
-"dispatched to a thread which isn't traced), will group-stop be initiated on "
-"I<all> tracees within the multithreaded process.  As usual, every tracee "
-"reports its group-stop separately to the corresponding tracer."
+msgid "When a (possibly multithreaded) process receives a stopping signal, all threads stop.  If some threads are traced, they enter a group-stop.  Note that the stopping signal will first cause signal-delivery-stop (on one tracee only), and only after it is injected by the tracer (or after it was dispatched to a thread which isn't traced), will group-stop be initiated on I<all> tracees within the multithreaded process.  As usual, every tracee reports its group-stop separately to the corresponding tracer."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1179
-msgid ""
-"Group-stop is observed by the tracer as B<waitpid>(2)  returning with "
-"I<WIFSTOPPED(status)> true, with the stopping signal available via "
-"I<WSTOPSIG(status)>.  The same result is returned by some other classes of "
-"ptrace-stops, therefore the recommended practice is to perform the call"
+msgid "Group-stop is observed by the tracer as B<waitpid>(2)  returning with I<WIFSTOPPED(status)> true, with the stopping signal available via I<WSTOPSIG(status)>.  The same result is returned by some other classes of ptrace-stops, therefore the recommended practice is to perform the call"
 msgstr ""
 
 #. type: Plain text
@@ -10167,53 +8099,27 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1202
-msgid ""
-"The call can be avoided if the signal is not B<SIGSTOP>, B<SIGTSTP>, "
-"B<SIGTTIN>, or B<SIGTTOU>; only these four signals are stopping signals.  If "
-"the tracer sees something else, it can't be a group-stop.  Otherwise, the "
-"tracer needs to call B<PTRACE_GETSIGINFO>.  If B<PTRACE_GETSIGINFO> fails "
-"with B<EINVAL>, then it is definitely a group-stop.  (Other failure codes "
-"are possible, such as B<ESRCH> (\"no such process\") if a B<SIGKILL> killed "
-"the tracee.)"
+msgid "The call can be avoided if the signal is not B<SIGSTOP>, B<SIGTSTP>, B<SIGTTIN>, or B<SIGTTOU>; only these four signals are stopping signals.  If the tracer sees something else, it can't be a group-stop.  Otherwise, the tracer needs to call B<PTRACE_GETSIGINFO>.  If B<PTRACE_GETSIGINFO> fails with B<EINVAL>, then it is definitely a group-stop.  (Other failure codes are possible, such as B<ESRCH> (\"no such process\") if a B<SIGKILL> killed the tracee.)"
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1212
-msgid ""
-"If tracee was attached using B<PTRACE_SEIZE>, group-stop is indicated by "
-"B<PTRACE_EVENT_STOP>: I<statusE<gt>E<gt>16 == PTRACE_EVENT_STOP>.  This "
-"allows detection of group-stops without requiring an extra "
-"B<PTRACE_GETSIGINFO> call."
+msgid "If tracee was attached using B<PTRACE_SEIZE>, group-stop is indicated by B<PTRACE_EVENT_STOP>: I<statusE<gt>E<gt>16 == PTRACE_EVENT_STOP>.  This allows detection of group-stops without requiring an extra B<PTRACE_GETSIGINFO> call."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1221
-msgid ""
-"As of Linux 2.6.38, after the tracer sees the tracee ptrace-stop and until "
-"it restarts or kills it, the tracee will not run, and will not send "
-"notifications (except B<SIGKILL> death) to the tracer, even if the tracer "
-"enters into another B<waitpid>(2)  call."
+msgid "As of Linux 2.6.38, after the tracer sees the tracee ptrace-stop and until it restarts or kills it, the tracee will not run, and will not send notifications (except B<SIGKILL> death) to the tracer, even if the tracer enters into another B<waitpid>(2)  call."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1235
-msgid ""
-"The kernel behavior described in the previous paragraph causes a problem "
-"with transparent handling of stopping signals.  If the tracer restarts the "
-"tracee after group-stop, the stopping signal is effectively ignored\\(emthe "
-"tracee doesn't remain stopped, it runs.  If the tracer doesn't restart the "
-"tracee before entering into the next B<waitpid>(2), future B<SIGCONT> "
-"signals will not be reported to the tracer; this would cause the B<SIGCONT> "
-"signals to have no effect on the tracee."
+msgid "The kernel behavior described in the previous paragraph causes a problem with transparent handling of stopping signals.  If the tracer restarts the tracee after group-stop, the stopping signal is effectively ignored\\(emthe tracee doesn't remain stopped, it runs.  If the tracer doesn't restart the tracee before entering into the next B<waitpid>(2), future B<SIGCONT> signals will not be reported to the tracer; this would cause the B<SIGCONT> signals to have no effect on the tracee."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1246
-msgid ""
-"Since Linux 3.4, there is a method to overcome this problem: instead of "
-"B<PTRACE_CONT>, a B<PTRACE_LISTEN> command can be used to restart a tracee "
-"in a way where it does not execute, but waits for a new event which it can "
-"report via B<waitpid>(2)  (such as when it is restarted by a B<SIGCONT>)."
+msgid "Since Linux 3.4, there is a method to overcome this problem: instead of B<PTRACE_CONT>, a B<PTRACE_LISTEN> command can be used to restart a tracee in a way where it does not execute, but waits for a new event which it can report via B<waitpid>(2)  (such as when it is restarted by a B<SIGCONT>)."
 msgstr ""
 
 #. type: SS
@@ -10224,18 +8130,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1252
-msgid ""
-"If the tracer sets B<PTRACE_O_TRACE_*> options, the tracee will enter ptrace-"
-"stops called B<PTRACE_EVENT> stops."
+msgid "If the tracer sets B<PTRACE_O_TRACE_*> options, the tracee will enter ptrace-stops called B<PTRACE_EVENT> stops."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1266
-msgid ""
-"B<PTRACE_EVENT> stops are observed by the tracer as B<waitpid>(2)  returning "
-"with I<WIFSTOPPED(status)>, and I<WSTOPSIG(status)> returns B<SIGTRAP>.  An "
-"additional bit is set in the higher byte of the status word: the value "
-"I<statusE<gt>E<gt>8> will be"
+msgid "B<PTRACE_EVENT> stops are observed by the tracer as B<waitpid>(2)  returning with I<WIFSTOPPED(status)>, and I<WSTOPSIG(status)> returns B<SIGTRAP>.  An additional bit is set in the higher byte of the status word: the value I<statusE<gt>E<gt>8> will be"
 msgstr ""
 
 #. type: Plain text
@@ -10257,11 +8157,7 @@ msgstr "B<PTRACE_EVENT_VFORK>"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1283
-msgid ""
-"Stop before return from B<vfork>(2)  or B<clone>(2)  with the B<CLONE_VFORK> "
-"flag.  When the tracee is continued after this stop, it will wait for child "
-"to exit/exec before continuing its execution (in other words, the usual "
-"behavior on B<vfork>(2))."
+msgid "Stop before return from B<vfork>(2)  or B<clone>(2)  with the B<CLONE_VFORK> flag.  When the tracee is continued after this stop, it will wait for child to exit/exec before continuing its execution (in other words, the usual behavior on B<vfork>(2))."
 msgstr ""
 
 #. type: TP
@@ -10272,9 +8168,7 @@ msgstr "B<PTRACE_EVENT_FORK>"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1291
-msgid ""
-"Stop before return from B<fork>(2)  or B<clone>(2)  with the exit signal set "
-"to B<SIGCHLD>."
+msgid "Stop before return from B<fork>(2)  or B<clone>(2)  with the exit signal set to B<SIGCHLD>."
 msgstr ""
 
 #. type: TP
@@ -10296,17 +8190,12 @@ msgstr "B<PTRACE_EVENT_VFORK_DONE>"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1305
-msgid ""
-"Stop before return from B<vfork>(2)  or B<clone>(2)  with the B<CLONE_VFORK> "
-"flag, but after the child unblocked this tracee by exiting or execing."
+msgid "Stop before return from B<vfork>(2)  or B<clone>(2)  with the B<CLONE_VFORK> flag, but after the child unblocked this tracee by exiting or execing."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1311
-msgid ""
-"For all four stops described above, the stop occurs in the parent (i.e., the "
-"tracee), not in the newly created thread.  B<PTRACE_GETEVENTMSG> can be used "
-"to retrieve the new thread's ID."
+msgid "For all four stops described above, the stop occurs in the parent (i.e., the tracee), not in the newly created thread.  B<PTRACE_GETEVENTMSG> can be used to retrieve the new thread's ID."
 msgstr ""
 
 #. type: TP
@@ -10317,9 +8206,7 @@ msgstr "B<PTRACE_EVENT_EXEC>"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1318
-msgid ""
-"Stop before return from B<execve>(2).  Since Linux 3.0, "
-"B<PTRACE_GETEVENTMSG> returns the former thread ID."
+msgid "Stop before return from B<execve>(2).  Since Linux 3.0, B<PTRACE_GETEVENTMSG> returns the former thread ID."
 msgstr ""
 
 #. type: TP
@@ -10330,12 +8217,7 @@ msgstr "B<PTRACE_EVENT_EXIT>"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1334
-msgid ""
-"Stop before exit (including death from B<exit_group>(2)), signal death, or "
-"exit caused by B<execve>(2)  in a multithreaded process.  "
-"B<PTRACE_GETEVENTMSG> returns the exit status.  Registers can be examined "
-"(unlike when \"real\" exit happens).  The tracee is still alive; it needs to "
-"be B<PTRACE_CONT>ed or B<PTRACE_DETACH>ed to finish exiting."
+msgid "Stop before exit (including death from B<exit_group>(2)), signal death, or exit caused by B<execve>(2)  in a multithreaded process.  B<PTRACE_GETEVENTMSG> returns the exit status.  Registers can be examined (unlike when \"real\" exit happens).  The tracee is still alive; it needs to be B<PTRACE_CONT>ed or B<PTRACE_DETACH>ed to finish exiting."
 msgstr ""
 
 #. type: TP
@@ -10346,33 +8228,23 @@ msgstr "B<PTRACE_EVENT_STOP>"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1346
-msgid ""
-"Stop induced by B<PTRACE_INTERRUPT> command, or group-stop, or initial "
-"ptrace-stop when a new child is attached (only if attached using "
-"B<PTRACE_SEIZE>), or B<PTRACE_EVENT_STOP> if B<PTRACE_SEIZE> was used."
+msgid "Stop induced by B<PTRACE_INTERRUPT> command, or group-stop, or initial ptrace-stop when a new child is attached (only if attached using B<PTRACE_SEIZE>), or B<PTRACE_EVENT_STOP> if B<PTRACE_SEIZE> was used."
 msgstr ""
 
 #. type: TP
 #: build/C/man2/ptrace.2:1346
-#, fuzzy, no-wrap
-#| msgid "B<PTRACE_EVENT_STOP>"
+#, no-wrap
 msgid "B<PTRACE_EVENT_SECCOMP>"
-msgstr "B<PTRACE_EVENT_STOP>"
+msgstr "B<PTRACE_EVENT_SECCOMP>"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1357
-msgid ""
-"Stop triggered by a B<seccomp>(2)  rule on tracee syscall entry when "
-"B<PTRACE_O_TRACESECCOMP> has been set by the tracer.  The seccomp event "
-"message data (from the B<SECCOMP_RET_DATA> portion of the seccomp filter "
-"rule) can be retrieved with B<PTRACE_GETEVENTMSG>."
+msgid "Stop triggered by a B<seccomp>(2)  rule on tracee syscall entry when B<PTRACE_O_TRACESECCOMP> has been set by the tracer.  The seccomp event message data (from the B<SECCOMP_RET_DATA> portion of the seccomp filter rule) can be retrieved with B<PTRACE_GETEVENTMSG>."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1369
-msgid ""
-"B<PTRACE_GETSIGINFO> on B<PTRACE_EVENT> stops returns B<SIGTRAP> in "
-"I<si_signo>, with I<si_code> set to I<(eventE<lt>E<lt>8)\\ |\\ SIGTRAP>."
+msgid "B<PTRACE_GETSIGINFO> on B<PTRACE_EVENT> stops returns B<SIGTRAP> in I<si_signo>, with I<si_code> set to I<(eventE<lt>E<lt>8)\\ |\\ SIGTRAP>."
 msgstr ""
 
 #. type: SS
@@ -10383,40 +8255,22 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1382
-msgid ""
-"If the tracee was restarted by B<PTRACE_SYSCALL>, the tracee enters syscall-"
-"enter-stop just prior to entering any system call.  If the tracer restarts "
-"the tracee with B<PTRACE_SYSCALL>, the tracee enters syscall-exit-stop when "
-"the system call is finished, or if it is interrupted by a signal.  (That is, "
-"signal-delivery-stop never happens between syscall-enter-stop and syscall-"
-"exit-stop; it happens I<after> syscall-exit-stop.)"
+msgid "If the tracee was restarted by B<PTRACE_SYSCALL>, the tracee enters syscall-enter-stop just prior to entering any system call.  If the tracer restarts the tracee with B<PTRACE_SYSCALL>, the tracee enters syscall-exit-stop when the system call is finished, or if it is interrupted by a signal.  (That is, signal-delivery-stop never happens between syscall-enter-stop and syscall-exit-stop; it happens I<after> syscall-exit-stop.)"
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1396
-msgid ""
-"Other possibilities are that the tracee may stop in a B<PTRACE_EVENT> stop, "
-"exit (if it entered B<_exit>(2)  or B<exit_group>(2)), be killed by "
-"B<SIGKILL>, or die silently (if it is a thread group leader, the "
-"B<execve>(2)  happened in another thread, and that thread is not traced by "
-"the same tracer; this situation is discussed later)."
+msgid "Other possibilities are that the tracee may stop in a B<PTRACE_EVENT> stop, exit (if it entered B<_exit>(2)  or B<exit_group>(2)), be killed by B<SIGKILL>, or die silently (if it is a thread group leader, the B<execve>(2)  happened in another thread, and that thread is not traced by the same tracer; this situation is discussed later)."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1411
-msgid ""
-"Syscall-enter-stop and syscall-exit-stop are observed by the tracer as "
-"B<waitpid>(2)  returning with I<WIFSTOPPED(status)> true, and "
-"I<WSTOPSIG(status)> giving B<SIGTRAP>.  If the B<PTRACE_O_TRACESYSGOOD> "
-"option was set by the tracer, then I<WSTOPSIG(status)> will give the value "
-"I<(SIGTRAP\\ |\\ 0x80)>."
+msgid "Syscall-enter-stop and syscall-exit-stop are observed by the tracer as B<waitpid>(2)  returning with I<WIFSTOPPED(status)> true, and I<WSTOPSIG(status)> giving B<SIGTRAP>.  If the B<PTRACE_O_TRACESYSGOOD> option was set by the tracer, then I<WSTOPSIG(status)> will give the value I<(SIGTRAP\\ |\\ 0x80)>."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1417
-msgid ""
-"Syscall-stops can be distinguished from signal-delivery-stop with B<SIGTRAP> "
-"by querying B<PTRACE_GETSIGINFO> for the following cases:"
+msgid "Syscall-stops can be distinguished from signal-delivery-stop with B<SIGTRAP> by querying B<PTRACE_GETSIGINFO> for the following cases:"
 msgstr ""
 
 #. type: TP
@@ -10427,11 +8281,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1429
-msgid ""
-"B<SIGTRAP> was delivered as a result of a user-space action, for example, a "
-"system call (B<tgkill>(2), B<kill>(2), B<sigqueue>(3), etc.), expiration of "
-"a POSIX timer, change of state on a POSIX message queue, or completion of an "
-"asynchronous I/O request."
+msgid "B<SIGTRAP> was delivered as a result of a user-space action, for example, a system call (B<tgkill>(2), B<kill>(2), B<sigqueue>(3), etc.), expiration of a POSIX timer, change of state on a POSIX message queue, or completion of an asynchronous I/O request."
 msgstr ""
 
 #. type: TP
@@ -10458,56 +8308,32 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1441
-msgid ""
-"However, syscall-stops happen very often (twice per system call), and "
-"performing B<PTRACE_GETSIGINFO> for every syscall-stop may be somewhat "
-"expensive."
+msgid "However, syscall-stops happen very often (twice per system call), and performing B<PTRACE_GETSIGINFO> for every syscall-stop may be somewhat expensive."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1464
-msgid ""
-"Some architectures allow the cases to be distinguished by examining "
-"registers.  For example, on x86, I<rax> == -B<ENOSYS> in syscall-enter-"
-"stop.  Since B<SIGTRAP> (like any other signal) always happens I<after> "
-"syscall-exit-stop, and at this point I<rax> almost never contains -"
-"B<ENOSYS>, the B<SIGTRAP> looks like \"syscall-stop which is not syscall-"
-"enter-stop\"; in other words, it looks like a \"stray syscall-exit-stop\" "
-"and can be detected this way.  But such detection is fragile and is best "
-"avoided."
+msgid "Some architectures allow the cases to be distinguished by examining registers.  For example, on x86, I<rax> == -B<ENOSYS> in syscall-enter-stop.  Since B<SIGTRAP> (like any other signal) always happens I<after> syscall-exit-stop, and at this point I<rax> almost never contains -B<ENOSYS>, the B<SIGTRAP> looks like \"syscall-stop which is not syscall-enter-stop\"; in other words, it looks like a \"stray syscall-exit-stop\" and can be detected this way.  But such detection is fragile and is best avoided."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1470
-msgid ""
-"Using the B<PTRACE_O_TRACESYSGOOD> option is the recommended method to "
-"distinguish syscall-stops from other kinds of ptrace-stops, since it is "
-"reliable and does not incur a performance penalty."
+msgid "Using the B<PTRACE_O_TRACESYSGOOD> option is the recommended method to distinguish syscall-stops from other kinds of ptrace-stops, since it is reliable and does not incur a performance penalty."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1481
-msgid ""
-"Syscall-enter-stop and syscall-exit-stop are indistinguishable from each "
-"other by the tracer.  The tracer needs to keep track of the sequence of "
-"ptrace-stops in order to not misinterpret syscall-enter-stop as syscall-exit-"
-"stop or vice versa.  The rule is that syscall-enter-stop is always followed "
-"by syscall-exit-stop, B<PTRACE_EVENT> stop or the tracee's death; no other "
-"kinds of ptrace-stop can occur in between."
+msgid "Syscall-enter-stop and syscall-exit-stop are indistinguishable from each other by the tracer.  The tracer needs to keep track of the sequence of ptrace-stops in order to not misinterpret syscall-enter-stop as syscall-exit-stop or vice versa.  The rule is that syscall-enter-stop is always followed by syscall-exit-stop, B<PTRACE_EVENT> stop or the tracee's death; no other kinds of ptrace-stop can occur in between."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1486
-msgid ""
-"If after syscall-enter-stop, the tracer uses a restarting command other than "
-"B<PTRACE_SYSCALL>, syscall-exit-stop is not generated."
+msgid "If after syscall-enter-stop, the tracer uses a restarting command other than B<PTRACE_SYSCALL>, syscall-exit-stop is not generated."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1498
-msgid ""
-"B<PTRACE_GETSIGINFO> on syscall-stops returns B<SIGTRAP> in I<si_signo>, "
-"with I<si_code> set to B<SIGTRAP> or I<(SIGTRAP|0x80)>."
+msgid "B<PTRACE_GETSIGINFO> on syscall-stops returns B<SIGTRAP> in I<si_signo>, with I<si_code> set to B<SIGTRAP> or I<(SIGTRAP|0x80)>."
 msgstr ""
 
 #. type: SS
@@ -10533,18 +8359,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1514
-msgid ""
-"Most ptrace commands (all except B<PTRACE_ATTACH>, B<PTRACE_SEIZE>, "
-"B<PTRACE_TRACEME>, B<PTRACE_INTERRUPT>, and B<PTRACE_KILL>)  require the "
-"tracee to be in a ptrace-stop, otherwise they fail with B<ESRCH>."
+msgid "Most ptrace commands (all except B<PTRACE_ATTACH>, B<PTRACE_SEIZE>, B<PTRACE_TRACEME>, B<PTRACE_INTERRUPT>, and B<PTRACE_KILL>)  require the tracee to be in a ptrace-stop, otherwise they fail with B<ESRCH>."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1519
-msgid ""
-"When the tracee is in ptrace-stop, the tracer can read and write data to the "
-"tracee using informational commands.  These commands leave the tracee in "
-"ptrace-stopped state:"
+msgid "When the tracee is in ptrace-stop, the tracer can read and write data to the tracee using informational commands.  These commands leave the tracee in ptrace-stopped state:"
 msgstr ""
 
 #. type: Plain text
@@ -10565,12 +8385,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1543
-msgid ""
-"Note that some errors are not reported.  For example, setting signal "
-"information (I<siginfo>)  may have no effect in some ptrace-stops, yet the "
-"call may succeed (return 0 and not set I<errno>); querying "
-"B<PTRACE_GETEVENTMSG> may succeed and return some random value if current "
-"ptrace-stop is not documented as returning a meaningful event message."
+msgid "Note that some errors are not reported.  For example, setting signal information (I<siginfo>)  may have no effect in some ptrace-stops, yet the call may succeed (return 0 and not set I<errno>); querying B<PTRACE_GETEVENTMSG> may succeed and return some random value if current ptrace-stop is not documented as returning a meaningful event message."
 msgstr ""
 
 #. type: Plain text
@@ -10586,18 +8401,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1556
-msgid ""
-"affects one tracee.  The tracee's current flags are replaced.  Flags are "
-"inherited by new tracees created and \"auto-attached\" via active "
-"B<PTRACE_O_TRACEFORK>, B<PTRACE_O_TRACEVFORK>, or B<PTRACE_O_TRACECLONE> "
-"options."
+msgid "affects one tracee.  The tracee's current flags are replaced.  Flags are inherited by new tracees created and \"auto-attached\" via active B<PTRACE_O_TRACEFORK>, B<PTRACE_O_TRACEVFORK>, or B<PTRACE_O_TRACECLONE> options."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1559
-msgid ""
-"Another group of commands makes the ptrace-stopped tracee run.  They have "
-"the form:"
+msgid "Another group of commands makes the ptrace-stopped tracee run.  They have the form:"
 msgstr ""
 
 #. type: Plain text
@@ -10608,13 +8417,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1582
-msgid ""
-"where I<cmd> is B<PTRACE_CONT>, B<PTRACE_LISTEN>, B<PTRACE_DETACH>, "
-"B<PTRACE_SYSCALL>, B<PTRACE_SINGLESTEP>, B<PTRACE_SYSEMU>, or "
-"B<PTRACE_SYSEMU_SINGLESTEP>.  If the tracee is in signal-delivery-stop, "
-"I<sig> is the signal to be injected (if it is nonzero).  Otherwise, I<sig> "
-"may be ignored.  (When restarting a tracee from a ptrace-stop other than "
-"signal-delivery-stop, recommended practice is to always pass 0 in I<sig>.)"
+msgid "where I<cmd> is B<PTRACE_CONT>, B<PTRACE_LISTEN>, B<PTRACE_DETACH>, B<PTRACE_SYSCALL>, B<PTRACE_SINGLESTEP>, B<PTRACE_SYSEMU>, or B<PTRACE_SYSEMU_SINGLESTEP>.  If the tracee is in signal-delivery-stop, I<sig> is the signal to be injected (if it is nonzero).  Otherwise, I<sig> may be ignored.  (When restarting a tracee from a ptrace-stop other than signal-delivery-stop, recommended practice is to always pass 0 in I<sig>.)"
 msgstr ""
 
 #. type: SS
@@ -10649,33 +8452,17 @@ msgstr ""
 #.  FIXME . Describe how to attach to a thread which is already group-stopped.
 #. type: Plain text
 #: build/C/man2/ptrace.2:1614
-msgid ""
-"B<PTRACE_ATTACH> sends B<SIGSTOP> to this thread.  If the tracer wants this "
-"B<SIGSTOP> to have no effect, it needs to suppress it.  Note that if other "
-"signals are concurrently sent to this thread during attach, the tracer may "
-"see the tracee enter signal-delivery-stop with other signal(s) first! The "
-"usual practice is to reinject these signals until B<SIGSTOP> is seen, then "
-"suppress B<SIGSTOP> injection.  The design bug here is that a ptrace attach "
-"and a concurrently delivered B<SIGSTOP> may race and the concurrent "
-"B<SIGSTOP> may be lost."
+msgid "B<PTRACE_ATTACH> sends B<SIGSTOP> to this thread.  If the tracer wants this B<SIGSTOP> to have no effect, it needs to suppress it.  Note that if other signals are concurrently sent to this thread during attach, the tracer may see the tracee enter signal-delivery-stop with other signal(s) first! The usual practice is to reinject these signals until B<SIGSTOP> is seen, then suppress B<SIGSTOP> injection.  The design bug here is that a ptrace attach and a concurrently delivered B<SIGSTOP> may race and the concurrent B<SIGSTOP> may be lost."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1621
-msgid ""
-"Since attaching sends B<SIGSTOP> and the tracer usually suppresses it, this "
-"may cause a stray B<EINTR> return from the currently executing system call "
-"in the tracee, as described in the \"Signal injection and suppression\" "
-"section."
+msgid "Since attaching sends B<SIGSTOP> and the tracer usually suppresses it, this may cause a stray B<EINTR> return from the currently executing system call in the tracee, as described in the \"Signal injection and suppression\" section."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1633
-msgid ""
-"Since Linux 3.4, B<PTRACE_SEIZE> can be used instead of B<PTRACE_ATTACH>.  "
-"B<PTRACE_SEIZE> does not stop the attached process.  If you need to stop it "
-"after attach (or at any other time) without sending it any signals, use "
-"B<PTRACE_INTERRUPT> command."
+msgid "Since Linux 3.4, B<PTRACE_SEIZE> can be used instead of B<PTRACE_ATTACH>.  B<PTRACE_SEIZE> does not stop the attached process.  If you need to stop it after attach (or at any other time) without sending it any signals, use B<PTRACE_INTERRUPT> command."
 msgstr ""
 
 #. type: Plain text
@@ -10691,10 +8478,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1643
-msgid ""
-"turns the calling thread into a tracee.  The thread continues to run "
-"(doesn't enter ptrace-stop).  A common practice is to follow the "
-"B<PTRACE_TRACEME> with"
+msgid "turns the calling thread into a tracee.  The thread continues to run (doesn't enter ptrace-stop).  A common practice is to follow the B<PTRACE_TRACEME> with"
 msgstr ""
 
 #. type: Plain text
@@ -10705,22 +8489,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1648
-msgid ""
-"and allow the parent (which is our tracer now) to observe our signal-"
-"delivery-stop."
+msgid "and allow the parent (which is our tracer now) to observe our signal-delivery-stop."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1672
-msgid ""
-"If the B<PTRACE_O_TRACEFORK>, B<PTRACE_O_TRACEVFORK>, or "
-"B<PTRACE_O_TRACECLONE> options are in effect, then children created by, "
-"respectively, B<vfork>(2)  or B<clone>(2)  with the B<CLONE_VFORK> flag, "
-"B<fork>(2)  or B<clone>(2)  with the exit signal set to B<SIGCHLD>, and "
-"other kinds of B<clone>(2), are automatically attached to the same tracer "
-"which traced their parent.  B<SIGSTOP> is delivered to the children, causing "
-"them to enter signal-delivery-stop after they exit the system call which "
-"created them."
+msgid "If the B<PTRACE_O_TRACEFORK>, B<PTRACE_O_TRACEVFORK>, or B<PTRACE_O_TRACECLONE> options are in effect, then children created by, respectively, B<vfork>(2)  or B<clone>(2)  with the B<CLONE_VFORK> flag, B<fork>(2)  or B<clone>(2)  with the exit signal set to B<SIGCHLD>, and other kinds of B<clone>(2), are automatically attached to the same tracer which traced their parent.  B<SIGSTOP> is delivered to the children, causing them to enter signal-delivery-stop after they exit the system call which created them."
 msgstr ""
 
 #. type: Plain text
@@ -10736,36 +8510,19 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1684
-msgid ""
-"B<PTRACE_DETACH> is a restarting operation; therefore it requires the tracee "
-"to be in ptrace-stop.  If the tracee is in signal-delivery-stop, a signal "
-"can be injected.  Otherwise, the I<sig> parameter may be silently ignored."
+msgid "B<PTRACE_DETACH> is a restarting operation; therefore it requires the tracee to be in ptrace-stop.  If the tracee is in signal-delivery-stop, a signal can be injected.  Otherwise, the I<sig> parameter may be silently ignored."
 msgstr ""
 
 #.  FIXME . Describe how to detach from a group-stopped tracee so that it
 #.         doesn't run, but continues to wait for SIGCONT.
 #. type: Plain text
 #: build/C/man2/ptrace.2:1708
-msgid ""
-"If the tracee is running when the tracer wants to detach it, the usual "
-"solution is to send B<SIGSTOP> (using B<tgkill>(2), to make sure it goes to "
-"the correct thread), wait for the tracee to stop in signal-delivery-stop for "
-"B<SIGSTOP> and then detach it (suppressing B<SIGSTOP> injection).  A design "
-"bug is that this can race with concurrent B<SIGSTOP>s.  Another complication "
-"is that the tracee may enter other ptrace-stops and needs to be restarted "
-"and waited for again, until B<SIGSTOP> is seen.  Yet another complication is "
-"to be sure that the tracee is not already ptrace-stopped, because no signal "
-"delivery happens while it is\\(emnot even B<SIGSTOP>."
+msgid "If the tracee is running when the tracer wants to detach it, the usual solution is to send B<SIGSTOP> (using B<tgkill>(2), to make sure it goes to the correct thread), wait for the tracee to stop in signal-delivery-stop for B<SIGSTOP> and then detach it (suppressing B<SIGSTOP> injection).  A design bug is that this can race with concurrent B<SIGSTOP>s.  Another complication is that the tracee may enter other ptrace-stops and needs to be restarted and waited for again, until B<SIGSTOP> is seen.  Yet another complication is to be sure that the tracee is not already ptrace-stopped, because no signal delivery happens while it is\\(emnot even B<SIGSTOP>."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1716
-msgid ""
-"If the tracer dies, all tracees are automatically detached and restarted, "
-"unless they were in group-stop.  Handling of restart from group-stop is "
-"currently buggy, but the \"as planned\" behavior is to leave tracee stopped "
-"and waiting for B<SIGCONT>.  If the tracee is restarted from signal-delivery-"
-"stop, the pending signal is injected."
+msgid "If the tracer dies, all tracees are automatically detached and restarted, unless they were in group-stop.  Handling of restart from group-stop is currently buggy, but the \"as planned\" behavior is to leave tracee stopped and waiting for B<SIGCONT>.  If the tracee is restarted from signal-delivery-stop, the pending signal is injected."
 msgstr ""
 
 #. type: SS
@@ -10782,91 +8539,47 @@ msgstr ""
 #.  In kernel 3.1 sources, see fs/exec.c::de_thread()
 #. type: Plain text
 #: build/C/man2/ptrace.2:1735
-msgid ""
-"When one thread in a multithreaded process calls B<execve>(2), the kernel "
-"destroys all other threads in the process, and resets the thread ID of the "
-"execing thread to the thread group ID (process ID).  (Or, to put things "
-"another way, when a multithreaded process does an B<execve>(2), at "
-"completion of the call, it appears as though the B<execve>(2)  occurred in "
-"the thread group leader, regardless of which thread did the B<execve>(2).)  "
-"This resetting of the thread ID looks very confusing to tracers:"
+msgid "When one thread in a multithreaded process calls B<execve>(2), the kernel destroys all other threads in the process, and resets the thread ID of the execing thread to the thread group ID (process ID).  (Or, to put things another way, when a multithreaded process does an B<execve>(2), at completion of the call, it appears as though the B<execve>(2)  occurred in the thread group leader, regardless of which thread did the B<execve>(2).)  This resetting of the thread ID looks very confusing to tracers:"
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1745
-msgid ""
-"All other threads stop in B<PTRACE_EVENT_EXIT> stop, if the "
-"B<PTRACE_O_TRACEEXIT> option was turned on.  Then all other threads except "
-"the thread group leader report death as if they exited via B<_exit>(2)  with "
-"exit code 0."
+msgid "All other threads stop in B<PTRACE_EVENT_EXIT> stop, if the B<PTRACE_O_TRACEEXIT> option was turned on.  Then all other threads except the thread group leader report death as if they exited via B<_exit>(2)  with exit code 0."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1753
-msgid ""
-"The execing tracee changes its thread ID while it is in the B<execve>(2).  "
-"(Remember, under ptrace, the \"pid\" returned from B<waitpid>(2), or fed "
-"into ptrace calls, is the tracee's thread ID.)  That is, the tracee's thread "
-"ID is reset to be the same as its process ID, which is the same as the "
-"thread group leader's thread ID."
+msgid "The execing tracee changes its thread ID while it is in the B<execve>(2).  (Remember, under ptrace, the \"pid\" returned from B<waitpid>(2), or fed into ptrace calls, is the tracee's thread ID.)  That is, the tracee's thread ID is reset to be the same as its process ID, which is the same as the thread group leader's thread ID."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1759
-msgid ""
-"Then a B<PTRACE_EVENT_EXEC> stop happens, if the B<PTRACE_O_TRACEEXEC> "
-"option was turned on."
+msgid "Then a B<PTRACE_EVENT_EXEC> stop happens, if the B<PTRACE_O_TRACEEXEC> option was turned on."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1780
-msgid ""
-"If the thread group leader has reported its B<PTRACE_EVENT_EXIT> stop by "
-"this time, it appears to the tracer that the dead thread leader \"reappears "
-"from nowhere\".  (Note: the thread group leader does not report death via "
-"I<WIFEXITED(status)> until there is at least one other live thread.  This "
-"eliminates the possibility that the tracer will see it dying and then "
-"reappearing.)  If the thread group leader was still alive, for the tracer "
-"this may look as if thread group leader returns from a different system call "
-"than it entered, or even \"returned from a system call even though it was "
-"not in any system call\".  If the thread group leader was not traced (or was "
-"traced by a different tracer), then during B<execve>(2)  it will appear as "
-"if it has become a tracee of the tracer of the execing tracee."
+msgid "If the thread group leader has reported its B<PTRACE_EVENT_EXIT> stop by this time, it appears to the tracer that the dead thread leader \"reappears from nowhere\".  (Note: the thread group leader does not report death via I<WIFEXITED(status)> until there is at least one other live thread.  This eliminates the possibility that the tracer will see it dying and then reappearing.)  If the thread group leader was still alive, for the tracer this may look as if thread group leader returns from a different system call than it entered, or even \"returned from a system call even though it was not in any system call\".  If the thread group leader was not traced (or was traced by a different tracer), then during B<execve>(2)  it will appear as if it has become a tracee of the tracer of the execing tracee."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1783
-msgid ""
-"All of the above effects are the artifacts of the thread ID change in the "
-"tracee."
+msgid "All of the above effects are the artifacts of the thread ID change in the tracee."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1803
-msgid ""
-"The B<PTRACE_O_TRACEEXEC> option is the recommended tool for dealing with "
-"this situation.  First, it enables B<PTRACE_EVENT_EXEC> stop, which occurs "
-"before B<execve>(2)  returns.  In this stop, the tracer can use "
-"B<PTRACE_GETEVENTMSG> to retrieve the tracee's former thread ID.  (This "
-"feature was introduced in Linux 3.0).  Second, the B<PTRACE_O_TRACEEXEC> "
-"option disables legacy B<SIGTRAP> generation on B<execve>(2)."
+msgid "The B<PTRACE_O_TRACEEXEC> option is the recommended tool for dealing with this situation.  First, it enables B<PTRACE_EVENT_EXEC> stop, which occurs before B<execve>(2)  returns.  In this stop, the tracer can use B<PTRACE_GETEVENTMSG> to retrieve the tracee's former thread ID.  (This feature was introduced in Linux 3.0).  Second, the B<PTRACE_O_TRACEEXEC> option disables legacy B<SIGTRAP> generation on B<execve>(2)."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1809
-msgid ""
-"When the tracer receives B<PTRACE_EVENT_EXEC> stop notification, it is "
-"guaranteed that except this tracee and the thread group leader, no other "
-"threads from the process are alive."
+msgid "When the tracer receives B<PTRACE_EVENT_EXEC> stop notification, it is guaranteed that except this tracee and the thread group leader, no other threads from the process are alive."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1817
-msgid ""
-"On receiving the B<PTRACE_EVENT_EXEC> stop notification, the tracer should "
-"clean up all its internal data structures describing the threads of this "
-"process, and retain only one data structure\\(emone which describes the "
-"single still running tracee, with"
+msgid "On receiving the B<PTRACE_EVENT_EXEC> stop notification, the tracer should clean up all its internal data structures describing the threads of this process, and retain only one data structure\\(emone which describes the single still running tracee, with"
 msgstr ""
 
 #. type: Plain text
@@ -10897,25 +8610,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1857
-msgid ""
-"If the B<PTRACE_O_TRACEEXEC> option is I<not> in effect for the execing "
-"tracee, the kernel delivers an extra B<SIGTRAP> to the tracee after "
-"B<execve>(2)  returns.  This is an ordinary signal (similar to one which can "
-"be generated by I<kill -TRAP>), not a special kind of ptrace-stop.  "
-"Employing B<PTRACE_GETSIGINFO> for this signal returns I<si_code> set to 0 "
-"(I<SI_USER>).  This signal may be blocked by signal mask, and thus may be "
-"delivered (much) later."
+msgid "If the B<PTRACE_O_TRACEEXEC> option is I<not> in effect for the execing tracee, the kernel delivers an extra B<SIGTRAP> to the tracee after B<execve>(2)  returns.  This is an ordinary signal (similar to one which can be generated by I<kill -TRAP>), not a special kind of ptrace-stop.  Employing B<PTRACE_GETSIGINFO> for this signal returns I<si_code> set to 0 (I<SI_USER>).  This signal may be blocked by signal mask, and thus may be delivered (much) later."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1876
-msgid ""
-"Usually, the tracer (for example, B<strace>(1))  would not want to show this "
-"extra post-execve B<SIGTRAP> signal to the user, and would suppress its "
-"delivery to the tracee (if B<SIGTRAP> is set to B<SIG_DFL>, it is a killing "
-"signal).  However, determining I<which> B<SIGTRAP> to suppress is not easy.  "
-"Setting the B<PTRACE_O_TRACEEXEC> option and thus suppressing this extra "
-"B<SIGTRAP> is the recommended approach."
+msgid "Usually, the tracer (for example, B<strace>(1))  would not want to show this extra post-execve B<SIGTRAP> signal to the user, and would suppress its delivery to the tracee (if B<SIGTRAP> is set to B<SIG_DFL>, it is a killing signal).  However, determining I<which> B<SIGTRAP> to suppress is not easy.  Setting the B<PTRACE_O_TRACEEXEC> option and thus suppressing this extra B<SIGTRAP> is the recommended approach."
 msgstr ""
 
 #. type: SS
@@ -10926,18 +8626,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1883
-msgid ""
-"The ptrace API (ab)uses the standard UNIX parent/child signaling over "
-"B<waitpid>(2).  This used to cause the real parent of the process to stop "
-"receiving several kinds of B<waitpid>(2)  notifications when the child "
-"process is traced by some other process."
+msgid "The ptrace API (ab)uses the standard UNIX parent/child signaling over B<waitpid>(2).  This used to cause the real parent of the process to stop receiving several kinds of B<waitpid>(2)  notifications when the child process is traced by some other process."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1886
-msgid ""
-"Many of these bugs have been fixed, but as of Linux 2.6.38 several still "
-"exist; see BUGS below."
+msgid "Many of these bugs have been fixed, but as of Linux 2.6.38 several still exist; see BUGS below."
 msgstr ""
 
 #. type: Plain text
@@ -10947,65 +8641,32 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1896
-msgid ""
-"exit/death by signal is reported first to the tracer, then, when the tracer "
-"consumes the B<waitpid>(2)  result, to the real parent (to the real parent "
-"only when the whole multithreaded process exits).  If the tracer and the "
-"real parent are the same process, the report is sent only once."
+msgid "exit/death by signal is reported first to the tracer, then, when the tracer consumes the B<waitpid>(2)  result, to the real parent (to the real parent only when the whole multithreaded process exits).  If the tracer and the real parent are the same process, the report is sent only once."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1901
-msgid ""
-"On success, the B<PTRACE_PEEK*> requests return the requested data (but see "
-"NOTES), while other requests return zero."
+msgid "On success, the B<PTRACE_PEEK*> requests return the requested data (but see NOTES), while other requests return zero."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1911
 #, fuzzy
-#| msgid ""
-#| "On success, B<PTRACE_PEEK*> requests return the requested data, while "
-#| "other requests return zero.  On error, all requests return -1, and "
-#| "I<errno> is set appropriately.  Since the value returned by a successful "
-#| "B<PTRACE_PEEK*> request may be -1, the caller must check I<errno> after "
-#| "such requests to determine whether or not an error occurred."
-msgid ""
-"On error, all requests return -1, and I<errno> is set appropriately.  Since "
-"the value returned by a successful B<PTRACE_PEEK*> request may be -1, the "
-"caller must clear I<errno> before the call, and then check it afterward to "
-"determine whether or not an error occurred."
-msgstr ""
-"成功すると、 B<PTRACE_PEEK*> の場合は要求したデータを返し、 それ以外の場合は "
-"0 を返す。 エラーの場合は -1 を返し、 I<errno> が適切に設定される。 "
-"B<PTRACE_PEEK*> が成功して返す値も　-1 になることがあるため、 そのような要求"
-"の場合には、呼び出し元は I<errno> を調べ、エラーか発生したのかどうかを判断し"
-"なければならない。"
+#| msgid "On success, B<PTRACE_PEEK*> requests return the requested data, while other requests return zero.  On error, all requests return -1, and I<errno> is set appropriately.  Since the value returned by a successful B<PTRACE_PEEK*> request may be -1, the caller must check I<errno> after such requests to determine whether or not an error occurred."
+msgid "On error, all requests return -1, and I<errno> is set appropriately.  Since the value returned by a successful B<PTRACE_PEEK*> request may be -1, the caller must clear I<errno> before the call, and then check it afterward to determine whether or not an error occurred."
+msgstr "成功すると、 B<PTRACE_PEEK*> の場合は要求したデータを返し、 それ以外の場合は 0 を返す。 エラーの場合は -1 を返し、 I<errno> が適切に設定される。 B<PTRACE_PEEK*> が成功して返す値も　-1 になることがあるため、 そのような要求の場合には、呼び出し元は I<errno> を調べ、エラーか発生したのかどうかを判断しなければならない。"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1915
-msgid ""
-"(i386 only) There was an error with allocating or freeing a debug register."
+msgid "(i386 only) There was an error with allocating or freeing a debug register."
 msgstr "(i386 のみ) デバッグレジスタの確保または解放でエラーが発生した。"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1926
 #, fuzzy
-#| msgid ""
-#| "There was an attempt to read from or write to an invalid area in the "
-#| "parent's or child's memory, probably because the area wasn't mapped or "
-#| "accessible.  Unfortunately, under Linux, different variations of this "
-#| "fault will return B<EIO> or B<EFAULT> more or less arbitrarily."
-msgid ""
-"There was an attempt to read from or write to an invalid area in the "
-"tracer's or the tracee's memory, probably because the area wasn't mapped or "
-"accessible.  Unfortunately, under Linux, different variations of this fault "
-"will return B<EIO> or B<EFAULT> more or less arbitrarily."
-msgstr ""
-"親プロセスまたは子プロセスのメモリの不正な領域に読み書きしようとした。 おそら"
-"くその領域がマッピングされていないか、 その領域へのアクセスが許されていないか"
-"である。 不運なことに、Linux ではこのようなエラーの場合、多かれ少なかれ 恣意"
-"的に B<EIO> を返したり B<EFAULT> を返したりすることがある。"
+#| msgid "There was an attempt to read from or write to an invalid area in the parent's or child's memory, probably because the area wasn't mapped or accessible.  Unfortunately, under Linux, different variations of this fault will return B<EIO> or B<EFAULT> more or less arbitrarily."
+msgid "There was an attempt to read from or write to an invalid area in the tracer's or the tracee's memory, probably because the area wasn't mapped or accessible.  Unfortunately, under Linux, different variations of this fault will return B<EIO> or B<EFAULT> more or less arbitrarily."
+msgstr "親プロセスまたは子プロセスのメモリの不正な領域に読み書きしようとした。 おそらくその領域がマッピングされていないか、 その領域へのアクセスが許されていないかである。 不運なことに、Linux ではこのようなエラーの場合、多かれ少なかれ 恣意的に B<EIO> を返したり B<EFAULT> を返したりすることがある。"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1929
@@ -11015,59 +8676,23 @@ msgstr "不正なオプションを設定しようとした。"
 #. type: Plain text
 #: build/C/man2/ptrace.2:1936
 #, fuzzy
-#| msgid ""
-#| "I<request> is invalid, or an attempt was made to read from or write to an "
-#| "invalid area in the parent's or child's memory, or there was a word-"
-#| "alignment violation, or an invalid signal was specified during a restart "
-#| "request."
-msgid ""
-"I<request> is invalid, or an attempt was made to read from or write to an "
-"invalid area in the tracer's or the tracee's memory, or there was a word-"
-"alignment violation, or an invalid signal was specified during a restart "
-"request."
-msgstr ""
-"I<request> が不正である。 または、親プロセスまたは子プロセスのメモリの 不正な"
-"領域に読み書きしようとした。 または、ワード境界違反があった。 または、実行再"
-"開の要求で不正なシグナルを指定した。"
+#| msgid "I<request> is invalid, or an attempt was made to read from or write to an invalid area in the parent's or child's memory, or there was a word-alignment violation, or an invalid signal was specified during a restart request."
+msgid "I<request> is invalid, or an attempt was made to read from or write to an invalid area in the tracer's or the tracee's memory, or there was a word-alignment violation, or an invalid signal was specified during a restart request."
+msgstr "I<request> が不正である。 または、親プロセスまたは子プロセスのメモリの 不正な領域に読み書きしようとした。 または、ワード境界違反があった。 または、実行再開の要求で不正なシグナルを指定した。"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1949
 #, fuzzy
-#| msgid ""
-#| "The specified process cannot be traced.  This could be because the parent "
-#| "has insufficient privileges (the required capability is "
-#| "B<CAP_SYS_PTRACE>); unprivileged processes cannot trace processes that "
-#| "they cannot send signals to or those running set-user-ID/set-group-ID "
-#| "programs, for obvious reasons.  Alternatively, the process may already be "
-#| "being traced, or be B<init>(8)  (PID 1)."
-msgid ""
-"The specified process cannot be traced.  This could be because the tracer "
-"has insufficient privileges (the required capability is B<CAP_SYS_PTRACE>); "
-"unprivileged processes cannot trace processes that they cannot send signals "
-"to or those running set-user-ID/set-group-ID programs, for obvious reasons.  "
-"Alternatively, the process may already be being traced, or (on kernels "
-"before 2.6.26) be B<init>(1)  (PID 1)."
-msgstr ""
-"指定したプロセスをトレースすることができない。これは親プロセスが 必要な権限 "
-"(必要なケーパビリティは B<CAP_SYS_PTRACE>)  を持っていないことが原因の場合が"
-"ある。 分かりやすい理由を挙げるなら、 非特権プロセスはシグナルを送ることがで"
-"きないプロセスをトレースできないし、 set-user-ID/set-group-ID プログラムを実"
-"行しているプロセスはトレースできない。 または、プロセスはすでにトレース中であ"
-"る、 または B<init>(8)  プロセス (PID が 1) である。"
+#| msgid "The specified process cannot be traced.  This could be because the parent has insufficient privileges (the required capability is B<CAP_SYS_PTRACE>); unprivileged processes cannot trace processes that they cannot send signals to or those running set-user-ID/set-group-ID programs, for obvious reasons.  Alternatively, the process may already be being traced, or be B<init>(8)  (PID 1)."
+msgid "The specified process cannot be traced.  This could be because the tracer has insufficient privileges (the required capability is B<CAP_SYS_PTRACE>); unprivileged processes cannot trace processes that they cannot send signals to or those running set-user-ID/set-group-ID programs, for obvious reasons.  Alternatively, the process may already be being traced, or (on kernels before 2.6.26) be B<init>(1)  (PID 1)."
+msgstr "指定したプロセスをトレースすることができない。これは親プロセスが 必要な権限 (必要なケーパビリティは B<CAP_SYS_PTRACE>)  を持っていないことが原因の場合がある。 分かりやすい理由を挙げるなら、 非特権プロセスはシグナルを送ることができないプロセスをトレースできないし、 set-user-ID/set-group-ID プログラムを実行しているプロセスはトレースできない。 または、プロセスはすでにトレース中である、 または B<init>(8)  プロセス (PID が 1) である。"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1954
 #, fuzzy
-#| msgid ""
-#| "The specified process does not exist, or is not currently being traced by "
-#| "the caller, or is not stopped (for requests that require that)."
-msgid ""
-"The specified process does not exist, or is not currently being traced by "
-"the caller, or is not stopped (for requests that require a stopped tracee)."
-msgstr ""
-"指定したプロセスが存在しない。 または、指定したプロセスは呼び出したプロセス"
-"が 現在トレース中の子プロセスではない。 または、指定したプロセスが停止してい"
-"ない (停止していることが必要な要求の場合)。"
+#| msgid "The specified process does not exist, or is not currently being traced by the caller, or is not stopped (for requests that require that)."
+msgid "The specified process does not exist, or is not currently being traced by the caller, or is not stopped (for requests that require a stopped tracee)."
+msgstr "指定したプロセスが存在しない。 または、指定したプロセスは呼び出したプロセスが 現在トレース中の子プロセスではない。 または、指定したプロセスが停止していない (停止していることが必要な要求の場合)。"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1956
@@ -11077,67 +8702,31 @@ msgstr "SVr4, 4.3BSD."
 #. type: Plain text
 #: build/C/man2/ptrace.2:1971
 #, fuzzy
-#| msgid ""
-#| "Although arguments to B<ptrace>()  are interpreted according to the "
-#| "prototype given, glibc currently declares B<ptrace>()  as a variadic "
-#| "function with only the I<request> argument fixed.  This means that "
-#| "unneeded trailing arguments may be omitted, though doing so makes use of "
-#| "undocumented B<gcc>(1)  behavior."
-msgid ""
-"Although arguments to B<ptrace>()  are interpreted according to the "
-"prototype given, glibc currently declares B<ptrace>()  as a variadic "
-"function with only the I<request> argument fixed.  It is recommended to "
-"always supply four arguments, even if the requested operation does not use "
-"them, setting unused/ignored arguments to I<0L> or I<(void\\ *)\\ 0>."
-msgstr ""
-"B<ptrace>()  の引き数は上のようなプロトタイプに基づいて解釈されるが、 glibc "
-"では、現在のところ B<ptrace>()  は I<request> 引き数だけが固定の可変長引き数"
-"関数として 宣言されている。 これは必要なければ残りの引き数は省略可能であるこ"
-"とを意味するが、 それは B<gcc>(1)  の明文化されていない動作を利用していること"
-"になる。"
+#| msgid "Although arguments to B<ptrace>()  are interpreted according to the prototype given, glibc currently declares B<ptrace>()  as a variadic function with only the I<request> argument fixed.  This means that unneeded trailing arguments may be omitted, though doing so makes use of undocumented B<gcc>(1)  behavior."
+msgid "Although arguments to B<ptrace>()  are interpreted according to the prototype given, glibc currently declares B<ptrace>()  as a variadic function with only the I<request> argument fixed.  It is recommended to always supply four arguments, even if the requested operation does not use them, setting unused/ignored arguments to I<0L> or I<(void\\ *)\\ 0>."
+msgstr "B<ptrace>()  の引き数は上のようなプロトタイプに基づいて解釈されるが、 glibc では、現在のところ B<ptrace>()  は I<request> 引き数だけが固定の可変長引き数関数として 宣言されている。 これは必要なければ残りの引き数は省略可能であることを意味するが、 それは B<gcc>(1)  の明文化されていない動作を利用していることになる。"
 
 #.  See commit 00cd5c37afd5f431ac186dd131705048c0a11fdb
 #. type: Plain text
 #: build/C/man2/ptrace.2:1976
-msgid ""
-"In Linux kernels before 2.6.26, B<init>(1), the process with PID 1, may not "
-"be traced."
-msgstr ""
-"バージョン 2.6.26 より前の Linux カーネルでは、 B<init>(1) すなわち PID が 1 "
-"のプロセスはトレースすることができない。"
+msgid "In Linux kernels before 2.6.26, B<init>(1), the process with PID 1, may not be traced."
+msgstr "バージョン 2.6.26 より前の Linux カーネルでは、 B<init>(1) すなわち PID が 1 のプロセスはトレースすることができない。"
 
 #.  See http://lkml.org/lkml/2008/5/8/375
 #. type: Plain text
 #: build/C/man2/ptrace.2:1983
-msgid ""
-"The layout of the contents of memory and the USER area are quite operating-"
-"system- and architecture-specific.  The offset supplied, and the data "
-"returned, might not entirely match with the definition of I<struct user>."
-msgstr ""
-"メモリや USER 領域の内容や配置はオペレーティングシステムごと、アーキテクチャ"
-"ごとに 非常に依存する。 オフセットが指定された場合、返されるデータは "
-"I<struct user> の定義と完全に一致しないこともありえる。"
+msgid "The layout of the contents of memory and the USER area are quite operating-system- and architecture-specific.  The offset supplied, and the data returned, might not entirely match with the definition of I<struct user>."
+msgstr "メモリや USER 領域の内容や配置はオペレーティングシステムごと、アーキテクチャごとに 非常に依存する。 オフセットが指定された場合、返されるデータは I<struct user> の定義と完全に一致しないこともありえる。"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1986
-msgid ""
-"The size of a \"word\" is determined by the operating-system variant (e.g., "
-"for 32-bit Linux it is 32 bits)."
-msgstr ""
-"「ワード (word) 」の大きさはオペレーティングシステムによって決まる。 (例え"
-"ば、32 ビットの Linux では 32 ビットである、など。)"
+msgid "The size of a \"word\" is determined by the operating-system variant (e.g., for 32-bit Linux it is 32 bits)."
+msgstr "「ワード (word) 」の大きさはオペレーティングシステムによって決まる。 (例えば、32 ビットの Linux では 32 ビットである、など。)"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:1994
-msgid ""
-"This page documents the way the B<ptrace>()  call works currently in Linux.  "
-"Its behavior differs significantly on other flavors of UNIX.  In any case, "
-"use of B<ptrace>()  is highly specific to the operating system and "
-"architecture."
-msgstr ""
-"このマニュアルは現在の Linux における B<ptrace>()  コールの動作について記述し"
-"ている。他の UNIX では その動作は著しく異なる。 いかなる場合も B<ptrace>()  "
-"を使うとオペレーションシステムやアーキテクチャに非常に依存したものになる。"
+msgid "This page documents the way the B<ptrace>()  call works currently in Linux.  Its behavior differs significantly on other flavors of UNIX.  In any case, use of B<ptrace>()  is highly specific to the operating system and architecture."
+msgstr "このマニュアルは現在の Linux における B<ptrace>()  コールの動作について記述している。他の UNIX では その動作は著しく異なる。 いかなる場合も B<ptrace>()  を使うとオペレーションシステムやアーキテクチャに非常に依存したものになる。"
 
 #. type: SS
 #: build/C/man2/ptrace.2:1994
@@ -11147,35 +8736,17 @@ msgstr "C ライブラリとカーネル ABI の違い"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:2006
-msgid ""
-"At the system call level, the B<PTRACE_PEEKTEXT>, B<PTRACE_PEEKDATA>, and "
-"B<PTRACE_PEEKUSER> requests have a different API: they store the result at "
-"the address specified by the I<data> parameter, and the return value is the "
-"error flag.  The glibc wrapper function provides the API given in "
-"DESCRIPTION above, with the result being returned via the function return "
-"value."
+msgid "At the system call level, the B<PTRACE_PEEKTEXT>, B<PTRACE_PEEKDATA>, and B<PTRACE_PEEKUSER> requests have a different API: they store the result at the address specified by the I<data> parameter, and the return value is the error flag.  The glibc wrapper function provides the API given in DESCRIPTION above, with the result being returned via the function return value."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:2017
-msgid ""
-"On hosts with 2.6 kernel headers, B<PTRACE_SETOPTIONS> is declared with a "
-"different value than the one for 2.4.  This leads to applications compiled "
-"with 2.6 kernel headers failing when run on 2.4 kernels.  This can be worked "
-"around by redefining B<PTRACE_SETOPTIONS> to B<PTRACE_OLDSETOPTIONS>, if "
-"that is defined."
-msgstr ""
-"カーネル 2.6 のヘッダがインストールされたホストでは、 B<PTRACE_SETOPTIONS> は"
-"カーネル 2.4 のヘッダとは異なる値で宣言される。 このため、カーネル 2.6 のヘッ"
-"ダでコンパイルされたアプリケーションは カーネル 2.4 では正しく動作しない。 こ"
-"の問題は、 B<PTRACE_SETOPTIONS> が定義されていた際は、 B<PTRACE_SETOPTIONS> "
-"を B<PTRACE_OLDSETOPTIONS> に定義し直すことで対処できる。"
+msgid "On hosts with 2.6 kernel headers, B<PTRACE_SETOPTIONS> is declared with a different value than the one for 2.4.  This leads to applications compiled with 2.6 kernel headers failing when run on 2.4 kernels.  This can be worked around by redefining B<PTRACE_SETOPTIONS> to B<PTRACE_OLDSETOPTIONS>, if that is defined."
+msgstr "カーネル 2.6 のヘッダがインストールされたホストでは、 B<PTRACE_SETOPTIONS> はカーネル 2.4 のヘッダとは異なる値で宣言される。 このため、カーネル 2.6 のヘッダでコンパイルされたアプリケーションは カーネル 2.4 では正しく動作しない。 この問題は、 B<PTRACE_SETOPTIONS> が定義されていた際は、 B<PTRACE_SETOPTIONS> を B<PTRACE_OLDSETOPTIONS> に定義し直すことで対処できる。"
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:2020
-msgid ""
-"Group-stop notifications are sent to the tracer, but not to real parent.  "
-"Last confirmed on 2.6.38.6."
+msgid "Group-stop notifications are sent to the tracer, but not to real parent.  Last confirmed on 2.6.38.6."
 msgstr ""
 
 #.  Note from Denys Vlasenko:
@@ -11190,37 +8761,17 @@ msgstr ""
 #.   FIXME . need to test/verify this scenario
 #. type: Plain text
 #: build/C/man2/ptrace.2:2051
-msgid ""
-"If a thread group leader is traced and exits by calling B<_exit>(2), a "
-"B<PTRACE_EVENT_EXIT> stop will happen for it (if requested), but the "
-"subsequent B<WIFEXITED> notification will not be delivered until all other "
-"threads exit.  As explained above, if one of other threads calls "
-"B<execve>(2), the death of the thread group leader will I<never> be "
-"reported.  If the execed thread is not traced by this tracer, the tracer "
-"will never know that B<execve>(2)  happened.  One possible workaround is to "
-"B<PTRACE_DETACH> the thread group leader instead of restarting it in this "
-"case.  Last confirmed on 2.6.38.6."
+msgid "If a thread group leader is traced and exits by calling B<_exit>(2), a B<PTRACE_EVENT_EXIT> stop will happen for it (if requested), but the subsequent B<WIFEXITED> notification will not be delivered until all other threads exit.  As explained above, if one of other threads calls B<execve>(2), the death of the thread group leader will I<never> be reported.  If the execed thread is not traced by this tracer, the tracer will never know that B<execve>(2)  happened.  One possible workaround is to B<PTRACE_DETACH> the thread group leader instead of restarting it in this case.  Last confirmed on 2.6.38.6."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:2061
-msgid ""
-"A B<SIGKILL> signal may still cause a B<PTRACE_EVENT_EXIT> stop before "
-"actual signal death.  This may be changed in the future; B<SIGKILL> is meant "
-"to always immediately kill tasks even under ptrace.  Last confirmed on "
-"2.6.38.6."
+msgid "A B<SIGKILL> signal may still cause a B<PTRACE_EVENT_EXIT> stop before actual signal death.  This may be changed in the future; B<SIGKILL> is meant to always immediately kill tasks even under ptrace.  Last confirmed on 2.6.38.6."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:2079
-msgid ""
-"Some system calls return with B<EINTR> if a signal was sent to a tracee, but "
-"delivery was suppressed by the tracer.  (This is very typical operation: it "
-"is usually done by debuggers on every attach, in order to not introduce a "
-"bogus B<SIGSTOP>).  As of Linux 3.2.9, the following system calls are "
-"affected (this list is likely incomplete): B<epoll_wait>(2), and B<read>(2)  "
-"from an B<inotify>(7)  file descriptor.  The usual symptom of this bug is "
-"that when you attach to a quiescent process with the command"
+msgid "Some system calls return with B<EINTR> if a signal was sent to a tracee, but delivery was suppressed by the tracer.  (This is very typical operation: it is usually done by debuggers on every attach, in order to not introduce a bogus B<SIGSTOP>).  As of Linux 3.2.9, the following system calls are affected (this list is likely incomplete): B<epoll_wait>(2), and B<read>(2)  from an B<inotify>(7)  file descriptor.  The usual symptom of this bug is that when you attach to a quiescent process with the command"
 msgstr ""
 
 #. type: Plain text
@@ -11248,9 +8799,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:2097
-msgid ""
-"('_' denotes the cursor position), you observe more than one line.  For "
-"example:"
+msgid "('_' denotes the cursor position), you observe more than one line.  For example:"
 msgstr ""
 
 #. type: Plain text
@@ -11263,31 +8812,13 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:2122
-msgid ""
-"What is not visible here is that the process was blocked in "
-"B<epoll_wait>(2)  before B<strace>(1)  has attached to it.  Attaching caused "
-"B<epoll_wait>(2)  to return to user space with the error B<EINTR>.  In this "
-"particular case, the program reacted to B<EINTR> by checking the current "
-"time, and then executing B<epoll_wait>(2)  again.  (Programs which do not "
-"expect such \"stray\" B<EINTR> errors may behave in an unintended way upon "
-"an B<strace>(1)  attach.)"
+msgid "What is not visible here is that the process was blocked in B<epoll_wait>(2)  before B<strace>(1)  has attached to it.  Attaching caused B<epoll_wait>(2)  to return to user space with the error B<EINTR>.  In this particular case, the program reacted to B<EINTR> by checking the current time, and then executing B<epoll_wait>(2)  again.  (Programs which do not expect such \"stray\" B<EINTR> errors may behave in an unintended way upon an B<strace>(1)  attach.)"
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/ptrace.2:2137
-#, fuzzy
-#| msgid ""
-#| "B<gdb>(1), B<strace>(1), B<clone>(2), B<execve>(2), B<fork>(2), "
-#| "B<gettid>(2), B<sigaction>(2), B<tgkill>(2), B<vfork>(2), B<waitpid>(2), "
-#| "B<exec>(3), B<capabilities>(7), B<signal>(7)"
-msgid ""
-"B<gdb>(1), B<strace>(1), B<clone>(2), B<execve>(2), B<fork>(2), "
-"B<gettid>(2), B<seccomp>(2), B<sigaction>(2), B<tgkill>(2), B<vfork>(2), "
-"B<waitpid>(2), B<exec>(3), B<capabilities>(7), B<signal>(7)"
-msgstr ""
-"B<gdb>(1), B<strace>(1), B<clone>(2), B<execve>(2), B<fork>(2),\n"
-"B<gettid>(2), B<sigaction>(2), B<tgkill>(2), B<vfork>(2),\n"
-"B<waitpid>(2), B<exec>(3), B<capabilities>(7), B<signal>(7)"
+msgid "B<gdb>(1), B<strace>(1), B<clone>(2), B<execve>(2), B<fork>(2), B<gettid>(2), B<seccomp>(2), B<sigaction>(2), B<tgkill>(2), B<vfork>(2), B<waitpid>(2), B<exec>(3), B<capabilities>(7), B<signal>(7)"
+msgstr "B<gdb>(1), B<strace>(1), B<clone>(2), B<execve>(2), B<fork>(2), B<gettid>(2), B<seccomp>(2), B<sigaction>(2), B<tgkill>(2), B<vfork>(2), B<waitpid>(2), B<exec>(3), B<capabilities>(7), B<signal>(7)"
 
 #. type: TH
 #: build/C/man2/quotactl.2:27
@@ -11325,63 +8856,25 @@ msgstr "B<int quotactl(int >I<cmd>B<, const char *>I<special>B<, int >I<id>B<, c
 #. type: Plain text
 #: build/C/man2/quotactl.2:49
 #, fuzzy
-#| msgid ""
-#| "The quota system defines for each user and/or group a soft limit and a "
-#| "hard limit bounding the amount of disk space that can be used on a given "
-#| "file system.  The hard limit cannot be crossed.  The soft limit can be "
-#| "crossed, but warnings will ensue.  Moreover, the user cannot be above the "
-#| "soft limit for more than one week (by default)  at a time: after this "
-#| "week the soft limit counts as hard limit."
-msgid ""
-"The quota system can be used to set per-user and per-group limits on the "
-"amount of disk space used on a filesystem.  For each user and/or group, a "
-"soft limit and a hard limit can be set for each filesystem.  The hard limit "
-"can't be exceeded.  The soft limit can be exceeded, but warnings will "
-"ensue.  Moreover, the user can't exceed the soft limit for more than one "
-"week (by default) at a time; after this time, the soft limit counts as a "
-"hard limit."
-msgstr ""
-"quota システムは、各々のユーザ及び/またはグループに対して、 ソフト・リミット"
-"及びハード・リミットを定める。これはあるファイル・システムで 使用する事が出来"
-"るディスク容量を制限する。 ハード・リミットは超過することは出来ない。 ソフ"
-"ト・リミットは超過する事が出来るが、警告が発せられる。 更に、(デフォルトで"
-"は) 一週間以上ソフト・リミットを超過したままに しておく事はできない: 一週間経"
-"過した後はハード・リミットを超過したと みなされる。"
+#| msgid "The quota system defines for each user and/or group a soft limit and a hard limit bounding the amount of disk space that can be used on a given file system.  The hard limit cannot be crossed.  The soft limit can be crossed, but warnings will ensue.  Moreover, the user cannot be above the soft limit for more than one week (by default)  at a time: after this week the soft limit counts as hard limit."
+msgid "The quota system can be used to set per-user and per-group limits on the amount of disk space used on a filesystem.  For each user and/or group, a soft limit and a hard limit can be set for each filesystem.  The hard limit can't be exceeded.  The soft limit can be exceeded, but warnings will ensue.  Moreover, the user can't exceed the soft limit for more than one week (by default) at a time; after this time, the soft limit counts as a hard limit."
+msgstr "quota システムは、各々のユーザ及び/またはグループに対して、 ソフト・リミット及びハード・リミットを定める。これはあるファイル・システムで 使用する事が出来るディスク容量を制限する。 ハード・リミットは超過することは出来ない。 ソフト・リミットは超過する事が出来るが、警告が発せられる。 更に、(デフォルトでは) 一週間以上ソフト・リミットを超過したままに しておく事はできない: 一週間経過した後はハード・リミットを超過したと みなされる。"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:74
 #, fuzzy
-#| msgid ""
-#| "The B<quotactl>()  system call manipulates these quota.  Its first "
-#| "argument is of the form B<QCMD(>I<subcmd>B<,>I<type>B<)> where I<type> is "
-#| "either B<USRQUOTA> or B<GRPQUOTA> (for user quota and group quota, "
-#| "respectively), and I<subcmd> is described below."
-msgid ""
-"The B<quotactl>()  call manipulates disk quotas.  The I<cmd> argument "
-"indicates a command to be applied to the user or group ID specified in "
-"I<id>.  To initialize the I<cmd> argument, use the I<QCMD(subcmd, type)> "
-"macro.  The I<type> value is either B<USRQUOTA>, for user quotas, or "
-"B<GRPQUOTA>, for group quotas.  The I<subcmd> value is described below."
-msgstr ""
-"B<quotactl>()  システムコールはこれらの quota に対する操作を行なう。 最初の引"
-"き数は B<QCMD(>I<subcmd>B<,>I<type>B<)> という形式である。 I<type> には、ユー"
-"ザー quota については B<USRQUOTA> を、グループ quota については B<GRPQUOTA> "
-"を指定する。 I<subcmd> は以下で説明する。"
+#| msgid "The B<quotactl>()  system call manipulates these quota.  Its first argument is of the form B<QCMD(>I<subcmd>B<,>I<type>B<)> where I<type> is either B<USRQUOTA> or B<GRPQUOTA> (for user quota and group quota, respectively), and I<subcmd> is described below."
+msgid "The B<quotactl>()  call manipulates disk quotas.  The I<cmd> argument indicates a command to be applied to the user or group ID specified in I<id>.  To initialize the I<cmd> argument, use the I<QCMD(subcmd, type)> macro.  The I<type> value is either B<USRQUOTA>, for user quotas, or B<GRPQUOTA>, for group quotas.  The I<subcmd> value is described below."
+msgstr "B<quotactl>()  システムコールはこれらの quota に対する操作を行なう。 最初の引き数は B<QCMD(>I<subcmd>B<,>I<type>B<)> という形式である。 I<type> には、ユーザー quota については B<USRQUOTA> を、グループ quota については B<GRPQUOTA> を指定する。 I<subcmd> は以下で説明する。"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:79
-msgid ""
-"The I<special> argument is a pointer to a null-terminated string containing "
-"the pathname of the (mounted) block special device for the filesystem being "
-"manipulated."
+msgid "The I<special> argument is a pointer to a null-terminated string containing the pathname of the (mounted) block special device for the filesystem being manipulated."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:87
-msgid ""
-"The I<addr> argument is the address of an optional, command-specific, data "
-"structure that is copied in or out of the system.  The interpretation of "
-"I<addr> is given with each command below."
+msgid "The I<addr> argument is the address of an optional, command-specific, data structure that is copied in or out of the system.  The interpretation of I<addr> is given with each command below."
 msgstr ""
 
 #. type: Plain text
@@ -11397,10 +8890,7 @@ msgstr "B<Q_QUOTAON>"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:98
-msgid ""
-"Turn on quotas for a filesystem.  The I<id> argument is the identification "
-"number of the quota format to be used.  Currently, there are three supported "
-"quota formats:"
+msgid "Turn on quotas for a filesystem.  The I<id> argument is the identification number of the quota format to be used.  Currently, there are three supported quota formats:"
 msgstr ""
 
 #. type: TP
@@ -11422,9 +8912,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:106
-msgid ""
-"The standard VFS v0 quota format, which can handle 32-bit UIDs and GIDs and "
-"quota limits up to 2^42 bytes and 2^32 inodes."
+msgid "The standard VFS v0 quota format, which can handle 32-bit UIDs and GIDs and quota limits up to 2^42 bytes and 2^32 inodes."
 msgstr ""
 
 #. type: TP
@@ -11435,18 +8923,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:110
-msgid ""
-"A quota format that can handle 32-bit UIDs and GIDs and quota limits of 2^64 "
-"bytes and 2^64 inodes."
+msgid "A quota format that can handle 32-bit UIDs and GIDs and quota limits of 2^64 bytes and 2^64 inodes."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:121
-msgid ""
-"The I<addr> argument points to the pathname of a file containing the quotas "
-"for the filesystem.  The quota file must exist; it is normally created with "
-"the B<quotacheck>(8)  program.  This operation requires privilege "
-"(B<CAP_SYS_ADMIN>)."
+msgid "The I<addr> argument points to the pathname of a file containing the quotas for the filesystem.  The quota file must exist; it is normally created with the B<quotacheck>(8)  program.  This operation requires privilege (B<CAP_SYS_ADMIN>)."
 msgstr ""
 
 #. type: TP
@@ -11457,9 +8939,7 @@ msgstr "B<Q_QUOTAOFF>"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:131
-msgid ""
-"Turn off quotas for a filesystem.  The I<addr> and I<id> arguments are "
-"ignored.  This operation requires privilege (B<CAP_SYS_ADMIN>)."
+msgid "Turn off quotas for a filesystem.  The I<addr> and I<id> arguments are ignored.  This operation requires privilege (B<CAP_SYS_ADMIN>)."
 msgstr ""
 
 #. type: TP
@@ -11471,16 +8951,9 @@ msgstr "B<Q_GETQUOTA>"
 #. type: Plain text
 #: build/C/man2/quotactl.2:142
 #, fuzzy
-#| msgid ""
-#| "Get limits and current usage of disk space.  The I<addr> argument is a "
-#| "pointer to a dqblk structure (defined in I<E<lt>sys/quota.hE<gt>>)."
-msgid ""
-"Get disk quota limits and current usage for user or group I<id>.  The "
-"I<addr> argument is a pointer to a I<dqblk> structure defined in I<E<lt>sys/"
-"quota.hE<gt>> as follows:"
-msgstr ""
-"ディスク使用量の制限値と現在の使用量を得る。 I<addr> 引き数は (I<E<lt>sys/"
-"quota.hE<gt>> で定義された) dqblk 構造体を指すポインタである。"
+#| msgid "Get limits and current usage of disk space.  The I<addr> argument is a pointer to a dqblk structure (defined in I<E<lt>sys/quota.hE<gt>>)."
+msgid "Get disk quota limits and current usage for user or group I<id>.  The I<addr> argument is a pointer to a I<dqblk> structure defined in I<E<lt>sys/quota.hE<gt>> as follows:"
+msgstr "ディスク使用量の制限値と現在の使用量を得る。 I<addr> 引き数は (I<E<lt>sys/quota.hE<gt>> で定義された) dqblk 構造体を指すポインタである。"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:147 build/C/man2/quotactl.2:234
@@ -11541,12 +9014,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:198
-msgid ""
-"The I<dqb_valid> field is a bit mask that is set to indicate the entries in "
-"the I<dqblk> structure that are valid.  Currently, the kernel fills in all "
-"entries of the I<dqblk> structure and marks them as valid in the "
-"I<dqb_valid> field.  Unprivileged users may retrieve only their own quotas; "
-"a privileged user (B<CAP_SYS_ADMIN>)  can retrieve the quotas of any user."
+msgid "The I<dqb_valid> field is a bit mask that is set to indicate the entries in the I<dqblk> structure that are valid.  Currently, the kernel fills in all entries of the I<dqblk> structure and marks them as valid in the I<dqb_valid> field.  Unprivileged users may retrieve only their own quotas; a privileged user (B<CAP_SYS_ADMIN>)  can retrieve the quotas of any user."
 msgstr ""
 
 #. type: TP
@@ -11557,13 +9025,7 @@ msgstr "B<Q_SETQUOTA>"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:218
-msgid ""
-"Set quota information for user or group I<id>, using the information "
-"supplied in the I<dqblk> structure pointed to by I<addr>.  The I<dqb_valid> "
-"field of the I<dqblk> structure indicates which entries in the structure "
-"have been set by the caller.  This operation supersedes the B<Q_SETQLIM> and "
-"B<Q_SETUSE> operations in the previous quota interfaces.  This operation "
-"requires privilege (B<CAP_SYS_ADMIN>)."
+msgid "Set quota information for user or group I<id>, using the information supplied in the I<dqblk> structure pointed to by I<addr>.  The I<dqb_valid> field of the I<dqblk> structure indicates which entries in the structure have been set by the caller.  This operation supersedes the B<Q_SETQLIM> and B<Q_SETUSE> operations in the previous quota interfaces.  This operation requires privilege (B<CAP_SYS_ADMIN>)."
 msgstr ""
 
 #. type: TP
@@ -11575,16 +9037,9 @@ msgstr "B<Q_GETINFO>"
 #. type: Plain text
 #: build/C/man2/quotactl.2:229
 #, fuzzy
-#| msgid ""
-#| "Get limits and current usage of disk space.  The I<addr> argument is a "
-#| "pointer to a dqblk structure (defined in I<E<lt>sys/quota.hE<gt>>)."
-msgid ""
-"Get information (like grace times) about quotafile.  The I<addr> argument "
-"should be a pointer to a I<dqinfo> structure.  This structure is defined in "
-"I<E<lt>sys/quota.hE<gt>> as follows:"
-msgstr ""
-"ディスク使用量の制限値と現在の使用量を得る。 I<addr> 引き数は (I<E<lt>sys/"
-"quota.hE<gt>> で定義された) dqblk 構造体を指すポインタである。"
+#| msgid "Get limits and current usage of disk space.  The I<addr> argument is a pointer to a dqblk structure (defined in I<E<lt>sys/quota.hE<gt>>)."
+msgid "Get information (like grace times) about quotafile.  The I<addr> argument should be a pointer to a I<dqinfo> structure.  This structure is defined in I<E<lt>sys/quota.hE<gt>> as follows:"
+msgstr "ディスク使用量の制限値と現在の使用量を得る。 I<addr> 引き数は (I<E<lt>sys/quota.hE<gt>> で定義された) dqblk 構造体を指すポインタである。"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:238
@@ -11666,11 +9121,7 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:277
-msgid ""
-"The I<dqi_valid> field in the I<dqinfo> structure indicates the entries in "
-"the structure that are valid.  Currently, the kernel fills in all entries of "
-"the I<dqinfo> structure and marks them all as valid in the I<dqi_valid> "
-"field.  The I<id> argument is ignored."
+msgid "The I<dqi_valid> field in the I<dqinfo> structure indicates the entries in the structure that are valid.  Currently, the kernel fills in all entries of the I<dqinfo> structure and marks them all as valid in the I<dqi_valid> field.  The I<id> argument is ignored."
 msgstr ""
 
 #. type: TP
@@ -11681,13 +9132,7 @@ msgstr "B<Q_SETINFO>"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:301
-msgid ""
-"Set information about quotafile.  The I<addr> argument should be a pointer "
-"to a I<dqinfo> structure.  The I<dqi_valid> field of the I<dqinfo> structure "
-"indicates the entries in the structure that have been set by the caller.  "
-"This operation supersedes the B<Q_SETGRACE> and B<Q_SETFLAGS> operations in "
-"the previous quota interfaces.  The I<id> argument is ignored.  This "
-"operation requires privilege (B<CAP_SYS_ADMIN>)."
+msgid "Set information about quotafile.  The I<addr> argument should be a pointer to a I<dqinfo> structure.  The I<dqi_valid> field of the I<dqinfo> structure indicates the entries in the structure that have been set by the caller.  This operation supersedes the B<Q_SETGRACE> and B<Q_SETFLAGS> operations in the previous quota interfaces.  The I<id> argument is ignored.  This operation requires privilege (B<CAP_SYS_ADMIN>)."
 msgstr ""
 
 #. type: TP
@@ -11698,10 +9143,7 @@ msgstr "B<Q_GETFMT>"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:308
-msgid ""
-"Get quota format used on the specified filesystem.  The I<addr> argument "
-"should be a pointer to a 4-byte buffer where the format number will be "
-"stored."
+msgid "Get quota format used on the specified filesystem.  The I<addr> argument should be a pointer to a 4-byte buffer where the format number will be stored."
 msgstr ""
 
 #. type: TP
@@ -11712,10 +9154,7 @@ msgstr "B<Q_SYNC>"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:319
-msgid ""
-"Update the on-disk copy of quota usages for a filesystem.  If I<special> is "
-"NULL, then all filesystems with active quotas are sync'ed.  The I<addr> and "
-"I<id> arguments are ignored."
+msgid "Update the on-disk copy of quota usages for a filesystem.  If I<special> is NULL, then all filesystems with active quotas are sync'ed.  The I<addr> and I<id> arguments are ignored."
 msgstr ""
 
 #. type: TP
@@ -11727,20 +9166,12 @@ msgstr "B<Q_GETSTATS>"
 #.  Q_GETSTATS was removed in kernel 2.4.22.
 #. type: Plain text
 #: build/C/man2/quotactl.2:339
-msgid ""
-"Get statistics and other generic information about the quota subsystem.  The "
-"I<addr> argument should be a pointer to a I<dqstats> structure in which data "
-"should be stored.  This structure is defined in I<E<lt>sys/quota.hE<gt>>.  "
-"The I<special> and I<id> arguments are ignored.  This operation is obsolete "
-"and not supported by recent kernels.  Files in I</proc/sys/fs/quota/> carry "
-"the information instead."
+msgid "Get statistics and other generic information about the quota subsystem.  The I<addr> argument should be a pointer to a I<dqstats> structure in which data should be stored.  This structure is defined in I<E<lt>sys/quota.hE<gt>>.  The I<special> and I<id> arguments are ignored.  This operation is obsolete and not supported by recent kernels.  Files in I</proc/sys/fs/quota/> carry the information instead."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:342
-msgid ""
-"For XFS filesystems making use of the XFS Quota Manager (XQM), the above "
-"commands are bypassed and the following commands are used:"
+msgid "For XFS filesystems making use of the XFS Quota Manager (XQM), the above commands are bypassed and the following commands are used:"
 msgstr ""
 
 #. type: TP
@@ -11751,14 +9182,7 @@ msgstr "B<Q_XQUOTAON>"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:363
-msgid ""
-"Turn on quotas for an XFS filesystem.  XFS provides the ability to turn on/"
-"off quota limit enforcement with quota accounting.  Therefore, XFS expects "
-"I<addr> to be a pointer to an I<unsigned int> that contains either the flags "
-"B<XFS_QUOTA_UDQ_ACCT> and/or B<XFS_QUOTA_UDQ_ENFD> (for user quota), or "
-"B<XFS_QUOTA_GDQ_ACCT> and/or B<XFS_QUOTA_GDQ_ENFD> (for group quota), as "
-"defined in I<E<lt>xfs/xqm.hE<gt>>.  This operation requires privilege "
-"(B<CAP_SYS_ADMIN>)."
+msgid "Turn on quotas for an XFS filesystem.  XFS provides the ability to turn on/off quota limit enforcement with quota accounting.  Therefore, XFS expects I<addr> to be a pointer to an I<unsigned int> that contains either the flags B<XFS_QUOTA_UDQ_ACCT> and/or B<XFS_QUOTA_UDQ_ENFD> (for user quota), or B<XFS_QUOTA_GDQ_ACCT> and/or B<XFS_QUOTA_GDQ_ENFD> (for group quota), as defined in I<E<lt>xfs/xqm.hE<gt>>.  This operation requires privilege (B<CAP_SYS_ADMIN>)."
 msgstr ""
 
 #. type: TP
@@ -11769,11 +9193,7 @@ msgstr "B<Q_XQUOTAOFF>"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:374
-msgid ""
-"Turn off quotas for an XFS filesystem.  As with B<Q_QUOTAON>, XFS "
-"filesystems expect a pointer to an I<unsigned int> that specifies whether "
-"quota accounting and/or limit enforcement need to be turned off.  This "
-"operation requires privilege (B<CAP_SYS_ADMIN>)."
+msgid "Turn off quotas for an XFS filesystem.  As with B<Q_QUOTAON>, XFS filesystems expect a pointer to an I<unsigned int> that specifies whether quota accounting and/or limit enforcement need to be turned off.  This operation requires privilege (B<CAP_SYS_ADMIN>)."
 msgstr ""
 
 #. type: TP
@@ -11784,12 +9204,7 @@ msgstr "B<Q_XGETQUOTA>"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:388
-msgid ""
-"Get disk quota limits and current usage for user I<id>.  The I<addr> "
-"argument is a pointer to an I<fs_disk_quota> structure (defined in "
-"I<E<lt>xfs/xqm.hE<gt>>).  Unprivileged users may retrieve only their own "
-"quotas; a privileged user (B<CAP_SYS_ADMIN>)  may retrieve the quotas of any "
-"user."
+msgid "Get disk quota limits and current usage for user I<id>.  The I<addr> argument is a pointer to an I<fs_disk_quota> structure (defined in I<E<lt>xfs/xqm.hE<gt>>).  Unprivileged users may retrieve only their own quotas; a privileged user (B<CAP_SYS_ADMIN>)  may retrieve the quotas of any user."
 msgstr ""
 
 #. type: TP
@@ -11800,10 +9215,7 @@ msgstr "B<Q_XSETQLIM>"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:400
-msgid ""
-"Set disk quota limits for user I<id>.  The I<addr> argument is a pointer to "
-"an I<fs_disk_quota> structure (defined in I<E<lt>xfs/xqm.hE<gt>>).  This "
-"operation requires privilege (B<CAP_SYS_ADMIN>)."
+msgid "Set disk quota limits for user I<id>.  The I<addr> argument is a pointer to an I<fs_disk_quota> structure (defined in I<E<lt>xfs/xqm.hE<gt>>).  This operation requires privilege (B<CAP_SYS_ADMIN>)."
 msgstr ""
 
 #. type: TP
@@ -11814,11 +9226,7 @@ msgstr "B<Q_XGETQSTAT>"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:408
-msgid ""
-"Returns an I<fs_quota_stat> structure containing XFS filesystem-specific "
-"quota information.  This is useful for finding out how much space is used to "
-"store quota information, and also to get quotaon/off status of a given local "
-"XFS filesystem."
+msgid "Returns an I<fs_quota_stat> structure containing XFS filesystem-specific quota information.  This is useful for finding out how much space is used to store quota information, and also to get quotaon/off status of a given local XFS filesystem."
 msgstr ""
 
 #. type: TP
@@ -11829,24 +9237,17 @@ msgstr "B<Q_XQUOTARM>"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:412
-msgid ""
-"Free the disk space taken by disk quotas.  Quotas must have already been "
-"turned off."
+msgid "Free the disk space taken by disk quotas.  Quotas must have already been turned off."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:419
-msgid ""
-"There is no command equivalent to B<Q_SYNC> for XFS since B<sync>(1)  writes "
-"quota information to disk (in addition to the other filesystem metadata that "
-"it writes out)."
+msgid "There is no command equivalent to B<Q_SYNC> for XFS since B<sync>(1)  writes quota information to disk (in addition to the other filesystem metadata that it writes out)."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:427
-msgid ""
-"On success, B<quotactl>()  returns 0; on error -1 is returned, and I<errno> "
-"is set to indicate the error."
+msgid "On success, B<quotactl>()  returns 0; on error -1 is returned, and I<errno> is set to indicate the error."
 msgstr ""
 "成功すると、 B<quotactl>()  は 0 を返す。\n"
 "エラーの場合、-1 を返し、 I<errno> をエラーを示す値に設定する。"
@@ -11884,16 +9285,12 @@ msgstr "I<special> がブロックデバイスではない。"
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:461
-msgid ""
-"The caller lacked the required privilege (B<CAP_SYS_ADMIN>)  for the "
-"specified operation."
+msgid "The caller lacked the required privilege (B<CAP_SYS_ADMIN>)  for the specified operation."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:465
-msgid ""
-"No disk quota is found for the indicated user.  Quotas have not been turned "
-"on for this filesystem."
+msgid "No disk quota is found for the indicated user.  Quotas have not been turned on for this filesystem."
 msgstr ""
 
 #. type: Plain text
@@ -11913,16 +9310,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:495
-msgid ""
-"The quota file pointed to by I<addr> exists, but is not a regular file; or, "
-"the quota file pointed to by I<addr> exists, but is not on the filesystem "
-"pointed to by I<special>."
+msgid "The quota file pointed to by I<addr> exists, but is not a regular file; or, the quota file pointed to by I<addr> exists, but is not on the filesystem pointed to by I<special>."
 msgstr ""
 
 #. type: Plain text
 #: build/C/man2/quotactl.2:501
-msgid ""
-"B<Q_QUOTAON> attempted, but another B<Q_QUOTAON> had already been performed."
+msgid "B<Q_QUOTAON> attempted, but another B<Q_QUOTAON> had already been performed."
 msgstr ""
 
 #. type: Plain text
@@ -11981,63 +9374,28 @@ msgstr "B<#include E<lt>sys/sendfile.hE<gt>>"
 #.  .B #endif
 #. type: Plain text
 #: build/C/man2/sendfile.2:47
-msgid ""
-"B<ssize_t sendfile(int>I< out_fd>B<, int>I< in_fd>B<, off_t *>I<offset>B<, "
-"size_t>I< count>B<);>"
-msgstr ""
-"B<ssize_t sendfile(int>I< out_fd>B<, int>I< in_fd>B<, off_t *>I<offset>B<, "
-"size_t>I< count>B<);>"
+msgid "B<ssize_t sendfile(int>I< out_fd>B<, int>I< in_fd>B<, off_t *>I<offset>B<, size_t>I< count>B<);>"
+msgstr "B<ssize_t sendfile(int>I< out_fd>B<, int>I< in_fd>B<, off_t *>I<offset>B<, size_t>I< count>B<);>"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:57
-msgid ""
-"B<sendfile>()  copies data between one file descriptor and another.  Because "
-"this copying is done within the kernel, B<sendfile>()  is more efficient "
-"than the combination of B<read>(2)  and B<write>(2), which would require "
-"transferring data to and from user space."
-msgstr ""
-"B<sendfile>()  は、あるファイル・ディスクリプタから別の ファイル・ディスクリ"
-"プタへのデータのコピーを行う。 このコピーはカーネル内で行われるので、 "
-"B<sendfile>()  は、 B<read>(2)  と B<write>(2)  を組み合わせるよりも効率がよ"
-"い。 B<read>(2)  や B<write>(2)  ではユーザ空間との間でデータの転送が必要とな"
-"るからである。"
+msgid "B<sendfile>()  copies data between one file descriptor and another.  Because this copying is done within the kernel, B<sendfile>()  is more efficient than the combination of B<read>(2)  and B<write>(2), which would require transferring data to and from user space."
+msgstr "B<sendfile>()  は、あるファイル・ディスクリプタから別の ファイル・ディスクリプタへのデータのコピーを行う。 このコピーはカーネル内で行われるので、 B<sendfile>()  は、 B<read>(2)  と B<write>(2)  を組み合わせるよりも効率がよい。 B<read>(2)  や B<write>(2)  ではユーザ空間との間でデータの転送が必要となるからである。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:62
-msgid ""
-"I<in_fd> should be a file descriptor opened for reading and I<out_fd> should "
-"be a descriptor opened for writing."
-msgstr ""
-"I<in_fd> は読み込みのためにオープンされたファイル・ディスクリプタ、 "
-"I<out_fd> は書き込みのためにオープンされたディスクリプタでなければならない。"
+msgid "I<in_fd> should be a file descriptor opened for reading and I<out_fd> should be a descriptor opened for writing."
+msgstr "I<in_fd> は読み込みのためにオープンされたファイル・ディスクリプタ、 I<out_fd> は書き込みのためにオープンされたディスクリプタでなければならない。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:83
-msgid ""
-"If I<offset> is not NULL, then it points to a variable holding the file "
-"offset from which B<sendfile>()  will start reading data from I<in_fd>.  "
-"When B<sendfile>()  returns, this variable will be set to the offset of the "
-"byte following the last byte that was read.  If I<offset> is not NULL, then "
-"B<sendfile>()  does not modify the current file offset of I<in_fd>; "
-"otherwise the current file offset is adjusted to reflect the number of bytes "
-"read from I<in_fd>."
-msgstr ""
-"I<offset> が NULL でない場合、 I<offset> は B<sendfile>()  が I<in_fd> のどこ"
-"からデータを読み始めるかを示すファイル・オフセットを保持する変数への ポインタ"
-"である。 B<sendfile>()  は復帰する時、この変数に最後に読み込んだバイトの 次の"
-"バイトのオフセットを書き込む。 I<offset> が NULL でない場合、 B<sendfile>()  "
-"は I<in_fd> のファイル・オフセットの現在値を変更しない。 NULL の場合は、ファ"
-"イル・オフセットの現在値を I<in_fd> から読み込んだバイト数を反映した位置に調"
-"整する。"
+msgid "If I<offset> is not NULL, then it points to a variable holding the file offset from which B<sendfile>()  will start reading data from I<in_fd>.  When B<sendfile>()  returns, this variable will be set to the offset of the byte following the last byte that was read.  If I<offset> is not NULL, then B<sendfile>()  does not modify the current file offset of I<in_fd>; otherwise the current file offset is adjusted to reflect the number of bytes read from I<in_fd>."
+msgstr "I<offset> が NULL でない場合、 I<offset> は B<sendfile>()  が I<in_fd> のどこからデータを読み始めるかを示すファイル・オフセットを保持する変数への ポインタである。 B<sendfile>()  は復帰する時、この変数に最後に読み込んだバイトの 次のバイトのオフセットを書き込む。 I<offset> が NULL でない場合、 B<sendfile>()  は I<in_fd> のファイル・オフセットの現在値を変更しない。 NULL の場合は、ファイル・オフセットの現在値を I<in_fd> から読み込んだバイト数を反映した位置に調整する。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:90
-msgid ""
-"If I<offset> is NULL, then data will be read from I<in_fd> starting at the "
-"current file offset, and the file offset will be updated by the call."
-msgstr ""
-"I<offset> が NULL の場合、データは I<in_fd> の現在のファイル・オフセットから"
-"読み出され、 ファイル・オフセットはこの呼び出しで更新される。"
+msgid "If I<offset> is NULL, then data will be read from I<in_fd> starting at the current file offset, and the file offset will be updated by the call."
+msgstr "I<offset> が NULL の場合、データは I<in_fd> の現在のファイル・オフセットから読み出され、 ファイル・オフセットはこの呼び出しで更新される。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:93
@@ -12046,52 +9404,33 @@ msgstr "I<count> は、ファイル・ディスクリプタ間でコピーする
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:100
-msgid ""
-"The I<in_fd> argument must correspond to a file which supports B<mmap>(2)-"
-"like operations (i.e., it cannot be a socket)."
+msgid "The I<in_fd> argument must correspond to a file which supports B<mmap>(2)-like operations (i.e., it cannot be a socket)."
 msgstr ""
-"I<in_fd> 引き数は B<mmap>(2) 風の操作ができるファイルを指していなければなら"
-"な\n"
+"I<in_fd> 引き数は B<mmap>(2) 風の操作ができるファイルを指していなければならな\n"
 "い (ソケットを指定することはできない)。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:108
-msgid ""
-"In Linux kernels before 2.6.33, I<out_fd> must refer to a socket.  Since "
-"Linux 2.6.33 it can be any file.  If it is a regular file, then "
-"B<sendfile>()  changes the file offset appropriately."
+msgid "In Linux kernels before 2.6.33, I<out_fd> must refer to a socket.  Since Linux 2.6.33 it can be any file.  If it is a regular file, then B<sendfile>()  changes the file offset appropriately."
 msgstr ""
-"2.6.33 より前の Linux カーネルでは I<out_fd> はソケットを参照していなければ"
-"な\n"
+"2.6.33 より前の Linux カーネルでは I<out_fd> はソケットを参照していなければな\n"
 "らない。Linux 2.6.33 以降では、任意のファイルを参照することができる。\n"
 "通常のファイルの場合には B<sendfile>() はファイルオフセットを適切に変更する。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:115
-msgid ""
-"If the transfer was successful, the number of bytes written to I<out_fd> is "
-"returned.  On error, -1 is returned, and I<errno> is set appropriately."
-msgstr ""
-"転送に成功した場合、 I<out_fd> に書き込まれたバイト数を返す。エラーの場"
-"合、-1 を返し、 I<errno> に適切な値を設定する。"
+msgid "If the transfer was successful, the number of bytes written to I<out_fd> is returned.  On error, -1 is returned, and I<errno> is set appropriately."
+msgstr "転送に成功した場合、 I<out_fd> に書き込まれたバイト数を返す。エラーの場合、-1 を返し、 I<errno> に適切な値を設定する。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:121
-msgid ""
-"Nonblocking I/O has been selected using B<O_NONBLOCK> and the write would "
-"block."
-msgstr ""
-"B<O_NONBLOCK> を用いて非ブロック I/O が選択されたが、書き込みがブロックされ"
-"た。"
+msgid "Nonblocking I/O has been selected using B<O_NONBLOCK> and the write would block."
+msgstr "B<O_NONBLOCK> を用いて非ブロック I/O が選択されたが、書き込みがブロックされた。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:125
-msgid ""
-"The input file was not opened for reading or the output file was not opened "
-"for writing."
-msgstr ""
-"入力ファイルが読み込みのためにオープンされていないか、 出力ファイルが書き込み"
-"のためにオープンされていない。"
+msgid "The input file was not opened for reading or the output file was not opened for writing."
+msgstr "入力ファイルが読み込みのためにオープンされていないか、 出力ファイルが書き込みのためにオープンされていない。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:128
@@ -12100,12 +9439,8 @@ msgstr "アドレスがおかしい。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:134
-msgid ""
-"Descriptor is not valid or locked, or an B<mmap>(2)-like operation is not "
-"available for I<in_fd>."
-msgstr ""
-"ディスクリプタが有効でないか、ロックされている。もしくは B<mmap>(2)  風の操作"
-"が I<in_fd> では利用できない。"
+msgid "Descriptor is not valid or locked, or an B<mmap>(2)-like operation is not available for I<in_fd>."
+msgstr "ディスクリプタが有効でないか、ロックされている。もしくは B<mmap>(2)  風の操作が I<in_fd> では利用できない。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:138
@@ -12119,12 +9454,8 @@ msgstr "I<in_fd> から読み込むための十分なメモリがない。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:148
-msgid ""
-"B<sendfile>()  is a new feature in Linux 2.2.  The include file I<E<lt>sys/"
-"sendfile.hE<gt>> is present since glibc 2.1."
-msgstr ""
-"B<sendfile> は Linux 2.2 の新しい機能である。 インクルードファイル "
-"I<E<lt>sys/sendfile.hE<gt>> は glibc 2.1 から存在している。"
+msgid "B<sendfile>()  is a new feature in Linux 2.2.  The include file I<E<lt>sys/sendfile.hE<gt>> is present since glibc 2.1."
+msgstr "B<sendfile> は Linux 2.2 の新しい機能である。 インクルードファイル I<E<lt>sys/sendfile.hE<gt>> は glibc 2.1 から存在している。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:150
@@ -12133,43 +9464,24 @@ msgstr "POSIX.1-2001 や他の標準では規定されていない。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:155
-msgid ""
-"Other UNIX systems implement B<sendfile>()  with different semantics and "
-"prototypes.  It should not be used in portable programs."
-msgstr ""
-"他の UNIX システムでは、異なった方式やプロトタイプで B<sendfile>()  を実装し"
-"ている。移植性を考慮したプログラムでは使用すべきではない。"
+msgid "Other UNIX systems implement B<sendfile>()  with different semantics and prototypes.  It should not be used in portable programs."
+msgstr "他の UNIX システムでは、異なった方式やプロトタイプで B<sendfile>()  を実装している。移植性を考慮したプログラムでは使用すべきではない。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:165
-msgid ""
-"If you plan to use B<sendfile>()  for sending files to a TCP socket, but "
-"need to send some header data in front of the file contents, you will find "
-"it useful to employ the B<TCP_CORK> option, described in B<tcp>(7), to "
-"minimize the number of packets and to tune performance."
-msgstr ""
-"B<sendfile>()  を使って TCP ソケットにファイルを送ろうとしていて、 ファイルの"
-"内容の前にヘッダ・データを付け加える必要がある場合は、 パケット数を最小にして"
-"性能を上げるために B<tcp>(7)  に記述されている B<TCP_CORK> オプションを使うと"
-"いいだろう。"
+msgid "If you plan to use B<sendfile>()  for sending files to a TCP socket, but need to send some header data in front of the file contents, you will find it useful to employ the B<TCP_CORK> option, described in B<tcp>(7), to minimize the number of packets and to tune performance."
+msgstr "B<sendfile>()  を使って TCP ソケットにファイルを送ろうとしていて、 ファイルの内容の前にヘッダ・データを付け加える必要がある場合は、 パケット数を最小にして性能を上げるために B<tcp>(7)  に記述されている B<TCP_CORK> オプションを使うといいだろう。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:171
-msgid ""
-"In Linux 2.4 and earlier, I<out_fd> could also refer to a regular file, and "
-"B<sendfile>()  changed the current offset of that file."
+msgid "In Linux 2.4 and earlier, I<out_fd> could also refer to a regular file, and B<sendfile>()  changed the current offset of that file."
 msgstr ""
-"Linux 2.4 とそれ以前のバージョンでも、 I<out_fd> は通常のファイルを参照で"
-"き、\n"
+"Linux 2.4 とそれ以前のバージョンでも、 I<out_fd> は通常のファイルを参照でき、\n"
 "B<sendfile>() はそのファイルのオフセットの現在値を変更していた。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:183
-msgid ""
-"The original Linux B<sendfile>()  system call was not designed to handle "
-"large file offsets.  Consequently, Linux 2.4 added B<sendfile64>(), with a "
-"wider type for the I<offset> argument.  The glibc B<sendfile>()  wrapper "
-"function transparently deals with the kernel differences."
+msgid "The original Linux B<sendfile>()  system call was not designed to handle large file offsets.  Consequently, Linux 2.4 added B<sendfile64>(), with a wider type for the I<offset> argument.  The glibc B<sendfile>()  wrapper function transparently deals with the kernel differences."
 msgstr ""
 "元々の Linux B<sendfile>() システムコールは大きなファイルオフセットを\n"
 "扱えるように設計されていなかった。その結果、Linux 2.4 で、\n"
@@ -12178,18 +9490,12 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:192
-msgid ""
-"Applications may wish to fall back to B<read>(2)/B<write>(2)  in the case "
-"where B<sendfile>()  fails with B<EINVAL> or B<ENOSYS>."
-msgstr ""
-"B<sendfile>()  が B<EINVAL> や B<ENOSYS> で失敗するような場合は、 アプリケー"
-"ションは B<read>(2)/B<write>(2)  に戻すことを考えてもよいかもしれない。"
+msgid "Applications may wish to fall back to B<read>(2)/B<write>(2)  in the case where B<sendfile>()  fails with B<EINVAL> or B<ENOSYS>."
+msgstr "B<sendfile>()  が B<EINVAL> や B<ENOSYS> で失敗するような場合は、 アプリケーションは B<read>(2)/B<write>(2)  に戻すことを考えてもよいかもしれない。"
 
 #. type: Plain text
 #: build/C/man2/sendfile.2:197
-msgid ""
-"The Linux-specific B<splice>(2)  call supports transferring data between "
-"arbitrary files (e.g., a pair of sockets)."
+msgid "The Linux-specific B<splice>(2)  call supports transferring data between arbitrary files (e.g., a pair of sockets)."
 msgstr ""
 "Linux 固有の B<splice>(2) システムコールは、任意のファイル間 (例えば、\n"
 "ソケット同士) でのデータ転送をサポートしている。"
@@ -12230,13 +9536,8 @@ msgstr "B<long set_tid_address(int *>I<tidptr>B<);>\n"
 
 #. type: Plain text
 #: build/C/man2/set_tid_address.2:40
-msgid ""
-"For each thread, the kernel maintains two attributes (addresses) called "
-"I<set_child_tid> and I<clear_child_tid>.  These two attributes contain the "
-"value NULL by default."
-msgstr ""
-"各スレッドについて、カーネルは I<set_child_tid> と I<clear_child_tid> という "
-"2 つの属性を保持する。この 2 つの属性はデフォルトでは NULL である。"
+msgid "For each thread, the kernel maintains two attributes (addresses) called I<set_child_tid> and I<clear_child_tid>.  These two attributes contain the value NULL by default."
+msgstr "各スレッドについて、カーネルは I<set_child_tid> と I<clear_child_tid> という 2 つの属性を保持する。この 2 つの属性はデフォルトでは NULL である。"
 
 #. type: TP
 #: build/C/man2/set_tid_address.2:40
@@ -12246,23 +9547,13 @@ msgstr "I<set_child_tid>"
 
 #. type: Plain text
 #: build/C/man2/set_tid_address.2:51
-msgid ""
-"If a thread is started using B<clone>(2)  with the B<CLONE_CHILD_SETTID> "
-"flag, I<set_child_tid> is set to the value passed in the I<ctid> argument of "
-"that system call."
-msgstr ""
-"スレッドが B<CLONE_CHILD_SETTID> フラグを指定した B<clone>(2)  によって開始さ"
-"れた場合、 I<set_child_tid> は B<clone>(2) のシステムコールの I<ctid> 引き数"
-"で渡された値に設定される。"
+msgid "If a thread is started using B<clone>(2)  with the B<CLONE_CHILD_SETTID> flag, I<set_child_tid> is set to the value passed in the I<ctid> argument of that system call."
+msgstr "スレッドが B<CLONE_CHILD_SETTID> フラグを指定した B<clone>(2)  によって開始された場合、 I<set_child_tid> は B<clone>(2) のシステムコールの I<ctid> 引き数で渡された値に設定される。"
 
 #. type: Plain text
 #: build/C/man2/set_tid_address.2:56
-msgid ""
-"When I<set_child_tid> is set, the very first thing the new thread does is to "
-"write its thread ID at this address."
-msgstr ""
-"I<set_child_tid> が設定された場合、一番最初に新しいスレッドが行うことは、 こ"
-"のアドレスに自身のスレッド ID を書き込むことである。"
+msgid "When I<set_child_tid> is set, the very first thing the new thread does is to write its thread ID at this address."
+msgstr "I<set_child_tid> が設定された場合、一番最初に新しいスレッドが行うことは、 このアドレスに自身のスレッド ID を書き込むことである。"
 
 #. type: TP
 #: build/C/man2/set_tid_address.2:56
@@ -12272,35 +9563,18 @@ msgstr "I<clear_child_tid>"
 
 #. type: Plain text
 #: build/C/man2/set_tid_address.2:67
-msgid ""
-"If a thread is started using B<clone>(2)  with the B<CLONE_CHILD_CLEARTID> "
-"flag, I<clear_child_tid> is set to the value passed in the I<ctid> argument "
-"of that system call."
-msgstr ""
-"スレッドが B<CLONE_CHILD_CLEARTID> フラグを指定した B<clone>(2) によって開始"
-"された場合、 I<clear_child_tid> は B<clone>(2) のシステムコールの I<ctid> 引"
-"き数で渡された値に設定される。"
+msgid "If a thread is started using B<clone>(2)  with the B<CLONE_CHILD_CLEARTID> flag, I<clear_child_tid> is set to the value passed in the I<ctid> argument of that system call."
+msgstr "スレッドが B<CLONE_CHILD_CLEARTID> フラグを指定した B<clone>(2) によって開始された場合、 I<clear_child_tid> は B<clone>(2) のシステムコールの I<ctid> 引き数で渡された値に設定される。"
 
 #. type: Plain text
 #: build/C/man2/set_tid_address.2:74
-msgid ""
-"The system call B<set_tid_address>()  sets the I<clear_child_tid> value for "
-"the calling thread to I<tidptr>."
-msgstr ""
-"システムコール B<set_tid_address>()  は呼び出し元スレッドの "
-"I<clear_child_tid> の値を I<tidptr> に設定する。"
+msgid "The system call B<set_tid_address>()  sets the I<clear_child_tid> value for the calling thread to I<tidptr>."
+msgstr "システムコール B<set_tid_address>()  は呼び出し元スレッドの I<clear_child_tid> の値を I<tidptr> に設定する。"
 
 #. type: Plain text
 #: build/C/man2/set_tid_address.2:82
-msgid ""
-"When a thread whose I<clear_child_tid> is not NULL terminates, then, if the "
-"thread is sharing memory with other threads, then 0 is written at the "
-"address specified in I<clear_child_tid> and the kernel performs the "
-"following operation:"
-msgstr ""
-"I<clear_child_tid> が NULL でないスレッドが終了すると、そのスレッドが他のス"
-"レッドとメモリを共有していれば、 I<clear_child_tid> で指定されたアドレスに 0 "
-"が書き込まれ、カーネルは以下の処理を実行する。"
+msgid "When a thread whose I<clear_child_tid> is not NULL terminates, then, if the thread is sharing memory with other threads, then 0 is written at the address specified in I<clear_child_tid> and the kernel performs the following operation:"
+msgstr "I<clear_child_tid> が NULL でないスレッドが終了すると、そのスレッドが他のスレッドとメモリを共有していれば、 I<clear_child_tid> で指定されたアドレスに 0 が書き込まれ、カーネルは以下の処理を実行する。"
 
 #. type: Plain text
 #: build/C/man2/set_tid_address.2:84
@@ -12310,13 +9584,8 @@ msgstr "    futex(clear_child_tid, FUTEX_WAKE, 1, NULL, NULL, 0);\n"
 
 #. type: Plain text
 #: build/C/man2/set_tid_address.2:88
-msgid ""
-"The effect of this operation is to wake a single thread that is performing a "
-"futex wait on the memory location.  Errors from the futex wake operation are "
-"ignored."
-msgstr ""
-"この処理の結果、このメモリアドレスに対する futex wait を実行しているスレッド"
-"を一つ起こす (wake)。 futex wake 操作でのエラーは無視される。"
+msgid "The effect of this operation is to wake a single thread that is performing a futex wait on the memory location.  Errors from the futex wake operation are ignored."
+msgstr "この処理の結果、このメモリアドレスに対する futex wait を実行しているスレッドを一つ起こす (wake)。 futex wake 操作でのエラーは無視される。"
 
 #. type: Plain text
 #: build/C/man2/set_tid_address.2:91
@@ -12330,12 +9599,8 @@ msgstr "B<set_tid_address>()  は常に成功する。"
 
 #. type: Plain text
 #: build/C/man2/set_tid_address.2:97
-msgid ""
-"This call is present since Linux 2.5.48.  Details as given here are valid "
-"since Linux 2.5.49."
-msgstr ""
-"この呼び出しは Linux 2.5.48 以降で存在する。 ここで書かれた詳細は Linux "
-"2.5.49 以降で有効である。"
+msgid "This call is present since Linux 2.5.48.  Details as given here are valid since Linux 2.5.49."
+msgstr "この呼び出しは Linux 2.5.48 以降で存在する。 ここで書かれた詳細は Linux 2.5.49 以降で有効である。"
 
 #. type: Plain text
 #: build/C/man2/set_tid_address.2:103
@@ -12382,17 +9647,8 @@ msgstr ""
 
 #. type: Plain text
 #: build/C/man2/splice.2:50
-msgid ""
-"B<splice>()  moves data between two file descriptors without copying between "
-"kernel address space and user address space.  It transfers up to I<len> "
-"bytes of data from the file descriptor I<fd_in> to the file descriptor "
-"I<fd_out>, where one of the descriptors must refer to a pipe."
-msgstr ""
-"B<splice>()  は、カーネルアドレス空間とユーザアドレス空間との間のコピーを伴わ"
-"ずに、 2 つのファイルディスクリプタ間でデータの移動を行う。 ファイルディスク"
-"リプタ I<fd_in> からファイルディスクリプタ I<fd_out> へ最大 I<len> バイトを転"
-"送する。 2 つのファイルディスクリプタのうち一つは パイプを参照していなければ"
-"ならない。"
+msgid "B<splice>()  moves data between two file descriptors without copying between kernel address space and user address space.  It transfers up to I<len> bytes of data from the file descriptor I<fd_in> to the file descriptor I<fd_out>, where one of the descriptors must refer to a pipe."
+msgstr "B<splice>()  は、カーネルアドレス空間とユーザアドレス空間との間のコピーを伴わずに、 2 つのファイルディスクリプタ間でデータの移動を行う。 ファイルディスクリプタ I<fd_in> からファイルディスクリプタ I<fd_out> へ最大 I<len> バイトを転送する。 2 つのファイルディスクリプタのうち一つは パイプを参照していなければならない。"
 
 #. type: Plain text
 #: build/C/man2/splice.2:55
@@ -12402,32 +9658,17 @@ msgstr "I<fd_in> と I<off_in> には以下のルールが適用される。"
 #. type: Plain text
 #: build/C/man2/splice.2:61
 msgid "If I<fd_in> refers to a pipe, then I<off_in> must be NULL."
-msgstr ""
-"I<fd_in> がパイプを参照している場合、 I<off_in> は NULL でなければならない。"
+msgstr "I<fd_in> がパイプを参照している場合、 I<off_in> は NULL でなければならない。"
 
 #. type: Plain text
 #: build/C/man2/splice.2:70
-msgid ""
-"If I<fd_in> does not refer to a pipe and I<off_in> is NULL, then bytes are "
-"read from I<fd_in> starting from the current file offset, and the current "
-"file offset is adjusted appropriately."
-msgstr ""
-"I<fd_in> がパイプを参照しておらず、かつ I<off_in> が NULL の場合、 バイトは "
-"I<fd_in> の現在のファイルオフセットから読み出され、 現在のファイルオフセット"
-"は適切に調整される。"
+msgid "If I<fd_in> does not refer to a pipe and I<off_in> is NULL, then bytes are read from I<fd_in> starting from the current file offset, and the current file offset is adjusted appropriately."
+msgstr "I<fd_in> がパイプを参照しておらず、かつ I<off_in> が NULL の場合、 バイトは I<fd_in> の現在のファイルオフセットから読み出され、 現在のファイルオフセットは適切に調整される。"
 
 #. type: Plain text
 #: build/C/man2/splice.2:83
-msgid ""
-"If I<fd_in> does not refer to a pipe and I<off_in> is not NULL, then "
-"I<off_in> must point to a buffer which specifies the starting offset from "
-"which bytes will be read from I<fd_in>; in this case, the current file "
-"offset of I<fd_in> is not changed."
-msgstr ""
-"I<fd_in> がパイプを参照しておらず、 I<off_in> が NULL でない場合、 I<off_in> "
-"は I<fd_in> からのデータ読み出しを開始する先頭オフセットを格納したバッファ へ"
-"のポインタでなければならない。この場合、 I<fd_in> の現在のファイルオフセット"
-"は変更されない。"
+msgid "If I<fd_in> does not refer to a pipe and I<off_in> is not NULL, then I<off_in> must point to a buffer which specifies the starting offset from which bytes will be read from I<fd_in>; in this case, the current file offset of I<fd_in> is not changed."
+msgstr "I<fd_in> がパイプを参照しておらず、 I<off_in> が NULL でない場合、 I<off_in> は I<fd_in> からのデータ読み出しを開始する先頭オフセットを格納したバッファ へのポインタでなければならない。この場合、 I<fd_in> の現在のファイルオフセットは変更されない。"
 
 #. type: Plain text
 #: build/C/man2/splice.2:88
@@ -12436,11 +9677,8 @@ msgstr "I<fd_out> と I<off_out> に関しても同様である。"
 
 #. type: Plain text
 #: build/C/man2/splice.2:93 build/C/man2/vmsplice.2:78
-msgid ""
-"The I<flags> argument is a bit mask that is composed by ORing together zero "
-"or more of the following values:"
-msgstr ""
-"I<flags> 引き数には、以下の値の 0 個以上をビット毎の論理和の形で指定する。"
+msgid "The I<flags> argument is a bit mask that is composed by ORing together zero or more of the following values:"
+msgstr "I<flags> 引き数には、以下の値の 0 個以上をビット毎の論理和の形で指定する。"
 
 #. type: TP
 #: build/C/man2/splice.2:93 build/C/man2/tee.2:62 build/C/man2/vmsplice.2:78
@@ -12450,20 +9688,8 @@ msgstr "B<SPLICE_F_MOVE>"
 
 #. type: Plain text
 #: build/C/man2/splice.2:106
-msgid ""
-"Attempt to move pages instead of copying.  This is only a hint to the "
-"kernel: pages may still be copied if the kernel cannot move the pages from "
-"the pipe, or if the pipe buffers don't refer to full pages.  The initial "
-"implementation of this flag was buggy: therefore starting in Linux 2.6.21 it "
-"is a no-op (but is still permitted in a B<splice>()  call); in the future, a "
-"correct implementation may be restored."
-msgstr ""
-"ページのコピーでなく移動を試みる。 これはカーネルに対するヒントでしかない。 "
-"つまり、カーネルがパイプからページを移動できない場合や、 パイプバッファがペー"
-"ジ全部を参照していない場合は、 ページのコピーが行われることもある。 このフラ"
-"グの最初の実装にはバグがあった。そのため、 Linux 2.6.21 以降ではこのフラグの"
-"操作はできないようになっている (ただし、 B<splice>()  コールでこのフラグを指"
-"定することは今も認められている)。 将来、正しい実装が行われることだろう。"
+msgid "Attempt to move pages instead of copying.  This is only a hint to the kernel: pages may still be copied if the kernel cannot move the pages from the pipe, or if the pipe buffers don't refer to full pages.  The initial implementation of this flag was buggy: therefore starting in Linux 2.6.21 it is a no-op (but is still permitted in a B<splice>()  call); in the future, a correct implementation may be restored."
+msgstr "ページのコピーでなく移動を試みる。 これはカーネルに対するヒントでしかない。 つまり、カーネルがパイプからページを移動できない場合や、 パイプバッファがページ全部を参照していない場合は、 ページのコピーが行われることもある。 このフラグの最初の実装にはバグがあった。そのため、 Linux 2.6.21 以降ではこのフラグの操作はできないようになっている (ただし、 B<splice>()  コールでこのフラグを指定することは今も認められている)。 将来、正しい実装が行われることだろう。"
 
 #. type: TP
 #: build/C/man2/splice.2:106 build/C/man2/tee.2:68 build/C/man2/vmsplice.2:84
@@ -12473,16 +9699,8 @@ msgstr "B<SPLICE_F_NONBLOCK>"
 
 #. type: Plain text
 #: build/C/man2/splice.2:115
-msgid ""
-"Do not block on I/O.  This makes the splice pipe operations nonblocking, but "
-"B<splice>()  may nevertheless block because the file descriptors that are "
-"spliced to/from may block (unless they have the B<O_NONBLOCK> flag set)."
-msgstr ""
-"入出力時に停止 (block) しない。 このフラグを指定すると、 splice によるパイプ"
-"操作を非停止モード (nonblocking) で 行おうとするが、その場合でも "
-"B<splice>()  は停止することもある。なぜなら、データのやり取りを行う ファイル"
-"ディスクリプタは (B<O_NONBLOCK> フラグをセットされていない場合) 停止する可能"
-"性があるからである。"
+msgid "Do not block on I/O.  This makes the splice pipe operations nonblocking, but B<splice>()  may nevertheless block because the file descriptors that are spliced to/from may block (unless they have the B<O_NONBLOCK> flag set)."
+msgstr "入出力時に停止 (block) しない。 このフラグを指定すると、 splice によるパイプ操作を非停止モード (nonblocking) で 行おうとするが、その場合でも B<splice>()  は停止することもある。なぜなら、データのやり取りを行う ファイルディスクリプタは (B<O_NONBLOCK> フラグをセットされていない場合) 停止する可能性があるからである。"
 
 #. type: TP
 #: build/C/man2/splice.2:115 build/C/man2/tee.2:73 build/C/man2/vmsplice.2:91
@@ -12492,14 +9710,8 @@ msgstr "B<SPLICE_F_MORE>"
 
 #. type: Plain text
 #: build/C/man2/splice.2:129
-msgid ""
-"More data will be coming in a subsequent splice.  This is a helpful hint "
-"when the I<fd_out> refers to a socket (see also the description of "
-"B<MSG_MORE> in B<send>(2), and the description of B<TCP_CORK> in B<tcp>(7))"
-msgstr ""
-"この後の splice でさらに転送されるデータがあることを示す。 このフラグは "
-"I<fd_out> がソケットを参照している場合に有用なヒントとなる (B<send>(2)  の "
-"B<MSG_MORE> や B<tcp>(7)  の B<TCP_CORK> の説明も参照)。"
+msgid "More data will be coming in a subsequent splice.  This is a helpful hint when the I<fd_out> refers to a socket (see also the description of B<MSG_MORE> in B<send>(2), and the description of B<TCP_CORK> in B<tcp>(7))"
+msgstr "この後の splice でさらに転送されるデータがあることを示す。 このフラグは I<fd_out> がソケットを参照している場合に有用なヒントとなる (B<send>(2)  の B<MSG_MORE> や B<tcp>(7)  の B<TCP_CORK> の説明も参照)。"
 
 #. type: TP
 #: build/C/man2/splice.2:129 build/C/man2/tee.2:79 build/C/man2/vmsplice.2:97
@@ -12514,56 +9726,31 @@ msgstr "B<splice>()  では使用しない。 B<vmsplice>(2)  参照。"
 
 #. type: Plain text
 #: build/C/man2/splice.2:144
-msgid ""
-"Upon successful completion, B<splice>()  returns the number of bytes spliced "
-"to or from the pipe.  A return value of 0 means that there was no data to "
-"transfer, and it would not make sense to block, because there are no writers "
-"connected to the write end of the pipe referred to by I<fd_in>."
-msgstr ""
-"成功して完了すると、 B<splice>()  はパイプから出し入れしたバイト数を返す。 返"
-"り値 0 はデータの転送が行わなかったことを示す。 この場合、処理を停止 (block) "
-"しても無意味である。 なぜなら、 I<fd_in> が参照するパイプの書き込み側に接続さ"
-"れている者がいないからである。"
+msgid "Upon successful completion, B<splice>()  returns the number of bytes spliced to or from the pipe.  A return value of 0 means that there was no data to transfer, and it would not make sense to block, because there are no writers connected to the write end of the pipe referred to by I<fd_in>."
+msgstr "成功して完了すると、 B<splice>()  はパイプから出し入れしたバイト数を返す。 返り値 0 はデータの転送が行わなかったことを示す。 この場合、処理を停止 (block) しても無意味である。 なぜなら、 I<fd_in> が参照するパイプの書き込み側に接続されている者がいないからである。"
 
 #. type: Plain text
 #: build/C/man2/splice.2:150
-msgid ""
-"On error, B<splice>()  returns -1 and I<errno> is set to indicate the error."
-msgstr ""
-"エラーの場合、 B<splice>()  は -1 を返し、 I<errno> にエラーを示す値を設定す"
-"る。"
+msgid "On error, B<splice>()  returns -1 and I<errno> is set to indicate the error."
+msgstr "エラーの場合、 B<splice>()  は -1 を返し、 I<errno> にエラーを示す値を設定する。"
 
 #. type: Plain text
 #: build/C/man2/splice.2:157 build/C/man2/tee.2:107
 #: build/C/man2/vmsplice.2:133
-msgid ""
-"B<SPLICE_F_NONBLOCK> was specified in I<flags>, and the operation would "
-"block."
-msgstr ""
-"B<SPLICE_F_NONBLOCK> が I<flags> に指定されていて、かつ操作が停止するような状"
-"態であった。"
+msgid "B<SPLICE_F_NONBLOCK> was specified in I<flags>, and the operation would block."
+msgstr "B<SPLICE_F_NONBLOCK> が I<flags> に指定されていて、かつ操作が停止するような状態であった。"
 
 #. type: Plain text
 #: build/C/man2/splice.2:161
-msgid ""
-"One or both file descriptors are not valid, or do not have proper read-write "
-"mode."
-msgstr ""
-"ファイルディスクリプタの一方または両方が有効ではない、 もしくは適切な read-"
-"write モードではない。"
+msgid "One or both file descriptors are not valid, or do not have proper read-write mode."
+msgstr "ファイルディスクリプタの一方または両方が有効ではない、 もしくは適切な read-write モードではない。"
 
 #.  The append-mode error is given since 2.6.27; in earlier kernels,
 #.  splice() in append mode was broken
 #. type: Plain text
 #: build/C/man2/splice.2:169
-msgid ""
-"Target filesystem doesn't support splicing; target file is opened in append "
-"mode; neither of the descriptors refers to a pipe; or offset given for "
-"nonseekable device."
-msgstr ""
-"対象のファイルシステムが splice に対応していない、 または対象のファイルが追記"
-"モードでオープンされている、 またはディスクリプタのどちらもパイプを参照してい"
-"ない、 または seek できないデバイスに対してオフセットが指定された。"
+msgid "Target filesystem doesn't support splicing; target file is opened in append mode; neither of the descriptors refers to a pipe; or offset given for nonseekable device."
+msgstr "対象のファイルシステムが splice に対応していない、 または対象のファイルが追記モードでオープンされている、 またはディスクリプタのどちらもパイプを参照していない、 または seek できないデバイスに対してオフセットが指定された。"
 
 #. type: Plain text
 #: build/C/man2/splice.2:172 build/C/man2/tee.2:120
@@ -12579,34 +9766,20 @@ msgstr "B<ESPIPE>"
 
 #. type: Plain text
 #: build/C/man2/splice.2:179
-msgid ""
-"Either I<off_in> or I<off_out> was not NULL, but the corresponding file "
-"descriptor refers to a pipe."
-msgstr ""
-"I<off_in> か I<off_out> のいずれかが NULL ではないが、対応するファイルディス"
-"クリプタが パイプを参照している。"
+msgid "Either I<off_in> or I<off_out> was not NULL, but the corresponding file descriptor refers to a pipe."
+msgstr "I<off_in> か I<off_out> のいずれかが NULL ではないが、対応するファイルディスクリプタが パイプを参照している。"
 
 #. type: Plain text
 #: build/C/man2/splice.2:184
-msgid ""
-"The B<splice>()  system call first appeared in Linux 2.6.17; library support "
-"was added to glibc in version 2.5."
+msgid "The B<splice>()  system call first appeared in Linux 2.6.17; library support was added to glibc in version 2.5."
 msgstr ""
 "B<splice>() システムコールは Linux 2.6.17 で初めて登場した。\n"
 "ライブラリによるサポートは glibc バージョン 2.5 で追加された。"
 
 #. type: Plain text
 #: build/C/man2/splice.2:196
-msgid ""
-"The three system calls B<splice>(), B<vmsplice>(2), and B<tee>(2), provide "
-"user-space programs with full control over an arbitrary kernel buffer, "
-"implemented within the kernel using the same type of buffer that is used for "
-"a pipe.  In overview, these system calls perform the following tasks:"
-msgstr ""
-"3 つのシステムコール (B<splice>(), B<vmsplice>(2), B<tee>(2))  を使うと、ユー"
-"ザ空間プログラムは任意のカーネルバッファに対する 完全な制御ができる。カーネル"
-"バッファは、パイプに使用されているのと 同種のバッファを使ってカーネル内に実装"
-"されている。 大まかにいうと、これらのシステムコールは以下の仕事を行う:"
+msgid "The three system calls B<splice>(), B<vmsplice>(2), and B<tee>(2), provide user-space programs with full control over an arbitrary kernel buffer, implemented within the kernel using the same type of buffer that is used for a pipe.  In overview, these system calls perform the following tasks:"
+msgstr "3 つのシステムコール (B<splice>(), B<vmsplice>(2), B<tee>(2))  を使うと、ユーザ空間プログラムは任意のカーネルバッファに対する 完全な制御ができる。カーネルバッファは、パイプに使用されているのと 同種のバッファを使ってカーネル内に実装されている。 大まかにいうと、これらのシステムコールは以下の仕事を行う:"
 
 #. type: TP
 #: build/C/man2/splice.2:196
@@ -12616,12 +9789,8 @@ msgstr "B<splice>()"
 
 #. type: Plain text
 #: build/C/man2/splice.2:200
-msgid ""
-"moves data from the buffer to an arbitrary file descriptor, or vice versa, "
-"or from one buffer to another."
-msgstr ""
-"バッファから任意のファイルディスクリプタや、その逆方向、 もしくはあるバッファ"
-"から別のバッファへの、データ移動を行う。"
+msgid "moves data from the buffer to an arbitrary file descriptor, or vice versa, or from one buffer to another."
+msgstr "バッファから任意のファイルディスクリプタや、その逆方向、 もしくはあるバッファから別のバッファへの、データ移動を行う。"
 
 #. type: TP
 #: build/C/man2/splice.2:200
@@ -12666,20 +9835,8 @@ msgstr "ユーザ空間からバッファへのデータ「コピー」を行う
 #.  users - for things like logging etc.).
 #. type: Plain text
 #: build/C/man2/splice.2:237
-msgid ""
-"Though we talk of copying, actual copies are generally avoided.  The kernel "
-"does this by implementing a pipe buffer as a set of reference-counted "
-"pointers to pages of kernel memory.  The kernel creates \"copies\" of pages "
-"in a buffer by creating new pointers (for the output buffer) referring to "
-"the pages, and increasing the reference counts for the pages: only pointers "
-"are copied, not the pages of the buffer."
-msgstr ""
-"ここではコピーの話をしているが、実際のコピーは一般的に回避される。 カーネル"
-"は、パイプ・バッファをカーネルメモリのページへのポインタ集合として 実装し、"
-"ページへの参照回数を管理することで、これを実現している。 カーネルは、対象とな"
-"るページを参照する (出力バッファ用の) ポインタを 新規に作成することでバッファ"
-"内のページの「コピー」を作成し、 そのページの参照回数を増やす。つまり、ポイン"
-"タだけがコピーされ、 バッファのページはコピーされない。"
+msgid "Though we talk of copying, actual copies are generally avoided.  The kernel does this by implementing a pipe buffer as a set of reference-counted pointers to pages of kernel memory.  The kernel creates \"copies\" of pages in a buffer by creating new pointers (for the output buffer) referring to the pages, and increasing the reference counts for the pages: only pointers are copied, not the pages of the buffer."
+msgstr "ここではコピーの話をしているが、実際のコピーは一般的に回避される。 カーネルは、パイプ・バッファをカーネルメモリのページへのポインタ集合として 実装し、ページへの参照回数を管理することで、これを実現している。 カーネルは、対象となるページを参照する (出力バッファ用の) ポインタを 新規に作成することでバッファ内のページの「コピー」を作成し、 そのページの参照回数を増やす。つまり、ポインタだけがコピーされ、 バッファのページはコピーされない。"
 
 #. type: Plain text
 #: build/C/man2/splice.2:240
@@ -12714,25 +9871,13 @@ msgstr "B<ssize_t tee(int >I<fd_in>B<, int >I<fd_out>B<, size_t >I<len>B<, unsig
 #.  one pipe to two other pipes.
 #. type: Plain text
 #: build/C/man2/tee.2:56
-msgid ""
-"B<tee>()  duplicates up to I<len> bytes of data from the pipe referred to by "
-"the file descriptor I<fd_in> to the pipe referred to by the file descriptor "
-"I<fd_out>.  It does not consume the data that is duplicated from I<fd_in>; "
-"therefore, that data can be copied by a subsequent B<splice>(2)."
-msgstr ""
-"B<tee>()  は、ファイルディスクリプタ I<fd_in> が参照するパイプからファイル"
-"ディスクリプタ I<fd_out> が参照するパイプへ最大 I<len> バイトのデータを複製す"
-"る。 この操作では、複製されるデータは I<fd_in> からは消費されない。したがっ"
-"て、これらのデータをこの後の B<splice>(2)  でコピーすることができる。"
+msgid "B<tee>()  duplicates up to I<len> bytes of data from the pipe referred to by the file descriptor I<fd_in> to the pipe referred to by the file descriptor I<fd_out>.  It does not consume the data that is duplicated from I<fd_in>; therefore, that data can be copied by a subsequent B<splice>(2)."
+msgstr "B<tee>()  は、ファイルディスクリプタ I<fd_in> が参照するパイプからファイルディスクリプタ I<fd_out> が参照するパイプへ最大 I<len> バイトのデータを複製する。 この操作では、複製されるデータは I<fd_in> からは消費されない。したがって、これらのデータをこの後の B<splice>(2)  でコピーすることができる。"
 
 #. type: Plain text
 #: build/C/man2/tee.2:62
-msgid ""
-"I<flags> is a series of modifier flags, which share the name space with "
-"B<splice>(2)  and B<vmsplice>(2):"
-msgstr ""
-"I<flags> は一連の修飾フラグであり、 B<splice>(2)  や B<vmsplice>(2)  と共通の"
-"名前である。"
+msgid "I<flags> is a series of modifier flags, which share the name space with B<splice>(2)  and B<vmsplice>(2):"
+msgstr "I<flags> は一連の修飾フラグであり、 B<splice>(2)  や B<vmsplice>(2)  と共通の名前である。"
 
 #. type: Plain text
 #: build/C/man2/tee.2:68
@@ -12748,12 +9893,8 @@ msgstr "入出力で停止 (block) しない。詳細は B<splice>(2)  参照。
 
 #. type: Plain text
 #: build/C/man2/tee.2:79
-msgid ""
-"Currently has no effect for B<tee>(), but may be implemented in the future; "
-"see B<splice>(2)."
-msgstr ""
-"現在のところ B<tee>()  では何の効果もないが、将来的には実装される可能性があ"
-"る。 B<splice>(2)  参照。"
+msgid "Currently has no effect for B<tee>(), but may be implemented in the future; see B<splice>(2)."
+msgstr "現在のところ B<tee>()  では何の効果もないが、将来的には実装される可能性がある。 B<splice>(2)  参照。"
 
 #. type: Plain text
 #: build/C/man2/tee.2:85
@@ -12762,62 +9903,35 @@ msgstr "B<tee>()  では未使用。 B<vmsplice>(2)  参照。"
 
 #. type: Plain text
 #: build/C/man2/tee.2:94
-msgid ""
-"Upon successful completion, B<tee>()  returns the number of bytes that were "
-"duplicated between the input and output.  A return value of 0 means that "
-"there was no data to transfer, and it would not make sense to block, because "
-"there are no writers connected to the write end of the pipe referred to by "
-"I<fd_in>."
-msgstr ""
-"成功して完了すると、 B<tee>()  は入出力間で複製されたバイト数を返す。 返り値 "
-"0 はデータの転送が行われなかったことを示す。 この場合、処理を停止 (block) し"
-"ても無意味である。 なぜなら、 I<fd_in> が参照するパイプの書き込み側に接続され"
-"ている者がいないからである。"
+msgid "Upon successful completion, B<tee>()  returns the number of bytes that were duplicated between the input and output.  A return value of 0 means that there was no data to transfer, and it would not make sense to block, because there are no writers connected to the write end of the pipe referred to by I<fd_in>."
+msgstr "成功して完了すると、 B<tee>()  は入出力間で複製されたバイト数を返す。 返り値 0 はデータの転送が行われなかったことを示す。 この場合、処理を停止 (block) しても無意味である。 なぜなら、 I<fd_in> が参照するパイプの書き込み側に接続されている者がいないからである。"
 
 #. type: Plain text
 #: build/C/man2/tee.2:100
-msgid ""
-"On error, B<tee>()  returns -1 and I<errno> is set to indicate the error."
-msgstr ""
-"エラーの場合、 B<tee>()  は -1 を返し、 I<errno> にエラーを示す値を設定する。"
+msgid "On error, B<tee>()  returns -1 and I<errno> is set to indicate the error."
+msgstr "エラーの場合、 B<tee>()  は -1 を返し、 I<errno> にエラーを示す値を設定する。"
 
 #. type: Plain text
 #: build/C/man2/tee.2:117
-msgid ""
-"I<fd_in> or I<fd_out> does not refer to a pipe; or I<fd_in> and I<fd_out> "
-"refer to the same pipe."
-msgstr ""
-"I<fd_in> と I<fd_out> のどちらかがパイプを参照していない。もしくは I<fd_in> "
-"と I<fd_out> が同じパイプを参照している。"
+msgid "I<fd_in> or I<fd_out> does not refer to a pipe; or I<fd_in> and I<fd_out> refer to the same pipe."
+msgstr "I<fd_in> と I<fd_out> のどちらかがパイプを参照していない。もしくは I<fd_in> と I<fd_out> が同じパイプを参照している。"
 
 #. type: Plain text
 #: build/C/man2/tee.2:125
-msgid ""
-"The B<tee>()  system call first appeared in Linux 2.6.17; library support "
-"was added to glibc in version 2.5."
+msgid "The B<tee>()  system call first appeared in Linux 2.6.17; library support was added to glibc in version 2.5."
 msgstr ""
 "B<tee>() システムコールは Linux 2.6.17 で初めて登場した。\n"
 "ライブラリによるサポートは glibc バージョン 2.5 で追加された。"
 
 #. type: Plain text
 #: build/C/man2/tee.2:136
-msgid ""
-"Conceptually, B<tee>()  copies the data between the two pipes.  In reality "
-"no real data copying takes place though: under the covers, B<tee>()  assigns "
-"data in the output by merely grabbing a reference to the input."
-msgstr ""
-"概念としては、 B<tee>()  は二つのパイプ間でデータのコピーを行う。 しかし、実"
-"際には実データのコピーは行われない。 内部では、 B<tee>()  は入力側に対する参"
-"照だけを作成することで出力側にデータを 追加する。"
+msgid "Conceptually, B<tee>()  copies the data between the two pipes.  In reality no real data copying takes place though: under the covers, B<tee>()  assigns data in the output by merely grabbing a reference to the input."
+msgstr "概念としては、 B<tee>()  は二つのパイプ間でデータのコピーを行う。 しかし、実際には実データのコピーは行われない。 内部では、 B<tee>()  は入力側に対する参照だけを作成することで出力側にデータを 追加する。"
 
 #. type: Plain text
 #: build/C/man2/tee.2:143
-msgid ""
-"The example below implements a basic B<tee>(1)  program using the B<tee>()  "
-"system call.  Here is an example of its use:"
-msgstr ""
-"以下の例は、 B<tee>()  システムコールを使って、 基本的な B<tee>(1)  プログラ"
-"ムを実装したものである。 以下は利用例である。"
+msgid "The example below implements a basic B<tee>(1)  program using the B<tee>()  system call.  Here is an example of its use:"
+msgstr "以下の例は、 B<tee>()  システムコールを使って、 基本的な B<tee>(1)  プログラムを実装したものである。 以下は利用例である。"
 
 #. type: Plain text
 #: build/C/man2/tee.2:150
@@ -13024,72 +10138,42 @@ msgstr "B<int vm86old(struct vm86_struct *>I<info>B<);>"
 #. type: Plain text
 #: build/C/man2/vm86.2:35
 msgid "B<int vm86(unsigned long >I<fn>B<, struct vm86plus_struct *>I<v86>B<);>"
-msgstr ""
-"B<int vm86(unsigned long >I<fn>B<, struct vm86plus_struct *>I<v86>B<);>"
+msgstr "B<int vm86(unsigned long >I<fn>B<, struct vm86plus_struct *>I<v86>B<);>"
 
 #. type: Plain text
 #: build/C/man2/vm86.2:48
-msgid ""
-"The system call B<vm86>()  was introduced in Linux 0.97p2.  In Linux 2.1.15 "
-"and 2.0.28, it was renamed to B<vm86old>(), and a new B<vm86>()  was "
-"introduced.  The definition of I<struct vm86_struct> was changed in 1.1.8 "
-"and 1.1.9."
-msgstr ""
-"B<vm86>()  システムコールは Linux 0.97p2 で導入された。 これは Linux 2.1.15 "
-"と 2.0.28 で B<vm86old>()  に名前が変更され、 新しい B<vm86>()  が導入され"
-"た。 I<struct vm86_struct> の定義は 1.1.8 と 1.1.9 で変更された。"
+msgid "The system call B<vm86>()  was introduced in Linux 0.97p2.  In Linux 2.1.15 and 2.0.28, it was renamed to B<vm86old>(), and a new B<vm86>()  was introduced.  The definition of I<struct vm86_struct> was changed in 1.1.8 and 1.1.9."
+msgstr "B<vm86>()  システムコールは Linux 0.97p2 で導入された。 これは Linux 2.1.15 と 2.0.28 で B<vm86old>()  に名前が変更され、 新しい B<vm86>()  が導入された。 I<struct vm86_struct> の定義は 1.1.8 と 1.1.9 で変更された。"
 
 #. type: Plain text
 #: build/C/man2/vm86.2:52
-msgid ""
-"These calls cause the process to enter VM86 mode (virtual-8086 in Intel "
-"literature), and are used by B<dosemu>."
-msgstr ""
-"これらのコールによってプロセスは VM86 モード (Intel の文書では仮想 8086 モー"
-"ド) へと移行する。 これらのコールは B<dosemu> で使用される。"
+msgid "These calls cause the process to enter VM86 mode (virtual-8086 in Intel literature), and are used by B<dosemu>."
+msgstr "これらのコールによってプロセスは VM86 モード (Intel の文書では仮想 8086 モード) へと移行する。 これらのコールは B<dosemu> で使用される。"
 
 #. type: Plain text
 #: build/C/man2/vm86.2:54
 msgid "VM86 mode is an emulation of real mode within a protected mode task."
-msgstr ""
-"VM86 モードはプロテクトモードタスクにおける リアルモードのエミュレーションで"
-"ある。"
+msgstr "VM86 モードはプロテクトモードタスクにおける リアルモードのエミュレーションである。"
 
 #. type: Plain text
 #: build/C/man2/vm86.2:64
-msgid ""
-"This return value is specific to i386 and indicates a problem with getting "
-"user-space data."
-msgstr ""
-"この返り値は i386 固有のものであり、 ユーザー空間のデータを取得する際に問題が"
-"あったことを示す。"
+msgid "This return value is specific to i386 and indicates a problem with getting user-space data."
+msgstr "この返り値は i386 固有のものであり、 ユーザー空間のデータを取得する際に問題があったことを示す。"
 
 #. type: Plain text
 #: build/C/man2/vm86.2:68
-msgid ""
-"This return value indicates the call is not implemented on the present "
-"architecture."
-msgstr ""
-"この返り値は、このコールが現在のアーキテクチャで実装されていないことを示す。"
+msgid "This return value indicates the call is not implemented on the present architecture."
+msgstr "この返り値は、このコールが現在のアーキテクチャで実装されていないことを示す。"
 
 #. type: Plain text
 #: build/C/man2/vm86.2:73
-msgid ""
-"Saved kernel stack exists.  (This is a kernel sanity check; the saved stack "
-"should exist only within vm86 mode itself.)"
-msgstr ""
-"保存されたカーネルスタックが既に存在している。(これはカーネルが通常の 状態で"
-"あるかをチェックしている。保存されたスタックは vm86 モードで しか存在しな"
-"い。)"
+msgid "Saved kernel stack exists.  (This is a kernel sanity check; the saved stack should exist only within vm86 mode itself.)"
+msgstr "保存されたカーネルスタックが既に存在している。(これはカーネルが通常の 状態であるかをチェックしている。保存されたスタックは vm86 モードで しか存在しない。)"
 
 #. type: Plain text
 #: build/C/man2/vm86.2:76
-msgid ""
-"This call is specific to Linux on 32-bit Intel processors, and should not be "
-"used in programs intended to be portable."
-msgstr ""
-"この関数は 32 ビット Intel プロセッサ上の Linux 特有の関数であり、 移植を意図"
-"したプログラムでは使用すべきでない。"
+msgid "This call is specific to Linux on 32-bit Intel processors, and should not be used in programs intended to be portable."
+msgstr "この関数は 32 ビット Intel プロセッサ上の Linux 特有の関数であり、 移植を意図したプログラムでは使用すべきでない。"
 
 #. type: TH
 #: build/C/man2/vmsplice.2:26
@@ -13139,23 +10223,13 @@ msgstr ""
 #.  after a successful write), but that is often easy to do.
 #. type: Plain text
 #: build/C/man2/vmsplice.2:57
-msgid ""
-"The B<vmsplice>()  system call maps I<nr_segs> ranges of user memory "
-"described by I<iov> into a pipe.  The file descriptor I<fd> must refer to a "
-"pipe."
-msgstr ""
-"B<vmsplice>()  システムコールは、 I<iov> で指定されたユーザ・メモリの "
-"I<nr_segs> の範囲をパイプにマッピングする。 I<fd> はパイプを参照していなけれ"
-"ばならない。"
+msgid "The B<vmsplice>()  system call maps I<nr_segs> ranges of user memory described by I<iov> into a pipe.  The file descriptor I<fd> must refer to a pipe."
+msgstr "B<vmsplice>()  システムコールは、 I<iov> で指定されたユーザ・メモリの I<nr_segs> の範囲をパイプにマッピングする。 I<fd> はパイプを参照していなければならない。"
 
 #. type: Plain text
 #: build/C/man2/vmsplice.2:64
-msgid ""
-"The pointer I<iov> points to an array of I<iovec> structures as defined in "
-"I<E<lt>sys/uio.hE<gt>>:"
-msgstr ""
-"ポインタ I<iov> は I<iovec> 構造体の配列を指す。 I<iovec> 構造体は "
-"I<E<lt>sys/uio.hE<gt>> で以下のように定義されている:"
+msgid "The pointer I<iov> points to an array of I<iovec> structures as defined in I<E<lt>sys/uio.hE<gt>>:"
+msgstr "ポインタ I<iov> は I<iovec> 構造体の配列を指す。 I<iovec> 構造体は I<E<lt>sys/uio.hE<gt>> で以下のように定義されている:"
 
 #. type: Plain text
 #: build/C/man2/vmsplice.2:71
@@ -13178,12 +10252,8 @@ msgstr "B<vmsplice>()  では未使用。 B<splice>(2)  参照。"
 
 #. type: Plain text
 #: build/C/man2/vmsplice.2:97
-msgid ""
-"Currently has no effect for B<vmsplice>(), but may be implemented in the "
-"future; see B<splice>(2)."
-msgstr ""
-"現在のところ B<vmsplice>()  では何の効果もないが、将来的には実装される可能性"
-"がある。 B<splice>(2)  参照。"
+msgid "Currently has no effect for B<vmsplice>(), but may be implemented in the future; see B<splice>(2)."
+msgstr "現在のところ B<vmsplice>()  では何の効果もないが、将来的には実装される可能性がある。 B<splice>(2)  参照。"
 
 #.  FIXME . Explain the following line in a little more detail:
 #.  FIXME
@@ -13192,31 +10262,13 @@ msgstr ""
 #.  .... if we expect to later SPLICE_F_MOVE to the cache.
 #. type: Plain text
 #: build/C/man2/vmsplice.2:117
-msgid ""
-"The user pages are a gift to the kernel.  The application may not modify "
-"this memory ever, or page cache and on-disk data may differ.  Gifting pages "
-"to the kernel means that a subsequent B<splice>(2)  B<SPLICE_F_MOVE> can "
-"successfully move the pages; if this flag is not specified, then a "
-"subsequent B<splice>(2)  B<SPLICE_F_MOVE> must copy the pages.  Data must "
-"also be properly page aligned, both in memory and length."
-msgstr ""
-"ユーザ・ページがカーネルへ渡すもの (gift) であることを示す。 アプリケーション"
-"はこのメモリを絶対に変更してはならない。 さもなければ、ページキャッシュとディ"
-"スク上のデータは 一致しなくなるだろう。 ページをカーネルに渡すと、この次の "
-"B<splice>(2)  B<SPLICE_F_MOVE> でそのページの移動を行うことができる。 このフ"
-"ラグが指定されなかった場合、この次の B<splice>(2)  B<SPLICE_F_MOVE> でその"
-"ページのコピーを行わなければならない。 データはメモリ上でページ境界にあってい"
-"なければならず、 長さもページ境界の倍数でなければならない。"
+msgid "The user pages are a gift to the kernel.  The application may not modify this memory ever, or page cache and on-disk data may differ.  Gifting pages to the kernel means that a subsequent B<splice>(2)  B<SPLICE_F_MOVE> can successfully move the pages; if this flag is not specified, then a subsequent B<splice>(2)  B<SPLICE_F_MOVE> must copy the pages.  Data must also be properly page aligned, both in memory and length."
+msgstr "ユーザ・ページがカーネルへ渡すもの (gift) であることを示す。 アプリケーションはこのメモリを絶対に変更してはならない。 さもなければ、ページキャッシュとディスク上のデータは 一致しなくなるだろう。 ページをカーネルに渡すと、この次の B<splice>(2)  B<SPLICE_F_MOVE> でそのページの移動を行うことができる。 このフラグが指定されなかった場合、この次の B<splice>(2)  B<SPLICE_F_MOVE> でそのページのコピーを行わなければならない。 データはメモリ上でページ境界にあっていなければならず、 長さもページ境界の倍数でなければならない。"
 
 #. type: Plain text
 #: build/C/man2/vmsplice.2:126
-msgid ""
-"Upon successful completion, B<vmsplice>()  returns the number of bytes "
-"transferred to the pipe.  On error, B<vmsplice>()  returns -1 and I<errno> "
-"is set to indicate the error."
-msgstr ""
-"成功して完了すると、 B<vmsplice>()  はパイプに転送したバイト数を返す。 エラー"
-"の場合、 B<vmplice>()  は -1 を返し、 I<errno> をエラーを示す値に設定する。"
+msgid "Upon successful completion, B<vmsplice>()  returns the number of bytes transferred to the pipe.  On error, B<vmsplice>()  returns -1 and I<errno> is set to indicate the error."
+msgstr "成功して完了すると、 B<vmsplice>()  はパイプに転送したバイト数を返す。 エラーの場合、 B<vmplice>()  は -1 を返し、 I<errno> をエラーを示す値に設定する。"
 
 #. type: Plain text
 #: build/C/man2/vmsplice.2:137
@@ -13225,34 +10277,20 @@ msgstr "I<fd> が有効でない、もしくはパイプを参照していない
 
 #. type: Plain text
 #: build/C/man2/vmsplice.2:145
-msgid ""
-"I<nr_segs> is greater than B<IOV_MAX>; or memory not aligned if "
-"B<SPLICE_F_GIFT> set."
-msgstr ""
-"I<nr_segs> が B<IOV_MAX> よりも大きい。または B<SPLICE_F_GIFT> が設定されたが"
-"メモリがページ境界にあっていない。"
+msgid "I<nr_segs> is greater than B<IOV_MAX>; or memory not aligned if B<SPLICE_F_GIFT> set."
+msgstr "I<nr_segs> が B<IOV_MAX> よりも大きい。または B<SPLICE_F_GIFT> が設定されたがメモリがページ境界にあっていない。"
 
 #. type: Plain text
 #: build/C/man2/vmsplice.2:153
-msgid ""
-"The B<vmsplice>()  system call first appeared in Linux 2.6.17; library "
-"support was added to glibc in version 2.5."
+msgid "The B<vmsplice>()  system call first appeared in Linux 2.6.17; library support was added to glibc in version 2.5."
 msgstr ""
 "B<vmsplice>() システムコールは Linux 2.6.17 で初めて登場した。\n"
 "ライブラリによるサポートは glibc バージョン 2.5 で追加された。"
 
 #. type: Plain text
 #: build/C/man2/vmsplice.2:164
-msgid ""
-"B<vmsplice>()  follows the other vectorized read/write type functions when "
-"it comes to limitations on number of segments being passed in.  This limit "
-"is B<IOV_MAX> as defined in I<E<lt>limits.hE<gt>>.  At the time of this "
-"writing, that limit is 1024."
-msgstr ""
-"指定されたセグメント数が上限に達した場合、 B<vmsplice>()  は他のベクトル形式"
-"の read/write を行う関数と同じ動作をする。 上限は B<IOV_MAX> であり、 "
-"I<E<lt>limits.hE<gt>> で定義されている。 このドキュメントを書いた時点での値"
-"は 1024 である。"
+msgid "B<vmsplice>()  follows the other vectorized read/write type functions when it comes to limitations on number of segments being passed in.  This limit is B<IOV_MAX> as defined in I<E<lt>limits.hE<gt>>.  At the time of this writing, that limit is 1024."
+msgstr "指定されたセグメント数が上限に達した場合、 B<vmsplice>()  は他のベクトル形式の read/write を行う関数と同じ動作をする。 上限は B<IOV_MAX> であり、 I<E<lt>limits.hE<gt>> で定義されている。 このドキュメントを書いた時点での値は 1024 である。"
 
 #. type: Plain text
 #: build/C/man2/vmsplice.2:167
@@ -13265,9 +10303,7 @@ msgstr "B<splice>(2), B<tee>(2)"
 #~ msgid "B<PERF_RECORD_MISC_MMAP_DATA>"
 #~ msgstr "B<PERF_RECORD_MISC_MMAP_DATA>"
 
-#~ msgid ""
-#~ "These system calls were added in Linux 2.6.17.  No library support is "
-#~ "provided; use B<syscall>(2)."
+#~ msgid "These system calls were added in Linux 2.6.17.  No library support is provided; use B<syscall>(2)."
 #~ msgstr ""
 #~ "これらのシステムコールは Linux 2.6.17 で追加された。ライブラリによる\n"
 #~ "サポートは提供されていない。 B<syscall>(2) を使うこと。"
@@ -13296,136 +10332,47 @@ msgstr "B<splice>(2), B<tee>(2)"
 #~ msgid "2012-04-25"
 #~ msgstr "2012-04-25"
 
-#~ msgid ""
-#~ "This function will return the current B<personality>()  when I<persona> "
-#~ "equals 0xffffffff.  Otherwise, it will make the execution domain "
-#~ "referenced by I<persona> the new execution domain of the calling process."
-#~ msgstr ""
-#~ "B<personality ()> 関数は、 I<persona> が 0xffffffff の場合は現在の B<パー"
-#~ "ソナリティ> を返す。 それ以外の場合、 I<persona> により参照される実行ドメ"
-#~ "インを、 呼び出し元のプロセスの新しい実行ドメインとする。"
+#~ msgid "This function will return the current B<personality>()  when I<persona> equals 0xffffffff.  Otherwise, it will make the execution domain referenced by I<persona> the new execution domain of the calling process."
+#~ msgstr "B<personality ()> 関数は、 I<persona> が 0xffffffff の場合は現在の B<パーソナリティ> を返す。 それ以外の場合、 I<persona> により参照される実行ドメインを、 呼び出し元のプロセスの新しい実行ドメインとする。"
 
-#~ msgid ""
-#~ "Depending on which operation was executed, the returned value for a "
-#~ "successful call can have differing meanings."
+#~ msgid "Depending on which operation was executed, the returned value for a successful call can have differing meanings."
 #~ msgstr "どの操作が実行されたかによって、 成功時の返り値の意味が変わる。"
 
-#~ msgid ""
-#~ "Returns 0 if the process was woken by a B<FUTEX_WAKE> call.  In case of "
-#~ "timeout, the operation fails with the error B<ETIMEDOUT>.  If the futex "
-#~ "was not equal to the expected value, the operation fails with the error "
-#~ "B<EWOULDBLOCK>.  Signals (see B<signal>(7))  or other spurious wakeups "
-#~ "cause B<FUTEX_WAIT> to fail with the error B<EINTR>."
-#~ msgstr ""
-#~ "プロセスが B<FUTEX_WAKE> の呼び出しで wake すると 0 を返す。 タイムアウト"
-#~ "の場合、操作はエラー B<ETIMEOUT> で失敗する。 futex が指定された値と等しく"
-#~ "ない場合、 エラー B<EWOULDBLOCK> で失敗する。 シグナルを受信するか "
-#~ "(B<signal>(7)  参照) 他の偽の wake があった場合には、エラー B<EINTR> で失"
-#~ "敗する。"
+#~ msgid "Returns 0 if the process was woken by a B<FUTEX_WAKE> call.  In case of timeout, the operation fails with the error B<ETIMEDOUT>.  If the futex was not equal to the expected value, the operation fails with the error B<EWOULDBLOCK>.  Signals (see B<signal>(7))  or other spurious wakeups cause B<FUTEX_WAIT> to fail with the error B<EINTR>."
+#~ msgstr "プロセスが B<FUTEX_WAKE> の呼び出しで wake すると 0 を返す。 タイムアウトの場合、操作はエラー B<ETIMEOUT> で失敗する。 futex が指定された値と等しくない場合、 エラー B<EWOULDBLOCK> で失敗する。 シグナルを受信するか (B<signal>(7)  参照) 他の偽の wake があった場合には、エラー B<EINTR> で失敗する。"
 
 #~ msgid "An operation was not defined or error in page alignment."
-#~ msgstr ""
-#~ "操作が定義されていない。またはページ・アラインメントでエラーが発生した。"
+#~ msgstr "操作が定義されていない。またはページ・アラインメントでエラーが発生した。"
 
-#~ msgid ""
-#~ "Stop the child at the next B<execve>(2)  call with I<SIGTRAP | "
-#~ "PTRACE_EVENT_EXEC\\ E<lt>E<lt>\\ 8>."
-#~ msgstr ""
-#~ "次の B<execve>(2)  呼び出し時に I<SIGTRAP | PTRACE_EVENT_EXEC\\ E<lt>E<lt>"
-#~ "\\ 8> で子プロセスの動作を停止させる。"
+#~ msgid "Stop the child at the next B<execve>(2)  call with I<SIGTRAP | PTRACE_EVENT_EXEC\\ E<lt>E<lt>\\ 8>."
+#~ msgstr "次の B<execve>(2)  呼び出し時に I<SIGTRAP | PTRACE_EVENT_EXEC\\ E<lt>E<lt>\\ 8> で子プロセスの動作を停止させる。"
 
-#~ msgid ""
-#~ "Stop the child at the completion of the next B<vfork>(2)  call with "
-#~ "I<SIGTRAP | PTRACE_EVENT_VFORK_DONE\\ E<lt>E<lt>\\ 8>."
-#~ msgstr ""
-#~ "次の B<vfork>(2)  呼び出し時に I<SIGTRAP | PTRACE_EVENT_VFORK_DONE\\ "
-#~ "E<lt>E<lt>\\ 8> で子プロセスの動作を停止させる。"
-
-#~ msgid ""
-#~ "Attaches to the process specified in I<pid>, making it a traced \"child\" "
-#~ "of the calling process; the behavior of the child is as if it had done a "
-#~ "B<PTRACE_TRACEME>.  The calling process actually becomes the parent of "
-#~ "the child process for most purposes (e.g., it will receive notification "
-#~ "of child events and appears in B<ps>(1)  output as the child's parent), "
-#~ "but a B<getppid>(2)  by the child will still return the PID of the "
-#~ "original parent.  The child is sent a B<SIGSTOP>, but will not "
-#~ "necessarily have stopped by the completion of this call; use B<wait>(2)  "
-#~ "to wait for the child to stop.  (I<addr> and I<data> are ignored.)"
-#~ msgstr ""
-#~ "I<pid> で指定されたプロセスに接続 (attach) し、それを呼び出し元のプロセス"
-#~ "の 子プロセスとしてトレースできるようにする。子プロセスは "
-#~ "B<PTRACE_TRACEME> したかのように振舞う。呼び出し元のプロセスはそのほとんど"
-#~ "の目的において、 その子プロセスの実際の親になる (例えば、子プロセスのイベ"
-#~ "ントの 通知を受けとったり、 B<ps>(1)  で親として表示されたりする)。しか"
-#~ "し、子プロセスで B<getppid>(2)  を実行した場合には元の親プロセスの PID が"
-#~ "返される。 子プロセスには B<SIGSTOP> が送られるが、この呼び出しが完了する"
-#~ "までに 必ずしも停止するとは限らない。子プロセスの停止を待つには "
-#~ "B<wait>(2)  を使用すること。(I<addr> と I<data> は無視される。)"
-
-#~ msgid ""
-#~ "Tracing causes a few subtle differences in the semantics of traced "
-#~ "processes.  For example, if a process is attached to with "
-#~ "B<PTRACE_ATTACH>, its original parent can no longer receive notification "
-#~ "via B<wait>(2)  when it stops, and there is no way for the new parent to "
-#~ "effectively simulate this notification."
-#~ msgstr ""
-#~ "トレースすることによってトレースされるプロセスの動作に些細な違いが 起こる"
-#~ "ことがある。例えば、プロセスが B<PTRACE_ATTACH> によって接続された場合に"
-#~ "は、そのプロセスが停止した時でも本来の親は B<wait>(2)  を使って通知を受け"
-#~ "ることができず、新しい親が効率よく この通知を真似る方法もない。"
-
-#~ msgid ""
-#~ "When the parent receives an event with B<PTRACE_EVENT_*> set, the child "
-#~ "is not in the normal signal delivery path.  This means the parent cannot "
-#~ "do B<ptrace>(PTRACE_CONT)  with a signal or B<ptrace>(PTRACE_KILL).  "
-#~ "B<kill>(2)  with a B<SIGKILL> signal can be used instead to kill the "
-#~ "child process after receiving one of these messages."
-#~ msgstr ""
-#~ "親プロセスが B<PTRACE_EVENT_*> がセットされたイベントを受信した場合、 子プ"
-#~ "ロセスは通常通りのシグナル配送が行われる状態にない。 つまり、親プロセス"
-#~ "が、 シグナルにより B<ptrace>(PTRACE_CONT)  を行ったり、 "
-#~ "B<ptrace>(PTRACE_KILL)  を行ったりできないということである。 こららのメッ"
-#~ "セージの受信後は、子プロセスを終了 (kill) するのに、 シグナル B<SIGKILL> "
-#~ "を指定して B<kill>(2)  を行う方法を代わりに使用できる。"
-
-#~ msgid ""
-#~ "The SunOS man page describes B<ptrace>()  as \"unique and arcane\", which "
-#~ "it is.  The proc-based debugging interface present in Solaris 2 "
-#~ "implements a superset of B<ptrace>()  functionality in a more powerful "
-#~ "and uniform way."
-#~ msgstr ""
-#~ "SunOS のマニュアル・ページには B<ptrace>()  は「独特で不可解」と記述されて"
-#~ "おり、まさしくそうである。 Solaris 2 では proc ベースの デバッグのインター"
-#~ "フェースとして B<ptrace>()  の上位互換関数が実装され、より強力で一貫性のあ"
-#~ "るものとなっている。"
-
-#~ msgid ""
-#~ "The second argument I<special> is the block special device these quota "
-#~ "apply to.  It must be mounted."
-#~ msgstr ""
-#~ "二番目の引き数 I<special> は quota を適用するデバイスのブロック・スペシャ"
-#~ "ル・ファイルである。 そのデバイスはマウントされていなくてはならない。"
+#~ msgid "Stop the child at the completion of the next B<vfork>(2)  call with I<SIGTRAP | PTRACE_EVENT_VFORK_DONE\\ E<lt>E<lt>\\ 8>."
+#~ msgstr "次の B<vfork>(2)  呼び出し時に I<SIGTRAP | PTRACE_EVENT_VFORK_DONE\\ E<lt>E<lt>\\ 8> で子プロセスの動作を停止させる。"
 
-#~ msgid ""
-#~ "The third argument I<id> is the user or group ID these quota apply to "
-#~ "(when relevant)."
-#~ msgstr ""
-#~ "三番目の引き数 I<id> には、(必要な場合に) quota を適用するユーザーもしくは"
-#~ "グループの ID を指定する。"
+#~ msgid "Attaches to the process specified in I<pid>, making it a traced \"child\" of the calling process; the behavior of the child is as if it had done a B<PTRACE_TRACEME>.  The calling process actually becomes the parent of the child process for most purposes (e.g., it will receive notification of child events and appears in B<ps>(1)  output as the child's parent), but a B<getppid>(2)  by the child will still return the PID of the original parent.  The child is sent a B<SIGSTOP>, but will not necessarily have stopped by the completion of this call; use B<wait>(2)  to wait for the child to stop.  (I<addr> and I<data> are ignored.)"
+#~ msgstr "I<pid> で指定されたプロセスに接続 (attach) し、それを呼び出し元のプロセスの 子プロセスとしてトレースできるようにする。子プロセスは B<PTRACE_TRACEME> したかのように振舞う。呼び出し元のプロセスはそのほとんどの目的において、 その子プロセスの実際の親になる (例えば、子プロセスのイベントの 通知を受けとったり、 B<ps>(1)  で親として表示されたりする)。しかし、子プロセスで B<getppid>(2)  を実行した場合には元の親プロセスの PID が返される。 子プロセスには B<SIGSTOP> が送られるが、この呼び出しが完了するまでに 必ずしも停止するとは限らない。子プロセスの停止を待つには B<wait>(2)  を使用すること。(I<addr> と I<data> は無視される。)"
 
-#~ msgid ""
-#~ "The fourth argument I<addr> is the address of a data structure, depending "
-#~ "on the command."
-#~ msgstr ""
-#~ "四番目の引き数 I<addr> には、コマンドごとに異ったデータ構造体のアドレスを"
-#~ "指定する。"
+#~ msgid "Tracing causes a few subtle differences in the semantics of traced processes.  For example, if a process is attached to with B<PTRACE_ATTACH>, its original parent can no longer receive notification via B<wait>(2)  when it stops, and there is no way for the new parent to effectively simulate this notification."
+#~ msgstr "トレースすることによってトレースされるプロセスの動作に些細な違いが 起こることがある。例えば、プロセスが B<PTRACE_ATTACH> によって接続された場合には、そのプロセスが停止した時でも本来の親は B<wait>(2)  を使って通知を受けることができず、新しい親が効率よく この通知を真似る方法もない。"
 
-#~ msgid ""
-#~ "Enable quota.  The I<addr> argument is the pathname of the file "
-#~ "containing the quota for the file system."
-#~ msgstr ""
-#~ "quota を有効にする。 I<addr> 引き数には、そのファイル・システムの quota が"
-#~ "記録されているファイルの パス名を指定する。"
+#~ msgid "When the parent receives an event with B<PTRACE_EVENT_*> set, the child is not in the normal signal delivery path.  This means the parent cannot do B<ptrace>(PTRACE_CONT)  with a signal or B<ptrace>(PTRACE_KILL).  B<kill>(2)  with a B<SIGKILL> signal can be used instead to kill the child process after receiving one of these messages."
+#~ msgstr "親プロセスが B<PTRACE_EVENT_*> がセットされたイベントを受信した場合、 子プロセスは通常通りのシグナル配送が行われる状態にない。 つまり、親プロセスが、 シグナルにより B<ptrace>(PTRACE_CONT)  を行ったり、 B<ptrace>(PTRACE_KILL)  を行ったりできないということである。 こららのメッセージの受信後は、子プロセスを終了 (kill) するのに、 シグナル B<SIGKILL> を指定して B<kill>(2)  を行う方法を代わりに使用できる。"
+
+#~ msgid "The SunOS man page describes B<ptrace>()  as \"unique and arcane\", which it is.  The proc-based debugging interface present in Solaris 2 implements a superset of B<ptrace>()  functionality in a more powerful and uniform way."
+#~ msgstr "SunOS のマニュアル・ページには B<ptrace>()  は「独特で不可解」と記述されており、まさしくそうである。 Solaris 2 では proc ベースの デバッグのインターフェースとして B<ptrace>()  の上位互換関数が実装され、より強力で一貫性のあるものとなっている。"
+
+#~ msgid "The second argument I<special> is the block special device these quota apply to.  It must be mounted."
+#~ msgstr "二番目の引き数 I<special> は quota を適用するデバイスのブロック・スペシャル・ファイルである。 そのデバイスはマウントされていなくてはならない。"
+
+#~ msgid "The third argument I<id> is the user or group ID these quota apply to (when relevant)."
+#~ msgstr "三番目の引き数 I<id> には、(必要な場合に) quota を適用するユーザーもしくはグループの ID を指定する。"
+
+#~ msgid "The fourth argument I<addr> is the address of a data structure, depending on the command."
+#~ msgstr "四番目の引き数 I<addr> には、コマンドごとに異ったデータ構造体のアドレスを指定する。"
+
+#~ msgid "Enable quota.  The I<addr> argument is the pathname of the file containing the quota for the file system."
+#~ msgstr "quota を有効にする。 I<addr> 引き数には、そのファイル・システムの quota が記録されているファイルの パス名を指定する。"
 
 #~ msgid "Disable quota."
 #~ msgstr "quota を無効にする。"
@@ -13445,12 +10392,8 @@ msgstr "B<splice>(2), B<tee>(2)"
 #~ msgid "Get collected stats."
 #~ msgstr "収集された統計を取得する。"
 
-#~ msgid ""
-#~ "On success, B<quotactl>()  returns 0.  On error, -1 is returned, and "
-#~ "I<errno> is set appropriately."
-#~ msgstr ""
-#~ "B<quotactl>()  は、成功時には 0 を返す。エラー時は、-1 を返すとともに、 "
-#~ "I<errno> が適切な値に設定される。"
+#~ msgid "On success, B<quotactl>()  returns 0.  On error, -1 is returned, and I<errno> is set appropriately."
+#~ msgstr "B<quotactl>()  は、成功時には 0 を返す。エラー時は、-1 を返すとともに、 I<errno> が適切な値に設定される。"
 
 #~ msgid "B<Q_QUOTAON> was asked, but quotas were enabled already."
 #~ msgstr "B<Q_QUOTAON> の要求がなされたが、quota(s) は既に有効になっている。"
@@ -13458,11 +10401,8 @@ msgstr "B<splice>(2), B<tee>(2)"
 #~ msgid "Bad I<addr> value."
 #~ msgstr "I<addr> の値に誤りがある。"
 
-#~ msgid ""
-#~ "I<type> is not a known quota type.  Or, I<special> could not be found."
-#~ msgstr ""
-#~ "I<type> が既知の quota の形式ではない。もしくは、 I<special> デバイスが見"
-#~ "付からなかった。"
+#~ msgid "I<type> is not a known quota type.  Or, I<special> could not be found."
+#~ msgstr "I<type> が既知の quota の形式ではない。もしくは、 I<special> デバイスが見付からなかった。"
 
 #~ msgid "Too many open files: cannot open quota file."
 #~ msgstr "ファイルをオープンしすぎている: quota ファイルをオープン出来ない。"
@@ -13473,18 +10413,8 @@ msgstr "B<splice>(2), B<tee>(2)"
 #~ msgid "The kernel was compiled without quota support."
 #~ msgstr "quota を使用可にしてカーネルをコンパイルしていない。"
 
-#~ msgid ""
-#~ "The process was not root (for the file system), and B<Q_GETQUOTA> was "
-#~ "asked for another I<id> than that of the process itself, or anything "
-#~ "other than B<Q_GETSTATS> or B<Q_SYNC> was asked."
-#~ msgstr ""
-#~ "プロセスが (そのファイル・システムの) root のものではなく、 かつプロセス自"
-#~ "身のものとは異なる I<id> に対して B<Q_GETQUOTA> 要求を行なった。 もしく"
-#~ "は、 B<Q_GETSTATS>, B<Q_SYNC> 以外の要求がなされた。"
+#~ msgid "The process was not root (for the file system), and B<Q_GETQUOTA> was asked for another I<id> than that of the process itself, or anything other than B<Q_GETSTATS> or B<Q_SYNC> was asked."
+#~ msgstr "プロセスが (そのファイル・システムの) root のものではなく、 かつプロセス自身のものとは異なる I<id> に対して B<Q_GETQUOTA> 要求を行なった。 もしくは、 B<Q_GETSTATS>, B<Q_SYNC> 以外の要求がなされた。"
 
-#~ msgid ""
-#~ "B<Q_GETQUOTA> or B<Q_SETQUOTA> or B<Q_SETUSE> or B<Q_SETQLIM> was asked "
-#~ "for a file system that didn't have quota enabled."
-#~ msgstr ""
-#~ "quota が有効になっていないファイル・システムに対して B<Q_GETQUOTA>, "
-#~ "B<Q_SETQUOTA>, B<Q_SETUSE>, B<Q_SETQLIM> のいずれかの要求がなされた。"
+#~ msgid "B<Q_GETQUOTA> or B<Q_SETQUOTA> or B<Q_SETUSE> or B<Q_SETQLIM> was asked for a file system that didn't have quota enabled."
+#~ msgstr "quota が有効になっていないファイル・システムに対して B<Q_GETQUOTA>, B<Q_SETQUOTA>, B<Q_SETUSE>, B<Q_SETQLIM> のいずれかの要求がなされた。"