diff options
Diffstat (limited to 'po/ko.po')
| -rw-r--r-- | po/ko.po | 95 |
1 files changed, 53 insertions, 42 deletions
diff --git a/po/ko.po b/po/ko.po index 44a5b50b..a97ae2d0 100644 --- a/po/ko.po +++ b/po/ko.po @@ -33,7 +33,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2020-08-23 16:31+0900\n" "Last-Translator: Changwoo Ryu <cwryu@debian.org>\n" "Language-Team: GNOME Korea <gnome-kr@googlegroups.com>\n" @@ -1181,7 +1181,7 @@ msgstr "예기치 않은 UUID %s, 기대한 값은 %s" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1524,7 +1524,7 @@ msgstr "인증서가 PKCS#11 토큰에 없는 경우 암호가 지원되지 않 #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1811,7 +1811,7 @@ msgstr "사용량 값 %d이(가) 유효하지 않습니다" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "%d 값은 유효하지 않습니다" @@ -1820,44 +1820,40 @@ msgstr "%d 값은 유효하지 않습니다" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "'%u' 플래그가 유효하지 않습니다. %s의 조합을 사용하십시오" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "DHCP 옵션은 255자를 초과할 수 없습니다" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "MUD URL이 유효한 URL이 아닙니다" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "잘못된 권한 \"%s\"" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "속성 유형을 '%s'(으)로 설정해야 합니다" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "연결에서 slave-type '%s'에는 '%s' 설정이 필요합니다." -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1866,13 +1862,13 @@ msgstr "" "'%s'(으)로 설정되고 포트 유형이 '%s'인 슬레이브 연결을 감지합니다. '%s'은" "(는) '%s'(으)로 설정해야 합니다" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" "'%s'이(가) '%s'(으)로 설정된 슬레이브 연결에는 '%s' 설정이 있으면 안 됩니다." -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6020,25 +6016,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7759,13 +7759,24 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:174 #: src/libnmc-setting/settings-docs.h.in:200 +#, fuzzy +#| msgid "" +#| "The gateway associated with this configuration. This is only meaningful " +#| "if \"addresses\" is also set. The gateway's main purpose is to control " +#| "the next hop of the standard default route on the device. Hence, the " +#| "gateway property conflicts with \"never-default\" and will be " +#| "automatically dropped if the IP configuration is set to never-default. As " +#| "an alternative to set the gateway, configure a static default route " +#| "with /0 as prefix length." msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" "이 구성과 연관된 게이트웨이. \"addresses\"도 설정한 경우에만 의미가 있습니" "다. 게이트웨이의 주요 목적은 장치에서 표준 기본 경로의 다음 홉을 제어하는 것" |