# Uzbek translation for pppoeconf
# Copyright (c) 2011 Rosetta Contributors and Canonical Ltd 2011
# This file is distributed under the same license as the pppoeconf package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2011.
#
msgid ""
msgstr ""
"Project-Id-Version: pppoeconf\n"
"Report-Msgid-Bugs-To: FULL NAME <EMAIL@ADDRESS>\n"
"POT-Creation-Date: 2011-04-18 01:10+0200\n"
"PO-Revision-Date: 2011-11-15 18:19+0000\n"
"Last-Translator: Umidjon Almasov <u.almasov@gmail.com>\n"
"Language-Team: Uzbek <uz@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Launchpad-Export-Date: 2014-04-10 12:59+0000\n"
"X-Generator: Launchpad (build 16976)\n"

#: ../pppoeconf:46
msgid "Please become root before running pppoeconf!"
msgstr "Сиз pppoeconf дастурини ишга туширишдан олдин root бўлишингиз керак!"

#: ../pppoeconf:48 ../pppoeconf:68
msgid "Press return to continue..."
msgstr "Давом эттириш учун return босинг..."

#: ../pppoeconf:66
msgid ""
"Please install ppp package and enable pppoe support in the kernel, or "
"install pppoe package!"
msgstr ""
"ppp пакетини ўрнатинг ва ядрода pppoe ишлатиш имконини ёқинг, ёки pppoe "
"пакетини ўрнатинг!"

#: ../pppoeconf:108
msgid "Or press ESC to abort here."
msgstr "Ёки шу ерда тўхтатиш учун ESC босинг."

#: ../pppoeconf:127
msgid ""
"\n"
"Most providers send the needed login information per mail. Some providers "
"describe it in odd ways, assuming the user to input the data in their \"user-"
"friendly\" setup programs. But in fact, these applications generate usuall "
"PPP user names and passwords from the entered data. You can find the real "
"names too and input the correct data in the dialog box.\n"
"\n"
"For example, this are methods used some german providers:\n"
"\n"
"Sample username (alias \"login\" or \"login name\"): 11111111111\n"
"\n"
"T-Online T-DSL:\n"
"  additional data:\n"
"    sample T-Onlinenummer: 222222222222\n"
"    sample Mitbenutzer: 0001\n"
"\n"
"  complete username: 111111111111222222222222#0001@t-online.de\n"
"\n"
"Telekom Business Online (DSL):\n"
"\n"
"  complete username: t-online-com/111111111111@t-online-com.de\n"
"\n"
"1und1 uses another scheme (using above example):\n"
"\n"
"  complete username: 1und1/11111111111\n"
"\n"
"Cyberfun:\n"
"\n"
"  complete username: sdt/11111111111\n"
"\n"
"Komtel:\n"
"  additional data:\n"
"    downstream speed class: 768\n"
"\n"
"  complete username: 11111111111@FoniNet-768\n"
"\n"
"Net Cologne:\n"
"\n"
"  complete username: 11111111111@netcologne.de\n"
"\n"
"Q-DSL:\n"
"\n"
"  complete username: 11111111111@q-dsl.de\n"
"\n"
"Versatel:\n"
"\n"
"  complete username: 11111111111@VersaNet-1024k\n"
"\n"
"Webnetix:\n"
"\n"
"  complete username: sdt/11111111111\n"
msgstr ""

#: ../pppoeconf:185
msgid "SCANNING DEVICE"
msgstr "УСКУНАЛАРНИ ТЕКШИРМОҚДА"

#: ../pppoeconf:186
#, sh-format
msgid "Looking for PPPoE Access Concentrator on $iface..."
msgstr ""

#: ../pppoeconf:188
msgid "(multi-modem mode)"
msgstr "(multi-modem усули)"

#: ../pppoeconf:210
msgid "NOT CONNECTED"
msgstr "УЛАНМАГАН"

#: ../pppoeconf:212
#, sh-format
msgid ""
"Sorry, I scanned $number interface, but the Access Concentrator of your "
"provider did not respond. Please check your network and modem cables. "
"Another reason for the scan failure may also be another running pppoe "
"process which controls the modem."
msgid_plural ""
"Sorry, I scanned $number interfaces, but the Access Concentrator of your "
"provider did not respond. Please check your network and modem cables. "
"Another reason for the scan failure may also be another running pppoe "
"process which controls the modem."
msgstr[0] ""
msgstr[1] ""

#: ../pppoeconf:226
msgid "OKAY TO MODIFY"
msgstr ""

#: ../pppoeconf:227
#, sh-format
msgid ""
"If you continue with this program, the configuration file $OPTSFILE will be "
"modified. Please make sure that you have a backup copy before saying Yes.\n"
"\n"
"Continue with configuration?"
msgstr ""

#: ../pppoeconf:307
msgid "POPULAR OPTIONS"
msgstr ""

#: ../pppoeconf:308
msgid ""
"Most people using popular dialup providers prefer the options 'noauth' and "
"'defaultroute' in their configuration and remove the 'nodetach' option. "
"Should I check your configuration file and change these settings where "
"neccessary?"
msgstr ""

#: ../pppoeconf:326
msgid "ENTER USERNAME"
msgstr ""

#: ../pppoeconf:327
msgid ""
"Please enter the username which you usually need for the PPP login to your "
"provider in the input box below. If you wish to see the help screen, delete "
"the username and press OK."
msgstr ""

#: ../pppoeconf:348
msgid "ENTER PASSWORD"
msgstr "МАХФИЙ СЎЗНИ КИРИТИНГ"

#: ../pppoeconf:349
msgid ""
"Please enter the password which you usually need for the PPP login to your "
"provider in the input box below.\n"
"\n"
"NOTE: you can see the password in plain text while typing."
msgstr ""

#: ../pppoeconf:369
msgid "USE PEER DNS"
msgstr ""

#: ../pppoeconf:370
msgid ""
"You need at least one DNS IP address to resolve the normal host names. "
"Normally your provider sends you addresses of useable servers when the "
"connection is established. Would you like to add these addresses "
"automatically to the list of nameservers in your local /etc/resolv.conf "
"file? (recommended)"
msgstr ""

#: ../pppoeconf:386
msgid "LIMITED MSS PROBLEM"
msgstr ""

#: ../pppoeconf:387
msgid ""
"Many providers have routers that do not support TCP packets with a MSS "
"higher than 1460. Usually, outgoing packets have this MSS when they go "
"through one real Ethernet link with the default MTU size (1500). "
"Unfortunately, if you are forwarding packets from other hosts (i.e. doing "
"masquerading) the MSS may be increased depending on the packet size and the "
"route to the client hosts, so your client machines won't be able to connect "
"to some sites. There is a solution: the maximum MSS can be limited by pppoe. "
"You can find more details about this issue in the pppoe documentation.\n"
"\n"
"Should pppoe clamp MSS at 1452 bytes?\n"
"\n"
"If unsure, say yes.\n"
"\n"
"(If you still get problems described above, try setting to 1412 in the dsl-"
"provider file.)"
msgstr ""

#: ../pppoeconf:416
msgid "DONE"
msgstr "ТАЙЁР"

#: ../pppoeconf:417
msgid ""
"Your PPPD is configured now. Would you like to start the connection at boot "
"time?"
msgstr ""

#: ../pppoeconf:434
msgid "ERROR"
msgstr "ХАТО"

#: ../pppoeconf:435
#, sh-format
msgid ""
"The interfaces file generated by pppoeconf appears to be invalid. This is "
"probably because pppoeconf is unable to handle your original interfaces "
"file. Should pppoeconf nevertheless change your interfaces file with the one "
"that appears to be invalid?\n"
"If you agree, you will probably break your network connectivity after "
"rebooting, and cause some local problems if lo is down. Your original "
"interfaces file will be moved to $REALINTFILE~ so you can restore it.\n"
"If not, you will have to make sure that $iface is configured before starting "
"your DSL connection and start the connection manually.\n"
"\n"
"Note that this situation is not expected and you should consider submitting "
"a bug report against pppoeconf including your original interfaces file and "
"the one generated by pppoeconf."
msgstr ""

#: ../pppoeconf:456
msgid "ESTABLISH A CONNECTION"
msgstr ""

#: ../pppoeconf:457
msgid ""
"Now, you can make a DSL connection with \"pon dsl-provider\" and terminate "
"it with \"poff\". Would you like to start the connection now?"
msgstr ""

#: ../pppoeconf:463
msgid "CONNECTION INITIATED"
msgstr ""

#: ../pppoeconf:464
msgid ""
"The DSL connection has been triggered. You can use the \"plog\" command to "
"see the status or \"ifconfig ppp0\" for general interface info."
msgstr ""

#: ../pppoeconf:476
msgid "NO INTERFACE FOUND"
msgstr "ИНТЕРФЕЙС ТОПИЛМАДИ"

#: ../pppoeconf:477
msgid "Sorry, no working ethernet card could be found."
msgstr "Ишлайдиган ethernet картани топиб бўлмади."
