From 99e39c8db49944b4c870c1a191a569cb31ccc4e6 Mon Sep 17 00:00:00 2001 From: Holger Wansing Date: Tue, 24 Jan 2017 19:04:04 +0000 Subject: [SILENT_COMMIT] Update of POT and PO files for the manual --- po/ko/boot-installer.po | 27 ++++++++++++++++++++------- 1 file changed, 20 insertions(+), 7 deletions(-) (limited to 'po/ko') diff --git a/po/ko/boot-installer.po b/po/ko/boot-installer.po index 0443657b6..3f8fe0278 100644 --- a/po/ko/boot-installer.po +++ b/po/ko/boot-installer.po @@ -11,7 +11,7 @@ msgid "" msgstr "" "Project-Id-Version: boot-installer.xml\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2016-11-25 19:03+0000\n" +"POT-Creation-Date: 2017-01-24 19:01+0000\n" "PO-Revision-Date: 2015-05-17 15:45+0900\n" "Last-Translator: Changwoo Ryu \n" "Language-Team: Korean \n" @@ -3458,7 +3458,19 @@ msgstr "" #. Tag: para #: boot-installer.xml:2481 -#, no-c-format +#, fuzzy, no-c-format +#| msgid "" +#| "In order to ensure the terminal type used by the installer matches your " +#| "terminal emulator, the parameter TERM=type can be added. Note that the installer only " +#| "supports the following terminal types: linux, " +#| "bterm, ansi, vt102 and dumb. The default for serial console in " +#| "&d-i; is vt102. If you are using a virtualization " +#| "tool which does not provide conversion into such terminals types itself, " +#| "e.g. QEMU/KVM, you can start it inside a screen " +#| "session. That will indeed perform translation into the screen terminal type, which is very close to vt102." msgid "" "In order to ensure the terminal type used by the installer matches your " "terminal emulator, the parameter TERM=typelinux, bterm, ansi, vt102 and " "dumb. The default for serial console in &d-i; is " -"vt102. If you are using a virtualization tool which " -"does not provide conversion into such terminals types itself, e.g. QEMU/KVM, " -"you can start it inside a screen session. That will " -"indeed perform translation into the screen terminal type, " -"which is very close to vt102." +"vt102. If you are using an IPMI console, or a " +"virtualization tool which does not provide conversion into such terminals " +"types itself, e.g. QEMU/KVM, you can start it inside a screen session. That will indeed perform translation into the " +"screen terminal type, which is very close to " +"vt102." msgstr "" "설치 프로그램이 사용하는 터미널 종류가 사용하고 있는 터미널 에뮬레이터에 맞도" "록 하려면, TERM=종류 파라미" -- cgit v1.2.3