[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

cgiemail 1.6-32.1: Please update debconf PO translation for the package cgiemail


A l10n NMU will happen on cgiemail pretty soon.

A round of translation updates is being launched to give all translators
a chance to get their translations in for that package.

Please send the updated file as a wishlist bug against the package.

The deadline for receiving the updated translation is
Tuesday, May 27, 2008.


#    Translators, if you are not familiar with the PO format, gettext
#    documentation is worth reading, especially sections dedicated to
#    this format, e.g. by running:
#         info -n '(gettext)PO Files'
#         info -n '(gettext)Header Entry'
#    Some information specific to po-debconf are available at
#            /usr/share/doc/po-debconf/README-trans
#         or http://www.debian.org/intl/l10n/po-debconf/README-trans
#    Developers do not need to manually edit POT or PO files.
msgid ""
msgstr ""
"Project-Id-Version: cgiemail_1.6-22\n"
"Report-Msgid-Bugs-To: cgiemail@packages.debian.org\n"
"POT-Creation-Date: 2008-05-08 10:39+0200\n"
"PO-Revision-Date: 2004-09-11 14:54+0900\n"
"Last-Translator: Hideki Yamane <henrich@samba.gr.jp>\n"
"Language-Team: Japanese <debian-japanese@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=EUC-JP\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: string
#. Description
#: ../templates:1001
#, fuzzy
msgid "Directory where you want to put the cgiemail's mail templates:"
msgstr "cgimail のメールテンプレートをどこに配置しますか?"

#. Type: string
#. Description
#: ../templates:1001
msgid ""
"In old versions of cgiemail, templates that were used for creating e-mails "
"to be sent could be placed anywhere that would be served up by the web "
"server.  This behaviour is a security vulnerability: an attacker can read "
"files that he shouldn't be able to, such as scripts in cgi-bin, if they "
"contain certain pieces of text."
msgstr ""
"cgiemail の以前のバージョンでは、送信されるメールの作成に使われるテンプレート"
"は、web サーバが使用するディレクトリならどこにでも配置できました。この挙動は"
"セキュリティ上の脆弱性となります: テンプレートがある種の文字列を含んでいた場"
"合、cgi-bin にあるスクリプトのような読めるべきではないファイルを攻撃者が読め"

#. Type: string
#. Description
#: ../templates:1001
msgid ""
"If you enter nothing (that is, erase the default directory, leaving this "
"empty), cgiemail will still work. This may be needed if you are, for "
"instance, hosting web services, and cannot move all of your clients cgiemail "
"templates to one directory.  Remember that this will LEAVE THE SECURITY HOLE "
"OPEN, and is only a choice for backwards compatibility."
msgstr ""
"何も入力しない場合 (つまり、デフォルトのディレクトリを消去し、これを空のまま"
"にする場合)、それでも cgiemail は動作します。もし、例えばあなたがホスティング"
"サービスを行っており、クライアント全ての cgiemail テンプレートを一つのディレ"

#. Type: string
#. Description
#: ../templates:1001
msgid ""
"To close the hole, enter a directory, which MUST be accessible by your web "
"server.  Template files that you want to use should go there. For further "
"instructions, please read the README.Debian and README files in /usr/share/"
msgstr ""
"この脆弱性を封じるには、ディレクトリ名を入力してください。これは web サーバか"
"に置かなければなりません。より詳細な説明については、/usr/share/doc/cgiemail/ "
"の README.Debian と README ファイルを読んでください。"

Reply to: