summaryrefslogtreecommitdiff
path: root/po
diff options
context:
space:
mode:
Diffstat (limited to 'po')
-rw-r--r--po/el/boot-new.po24
-rw-r--r--po/es/boot-new.po13
-rw-r--r--po/fi/boot-new.po22
-rw-r--r--po/fr/boot-new.po5
-rw-r--r--po/hu/boot-new.po23
-rw-r--r--po/ja/boot-new.po23
-rw-r--r--po/sv/boot-new.po23
-rw-r--r--po/vi/boot-new.po23
-rw-r--r--po/zh_CN/boot-new.po22
9 files changed, 22 insertions, 156 deletions
diff --git a/po/el/boot-new.po b/po/el/boot-new.po
index 3a339e9cd..771140fc9 100644
--- a/po/el/boot-new.po
+++ b/po/el/boot-new.po
@@ -291,12 +291,7 @@ msgstr "Προσάρτηση κρυπτογραφημένων τόμων"
#. Tag: para
#: boot-new.xml:147
-#, fuzzy, no-c-format
-#| msgid ""
-#| "If you created encrypted volumes during the installation and assigned "
-#| "them mount points, you will be asked to enter the passphrase for each of "
-#| "these volumes during the boot. The actual procedure differs slightly "
-#| "between dm-crypt and loop-AES."
+#, no-c-format
msgid ""
"If you created encrypted volumes during the installation and assigned them "
"mount points, you will be asked to enter the passphrase for each of these "
@@ -304,9 +299,7 @@ msgid ""
msgstr ""
"Αν δημιουργήσατε κρυπτογραφημένους τόμους κατά την διάρκεια της εγκατάστασης "
"και τους αποδώσατε σημεία προσάρτησης, θα σας ζητηθεί να εισάγετε την "
-"συνθηματική φράση για κάθε έναν από τους τόμους αυτούς στην εκκίνηση. Η "
-"διαδικασία στην πράξη διαφέρει ελαφρά μεταξύ κρυπτογραφήσεων dm-crypt και "
-"loop-AES."
+"συνθηματική φράση για κάθε έναν από τους τόμους αυτούς στην εκκίνηση."
#. Tag: para
#: boot-new.xml:155
@@ -446,18 +439,7 @@ msgstr ""
#. Tag: para
#: boot-new.xml:226
-#, fuzzy, no-c-format
-#| msgid ""
-#| "For dm-crypt this is a bit trickier. First you need to register the "
-#| "volumes with <application>device mapper</application> by running: "
-#| "<informalexample><screen>\n"
-#| "<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
-#| "</screen></informalexample> This will scan all volumes mentioned in "
-#| "<filename>/etc/crypttab</filename> and will create appropriate devices "
-#| "under the <filename>/dev</filename> directory after entering the correct "
-#| "passphrases. (Already registered volumes will be skipped, so you can "
-#| "repeat this command several times without worrying.) After successful "
-#| "registration you can simply mount the volumes the usual way:"
+#, no-c-format
msgid ""
"However for dm-crypt this is a bit tricky. First you need to register the "
"volumes with <application>device mapper</application> by running: "
diff --git a/po/es/boot-new.po b/po/es/boot-new.po
index 52b02fc04..e63c69da3 100644
--- a/po/es/boot-new.po
+++ b/po/es/boot-new.po
@@ -452,18 +452,7 @@ msgstr ""
#. Tag: para
#: boot-new.xml:226
-#, fuzzy, no-c-format
-#| msgid ""
-#| "For dm-crypt this is a bit trickier. First you need to register the "
-#| "volumes with <application>device mapper</application> by running: "
-#| "<informalexample><screen>\n"
-#| "<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
-#| "</screen></informalexample> This will scan all volumes mentioned in "
-#| "<filename>/etc/crypttab</filename> and will create appropriate devices "
-#| "under the <filename>/dev</filename> directory after entering the correct "
-#| "passphrases. (Already registered volumes will be skipped, so you can "
-#| "repeat this command several times without worrying.) After successful "
-#| "registration you can simply mount the volumes the usual way:"
+#, no-c-format
msgid ""
"However for dm-crypt this is a bit tricky. First you need to register the "
"volumes with <application>device mapper</application> by running: "
diff --git a/po/fi/boot-new.po b/po/fi/boot-new.po
index 121484c4e..b5a13e15e 100644
--- a/po/fi/boot-new.po
+++ b/po/fi/boot-new.po
@@ -274,12 +274,7 @@ msgstr "Salattujen levyniteiden liittäminen"
#. Tag: para
#: boot-new.xml:147
-#, fuzzy, no-c-format
-#| msgid ""
-#| "If you created encrypted volumes during the installation and assigned "
-#| "them mount points, you will be asked to enter the passphrase for each of "
-#| "these volumes during the boot. The actual procedure differs slightly "
-#| "between dm-crypt and loop-AES."
+#, no-c-format
msgid ""
"If you created encrypted volumes during the installation and assigned them "
"mount points, you will be asked to enter the passphrase for each of these "
@@ -287,7 +282,7 @@ msgid ""
msgstr ""
"Jos asennuksen aikana tehtiin salattuja levyniteitä ja niille annettiin "
"liitoskohdat, pyydetään jokaisen levyniteen tunnuslause käynnistyksen "
-"aikana. Tässä kohtaa dm-crypt ja loop-AES toimivat hieman eri tavoin."
+"aikana."
#. Tag: para
#: boot-new.xml:155
@@ -420,18 +415,7 @@ msgstr ""
#. Tag: para
#: boot-new.xml:226
-#, fuzzy, no-c-format
-#| msgid ""
-#| "For dm-crypt this is a bit trickier. First you need to register the "
-#| "volumes with <application>device mapper</application> by running: "
-#| "<informalexample><screen>\n"
-#| "<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
-#| "</screen></informalexample> This will scan all volumes mentioned in "
-#| "<filename>/etc/crypttab</filename> and will create appropriate devices "
-#| "under the <filename>/dev</filename> directory after entering the correct "
-#| "passphrases. (Already registered volumes will be skipped, so you can "
-#| "repeat this command several times without worrying.) After successful "
-#| "registration you can simply mount the volumes the usual way:"
+#, no-c-format
msgid ""
"However for dm-crypt this is a bit tricky. First you need to register the "
"volumes with <application>device mapper</application> by running: "
diff --git a/po/fr/boot-new.po b/po/fr/boot-new.po
index 983dfb69d..78d05a05d 100644
--- a/po/fr/boot-new.po
+++ b/po/fr/boot-new.po
@@ -173,11 +173,6 @@ msgstr ""
#. Tag: para
#: boot-new.xml:84
#, no-c-format
-#| msgid ""
-#| "If you use <command>BootX</command> to boot into the installed system, "
-#| "just select your desired kernel in the <filename>Linux Kernels</filename> "
-#| "folder, un-choose the ramdisk option, and add a root device corresponding "
-#| "to your installation; e.g. <userinput>/dev/hda8</userinput>."
msgid ""
"If you use <command>BootX</command> to boot into the installed system, just "
"select your desired kernel in the <filename>Linux Kernels</filename> folder, "
diff --git a/po/hu/boot-new.po b/po/hu/boot-new.po
index 6bb787f73..a41c942aa 100644
--- a/po/hu/boot-new.po
+++ b/po/hu/boot-new.po
@@ -270,20 +270,14 @@ msgstr "Titkosított kötetek csatolása"
#. Tag: para
#: boot-new.xml:147
-#, fuzzy, no-c-format
-#| msgid ""
-#| "If you created encrypted volumes during the installation and assigned "
-#| "them mount points, you will be asked to enter the passphrase for each of "
-#| "these volumes during the boot. The actual procedure differs slightly "
-#| "between dm-crypt and loop-AES."
+#, no-c-format
msgid ""
"If you created encrypted volumes during the installation and assigned them "
"mount points, you will be asked to enter the passphrase for each of these "
"volumes during the boot."
msgstr ""
"Ha a telepítéskor titkosított köteteket hoztál létre és csatolási pontokhoz "
-"rendelted ezeket, az indításkor meg kell adnod majd a jelmondatokat ezekhez. "
-"Az eljárás csöppet eltér a dm-crypt és loop-AES közt."
+"rendelted ezeket, az indításkor meg kell adnod majd a jelmondatokat ezekhez."
#. Tag: para
#: boot-new.xml:155
@@ -412,18 +406,7 @@ msgstr ""
#. Tag: para
#: boot-new.xml:226
-#, fuzzy, no-c-format
-#| msgid ""
-#| "For dm-crypt this is a bit trickier. First you need to register the "
-#| "volumes with <application>device mapper</application> by running: "
-#| "<informalexample><screen>\n"
-#| "<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
-#| "</screen></informalexample> This will scan all volumes mentioned in "
-#| "<filename>/etc/crypttab</filename> and will create appropriate devices "
-#| "under the <filename>/dev</filename> directory after entering the correct "
-#| "passphrases. (Already registered volumes will be skipped, so you can "
-#| "repeat this command several times without worrying.) After successful "
-#| "registration you can simply mount the volumes the usual way:"
+#, no-c-format
msgid ""
"However for dm-crypt this is a bit tricky. First you need to register the "
"volumes with <application>device mapper</application> by running: "
diff --git a/po/ja/boot-new.po b/po/ja/boot-new.po
index 50e8de4a4..722a0cf3b 100644
--- a/po/ja/boot-new.po
+++ b/po/ja/boot-new.po
@@ -271,20 +271,14 @@ msgstr "暗号化ボリュームのマウント"
#. Tag: para
#: boot-new.xml:147
-#, fuzzy, no-c-format
-#| msgid ""
-#| "If you created encrypted volumes during the installation and assigned "
-#| "them mount points, you will be asked to enter the passphrase for each of "
-#| "these volumes during the boot. The actual procedure differs slightly "
-#| "between dm-crypt and loop-AES."
+#, no-c-format
msgid ""
"If you created encrypted volumes during the installation and assigned them "
"mount points, you will be asked to enter the passphrase for each of these "
"volumes during the boot."
msgstr ""
"インストール中に暗号化ボリュームを作成し、マウントポイントに割り当てると、そ"
-"のボリュームに対して、起動中にパスフレーズを入力するように訊いてきます。実際"
-"の手順は、dm-crypt と loop-AES では若干異なります。"
+"のボリュームに対して、起動中にパスフレーズを入力するように訊いてきます。"
#. Tag: para
#: boot-new.xml:155
@@ -414,18 +408,7 @@ msgstr ""
#. Tag: para
#: boot-new.xml:226
-#, fuzzy, no-c-format
-#| msgid ""
-#| "For dm-crypt this is a bit trickier. First you need to register the "
-#| "volumes with <application>device mapper</application> by running: "
-#| "<informalexample><screen>\n"
-#| "<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
-#| "</screen></informalexample> This will scan all volumes mentioned in "
-#| "<filename>/etc/crypttab</filename> and will create appropriate devices "
-#| "under the <filename>/dev</filename> directory after entering the correct "
-#| "passphrases. (Already registered volumes will be skipped, so you can "
-#| "repeat this command several times without worrying.) After successful "
-#| "registration you can simply mount the volumes the usual way:"
+#, no-c-format
msgid ""
"However for dm-crypt this is a bit tricky. First you need to register the "
"volumes with <application>device mapper</application> by running: "
diff --git a/po/sv/boot-new.po b/po/sv/boot-new.po
index 5150dd560..2f44759af 100644
--- a/po/sv/boot-new.po
+++ b/po/sv/boot-new.po
@@ -274,12 +274,7 @@ msgstr "Montering av krypterade volymer"
#. Tag: para
#: boot-new.xml:147
-#, fuzzy, no-c-format
-#| msgid ""
-#| "If you created encrypted volumes during the installation and assigned "
-#| "them mount points, you will be asked to enter the passphrase for each of "
-#| "these volumes during the boot. The actual procedure differs slightly "
-#| "between dm-crypt and loop-AES."
+#, no-c-format
msgid ""
"If you created encrypted volumes during the installation and assigned them "
"mount points, you will be asked to enter the passphrase for each of these "
@@ -287,8 +282,7 @@ msgid ""
msgstr ""
"Om du skapade krypterade volymer under installationen och tilldelade "
"monteringspunkter till dem, kommer du att bli efterfrågad vid uppstart om "
-"att ange lösenfrasen för varje av dessa volymer. Det faktiska proceduren för "
-"detta skiljer sig markant mellan dm-crypt och loop-AES."
+"att ange lösenfrasen för varje av dessa volymer."
#. Tag: para
#: boot-new.xml:155
@@ -424,18 +418,7 @@ msgstr ""
#. Tag: para
#: boot-new.xml:226
-#, fuzzy, no-c-format
-#| msgid ""
-#| "For dm-crypt this is a bit trickier. First you need to register the "
-#| "volumes with <application>device mapper</application> by running: "
-#| "<informalexample><screen>\n"
-#| "<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
-#| "</screen></informalexample> This will scan all volumes mentioned in "
-#| "<filename>/etc/crypttab</filename> and will create appropriate devices "
-#| "under the <filename>/dev</filename> directory after entering the correct "
-#| "passphrases. (Already registered volumes will be skipped, so you can "
-#| "repeat this command several times without worrying.) After successful "
-#| "registration you can simply mount the volumes the usual way:"
+#, no-c-format
msgid ""
"However for dm-crypt this is a bit tricky. First you need to register the "
"volumes with <application>device mapper</application> by running: "
diff --git a/po/vi/boot-new.po b/po/vi/boot-new.po
index 07bcccc8d..0ba816046 100644
--- a/po/vi/boot-new.po
+++ b/po/vi/boot-new.po
@@ -278,12 +278,7 @@ msgstr "Gắn kết khối tin đã mật mã"
#. Tag: para
#: boot-new.xml:147
-#, fuzzy, no-c-format
-#| msgid ""
-#| "If you created encrypted volumes during the installation and assigned "
-#| "them mount points, you will be asked to enter the passphrase for each of "
-#| "these volumes during the boot. The actual procedure differs slightly "
-#| "between dm-crypt and loop-AES."
+#, no-c-format
msgid ""
"If you created encrypted volumes during the installation and assigned them "
"mount points, you will be asked to enter the passphrase for each of these "
@@ -291,8 +286,7 @@ msgid ""
msgstr ""
"Nếu bạn đã tạo khối tin đã mật mã trong tiến trình cài đặt, cũng đã gán "
"chúng cho điểm lắp, bạn sẽ được nhắc nập cụm từ mật khẩu dành cho mỗi khối "
-"tin trong khi khởi động. Thu tục thật khác biệt một ít giữa <filename>dm-"
-"crypt</filename> và <filename>loop-AES</filename>."
+"tin trong khi khởi động."
#. Tag: para
#: boot-new.xml:155
@@ -431,18 +425,7 @@ msgstr ""
#. Tag: para
#: boot-new.xml:226
-#, fuzzy, no-c-format
-#| msgid ""
-#| "For dm-crypt this is a bit trickier. First you need to register the "
-#| "volumes with <application>device mapper</application> by running: "
-#| "<informalexample><screen>\n"
-#| "<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
-#| "</screen></informalexample> This will scan all volumes mentioned in "
-#| "<filename>/etc/crypttab</filename> and will create appropriate devices "
-#| "under the <filename>/dev</filename> directory after entering the correct "
-#| "passphrases. (Already registered volumes will be skipped, so you can "
-#| "repeat this command several times without worrying.) After successful "
-#| "registration you can simply mount the volumes the usual way:"
+#, no-c-format
msgid ""
"However for dm-crypt this is a bit tricky. First you need to register the "
"volumes with <application>device mapper</application> by running: "
diff --git a/po/zh_CN/boot-new.po b/po/zh_CN/boot-new.po
index b7c9897ae..5c1af012d 100644
--- a/po/zh_CN/boot-new.po
+++ b/po/zh_CN/boot-new.po
@@ -247,19 +247,14 @@ msgstr "挂载加密卷"
#. Tag: para
#: boot-new.xml:147
-#, fuzzy, no-c-format
-#| msgid ""
-#| "If you created encrypted volumes during the installation and assigned "
-#| "them mount points, you will be asked to enter the passphrase for each of "
-#| "these volumes during the boot. The actual procedure differs slightly "
-#| "between dm-crypt and loop-AES."
+#, no-c-format
msgid ""
"If you created encrypted volumes during the installation and assigned them "
"mount points, you will be asked to enter the passphrase for each of these "
"volumes during the boot."
msgstr ""
"假如您在安装的时候创建了加密卷并设置了挂载点,在启动的时候每个这样的卷将会要"
-"求输入密码。对于 dm-crypt 和 loop-AES 具体的过程稍有不同。"
+"求输入密码。"
#. Tag: para
#: boot-new.xml:155
@@ -383,18 +378,7 @@ msgstr ""
#. Tag: para
#: boot-new.xml:226
-#, fuzzy, no-c-format
-#| msgid ""
-#| "For dm-crypt this is a bit trickier. First you need to register the "
-#| "volumes with <application>device mapper</application> by running: "
-#| "<informalexample><screen>\n"
-#| "<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
-#| "</screen></informalexample> This will scan all volumes mentioned in "
-#| "<filename>/etc/crypttab</filename> and will create appropriate devices "
-#| "under the <filename>/dev</filename> directory after entering the correct "
-#| "passphrases. (Already registered volumes will be skipped, so you can "
-#| "repeat this command several times without worrying.) After successful "
-#| "registration you can simply mount the volumes the usual way:"
+#, no-c-format
msgid ""
"However for dm-crypt this is a bit tricky. First you need to register the "
"volumes with <application>device mapper</application> by running: "