Fix up lots of fuzzy translations

3 files changed, 20 insertions, 127 deletions

diff --git a/po/ko/boot-installer.po b/po/ko/boot-installer.po
index 5badb3c8d..e1090e3cb 100644
--- a/po/ko/boot-installer.po
+++ b/po/ko/boot-installer.po
@@ -83,14 +83,7 @@ msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:47
-#, fuzzy, no-c-format
-#| msgid ""
-#| "uImage/uInitrd are image formats designed for the U-Boot firmware that is "
-#| "used on many ARM-based systems. Older U-Boot versions can only boot files "
-#| "in uImage/uInitrd format, so these are often used on older armel systems. "
-#| "Newer U-Boot versions can - besides booting uImages/uInitrds - also boot "
-#| "standard Linux kernels and ramdisk images, but the command syntax to do "
-#| "that is slightly different from that for booting uImages."
+#, no-c-format
 msgid ""
 "uImage/uInitrd are image formats designed for the U-Boot firmware that is "
 "used on many ARM-based systems. Older U-Boot versions can only boot files in "
@@ -190,19 +183,13 @@ msgstr ""
 
 #. Tag: title
 #: boot-installer.xml:108
-#, fuzzy, no-c-format
-#| msgid "TFTP-booting in U-Boot"
+#, no-c-format
 msgid "TFTP-booting in U-Boot"
 msgstr "U-Boot에서 TFTP 부팅"
 
 #. Tag: para
 #: boot-installer.xml:109
-#, fuzzy, no-c-format
-#| msgid ""
-#| "Network booting on systems using the U-Boot firmware consists of three "
-#| "steps: a) configuring the network, b) loading the images (kernel/initial "
-#| "ramdisk/dtb) into memory and c) actually executing the previosly loaded "
-#| "code."
+#, no-c-format
 msgid ""
 "Network booting on systems using the U-Boot firmware consists of three "
 "steps: a) configuring the network, b) loading the images (kernel/initial "
@@ -265,18 +252,7 @@ msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:132
-#, fuzzy, no-c-format
-#| msgid ""
-#| "On some systems, U-Boot predefines a set of environment variables with "
-#| "suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. "
-#| "You can check whether they are defined by running "
-#| "<informalexample><screen>\n"
-#| "printenv kernel_addr_r ramdisk_addr_r fdt_addr_r\n"
-#| "</screen></informalexample> If they are not defined, you have to check "
-#| "your system's documentation for appropriate values and set them manually. "
-#| "For systems based on Allwinner SunXi SOCs (e.g. the Allwinner A10, "
-#| "architecture name <quote>sun4i</quote> or the Allwinner A20, architecture "
-#| "name <quote>sun7i</quote>), you can e.g. use the follwing values:"
+#, no-c-format
 msgid ""
 "On some systems, U-Boot predefines a set of environment variables with "
 "suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. You "
@@ -334,21 +310,7 @@ msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:150
-#, fuzzy, no-c-format
-#| msgid ""
-#| "The third part is setting the kernel commandline and actually executing "
-#| "the loaded code. U-boot passes the content of the <quote>bootargs</quote> "
-#| "environment variable as commandline to the kernel, so any parameters for "
-#| "the kernel and the installer - such as the console device (see <xref "
-#| "linkend=\"boot-console\"/>) or preseeding options (see <xref linkend="
-#| "\"installer-args\"/> and <xref linkend=\"appendix-preseed\"/>) - can be "
-#| "set with a command like <informalexample><screen>\n"
-#| "setenv bootargs console=ttyS0,115200 rootwait panic=10\n"
-#| "</screen></informalexample> The exact command to execute the previously "
-#| "loaded code depends on the image format used. With uImage/uInitrd, the "
-#| "command is <informalexample><screen>\n"
-#| "bootm ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}\n"
-#| "</screen></informalexample> and with native Linux images it is"
+#, no-c-format
 msgid ""
 "The third part is setting the kernel commandline and actually executing the "
 "loaded code. U-Boot passes the content of the <quote>bootargs</quote> "
@@ -385,14 +347,7 @@ msgstr "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}"
 
 #. Tag: para
 #: boot-installer.xml:165
-#, fuzzy, no-c-format
-#| msgid ""
-#| "Note: When booting standard linux images, it is important to load the "
-#| "initial ramdisk image after the kernel and the dtb as U-Boot sets the "
-#| "filesize variable to the size of the last file loaded and the bootz "
-#| "command requires the size of the ramdisk image to work correctly. In case "
-#| "of booting a platform-specific kernel, i.e. a kernel without device-tree, "
-#| "simply omit the ${fdt_addr_r} parameter."
+#, no-c-format
 msgid ""
 "Note: When booting standard linux images, it is important to load the "
 "initial ramdisk image after the kernel and the dtb as U-Boot sets the "
@@ -461,18 +416,13 @@ msgstr ""
 
 #. Tag: title
 #: boot-installer.xml:206
-#, fuzzy, no-c-format
-#| msgid "Booting from a USB stick in U-Boot"
+#, no-c-format
 msgid "Booting from a USB stick in U-Boot"
 msgstr "U-Boot 이용해 USB 메모리에서 부팅하기"
 
 #. Tag: para
 #: boot-installer.xml:207
-#, fuzzy, no-c-format
-#| msgid ""
-#| "Many modern U-Boot versions have USB support and allow booting from USB "
-#| "mass storage devices such as USB sticks. Unfortunately the exact steps "
-#| "required to do that can vary quite a bit from device to device."
+#, no-c-format
 msgid ""
 "Many modern U-Boot versions have USB support and allow booting from USB mass "
 "storage devices such as USB sticks. Unfortunately the exact steps required "
@@ -525,15 +475,7 @@ msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:233
-#, fuzzy, no-c-format
-#| msgid ""
-#| "The autoboot framework in modern U-Boot versions works similar to the "
-#| "boot ordering options in a PC BIOS, i.e. it checks a list of possible "
-#| "boot devices for a valid boot image and starts the first one it finds. If "
-#| "there is no operating system installed, plugging in the USB stick and "
-#| "powering up the system should result in starting the installer. You can "
-#| "also initiate the USB-boot process any time from the U-Boot prompt by "
-#| "entering the <quote>run usb_boot</quote> command."
+#, no-c-format
 msgid ""
 "The autoboot framework in modern U-Boot versions works similar to the boot "
 "ordering options in a PC BIOS, i.e. it checks a list of possible boot "
@@ -552,23 +494,7 @@ msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:243
-#, fuzzy, no-c-format
-#| msgid ""
-#| "One problem that can come up when booting from a USB stick while using a "
-#| "serial console can be a console baudrate mismatch. If a console variable "
-#| "is defined in U-Boot, the &d-i; boot script automatically passes it to "
-#| "the kernel to set the primary console device and, if applicable, the "
-#| "console baudrate. Unfortunately the handling of the console variable "
-#| "varies from platform to platform - on some platforms, the console "
-#| "variable includes the baudrate (as in <quote>console=ttyS0,115200</"
-#| "quote>), while on other platforms the console variable contains only the "
-#| "device (as in <quote>console=ttyS0</quote>). The latter case leads to a "
-#| "garbled console output when the default baudrate differs between U-Boot "
-#| "and the kernel. Modern U-Boot versions often use 115200 baud while the "
-#| "kernel still defaults to the traditional 9600 baud. If this happens, you "
-#| "should manually set the console variable to contain the correct baudrate "
-#| "for your system and then start the installer with the <quote>run "
-#| "usb_boot</quote> command."
+#, no-c-format
 msgid ""
 "One problem that can come up when booting from a USB stick while using a "
 "serial console can be a console baudrate mismatch. If a console variable is "
diff --git a/po/ko/hardware.po b/po/ko/hardware.po
index fc447b9ac..ae068e878 100644
--- a/po/ko/hardware.po
+++ b/po/ko/hardware.po
@@ -361,10 +361,9 @@ msgstr "prep"
 
 #. Tag: entry
 #: hardware.xml:148
-#, fuzzy, no-c-format
-#| msgid "Amiga Power-UP Systems (APUS)"
+#, no-c-format
 msgid "Power Systems"
-msgstr "Amiga Power-UP Systems (APUS)"
+msgstr "Power Systems"
 
 #. Tag: entry
 #: hardware.xml:149
@@ -3085,10 +3084,9 @@ msgstr "CHRP에서는, 현재 플로피 지원이 동작하지 않는 상태입�
 
 #. Tag: title
 #: hardware.xml:2044
-#, fuzzy, no-c-format
-#| msgid "CD-ROM/DVD-ROM"
+#, no-c-format
 msgid "CD-ROM/DVD-ROM/BD-ROM"
-msgstr "CD-ROM/DVD-ROM"
+msgstr "CD-ROM/DVD-ROM/BD-ROM"
 
 #. Tag: para
 #: hardware.xml:2046
diff --git a/po/ko/preparing.po b/po/ko/preparing.po
index 06c650565..407edc23d 100644
--- a/po/ko/preparing.po
+++ b/po/ko/preparing.po
@@ -2534,8 +2534,7 @@ msgstr ""
 
 #. Tag: title
 #: preparing.xml:1706
-#, fuzzy, no-c-format
-#| msgid "Setting the ethernet MAC address in U-Boot"
+#, no-c-format
 msgid "Setting the ethernet MAC address in U-Boot"
 msgstr "U-Boot에서 이더넷 MAC 주소 설정하기"
 
@@ -2597,14 +2596,7 @@ msgstr ""
 
 #. Tag: para
 #: preparing.xml:1736
-#, fuzzy, no-c-format
-#| msgid ""
-#| "On systems using U-Boot as system firmware, the ethernet MAC address is "
-#| "placed in the <quote>ethaddr</quote> environment variable. It can be "
-#| "checked at the U-Boot command prompt with the command <quote>printenv "
-#| "ethaddr</quote> and can be set with the command <quote>setenv ethaddr ca:"
-#| "ff:ee:12:34:56</quote>. After setting the value, the command "
-#| "<quote>saveenv</quote> makes the assignment permanent."
+#, no-c-format
 msgid ""
 "On systems using U-Boot as system firmware, the ethernet MAC address is "
 "placed in the <quote>ethaddr</quote> environment variable. It can be checked "
@@ -2621,21 +2613,13 @@ msgstr ""
 
 #. Tag: title
 #: preparing.xml:1747
-#, fuzzy, no-c-format
-#| msgid "Kernel/Initrd/Device-Tree relocation issues in U-Boot"
+#, no-c-format
 msgid "Kernel/Initrd/Device-Tree relocation issues in U-Boot"
 msgstr "U-Boot의 커널/최초 램디스크/디바이스 트리 재배치 문제"
 
 #. Tag: para
 #: preparing.xml:1748
-#, fuzzy, no-c-format
-#| msgid ""
-#| "On some systems with older U-Boot versions there can be problems with "
-#| "properly relocating the Linux kernel, the initial ramdisk and the device-"
-#| "tree blob in memory during the boot process. In this case, U-Boot shows "
-#| "the message <quote>Starting kernel ...</quote>, but the system freezes "
-#| "afterwards without further output. These issues have been solved with "
-#| "newer U-Boot versions from v2014.07 onwards."
+#, no-c-format
 msgid ""
 "On some systems with older U-Boot versions there can be problems with "
 "properly relocating the Linux kernel, the initial ramdisk and the device-"
@@ -2652,17 +2636,7 @@ msgstr ""
 
 #. Tag: para
 #: preparing.xml:1757
-#, fuzzy, no-c-format
-#| msgid ""
-#| "If the system has originally used a U-Boot version older than v2014.07 "
-#| "and has been upgraded to a newer version later, the problem might still "
-#| "occur even after upgrading U-Boot. Upgrading U-Boot usually does not "
-#| "modify the existing U-Boot environment variables and the fix requires an "
-#| "additional environment variable (bootm_size) to be set, which U-Boot does "
-#| "automatically only on fresh installations without existing environment "
-#| "data. It is possible to manually set bootm_size to the new U-Boot's "
-#| "default value by running the command <quote>env default bootm_size; "
-#| "saveenv</quote> at the U-Boot prompt."
+#, no-c-format
 msgid ""
 "If the system has originally used a U-Boot version older than v2014.07 and "
 "has been upgraded to a newer version later, the problem might still occur "
@@ -2684,12 +2658,7 @@ msgstr ""
 
 #. Tag: para
 #: preparing.xml:1768
-#, fuzzy, no-c-format
-#| msgid ""
-#| "Another possibility to circumvent relocation-related problems is to run "
-#| "the command <quote>setenv fdt_high ffffffff; setenv initrd_high "
-#| "0xffffffff; saveenv</quote> at the U-Boot prompt to completely disable "
-#| "the relocation of the initial ramdisk and the device-tree blob."
+#, no-c-format
 msgid ""
 "Another possibility to circumvent relocation-related problems is to run the "
 "command <quote>setenv fdt_high ffffffff; setenv initrd_high 0xffffffff; "