Update of POT and PO files for the manual

1 files changed, 16 insertions, 15 deletions

diff --git a/po/ko/boot-installer.po b/po/ko/boot-installer.po
index bbd314e3f..9173f95bd 100644
--- a/po/ko/boot-installer.po
+++ b/po/ko/boot-installer.po
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: boot-installer.xml\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2006-11-04 17:26+0000\n"
+"POT-Creation-Date: 2006-11-10 03:17+0000\n"
 "PO-Revision-Date: 2006-10-07 17:00+0900\n"
 "Last-Translator: Seok-moon Jang <drssay97@gmail.com>\n"
 "Language-Team: Korean <debian-i10n-korean@lists.debian.org>\n"
@@ -4364,13 +4364,13 @@ msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:3363
-#, no-c-format
+#, fuzzy, no-c-format
 msgid ""
 "The boot floppy is the floppy with the worst problems, because it is read by "
 "the hardware directly, before Linux boots. Often, the hardware doesn't read "
 "as reliably as the Linux floppy disk driver, and may just stop without "
 "printing an error message if it reads incorrect data. There can also be "
-"failures in the Driver Floppies most of which indicate themselves with a "
+"failures in the driver floppies, most of which indicate themselves with a "
 "flood of messages about disk I/O errors."
 msgstr ""
 "부트 플로피가 가장 문제가 많은 플로피입니다. 부트 플로피는 리눅스가 아니라 하"
@@ -4384,10 +4384,11 @@ msgstr ""
 #, fuzzy, no-c-format
 msgid ""
 "If you are having the installation stall at a particular floppy, the first "
-"thing you should write it to a <emphasis>different</emphasis> floppy. Simply "
-"reformatting the old floppy may not be sufficient, even if it appears that "
-"the floppy was reformatted and written with no errors. It is sometimes "
-"useful to try writing the floppy on a different system."
+"thing you should do is write the image to a <emphasis>different</emphasis> "
+"floppy and see if that solves the problem. Simply reformatting the old "
+"floppy may not be sufficient, even if it appears that the floppy was "
+"reformatted and written with no errors. It is sometimes useful to try "
+"writing the floppy on a different system."
 msgstr ""
 "설치 도중에 특정 플로피에서 멈추는 현상이 발생하면, 가장 먼저 할 일은 플로피 "
 "디스크 이미지를 다시 받아서 <emphasis>다른</emphasis> 플로피에 만들어 보는 것"
@@ -4398,21 +4399,21 @@ msgstr ""
 #: boot-installer.xml:3381
 #, no-c-format
 msgid ""
-"Normally you should not have download a floppy image again, but if you are "
-"experiencing problems it is always useful to verify that the images were "
-"downloaded correctly by verifying their md5sums."
+"One user reports he had to write the images to floppy <emphasis>three</"
+"emphasis> times before one worked, and then everything was fine with the "
+"third floppy."
 msgstr ""
+"어떤 사용자는 플로피가 제대로 동작할 때까지 이미지를 무려 <emphasis>세 번</"
+"emphasis> 써야 했다고 하고, 세 번째 플로피에서 제대로 동작했다고 합니다."
 
 #. Tag: para
 #: boot-installer.xml:3387
 #, no-c-format
 msgid ""
-"One user reports he had to write the images to floppy <emphasis>three</"
-"emphasis> times before one worked, and then everything was fine with the "
-"third floppy."
+"Normally you should not have to download a floppy image again, but if you "
+"are experiencing problems it is always useful to verify that the images were "
+"downloaded correctly by verifying their md5sums."
 msgstr ""
-"어떤 사용자는 플로피가 제대로 동작할 때까지 이미지를 무려 <emphasis>세 번</"
-"emphasis> 써야 했다고 하고, 세 번째 플로피에서 제대로 동작했다고 합니다."
 
 #. Tag: para
 #: boot-installer.xml:3393