[debian-doc 00086] po4a (pod part2 po4a.7.pod分)

victory victory.deb @ gmail.com
2019年 1月 24日 (木) 17:48:57 JST

#: doc/po4a.7.pod:53
msgid ""
"Po4a can also handle some more rare or specialized formats, such as the "
"documentation of compilation options for the 2.4+ Linux kernels or the "
"diagrams produced by the dia tool. Adding a new one is often very easy and "
"the main task is to come up with a parser of your target format. See "
"L<Locale::Po4a::TransTractor(3pm)> for more information about this."
msgstr ""
"po4a は、カーネル 2.4 以降のコンパイルオプションのドキュメントや、dia ツール"
"のが主なタスクとなっています。この詳細情報は L<Locale::Po4a::"
"TransTractor(3pm)> を参照してください。"

#: doc/po4a.7.pod:117
msgid ""
"So, when the same paragraph appears twice in the original but both are not "
"translated in the exact same way each time, you will get the feeling that a "
"paragraph of the original disappeared. Just kill the new translation. If you "
"prefer to kill the first translation instead when the second one was "
"actually better, replace the first one with the second."
msgstr ""

最初変更 最後追加
#: doc/po4a.7.pod:126
msgid ""
"The header line which specify context has a pretty rigid syntax: It must "
"begin with the string B<PO4A-HEADER:>, followed by a semi-colon (B<;>) "
"separated list of I<key>B<=>I<value> fields. White spaces ARE important. "
"Note that you cannot use the semi-colon char (B<;>) in the value, and that "
"quoting it doesn't help.  Optionally, spaces (B< >) may be inserted before "
"I<key> for readability."
msgstr ""
"HEADER:> で始めなければならず、セミコロン (B<;>) 区切りの I<key>B<=>I<value> "
"フィールドが続きます。空白が重要です。値にはセミコロン (B<;>) を使えません。"
"引用符で囲んでも使えないことに注意してください。また、I<key>の前に空白 (B< "
">) を入れて見やすいように整形することもできます。"

#: doc/po4a.7.pod:127
msgid ""
"Although this context search may be considered to operate roughly on each "
"line of the translated document, it actually operates on the internal data "
"string of the translated document.  This internal data string may be a text "
"spanning a paragraph containing multiple lines or may be a XML tag itself "
"alone.  The exact I<insertion point> of the addendum must be before or after "
"the internal data string and can not be within the internal data string."
msgstr ""
"字列は複数の行を含む段落全文であったり、あるいは XML のタグ一つだけであったり"

#: doc/po4a.7.pod:128
msgid ""
"The actual internal data string of the translated document can be visualized "
"by executing po4a in debug mode."
msgstr ""
"po4a をデバッグモードで実行することで翻訳後文書の実際の内部データ文字列を確認"

#: doc/po4a.7.pod:132
msgid "It can be either the string B<before> or B<after>."
msgstr "この値には  B<before> か B<after> のどちらかの文字列を指定できます。"

#: doc/po4a.7.pod:133
msgid ""
"If B<mode=before>, the I<insertion point> is determined by one step regex "
"match specified by the B<position> argument regex.  The I<insertion point> "
"is immediately before the uniquely matched internal data string of the "
"translated document."
msgstr ""
"B<mode=before> の場合、I<追加位置>は B<position> 引数で指定された正規表現によ"

#: doc/po4a.7.pod:134
msgid ""
"If B<mode=after>, the I<insertion point> is determined by two step regex "
"matches specified by the B<position> argument regex; and by the "
"B<beginboundary> or B<endboundary> argument regex."
msgstr ""
"B<mode=after> の場合、I<追加位置>は B<position> 引数で指定された正規表現と、"
"B<beginboundary> または B<endboundary> 引数で指定された正規表現の二段階の正規"

#: doc/po4a.7.pod:135
msgid ""
"Since there may be multiple sections for the assumed case, let's use 2 step "
msgstr ""

#: doc/po4a.7.pod:138
msgid "A Perl regexp for specifying the context."
msgstr "文脈を特定するための Perl の正規表現を指定します。"

#: doc/po4a.7.pod:139
msgid ""
"If more than one internal data strings match this expression (or none), the "
"search for the I<insertion point> and addition of the addendum will fail. It "
"is indeed better to report an error than inserting the addendum at the wrong "
msgstr ""
"この正規表現に該当する内部データ文字列が複数ある (もしくはない) 場合、I<追加"

#: doc/po4a.7.pod:140
msgid ""
"If B<mode=before>, the I<insertion point> is specified to be immediately "
"before the internal data string uniquely matching the B<position> argument "
msgstr ""
"B<mode=before> の場合、I<追加位置>は翻訳後文書の内部データ文字列で "
"B<position> 引数で指定された正規表現と一意に該当した部分の直前で確定します。"

#: doc/po4a.7.pod:141
msgid ""
"If B<mode=after>, the search for the I<insertion point> is narrowed down to "
"the data after the internal data string uniquely matching the B<position> "
"argument regex.  The exact I<insertion point> is further specified by the "
"B<beginboundary> or B<endboundary>."
msgstr ""
"B<mode=after> の場合、I<追加位置>の検索は B<position> 引数の正規表現と一意に"
"該当する内部データ文字列の後に絞り込まれます。実際のI<追加位置>は "
"B<beginboundary> か B<endboundary> でさらに特定します。"

#: doc/po4a.7.pod:142
msgid ""
"In our case, we need to skip several preceding sections by narrowing down "
"search using the section title string."
msgstr ""

#: doc/po4a.7.pod:144
msgid ""
"(In reality, you need to use the translated section title string here, "
msgstr "(実際には、原文ではなく翻訳後の節タイトル文字列を使う必要があります)"

#: doc/po4a.7.pod:147
msgid ""
"A second Perl regexp required only when B<mode=after>. The addendum will be "
"placed immediately before or after the first internal data string matching "
"the B<beginboundary> or B<endboundary> argument regexp, respectively."
msgstr ""
"二度目の Perl 正規表現で、B<mode=after> の場合にのみ必要となります。追加内容"
"は B<beginboundary> または B<endboundary> 引数の正規表現に該当する最初の内部"

#: doc/po4a.7.pod:159
msgid ""
"You should select two step approach by setting B<mode=after>.  Then you "
"should narrow down search to the line after B<AUTHORS> with the B<position> "
"argument regex.  Then, you should match the beginning of the next section (i."
"e., B<^\\.SH>) with the B<beginboundary> argument regex. That is to say:"
msgstr ""
"B<mode=after> を指定する二段階の方法を選択する必要があります。それから "
"B<position> 引数の正規表現で B<AUTHORS> の後の行を検索するように絞り込む必要"
"があります。それからさらに B<beginboundary> 引数の正規表現を次の節 (つまり "
"B<^\\.SH>) に該当させる必要があります。このようになります:"

#: doc/po4a.7.pod:176
msgid ""
"This works because the next line matching the B<beginboundary> /^=head1/ "
"after the section \"NAME\" (translated to \"NOM\" in French), is the one "
"declaring the authors. So, the addendum will be put between both sections. "
"Note that if another section is added between NAME and AUTHOR sections "
"later, po4a will wrongfully put the addenda before the new section."
msgstr ""
"これは、\"NAME\" 節 (フランス語では \"NOM\") の後にある B<beginboundary> /"
"^=head1/ にマッチした次の行が作者を定義している、ということで動作します。その"
"ため、両方の節の間に追加内容が挿入されます。この名前 (NAME) 節と作者 "
"(AUTHOR) 節の間に別の節が追加されてしまうと、po4a は誤って新しい節の前に追加"

#: doc/po4a.7.pod:177
msgid "To avoid this you may accomplish the same using B<mode>=I<before>:"
msgstr ""
"これを避けるために B<mode>=I<before> を使って同一の結果を得ることもできます:"

#: doc/po4a.7.pod:185
msgid ""
"You can also edit the source code of the existing modules or even write your "
"own modules. To make them visible to po4a, copy your modules into a path "
"called C</bli/blah/blu/lib/Locale/Po4a/> and then adding the path C</bli/"
"blah/blu> in the C<PERLIB> or C<PERL5LIB> environment variable. For example:"
msgstr ""
"ます。po4a から見えるようにするには、そのモジュールを C</bli/blah/blu/lib/"
"Locale/Po4a/> のようなパスにコピーしてパス C</bli/blah/blu> を C<PERLLIB> ま"
"たは C<PERL5LIB> 環境変数に追加します。例えば:"

#: doc/po4a.7.pod:194
msgid ""
"This little bone is the core of all the po4a architecture. If you omit the "
"input PO and the output document, you get B<po4a-gettextize>. If you provide "
"both input and disregard the output PO, you get B<po4a-translate>.  The "
"B<po4a> calls TransTractor twice and calls B<msgmerge -U> between these "
"TransTractor invocations to provide one-stop solution with a single "
"configuration file."
msgstr ""
"この小さな骨状の絵は、po4a アーキテクチャのすべてのコアを表しています。入力 "
"PO や出力ドキュメントを省略すると、B<po4a-gettextize> になります。両方の入力"
"を行い、出力 PO を無視すると、B<po4a-translate> になります。B<po4a> は "
"TransTractor を二度呼び出し、その中間で B<msgmerge -U> を呼び出すことで、一つ"

#: doc/po4a.7.pod:197
msgid ""
"On line 6 and 7, we encounter C<shiftline()> and C<unshiftline()>.  These "
"help you to read and unread the head of internal input data stream of master "
"document into the line string and its reference.  Here, the reference is "
"provided by a string C<< $filename:$linenum >>.  Please remember Perl only "
"has one dimensional array data structure.  So codes handling the internal "
"input data stream line are a bit cryptic."
msgstr ""
"6行目と7行目に C<shiftline()> と C<unshiftline()> があります。この2つの関数は"
"して取り出す/戻す処理を支援します。参照情報は C<< $filename:$linenum >> 形式"
"の文字列として提供されます。Perl には一面的なデータ構造の配列しかないことに注"

"po4a" というプロジェクト(=po4a.org)ではないと思う
#: doc/po4a.7.pod:256
msgid ""
"In the po4a project, translated documents are not source files anymore, in "
"the sense that these files are not the preferred form of the work for making "
"modifications to it. Since this is rather unconventional, that's a source of "
"easy mistakes. That's why all files present this header:"
msgstr ""
"po4a のプロジェクトでは、変更を加える作業にとって望ましい形式ではないという意"

#: doc/po4a.7.pod:281
msgid ""
"One of my dreams would be to integrate somehow po4a to Gtranslator or "
"Lokalize. When a documentation file is opened, the strings are automatically "
"extracted, and a translated file + po file can be written to disk. If we "
"manage to do an MS Word (TM) module (or at least RTF) professional "
"translators may even use it."
msgstr ""
"私の夢の一つは Gtranslator や Lokalize に何らかの形で統合することです。文書"
"ファイルを開くと、文字列を自動的に抽出し、保存すると、翻訳済みファイルと po "
"ファイルをディスクに書き込むことができる。MS Word (TM) モジュール (少なくと"
"も RTF) でこれができれば、プロの翻訳家もこれを使ってくれるかも知れません。"


debian-doc メーリングリストの案内