[pkg-kolab] Bug#393213: kolab-cyrus-common: [INTL:ja] Updated
Japanese po-debconf template translation (ja.po)
Hideki Yamane (Debian-JP)
henrich at debian.or.jp
Sun Oct 15 15:10:02 UTC 2006
Package: kolab-cyrus-common
Version: 2.2.12
Severity: wishlist
Tags: patch l10n
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear maintainer,
Here's updated Japanese po-debconf template (ja.po) file that
reviewed by several Japanese Debian developers and users.
Could you apply it, please?
- --
Regards,
Hideki Yamane henrich @ debian.or.jp/samba.gr.jp/iijmio-mail.jp
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFMk9KIu0hy8THJksRAmQ1AJ4sjjEpOM9CYbptl67AMlAULX5xeQCghsiF
meKmtWVMuVPln4Nnl488a7U=
=TQCO
-----END PGP SIGNATURE-----
-------------- next part --------------
#
# 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: kolab-cyrus-imapd 2.2.12-7\n"
"Report-Msgid-Bugs-To: pkg-kolab-devel at lists.alioth.debian.org\n"
"POT-Creation-Date: 2006-03-31 14:55+0200\n"
"PO-Revision-Date: 2006-10-15 13:52+0900\n"
"Last-Translator: Hideki Yamane (Debian-JP) <henrich at debian.or.jp>\n"
"Language-Team: Japanese <debian-japanese at lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: note
#. Description
#: ../kolab-cyrus-common.templates:3
msgid "Database backends have changed!"
msgstr "?????????????????????!"
#. Type: note
#. Description
#: ../kolab-cyrus-common.templates:3
msgid ""
"Comparation between /usr/lib/cyrus/cyrus-db-types.txt and /usr/lib/cyrus/"
"cyrus-db-types.active shows that database backends for Cyrus IMAPd have been "
"changed."
msgstr ""
"/usr/lib/cyrus/cyrus-db-types.txt ? /usr/lib/cyrus/cyrus-db-types.active ?"
"??????? Cyrus IMAPd ?????????????????"
#. Type: note
#. Description
#: ../kolab-cyrus-common.templates:3
msgid ""
"This means that those databases for which the database backends changed "
"might need to be converted manually to the new format, using the cvt_cyrusdb"
"(8) utility."
msgstr ""
"??????????????????????? cvt_cyrusdb(8) ???????"
"?????????????????????????"
#. Type: note
#. Description
#: ../kolab-cyrus-common.templates:3
msgid ""
"Please refer to /usr/share/doc/kolab-cyrus-common/README.Debian.database for "
"more information. Do not start cyrmaster until you have converted the "
"databases to the new format."
msgstr ""
"??????? /usr/share/doc/kolab-cyrus-common/README.Debian.database ??"
"??????????????????????????? cyrmaster ??????"
"??????"
#. Type: boolean
#. Description
#: ../kolab-cyrus-common.templates:19
msgid "Remove the Cyrus spools, and user sieve scripts?"
msgstr "Cyrus ?????????? sieve ?????????????"
#. Type: boolean
#. Description
#: ../kolab-cyrus-common.templates:19
msgid ""
"Should I remove the Cyrus mail and news spools, as well as the user's sieve "
"scripts, when the package is purged ?"
msgstr ""
"????????????????sieve ????????? Cyrus ???????"
"???????????????????"
#. Type: boolean
#. Description
#: ../kolab-cyrus-common.templates:19
msgid ""
"This question only applies to the default spools and sieve script "
"directories in /var. If you modified their location in imapd.conf, the new "
"locations will not be removed; just the old ones in /var."
msgstr ""
"????? /var ??????????? sieve ????????????????"
"?????imapd.conf ????????????????????????????"
"?????????????/var ????????????"
More information about the pkg-kolab-devel
mailing list