Bug#396400: mdadm: [INTL:ja] Updated Japanese po-debconf template translation (ja.po)

[Hideki Yamane (Debian-JP)]

Package: mdadm
Version: 2.5.5-1
Severity: wishlist
Tags: l10n patch

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear mdadm 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)

iD8DBQFFR2I1Iu0hy8THJksRAmFCAJwN9WRZLB6o6K2Tp6KfZa8qdxFdawCgrSXI
X06eIhj+2G7o9xgWmnCkSw0=
=TaPb
-----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: mdadm 2.5.5-1\n"
"Report-Msgid-Bugs-To: pkg-mdadm-devel at lists.alioth.debian.org\n"
"POT-Creation-Date: 2006-09-16 13:03+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: string
#. Description
#: ../mdadm.templates:1001
msgid "MD arrays needed for the root filesystem:"
msgstr "root ???????????? MD ???:"

#. Type: string
#. Description
#: ../mdadm.templates:1001
msgid "${msg}"
msgstr "${msg}"

#. Type: string
#. Description
#: ../mdadm.templates:1001
msgid ""
"Please enter a space-separated list of devices, 'all', or 'none'. You may "
"omit the leading '/dev/' and just enter e.g. \"md0 md1\", or \"md/1 md/d0\"."
msgstr ""
"????????????????????????? 'all' ??? 'none' ?????"
"??????? '/dev/' ???????? \"md0 md1\" ???? \"md/1 md/d0\" ??"
"??????????"

#. Type: text
#. Description
#: ../mdadm.templates:2001
msgid "for internal use - only the long description is needed."
msgstr "?????????? - ?????????????"

#. Type: text
#. Description
#: ../mdadm.templates:2001
msgid ""
"If your system has its root filesystem on an MD array (RAID), it needs to be "
"started early during the boot sequence. If your root filesystem is on a "
"logical volume (LVM), which is on MD, all constituent arrays need to be "
"started."
msgstr ""
"????????? root ????????? MD ??? (RAID) ?????????"
"????????????????? MD ????????????????root ???"
"?????? MD ????????? (LVM) ???????????????????"
"????????"

#. Type: text
#. Description
#: ../mdadm.templates:2001
msgid ""
"If you know exactly which arrays are needed to bring up the root filesystem, "
"and you want to postpone starting all other arrays to a later point in the "
"boot sequence, enter the arrays to start here. Alternatively, enter 'all' to "
"simply start all available arrays."
msgstr ""
"?????? root ??????????????????????????????"
"???????????????????????????????????????"
"???????????????????????????????'all' ?????"
"???????????????????????????"

#. Type: text
#. Description
#: ../mdadm.templates:2001
msgid ""
"If you do not need or want to start any arrays for the root filesystem, "
"leave the answer blank (or enter 'none'). This may be the case if you are "
"using kernel autostart or do not need any arrays to boot."
msgstr ""
"root ???????????????????????????????????????"
"???????????????? (???? 'none' ???) ???????"
"??????????????????????????????????????"
"?????"

#. Type: text
#. Description
#: ../mdadm.templates:3001
msgid "An error occurred: device node does not exist"
msgstr "??????????: ??????????????"

#. Type: text
#. Description
#: ../mdadm.templates:4001
msgid "An error occurred: not a block device"
msgstr "??????????: ???????????????"

#. Type: text
#. Description
#: ../mdadm.templates:5001
msgid "An error occurred: not an MD array"
msgstr "??????????: MD ??????????"

#. Type: text
#. Description
#: ../mdadm.templates:6001
msgid "An error occurred: array not listed in mdadm.conf file"
msgstr "??????????: mdadm.conf ??????????????????"

#. Type: boolean
#. Description
#: ../mdadm.templates:7001
msgid "Proceed with starting arrays not listed in mdadm.conf?"
msgstr "mdadm.conf ???????????????????????"

#. Type: boolean
#. Description
#: ../mdadm.templates:7001
msgid ""
"The array you have specified (${array}) is not listed in the configuration "
"file ${config}. Therefore it cannot be started during boot, unless you "
"correct the configuration file and recreate the initial ramdisk."
msgstr ""
"??????? (${array}) ??????? ${config} ???????????"
"???????????????? initrd ??????????????????????"

#. Type: boolean
#. Description
#: ../mdadm.templates:7001
msgid ""
"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend "
"to continue."
msgstr ""
"?????????/usr/share/doc/mdadm/README.upgrading-2.5.3.gz "
"??????????"

#. Type: boolean
#. Description
#: ../mdadm.templates:7001
msgid ""
"This warning is only relevant if you need arrays to be started from the "
"initial ramdisk to be able to boot. If you use kernel autostarting, or do "
"not need any arrays to be started as early as the initial ramdisk is loaded, "
"you can simply continue. Alternatively, choose not to continue and enter "
"'none' when prompted which arrays to start from the initial ramdisk."
msgstr ""
"??????????????????? initrd ?????????????????"
"??????????????????????????????????? initrd ?"
"????????????????????????????????????????"
"?????????????????????????? initrd ????????"
"??????? 'none' ???????"

#. Type: boolean
#. Description
#: ../mdadm.templates:8001
msgid "Do you want to start MD arrays automatically?"
msgstr "MD ???????????????"

#. Type: boolean
#. Description
#: ../mdadm.templates:8001
msgid ""
"Once the base system has come up, mdadm can start all MD arrays (RAIDs) "
"specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless "
"you have compiled multiple device (MD) support into the kernel and marked "
"all partitions part of MD arrays with type 0xfd (as those and only those "
"will be started automatically by the kernel), this is probably what you want."
msgstr ""
"????????????????mdadm ? /etc/mdadm/mdadm.conf ??????"
"???????????? MD ??? (RAID) ??????????????? (MD) "
"?????????????????????????MD ???????????????"
"??????????? 0xfd ????????????????? (??????????"
"?????????????????????????????????) ?"

#. Type: boolean
#. Description
#: ../mdadm.templates:9001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr "mdadm ???? MD ??????????????????"

#. Type: boolean
#. Description
#: ../mdadm.templates:9001
msgid ""
"If your kernel supports it (>> 2.6.14), mdadm can periodically check the "
"redundancy of your MD arrays (RAIDs). This may be a resource-intensive "
"process, depending on your setup, but it could help prevent rare cases of "
"data loss. Note that this is a read-only check unless errors are found; if "
"errors are found, mdadm will try to correct them, which may result in write "
"access to the media."
msgstr ""
"??????????????? (2.6.14 ??)?mdadm ????? MD ??? (RAID) "
"?????????????????????????????????????????"
"???????????????????????????????????????"
"?????????????????????????????????????????"
"????????????mdadm ????????????????????????"
"?????"

#. Type: boolean
#. Description
#: ../mdadm.templates:9001
msgid ""
"The default, if turned on, is to run the checks on the first Sunday of every "
"month at 01:06 o'clock."
msgstr ""
"????????????????????? 01:06 ?????????????"

#. Type: boolean
#. Description
#: ../mdadm.templates:10001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "MD ??????????????"

#. Type: boolean
#. Description
#: ../mdadm.templates:10001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure). You probably want to enable it."
msgstr ""
"MD (RAID) ??????????? MD ??????? (????????) ????"
"??????????????????????????"

#. Type: string
#. Description
#: ../mdadm.templates:11001
msgid "Recipient for email notifications:"
msgstr "????????:"

#. Type: string
#. Description
#: ../mdadm.templates:11001
msgid ""
"Please enter the email address of the user who should get the email "
"notification for important MD events."
msgstr ""
"MD ????????????????????????????????????"
"???????????????????"

#~ msgid "Initialise the superblock if you reuse hard disks"
#~ msgstr "???????????????? superblock ??????????"

#~ msgid ""
#~ "WARNING! If you are using hard disks which have RAID superblocks from "
#~ "earlier installations in different RAID arrays, you MUST zero each "
#~ "superblock *before* activating the autostart feature."
#~ msgstr ""
#~ "??! ??????????????? RAID ??????? RAID superblock "
#~ "???????????????????????????????????"
#~ "??????? superblock ???????????????????"

#~ msgid ""
#~ "To do this, do not start the RAID devices automatically. First, zero the "
#~ "superblock (mdadm --zero-superblock /dev/mdX). Next, use `dpkg-"
#~ "reconfigure mdadm` to reactivate the autostart feature."
#~ msgstr ""
#~ "????????RAID ??????????????????????? "
#~ "superblock ?????????? (mdadm --zero-superblock /dev/xxx)? ??"
#~ "?????????????????'dpkg-reconfigure mdadm' ???????"
#~ "????"

#~ msgid ""
#~ "You have the option to start all other arrays (those not needed for the "
#~ "root filesystem) later in the boot sequence. Doing so will give you "
#~ "greater control over the arrays with the mdadm configuration file. "
#~ "Starting all arrays at boot-time may be safer though."
#~ msgstr ""
#~ "?????????????? (root ??????????????) ????"
#~ "???????????????????????????mdadm ???????"
#~ "?????????????????????????????????????"
#~ "??????????????????????????"

#~ msgid ""
#~ "If RAID devices are started automatically, all RAID devices are "
#~ "discovered and assembled automatically at system startup. This option "
#~ "should only be used if the md driver is compiled as a module. If it is "
#~ "compiled into your kernel, the automatic startup will be performed at "
#~ "boot time by the kernel and therefore you should not choose this option."
#~ msgstr ""
#~ "RAID ??????????????????????????????? RAID "
#~ "????????????????????????????? md ??????"
#~ "?????????????????????????????????????"
#~ "?????????????????????????????????????"
#~ "???????????????????????"

#~ msgid ""
#~ "When the RAID monitor daemon runs, email notifications are sent when a "
#~ "disk belonging to a RAID array fails or changes its status for some "
#~ "reason."
#~ msgstr ""
#~ "RAID ????????????????RAID ????????????????"
#~ "?????????????????????????????"