summaryrefslogtreecommitdiff
path: root/po/da
diff options
context:
space:
mode:
Diffstat (limited to 'po/da')
-rw-r--r--po/da/boot-installer.po103
-rw-r--r--po/da/hardware.po27
-rw-r--r--po/da/random-bits.po5
3 files changed, 22 insertions, 113 deletions
diff --git a/po/da/boot-installer.po b/po/da/boot-installer.po
index bf6933fb4..f8093da10 100644
--- a/po/da/boot-installer.po
+++ b/po/da/boot-installer.po
@@ -80,14 +80,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 "
@@ -188,19 +181,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 "TFTP-opstart i U-Boot"
#. 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 "
@@ -267,18 +254,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 "
@@ -336,21 +312,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> "
@@ -388,14 +350,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 "
@@ -465,18 +420,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 "Opstart fra et USB-hukommelsesdrev i U-Boot"
#. 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 "
@@ -504,14 +454,7 @@ msgstr ""
#. Tag: para
#: boot-installer.xml:223
-#, fuzzy, no-c-format
-#| msgid ""
-#| "To build a bootable USB stick for installing &debian;, unpack the hd-"
-#| "media tarball (see <xref linkend=\"where-files\"/>) onto a USB stick "
-#| "formatted with a filesystem supported by the U-Boot version on your "
-#| "device. For modern U-Boot versions, any of FAT16 / FAT32 / ext2 / ext3 / "
-#| "ext4 usually works. Then copy the ISO image file of the first &debian; "
-#| "installation CD or DVD onto the stick."
+#, no-c-format
msgid ""
"To build a bootable USB stick for installing &debian;, unpack the hd-media "
"tarball (see <xref linkend=\"where-files\"/>) onto a USB stick formatted "
@@ -529,15 +472,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 bootcmd_usb0</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 "
@@ -557,23 +492,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 "
-#| "bootcmd_usb0</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/da/hardware.po b/po/da/hardware.po
index 422c6dd7c..4f11c2032 100644
--- a/po/da/hardware.po
+++ b/po/da/hardware.po
@@ -81,15 +81,12 @@ msgstr "Understøttede arkitekturer"
#. Tag: para
#: hardware.xml:42
-#, fuzzy, no-c-format
-#| msgid ""
-#| "&debian; GNU/Linux &release; supports eight major architectures and "
-#| "several variations of each architecture known as <quote>flavors</quote>."
+#, no-c-format
msgid ""
"&debian; GNU/Linux &release; supports ten major architectures and several "
"variations of each architecture known as <quote>flavors</quote>."
msgstr ""
-"&debian; GNU/Linux &release; understøtter otte væsentlige arkitekturer og "
+"&debian; GNU/Linux &release; understøtter 10 væsentlige arkitekturer og "
"flere variationer af hver arkitektur kendt som <quote>varianter (flavors)</"
"quote>."
@@ -359,10 +356,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
@@ -627,10 +623,9 @@ msgstr ""
#. Tag: title
#: hardware.xml:357
-#, fuzzy, no-c-format
-#| msgid "Platforms supported by Debian/armel"
+#, no-c-format
msgid "Platforms supported by Debian/arm64"
-msgstr "Platforme understøttet af Debian/armel"
+msgstr "Platforme understøttet af Debian/arm64"
#. Tag: para
#: hardware.xml:359
@@ -774,10 +769,7 @@ msgstr "Versatile Express"
#. Tag: para
#: hardware.xml:450
-#, fuzzy, no-c-format
-#| msgid ""
-#| "The Versatile Express is a development board series from ARM consisting "
-#| "of a baseboard which can be equipped with various CPU daughterboards."
+#, no-c-format
msgid ""
"The Versatile Express is a development board series from ARM consisting of a "
"baseboard which can be equipped with various CPU daughter boards."
@@ -3183,10 +3175,9 @@ msgstr "For CHRP fungerer understøttelse af diskettedrev ikke i øjeblikket."
#. 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/da/random-bits.po b/po/da/random-bits.po
index 3b1f66b80..2f8aeae3d 100644
--- a/po/da/random-bits.po
+++ b/po/da/random-bits.po
@@ -113,10 +113,9 @@ msgstr "sda1"
#. Tag: entry
#: random-bits.xml:44
-#, fuzzy, no-c-format
-#| msgid "First partition of the first IDE hard disk"
+#, no-c-format
msgid "First partition of the first hard disk"
-msgstr "Første partition på den første IDE-harddisk"
+msgstr "Første partition på den første harddisk"
#. Tag: filename
#: random-bits.xml:46