diff options
| author | Ray Strode <rstrode@redhat.com> | 2015-10-27 15:56:04 -0400 |
|---|---|---|
| committer | Ray Strode <rstrode@redhat.com> | 2015-10-27 15:56:04 -0400 |
| commit | 1c78f2dfccea17fe377349cbc74326e01347283e (patch) | |
| tree | da62dde3f3e3568f92275200c31781633bc914c2 /docs | |
| parent | 755565a16ed914af4ab59529e385c29fec077e74 (diff) | |
| download | gdm-1c78f2dfccea17fe377349cbc74326e01347283e.tar.gz | |
get rid of references to slaves
I really don't want
$ git grep slave
to return hits.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/C/index.docbook | 2 | ||||
| -rw-r--r-- | docs/ca/ca.po | 2 | ||||
| -rw-r--r-- | docs/cs/cs.po | 2 | ||||
| -rw-r--r-- | docs/de/de.po | 4 | ||||
| -rw-r--r-- | docs/el/el.po | 4 | ||||
| -rw-r--r-- | docs/en_GB/en_GB.po | 8821 | ||||
| -rw-r--r-- | docs/es/es.po | 2 | ||||
| -rw-r--r-- | docs/fr/fr.po | 2 | ||||
| -rw-r--r-- | docs/gl/gl.po | 2 | ||||
| -rw-r--r-- | docs/hu/hu.po | 2 | ||||
| -rw-r--r-- | docs/id/id.po | 4 | ||||
| -rw-r--r-- | docs/ko/ko.po | 28 | ||||
| -rw-r--r-- | docs/oc/oc.po | 121 | ||||
| -rw-r--r-- | docs/pt_BR/pt_BR.po | 10 | ||||
| -rw-r--r-- | docs/ro/ro.po | 2 | ||||
| -rw-r--r-- | docs/ru/ru.po | 10 | ||||
| -rw-r--r-- | docs/sl/sl.po | 4 | ||||
| -rw-r--r-- | docs/sv/sv.po | 11 | ||||
| -rw-r--r-- | docs/te/te.po | 9 | ||||
| -rw-r--r-- | docs/uk/uk.po | 98 | ||||
| -rw-r--r-- | docs/zh_CN/zh_CN.po | 2 |
21 files changed, 15 insertions, 9127 deletions
diff --git a/docs/C/index.docbook b/docs/C/index.docbook index f41afba3..134b9bcb 100644 --- a/docs/C/index.docbook +++ b/docs/C/index.docbook @@ -1551,7 +1551,7 @@ gdm:.my.domain <para> If the Xserver does not respond in the specified number of seconds, then the connection is stopped and the session ended. - When this happens the slave daemon dies with an ALARM signal. + When this happens the daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied this setting by 2, so it may be necessary to increase the timeout if upgrading from GDM 2.20 and earlier to a newer version. diff --git a/docs/ca/ca.po b/docs/ca/ca.po index 9d6f2333..b06d3635 100644 --- a/docs/ca/ca.po +++ b/docs/ca/ca.po @@ -2704,7 +2704,7 @@ msgstr "PingIntervalSeconds=60" #: C/index.docbook:1551 msgid "" "If the Xserver does not respond in the specified number of seconds, then the " -"connection is stopped and the session ended. When this happens the slave " +"connection is stopped and the session ended. When this happens the " "daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied " "this setting by 2, so it may be necessary to increase the timeout if " "upgrading from GDM 2.20 and earlier to a newer version." diff --git a/docs/cs/cs.po b/docs/cs/cs.po index 8b90876e..efa2be24 100644 --- a/docs/cs/cs.po +++ b/docs/cs/cs.po @@ -2634,7 +2634,7 @@ msgstr "PingIntervalSeconds=60" #: C/index.docbook:1551 msgid "" "If the Xserver does not respond in the specified number of seconds, then the " -"connection is stopped and the session ended. When this happens the slave " +"connection is stopped and the session ended. When this happens the " "daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied " "this setting by 2, so it may be necessary to increase the timeout if " "upgrading from GDM 2.20 and earlier to a newer version." diff --git a/docs/de/de.po b/docs/de/de.po index d52ebad3..902b0c6f 100644 --- a/docs/de/de.po +++ b/docs/de/de.po @@ -2730,14 +2730,14 @@ msgstr "PingIntervalSeconds=60" #: C/index.docbook:1551 msgid "" "If the Xserver does not respond in the specified number of seconds, then the " -"connection is stopped and the session ended. When this happens the slave " +"connection is stopped and the session ended. When this happens the " "daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied " "this setting by 2, so it may be necessary to increase the timeout if " "upgrading from GDM 2.20 and earlier to a newer version." msgstr "" "Wenn der Xserver nicht in der festgelegten Anzahl Sekunden antwortet, dann " "wird die Verbindung unterbrochen und die Sitzung beendet. In diesem Fall " -"wird der Slave-Daemon mit einem ALARM-Signal beendet. Beachten Sie, dass GDM " +"wird der Daemon mit einem ALARM-Signal beendet. Beachten Sie, dass GDM " "2.20 und ältere diese Einstellung mit 2 multiplizierten, d.h. es kann " "erforderlich sein, dass der Zeitablauf bei einer Aktualisierung von GDM 2.20 " "oder älteren auf eine neuere Version erhöht werden muss." diff --git a/docs/el/el.po b/docs/el/el.po index e75e176f..9ae76b3a 100644 --- a/docs/el/el.po +++ b/docs/el/el.po @@ -2118,11 +2118,11 @@ msgstr "PingIntervalSeconds=60" #: C/index.docbook:1551 msgid "" "If the Xserver does not respond in the specified number of seconds, then the connection is stopped and the session ended. When this " -"happens the slave daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied this setting by 2, so it may be necessary " +"happens the daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied this setting by 2, so it may be necessary " "to increase the timeout if upgrading from GDM 2.20 and earlier to a newer version." msgstr "" "Αν ο Xserver δεν ανταποκριθεί στον προσδιορισμένο χρόνο δευτερολέπτων, τότε η σύνδεση σταματάει και η συνεδρίαση τερματίζεται. Όταν " -"αυτό γίνεται ο slave daemon τερματίζει με ένα σήμα ΣΥΝΑΓΕΡΜΟΥ. Σημειώστε ότι το GDM 2.20 και νωρίτερα πολλαπλασίαζε αυτή την επιλογή " +"αυτό γίνεται ο daemon τερματίζει με ένα σήμα ΣΥΝΑΓΕΡΜΟΥ. Σημειώστε ότι το GDM 2.20 και νωρίτερα πολλαπλασίαζε αυτή την επιλογή " "επί 2, οπότε μπορεί να είναι απαραίτητο να αυξήσετε το χρονικό όριο αν αναβαθμίζετε από το GDM 2.20 και νωρίτερα σε μία πιο πρόσφατη " "έκδοση." diff --git a/docs/en_GB/en_GB.po b/docs/en_GB/en_GB.po index 39242cfd..907568d4 100644 --- a/docs/en_GB/en_GB.po +++ b/docs/en_GB/en_GB.po @@ -2988,8824 +2988,3 @@ msgid "translator-credits" msgstr "" "David Lodge <dave@cirt.net>, 2007\n" "Philip Withnall <philip@tecnocode.co.uk>, 2009" - -#~ msgid "Bill" -#~ msgstr "Bill" - -#~ msgid "Haneman" -#~ msgstr "Haneman" - -#~ msgid "Bill.Haneman@Sun.COM" -#~ msgstr "Bill.Haneman@Sun.COM" - -#~ msgid "" -#~ "Configurator - The configuration application (<command>gdmsetup</" -#~ "command>)." -#~ msgstr "" -#~ "Configurator - The configuration application (<command>gdmsetup</" -#~ "command>)." - -#~ msgid "gdm - The Gnome Display Manager daemon (<command>gdm</command>)." -#~ msgstr "gdm - The Gnome Display Manager daemon (<command>gdm</command>)." - -#~ msgid "" -#~ "Greeter - The graphical login window (<command>gdmlogin</command> or " -#~ "<command>gdmgreeter</command>)." -#~ msgstr "" -#~ "Greeter - The graphical login window (<command>gdmlogin</command> or " -#~ "<command>gdmgreeter</command>)." - -#~ msgid "" -#~ "GTK+ Greeter - The standard login window (<command>gdmlogin</command>)." -#~ msgstr "" -#~ "GTK+ Greeter - The standard login window (<command>gdmlogin</command>)." - -#~ msgid "" -#~ "Paths that start with a word in angle brackets are relative to the " -#~ "installation prefix. I.e. <filename><share>/pixmaps/</filename> " -#~ "refers to <filename><share>/pixmaps</filename> if GDM was " -#~ "configured with <command>--prefix=/usr</command>. Normally also note that " -#~ "GDM is installed with <command>--sysconfigdir=<etc>/X11</command>, " -#~ "meaning any path to which we refer to as <filename><etc>/gdm/" -#~ "PreSession</filename> usually means <filename><etc/X11>/gdm/" -#~ "PreSession</filename>. Note that for interoperability it is recommended " -#~ "that you use a --prefix of <filename>/usr</filename> and a --sysconfdir " -#~ "of <filename><etc>/X11</filename>." -#~ msgstr "" -#~ "Paths that start with a word in angle brackets are relative to the " -#~ "installation prefix. I.e. <filename><share>/pixmaps/</filename> " -#~ "refers to <filename><share>/pixmaps</filename> if GDM was " -#~ "configured with <command>--prefix=/usr</command>. Normally also note that " -#~ "GDM is installed with <command>--sysconfigdir=<etc>/X11</command>, " -#~ "meaning any path to which we refer to as <filename><etc>/gdm/" -#~ "PreSession</filename> usually means <filename><etc/X11>/gdm/" -#~ "PreSession</filename>. Note that for interoperability it is recommended " -#~ "that you use a --prefix of <filename>/usr</filename> and a --sysconfdir " -#~ "of <filename><etc>/X11</filename>." - -#~ msgid "" -#~ "For further information about GDM, see the <ulink type=\"http\" url=" -#~ "\"http://www.gnome.org/projects/gdm/\"> the GDM project website</ulink>. " -#~ "Please submit any bug reports or enhancement requests to the \"gdm\" " -#~ "category in <ulink type=\"http\" url=\"http://bugzilla.gnome.org/" -#~ "\">bugzilla.gnome.org</ulink>. You can also send a message to the " -#~ "<address><email>gdm-list@gnome.org</email></address> mail list to discuss " -#~ "any issues or concerns with the GDM program." -#~ msgstr "" -#~ "For further information about GDM, see the <ulink type=\"http\" url=" -#~ "\"http://www.gnome.org/projects/gdm/\"> the GDM project website</ulink>. " -#~ "Please submit any bug reports or enhancement requests to the \"gdm\" " -#~ "category in <ulink type=\"http\" url=\"http://bugzilla.gnome.org/" -#~ "\">bugzilla.gnome.org</ulink>. You can also send a message to the " -#~ "<address><email>gdm-list@gnome.org</email></address> mail list to discuss " -#~ "any issues or concerns with the GDM program." - -#~ msgid "" -#~ "The key/value pairs defined in the GDM configuration files and the " -#~ "location of these files are considered \"stable\" interfaces and should " -#~ "only change in ways that are backwards compatible. Note that this " -#~ "includes functionality like the GDM scripts (Init, PreSession, " -#~ "PostSession, PostLogin, XKeepsCrashing, etc.); directory locations " -#~ "(ServAuthDir, PidFile, etc.), system applications (SoundProgram), etc. " -#~ "Some configuration values depend on OS interfaces may need to be modified " -#~ "to work on a given OS. Typical examples are HaltCommand, RebootCommand, " -#~ "CustomCommands, SuspendCommand, StandardXServer, Xnest, SoundProgram, and " -#~ "the \"command\" value for each \"server-foo\"." -#~ msgstr "" -#~ "The key/value pairs defined in the GDM configuration files and the " -#~ "location of these files are considered \"stable\" interfaces and should " -#~ "only change in ways that are backwards compatible. Note that this " -#~ "includes functionality like the GDM scripts (Init, PreSession, " -#~ "PostSession, PostLogin, XKeepsCrashing, etc.); directory locations " -#~ "(ServAuthDir, PidFile, etc.); system applications (SoundProgram); etc. " -#~ "Some configuration values depend on OS interfaces may need to be modified " -#~ "to work on a given OS. Typical examples are HaltCommand, RebootCommand, " -#~ "CustomCommands, SuspendCommand, StandardXServer, Xnest, SoundProgram and " -#~ "the \"command\" value for each \"server-foo\"." - -#~ msgid "" -#~ "Note: distributions often change the default values of keys to support " -#~ "their platform. Command-line interfaces for GDM programs installed to " -#~ "<filename><bin></filename> and <filename><sbin></filename> " -#~ "are considered stable. Refer to your distribution documentation to see if " -#~ "there are any distribution-specific changes to these GDM interfaces and " -#~ "what support exists for them." -#~ msgstr "" -#~ "Note: distributions often change the default values of keys to support " -#~ "their platform. Command-line interfaces for GDM programs installed to " -#~ "<filename><bin></filename> and <filename><sbin></filename> " -#~ "are considered stable. Refer to your distribution documentation to see if " -#~ "there are any distribution-specific changes to these GDM interfaces and " -#~ "what support exists for them." - -#~ msgid "" -#~ "As of the GDM 2.15 development series, some one-dash arguments are no " -#~ "longer supported. This includes the \"-xdmaddress\", \"-clientaddress\", " -#~ "and \"-connectionType\" arguments used by <command>gdmchooser</command>. " -#~ "These arguments have been changed to now use two dashes." -#~ msgstr "" -#~ "As of the GDM 2.15 development series, some one-dash arguments are no " -#~ "longer supported. This includes the \"-xdmaddress\", \"-clientaddress\", " -#~ "and \"-connectionType\" arguments used by <command>gdmchooser</command>. " -#~ "These arguments have been changed to use two dashes." - -#~ msgid "" -#~ "If issues are discovered that break compatibility, please file a bug with " -#~ "an \"urgent\" priority." -#~ msgstr "" -#~ "If issues are discovered that break compatibility, please file a bug with " -#~ "an \"urgent\" priority." - -#~ msgid "The GDM Daemon" -#~ msgstr "The GDM Daemon" - -#~ msgid "" -#~ "The GDM daemon supports a UNIX domain socket protocol which can be used " -#~ "to control aspects of its behavior and to query information. This " -#~ "protocol is described in the \"Controlling GDM\" section of this document." -#~ msgstr "" -#~ "The GDM daemon supports a UNIX domain socket protocol which can be used " -#~ "to control aspects of its behavior and to query information. This " -#~ "protocol is described in the \"Controlling GDM\" section of this document." - -#~ msgid "" -#~ "GDM can be asked to manage a display a number of ways. Local displays are " -#~ "always managed when GDM starts and will be restarted when a user's " -#~ "session is finished. Displays can be requested via XDMCP, flexible " -#~ "displays can be requested by running the <command>gdmflexiserver</" -#~ "command> command. Displays that are started on request are not restarted " -#~ "on session exit. GDM also provides the <command>gdmdynamic</command> " -#~ "command to allow easier management of displays on a multi-user server. " -#~ "These display types are discussed further in the next section." -#~ msgstr "" -#~ "GDM can be asked to manage a display a number of ways. Local displays are " -#~ "always managed when GDM starts and will be restarted when a user's " -#~ "session is finished. Displays can be requested via XDMCP, flexible " -#~ "displays can be requested by running the <command>gdmflexiserver</" -#~ "command> command. Displays that are started on request are not restarted " -#~ "on session exit. GDM also provides the <command>gdmdynamic</command> " -#~ "command to allow easier management of displays on a multi-user server. " -#~ "These display types are discussed further in the next section." - -#~ msgid "" -#~ "When the GDM daemon is asked to manage a display, it will fork an X " -#~ "server process, then run the <filename>Init</filename> script as the root " -#~ "user, and start the login GUI dialog as a slave process on the display. " -#~ "GDM can be configured to use either <command>gdmgreeter</command> (the " -#~ "default) or <command>gdmlogin</command> as the GUI dialog program. The " -#~ "<command>gdmlogin</command> program supports accessibility while the " -#~ "<command>gdmgreeter</command> program supports greater themeability. The " -#~ "GUI dialog is run as the unpriviledged \"gdm\" user/group which is " -#~ "described in the \"Security\" section below. The GUI dialog communicates " -#~ "with the daemon via a sockets protocol and via standard input/output. The " -#~ "slave, for example passes the username and password information to the " -#~ "GDM daemon via standard input/output so the daemon can handle the actual " -#~ "authentication." -#~ msgstr "" -#~ "When the GDM daemon is asked to manage a display, it will fork an X " -#~ "server process, then run the <filename>Init</filename> script as the root " -#~ "user, and start the login GUI dialogue as a slave process on the display. " -#~ "GDM can be configured to use either <command>gdmgreeter</command> (the " -#~ "default) or <command>gdmlogin</command> as the GUI dialogue program. The " -#~ "<command>gdmlogin</command> program supports accessibility while the " -#~ "<command>gdmgreeter</command> program supports greater themeability. The " -#~ "GUI dialogue is run as the unprivileged \"gdm\" user/group which is " -#~ "described in the \"Security\" section below. The GUI dialogue " -#~ "communicates with the daemon via a sockets protocol and via standard " -#~ "input/output. The slave, for example passes the username and password " -#~ "information to the GDM daemon via standard input/output so the daemon can " -#~ "handle the actual authentication." - -#~ msgid "" -#~ "The login GUI dialog screen allows the user to select which session they " -#~ "wish to start and which language they wish to use. Sessions are defined " -#~ "by files that end in the .desktop extension and more information about " -#~ "these files can be found in the \"Configuration\" section. The user " -#~ "enters their name and password and if these successfully authenticate, " -#~ "GDM will start the requested session for the user. It is possible to " -#~ "configure GDM to avoid the authentication process by turning on the " -#~ "Automatic or Timed Login features in the GDM configuration. The login GUI " -#~ "can also be configured to provide additional features to the user, such " -#~ "as the Face Browser; the ability to halt, restart, or suspend the system; " -#~ "and/or edit the login configuration (after entering the root password)." -#~ msgstr "" -#~ "The login GUI dialogue screen allows the user to select which session " -#~ "they wish to start and which language they wish to use. Sessions are " -#~ "defined by files that end in the .desktop extension and more information " -#~ "about these files can be found in the \"Configuration\" section. The user " -#~ "enters their name and password and if these successfully authenticate, " -#~ "GDM will start the requested session for the user. It is possible to " -#~ "configure GDM to avoid the authentication process by turning on the " -#~ "Automatic or Timed Login features in the GDM configuration. The login GUI " -#~ "can also be configured to provide additional features to the user, such " -#~ "as the Face Browser; the ability to halt, restart or suspend the system; " -#~ "and/or edit the login configuration (after entering the root password)." - -#~ msgid "" -#~ "GDM, by default, will use Pluggable Authentication Modules (PAM) for " -#~ "authentication, but can also support regular crypt and shadow passwords " -#~ "on legacy systems. After authenticating a user, the daemon runs the " -#~ "<filename>PostLogin</filename> script as root, and forks a slave process " -#~ "to start the requested session. This slave process runs the " -#~ "<filename>PreSession</filename> script as root, sets up the user's " -#~ "environment, and starts the requested session. GDM keeps track of the " -#~ "user's default session and language in the user's <filename>~/.dmrc</" -#~ "filename> and will use these defaults if the user did not pick a session " -#~ "or language in the login GUI. On Solaris, GDM (since version 2.8.0.3) " -#~ "uses the SDTLOGIN interface after user authentication to tell the X " -#~ "server to be restarted as the user instead of as root for added security. " -#~ "When the user's session exits, the GDM daemon will run the " -#~ "<filename>PostSession</filename> script as root." -#~ msgstr "" -#~ "GDM, by default, will use Pluggable Authentication Modules (PAM) for " -#~ "authentication, but can also support regular crypt and shadow passwords " -#~ "on legacy systems. After authenticating a user, the daemon runs the " -#~ "<filename>PostLogin</filename> script as root, and forks a slave process " -#~ "to start the requested session. This slave process runs the " -#~ "<filename>PreSession</filename> script as root, sets up the user's " -#~ "environment, and starts the requested session. GDM keeps track of the " -#~ "user's default session and language in the user's <filename>~/.dmrc</" -#~ "filename> and will use these defaults if the user did not pick a session " -#~ "or language in the login GUI. On Solaris, GDM (since version 2.8.0.3) " -#~ "uses the SDTLOGIN interface after user authentication to tell the X " -#~ "server to be restarted as the user instead of as root for added security. " -#~ "When the user's session exits, the GDM daemon will run the " -#~ "<filename>PostSession</filename> script as root." - -#~ msgid "" -#~ "For those looking at the code, the gdm_verify_user function in " -#~ "<filename>daemon/verify-pam.c</filename> is used for normal login and the " -#~ "gdm_verify_setup_user function is used for automatic login." -#~ msgstr "" -#~ "For those looking at the code, the gdm_verify_user function in " -#~ "<filename>daemon/verify-pam.c</filename> is used for normal login and the " -#~ "gdm_verify_setup_user function is used for automatic login." - -#~ msgid "Different Display Types" -#~ msgstr "Different Display Types" - -#~ msgid "" -#~ "GDM supports three different display types: static (local) displays, " -#~ "flexible (on-demand) displays, and XDMCP (remote) displays. The \"X " -#~ "Server Definitions\" and the \"Local Static X Display Configuration\" " -#~ "subsections of the \"Configuration\" section explains how these various " -#~ "types of displays are defined in the GDM configuration file." -#~ msgstr "" -#~ "GDM supports three different display types: static (local) displays, " -#~ "flexible (on-demand) displays, and XDMCP (remote) displays. The \"X " -#~ "Server Definitions\" and the \"Local Static X Display Configuration\" " -#~ "subsections of the \"Configuration\" section explains how these various " -#~ "types of displays are defined in the GDM configuration file." - -#~ msgid "" -#~ "Local static displays are always started by the daemon, and when they die " -#~ "or are killed, they are restarted. GDM can run as many of these as " -#~ "needed. GDM can also manage displays on which it does not manage a GUI " -#~ "login, thus GDM can be used for supporting X terminals." -#~ msgstr "" -#~ "Local static displays are always started by the daemon, and when they die " -#~ "or are killed, they are restarted. GDM can run as many of these as " -#~ "needed. GDM can also manage displays on which it does not manage a GUI " -#~ "login, thus GDM can be used for supporting X terminals." - -#~ msgid "" -#~ "Flexible, or on demand displays, are started via the socket protocol with " -#~ "the <command>gdmflexiserver</command> command. This feature is only " -#~ "available to users logged in on the console and will display a new login " -#~ "screen. If a flexible display has previously been started on the console, " -#~ "running <command>gdmflexiserver</command> again will display a menu " -#~ "allowing users to switch back to a previous session or start a new " -#~ "flexible session. The <command>gdmflexiserver</command> locks the current " -#~ "session before starting a new flexible display, so the user's password " -#~ "must be entered before returning to an existing session. The " -#~ "<command>gdmflexiserver</command> command can also be used to launch " -#~ "nested <command>Xnest</command> display. These are launched in a window " -#~ "in the user's current session. Nested displays can be started even if not " -#~ "logged into the console and are started by running the " -#~ "<command>gdmflexiserver -n</command> command. Flexible displays are not " -#~ "restarted when the user session ends. Flexible displays require virtual " -#~ "terminal (VT) support in the kernel, and will not be available if not " -#~ "supported (such as on Solaris). Nested displays require that the X server " -#~ "supports Xnest." -#~ msgstr "" -#~ "Flexible, or on demand displays, are started via the socket protocol with " -#~ "the <command>gdmflexiserver</command> command. This feature is only " -#~ "available to users logged in on the console and will display a new login " -#~ "screen. If a flexible display has previously been started on the console, " -#~ "running <command>gdmflexiserver</command> again will display a menu " -#~ "allowing users to switch back to a previous session or start a new " -#~ "flexible session. The <command>gdmflexiserver</command> locks the current " -#~ "session before starting a new flexible display, so the user's password " -#~ "must be entered before returning to an existing session. The " -#~ "<command>gdmflexiserver</command> command can also be used to launch " -#~ "nested <command>Xnest</command> display. These are launched in a window " -#~ "in the user's current session. Nested displays can be started even if not " -#~ "logged into the console and are started by running the " -#~ "<command>gdmflexiserver -n</command> command. Flexible displays are not " -#~ "restarted when the user session ends. Flexible displays require virtual " -#~ "terminal (VT) support in the kernel, and will not be available if not " -#~ "supported (such as on Solaris). Nested displays require that the X server " -#~ "supports Xnest." - -#~ msgid "" -#~ "The last display type is the XDMCP remote displays which are described in " -#~ "the next section. Remote hosts can connect to GDM and present the login " -#~ "screen if this is enabled. Some things are different for remote sessions. " -#~ "For example, the Actions menu which allows you to shut down, restart, " -#~ "suspend, or configure GDM are not shown." -#~ msgstr "" -#~ "The last display type is the XDMCP remote displays which are described in " -#~ "the next section. Remote hosts can connect to GDM and present the login " -#~ "screen if this is enabled. Some things are different for remote sessions. " -#~ "For example, the Actions menu which allows you to shut down, restart, " -#~ "suspend, or configure GDM are not shown." - -#~ msgid "" -#~ "Displays started via the <command>gdmdynamic</command> command are " -#~ "treated as local displays, so they are restarted automatically on when " -#~ "the session exits. This command is intended to more effectively manage " -#~ "the displays on a multi-user server (many displays connected to a single " -#~ "server)." -#~ msgstr "" -#~ "Displays started via the <command>gdmdynamic</command> command are " -#~ "treated as local displays, so they are restarted automatically on when " -#~ "the session exits. This command is intended to more effectively manage " -#~ "the displays on a multi-user server (many displays connected to a single " -#~ "server)." - -#~ msgid "Securing Remote Connection Through SSH" -#~ msgstr "Securing Remote Connection Through SSH" - -#~ msgid "" -#~ "As explained in the \"Security\" section, XDMCP does not use any kind of " -#~ "encryption and as such is inherently insecure. As XDMCP uses UDP as a " -#~ "network transport layer, it is not possible to simply secure it through " -#~ "an SSH tunnel." -#~ msgstr "" -#~ "As explained in the \"Security\" section, XDMCP does not use any kind of " -#~ "encryption and as such is inherently insecure. As XDMCP uses UDP as a " -#~ "network transport layer, it is not possible to simply secure it through " -#~ "an SSH tunnel." - -#~ msgid "" -#~ "To remedy this problem, gdm can be configured at compilation-time with " -#~ "the option --enable-secureremote, in which case gdm proposes as a built-" -#~ "in session a session called \"Secure Remote Connection\". Starting such a " -#~ "session allows the user to enter the name or the address of the host on " -#~ "which to connect; provided the said host runs an SSH server, the user " -#~ "then gets connected to the server on which the default X session is " -#~ "started and displayed on the local host." -#~ msgstr "" -#~ "To remedy this problem, gdm can be configured at compilation-time with " -#~ "the option --enable-secureremote, in which case gdm proposes as a built-" -#~ "in session a session called \"Secure Remote Connection\". Starting such a " -#~ "session allows the user to enter the name or the address of the host on " -#~ "which to connect, provided the said host runs an SSH server, the user is " -#~ "then connected to the server on which the default X session is started " -#~ "and displayed on the local host." - -#~ msgid "" -#~ "Using this session allows a much more secure network connection and only " -#~ "necessitates to have an SSH server running on the remote host." -#~ msgstr "" -#~ "Using this session allows a much more secure network connection and only " -#~ "necessitates to have an SSH server running on the remote host." - -#~ msgid "The GTK+ Greeter" -#~ msgstr "The GTK+ Greeter" - -#~ msgid "" -#~ "The GTK+ Greeter is the default graphical user interface that is " -#~ "presented to the user. The greeter contains a menu at the top, an " -#~ "optional face browser, an optional logo and a text entry widget. This " -#~ "greeter has full accessibility support, and should be used by users with " -#~ "accessibility needs." -#~ msgstr "" -#~ "The GTK+ Greeter is the default graphical user interface that is " -#~ "presented to the user. The greeter contains a menu at the top, an " -#~ "optional face browser, an optional logo and a text entry widget. This " -#~ "greeter has full accessibility support and should be used by users with " -#~ "accessibility needs." - -#~ msgid "" -#~ "The text entry field is used for entering logins, passwords, passphrases " -#~ "etc. <command>gdmlogin</command> is controlled by the underlying daemon " -#~ "and is basically stateless. The daemon controls the greeter through a " -#~ "simple protocol where it can ask the greeter for a text string with echo " -#~ "turned on or off. Similarly, the daemon can change the label above the " -#~ "text entry widget to correspond to the value the authentication system " -#~ "wants the user to enter." -#~ msgstr "" -#~ "The text entry field is used for entering logins, passwords, passphrases " -#~ "etc. <command>gdmlogin</command> is controlled by the underlying daemon " -#~ "and is basically stateless. The daemon controls the greeter through a " -#~ "simple protocol where it can ask the greeter for a text string with echo " -#~ "turned on or off. Similarly, the daemon can change the label above the " -#~ "text entry widget to correspond to the value the authentication system " -#~ "wants the user to enter." - -#~ msgid "" -#~ "The menu bar in the top of the greeter enables the user to select the " -#~ "requested session type/desktop environment, select an appropriate locale/" -#~ "language, halt/restart/suspend the computer, configure GDM (given the " -#~ "user knows the root password), change the GTK+ theme, or start an XDMCP " -#~ "chooser." -#~ msgstr "" -#~ "The menu bar in the top of the greeter enables the user to select the " -#~ "requested session type/desktop environment, select an appropriate locale/" -#~ "language, halt/restart/suspend the computer, configure GDM (given the " -#~ "user knows the root password), change the GTK+ theme or start an XDMCP " -#~ "chooser." - -#~ msgid "" -#~ "The greeter can optionally display a logo in the login window. The image " -#~ "must be in a format readable to the gdk-pixbuf library (GIF, JPG, PNG, " -#~ "TIFF, XPM and possibly others), and it must be readable to the GDM user. " -#~ "See the <filename>Logo</filename> option in the reference section below " -#~ "for details." -#~ msgstr "" -#~ "The greeter can optionally display a logo in the login window. The image " -#~ "must be in a format readable to the gdk-pixbuf library (GIF, JPG, PNG, " -#~ "TIFF, XPM and possibly others), and it must be readable to the GDM user. " -#~ "See the <filename>Logo</filename> option in the reference section below " -#~ "for details." - -#~ msgid "The Themed Greeter" -#~ msgstr "The Themed Greeter" - -#~ msgid "" -#~ "The Themed Greeter is a greeter interface that takes up the whole screen " -#~ "and is very themable. Themes can be selected and new themes can be " -#~ "installed by the configuration application or by setting the " -#~ "<filename>GraphicalTheme</filename> configuration key. The Themed Greeter " -#~ "is much like the GTK+ Greeter in that it is controlled by the underlying " -#~ "daemon, is stateless, and is controlled by the daemon using the same " -#~ "simple protocol." -#~ msgstr "" -#~ "The Themed Greeter is a greeter interface that takes up the whole screen " -#~ "and is very themable. Themes can be selected and new themes can be " -#~ "installed by the configuration application or by setting the " -#~ "<filename>GraphicalTheme</filename> configuration key. The Themed Greeter " -#~ "is much like the GTK+ Greeter in that it is controlled by the underlying " -#~ "daemon, is stateless, and is controlled by the daemon using the same " -#~ "simple protocol." - -#~ msgid "" -#~ "The look and feel of this greeter is really controlled by the theme and " -#~ "so the user interface elements that are present may be different. The " -#~ "only thing that must always be present is the text entry field as " -#~ "described above in the GTK+ Greeter. The theme can include buttons that " -#~ "allow the user to select an appropriate locale/language, halt/restart/" -#~ "suspend the computer, configure GDM (given the user knows the root " -#~ "password), or start an XDMCP chooser." -#~ msgstr "" -#~ "The look and feel of this greeter is really controlled by the theme and " -#~ "so the user interface elements that are present may be different. The " -#~ "only thing that must always be present is the text entry field as " -#~ "described above in the GTK+ Greeter. The theme can include buttons that " -#~ "allow the user to select an appropriate locale/language, halt/restart/" -#~ "suspend the computer, configure GDM (given the user knows the root " -#~ "password) or start an XDMCP chooser." - -#~ msgid "" -#~ "You can always get a menu of available actions by pressing the F10 key. " -#~ "This can be useful if the theme doesn't provide certain buttons when you " -#~ "wish to do some action allowed by the GDM configuration." -#~ msgstr "" -#~ "You can always get a menu of available actions by pressing the F10 key. " -#~ "This can be useful if the theme doesn't provide certain buttons when you " -#~ "wish to do some action allowed by the GDM configuration." - -#~ msgid "" -#~ "GDM supports a face browser which will display a list of users who can " -#~ "login and an icon for each user. This feature can be used with the GTK+ " -#~ "Greeter if the <filename>Browser</filename> configuration option is set " -#~ "to \"true\". This feature can be used with the Themed Greeter if using a " -#~ "GDM theme which includes a \"userlist\" item type is defined, such as " -#~ "\"happygnome-list\"" -#~ msgstr "" -#~ "GDM supports a face browser which will display a list of users who can " -#~ "login and an icon for each user. This feature can be used with the GTK+ " -#~ "Greeter if the <filename>Browser</filename> configuration option is set " -#~ "to \"true\". This feature can be used with the Themed Greeter if using a " -#~ "GDM theme which includes a \"userlist\" item type is defined, such as " -#~ "\"happygnome-list\"" - -#~ msgid "" -#~ "By default, the face browser is disabled since revealing usernames on the " -#~ "login screen is not appropriate on many systems for security reasons. " -#~ "Also GDM requires some setup to specify which users should be visible. " -#~ "Setup can be done on the \"Users\" tab in <command>gdmsetup</command>. " -#~ "This feature is most practical to use on a system with a smaller number " -#~ "of users." -#~ msgstr "" -#~ "By default, the face browser is disabled since revealing usernames on the " -#~ "login screen is not appropriate on many systems for security reasons. " -#~ "Also GDM requires some setup to specify which users should be visible. " -#~ "Setup can be done on the \"Users\" tab in <command>gdmsetup</command>. " -#~ "This feature is most practical to use on a system with a smaller number " -#~ "of users." - -#~ msgid "" -#~ "Users may run the <command>gdmphotosetup</command> command to configure " -#~ "the image to use for their userid. This program properly scales the file " -#~ "down if it is larger than the <filename>MaxIconWidth</filename> or " -#~ "<filename>MaxIconHeight</filename> configuration options and places the " -#~ "icon in a file called <filename>~/.face</filename>. Although " -#~ "<command>gdmphotosetup</command> scales user images automatically, this " -#~ "does not guarantee that user images are properly scaled since a user may " -#~ "create their <filename>~/.face</filename> file by hand." -#~ msgstr "" -#~ "Users may run the <command>gdmphotosetup</command> command to configure " -#~ "the image to use for their userid. This program properly scales the file " -#~ "down if it is larger than the <filename>MaxIconWidth</filename> or " -#~ "<filename>MaxIconHeight</filename> configuration options and places the " -#~ "icon in a file called <filename>~/.face</filename>. Although " -#~ "<command>gdmphotosetup</command> scales user images automatically, this " -#~ "does not guarantee that user images are properly scaled since a user may " -#~ "create their <filename>~/.face</filename> file by hand." - -#~ msgid "" -#~ "Please note that loading and scaling face icons located in user home " -#~ "directories can be a very time-consuming task. Since it not practical to " -#~ "load images over NIS or NFS, GDM does not attempt to load face images " -#~ "from remote home directories. Furthermore, GDM will give up loading face " -#~ "images after 5 seconds of activity and will only display the users whose " -#~ "pictures it has gotten so far. The <filename>Include</filename> " -#~ "configuration option can be used to specify a set of users who should " -#~ "appear on the face browser. As long as the users to include is of a " -#~ "reasonable size, there should not be a problem with GDM being unable to " -#~ "access the face images. To work around such problems, it is recommended " -#~ "to place face images in the directory specified by the " -#~ "<filename>GlobalFaceDir</filename> configuration option." -#~ msgstr "" -#~ "Please note that loading and scaling face icons located in user home " -#~ "directories can be a very time-consuming task. Since it not practical to " -#~ "load images over NIS or NFS, GDM does not attempt to load face images " -#~ "from remote home directories. Furthermore, GDM will give up loading face " -#~ "images after 5 seconds of activity and will only display the users whose " -#~ "pictures it has gotten so far. The <filename>Include</filename> " -#~ "configuration option can be used to specify a set of users who should " -#~ "appear on the face browser. As long as the users to include is of a " -#~ "reasonable size, there should not be a problem with GDM being unable to " -#~ "access the face images. To work around such problems, it is recommended " -#~ "to place face images in the directory specified by the " -#~ "<filename>GlobalFaceDir</filename> configuration option." - -#~ msgid "" -#~ "To control the users who get displayed in the face browser, there are a " -#~ "number of configuration options that can be used. If the " -#~ "<filename>IncludeAll</filename> option is set to true, then the password " -#~ "file will be scanned and all users will be displayed. If " -#~ "<filename>IncludeAll</filename> option is set to false, then the " -#~ "<filename>Include</filename> option should contain a list of users " -#~ "separated by commas. Only the users specified will be displayed. Any user " -#~ "listed in the <filename>Exclude</filename> option and users whose UID's " -#~ "is lower than <filename>MinimalUID</filename> will be filtered out " -#~ "regardless of the <filename>IncludeAll</filename> setting. " -#~ "<filename>IncludeAll</filename> is not recommended for systems where the " -#~ "passwords are loaded over a network (such as when NIS is used), since it " -#~ "can be very slow to load more than a small number of users over the " -#~ "network.." -#~ msgstr "" -#~ "To control the users who get displayed in the face browser, there are a " -#~ "number of configuration options that can be used. If the " -#~ "<filename>IncludeAll</filename> option is set to true, then the password " -#~ "file will be scanned and all users will be displayed. If " -#~ "<filename>IncludeAll</filename> option is set to false, then the " -#~ "<filename>Include</filename> option should contain a list of users " -#~ "separated by commas. Only the users specified will be displayed. Any user " -#~ "listed in the <filename>Exclude</filename> option and users whose UID's " -#~ "is lower than <filename>MinimalUID</filename> will be filtered out " -#~ "regardless of the <filename>IncludeAll</filename> setting. " -#~ "<filename>IncludeAll</filename> is not recommended for systems where the " -#~ "passwords are loaded over a network (such as when NIS is used), since it " -#~ "can be very slow to load more than a small number of users over the " -#~ "network.." - -#~ msgid "" -#~ "When the browser is turned on, valid usernames on the computer are " -#~ "inherently exposed to a potential intruder. This may be a bad idea if you " -#~ "do not know who can get to a login screen. This is especially true if you " -#~ "run XDMCP (turned off by default)." -#~ msgstr "" -#~ "When the browser is turned on, valid usernames on the computer are " -#~ "inherently exposed to a potential intruder. This may be a bad idea if you " -#~ "do not know who can get to a login screen. This is especially true if you " -#~ "run XDMCP (turned off by default)." - -#~ msgid "" -#~ "Output from the various X servers is stored in the GDM log directory, " -#~ "which is configurable, but is usually <filename><var>/log/gdm/</" -#~ "filename>. The output from the session can be found in a file called " -#~ "<filename><display>.log</filename>. Four older files are also " -#~ "stored with <filename>.1</filename> through <filename>.4</filename> " -#~ "appended. These will be rotated as new sessions on that display are " -#~ "started. You can use these logs to view what the X server said when it " -#~ "started up." -#~ msgstr "" -#~ "Output from the various X servers is stored in the GDM log directory, " -#~ "which is configurable, but is usually <filename><var>/log/gdm/</" -#~ "filename>. The output from the session can be found in a file called " -#~ "<filename><display>.log</filename>. Four older files are also " -#~ "stored with <filename>.1</filename> through <filename>.4</filename> " -#~ "appended. These will be rotated as new sessions on that display are " -#~ "started. You can use these logs to view what the X server said when it " -#~ "started up." - -#~ msgid "" -#~ "The output from the user session is redirected to <filename>~/.xsession-" -#~ "errors</filename> before even the <filename>PreSession</filename> script " -#~ "is started. So it is not really necessary to redirect this again in the " -#~ "session setup script. As is usually done. If the user session lasted less " -#~ "then 10 seconds, GDM assumes that the session crashed and allows the user " -#~ "to view this file in a dialog before returning to the login screen. This " -#~ "way the user can view the session errors from the last session and " -#~ "correct the problem this way." -#~ msgstr "" -#~ "The output from the user session is redirected to <filename>~/.xsession-" -#~ "errors</filename> before even the <filename>PreSession</filename> script " -#~ "is started. So it is not really necessary to redirect this again in the " -#~ "session setup script. As is usually done. If the user session lasted less " -#~ "then 10 seconds, GDM assumes that the session crashed and allows the user " -#~ "to view this file in a dialogue before returning to the login screen. " -#~ "This way the user can view the session errors from the last session and " -#~ "correct the problem this way." - -#~ msgid "" -#~ "You can suppress the 10 second warning by returning code 66 from the " -#~ "<filename>Xsession</filename>script or from your session binary (the " -#~ "default <filename>Xsession</filename> script propagates those codes " -#~ "back). This is useful if you have some sort of special logins for which " -#~ "it is not an error to return less then 10 seconds later, or if you setup " -#~ "the session to already display some error message and the GDM message " -#~ "would be confusing and redundant." -#~ msgstr "" -#~ "You can suppress the 10 second warning by returning code 66 from the " -#~ "<filename>Xsession</filename>script or from your session binary (the " -#~ "default <filename>Xsession</filename> script propagates those codes " -#~ "back). This is useful if you have some sort of special logins for which " -#~ "it is not an error to return less then 10 seconds later, or if you setup " -#~ "the session to already display some error message and the GDM message " -#~ "would be confusing and redundant." - -#~ msgid "" -#~ "The session output is piped through the GDM daemon and so the " -#~ "<filename>~/.xsession-errors</filename> file is capped at about 200 " -#~ "kilobytes by GDM to prevent a possible denial of service attack on the " -#~ "session. An app could perhaps on reading some wrong data print out " -#~ "warnings or errors on the stderr or stdout. This could perhaps fill up " -#~ "the user's home directory who would then have to log out and log back in " -#~ "to clear this. This could be especially nasty if quotas are set. GDM also " -#~ "correctly traps the XFSZ signal and stops writing the file, which would " -#~ "lead to killed sessions if the file was redirected in the old fashioned " -#~ "way from the script." -#~ msgstr "" -#~ "The session output is piped through the GDM daemon and so the " -#~ "<filename>~/.xsession-errors</filename> file is capped at about 200 " -#~ "kilobytes by GDM to prevent a possible denial of service attack on the " -#~ "session. An app could, perhaps on reading some wrong data, print out " -#~ "warnings or errors on stderr or stdout. This could fill up the user's " -#~ "home directory, who would then have to log out and log back in to clear " -#~ "this. This could be especially nasty if quotas are set. GDM also " -#~ "correctly traps the XFSZ signal and stops writing the file, which would " -#~ "lead to killed sessions if the file was redirected in the old fashioned " -#~ "way from the script." - -#~ msgid "" -#~ "Note that some distributors seem to override the <filename>~/.xsession-" -#~ "errors</filename> redirection and do it themselves in their own Xsession " -#~ "script (set by the <filename>BaseXsession</filename> configuration key) " -#~ "which means that GDM will not be able to trap the output and cap this " -#~ "file. You also lose output from the <filename>PreSession</filename> " -#~ "script which can make debugging things harder to figure out as perhaps " -#~ "useful output of what is wrong will not be printed out. See the " -#~ "description of the <filename>BaseXsession</filename> configuration key " -#~ "for more information, especially on how to handle multiple display " -#~ "managers using the same script." -#~ msgstr "" -#~ "Note that some distributors seem to override the <filename>~/.xsession-" -#~ "errors</filename> redirection and do it themselves in their own Xsession " -#~ "script (set by the <filename>BaseXsession</filename> configuration key) " -#~ "which means that GDM will not be able to trap the output and cap this " -#~ "file. You also lose output from the <filename>PreSession</filename> " -#~ "script which can make debugging things harder to figure out as perhaps " -#~ "useful output of what is wrong will not be printed out. See the " -#~ "description of the <filename>BaseXsession</filename> configuration key " -#~ "for more information, especially on how to handle multiple display " -#~ "managers using the same script." - -#~ msgid "" -#~ "If you run a system with quotas set, it would be good to delete the " -#~ "<filename>~/.xsession-errors</filename> in the <filename>PostSession</" -#~ "filename> script. Such that this log file doesn't unnecessarily stay " -#~ "around." -#~ msgstr "" -#~ "If you run a system with quotas set, it would be a good idea to delete " -#~ "the <filename>~/.xsession-errors</filename> in the <filename>PostSession</" -#~ "filename> script. So that this log file doesn't take up unnecessarily " -#~ "disk space." - -#~ msgid "Accessing Files" -#~ msgstr "Accessing Files" - -#~ msgid "" -#~ "In general GDM is very reluctant regarding reading/writing of user files " -#~ "(such as the <filename>~/.dmrc</filename>, <filename>~/.face</filename>, " -#~ "<filename>~/.xsession-errors</filename>, and <filename>~/.Xauthority</" -#~ "filename> files). For instance it refuses to access anything but regular " -#~ "files. Links, sockets and devices are ignored. The value of the " -#~ "<filename>RelaxPermissions</filename> parameter determines whether GDM " -#~ "should accept files writable by the user's group or others. These are " -#~ "ignored by default." -#~ msgstr "" -#~ "In general GDM is very reluctant regarding reading/writing of user files " -#~ "(such as the <filename>~/.dmrc</filename>, <filename>~/.face</filename>, " -#~ "<filename>~/.xsession-errors</filename>, and <filename>~/.Xauthority</" -#~ "filename> files). For instance it refuses to access anything but regular " -#~ "files. Links, sockets and devices are ignored. The value of the " -#~ "<filename>RelaxPermissions</filename> parameter determines whether GDM " -#~ "should accept files writable by the user's group or others. These are " -#~ "ignored by default." - -#~ msgid "" -#~ "All operations on user files are done with the effective user id of the " -#~ "user. If the sanity check fails on the user's <filename>.Xauthority</" -#~ "filename> file, a fallback cookie is created in the directory specified " -#~ "by the <filename>UserAuthFBDir</filename> configuration setting " -#~ "(<filename>/tmp</filename> by default)." -#~ msgstr "" -#~ "All operations on user files are done with the effective user id of the " -#~ "user. If the sanity check fails on the user's <filename>.Xauthority</" -#~ "filename> file, a fallback cookie is created in the directory specified " -#~ "by the <filename>UserAuthFBDir</filename> configuration setting " -#~ "(<filename>/tmp</filename> by default)." - -#~ msgid "" -#~ "Finally, the sysadmin can specify the maximum file size GDM should " -#~ "accept, and, if the face browser is enabled, a tunable maximum icon size " -#~ "is also enforced. On large systems it is still advised to turn off the " -#~ "face browser for performance reasons. Looking up icons in home " -#~ "directories, scaling and rendering face icons can take a long time." -#~ msgstr "" -#~ "Finally, the sysadmin can specify the maximum file size GDM should " -#~ "accept, and, if the face browser is enabled, a tunable maximum icon size " -#~ "is also enforced. On large systems it is still advised to turn off the " -#~ "face browser for performance reasons. Looking up icons in home " -#~ "directories, scaling and rendering face icons can take a long time." - -#~ msgid "GDM Performance" -#~ msgstr "GDM Performance" - -#~ msgid "" -#~ "To speed performance it is possible to build GDM so that it will preload " -#~ "libraries when GDM first displays a greeter program. This has been shown " -#~ "to speed first time login since these libraries can be loaded into memory " -#~ "while the user types in their username and password." -#~ msgstr "" -#~ "To speed performance it is possible to build GDM so that it will preload " -#~ "libraries when GDM first displays a greeter program. This has been shown " -#~ "to speed first time login since these libraries can be loaded into memory " -#~ "while the user types in their username and password." - -#~ msgid "" -#~ "To use this feature, configure GDM with the <command>--with-prefetch</" -#~ "command> option. This will cause GDM to install the <command>gdmprefetch</" -#~ "command> program to the <filename>libexecdir</filename> directory, " -#~ "install the <filename>gdmprefetchlist</filename> to the <filename><" -#~ "etc>/gdm</filename> directory, and set the <filename>PreFetchProgram</" -#~ "filename> configuration variable so that the <command>gdmprefetch</" -#~ "command> program is called with the default <filename>gdmprefetchlist</" -#~ "filename> file. The default <filename>gdmprefetchlist</filename> file was " -#~ "optimized for a GNOME desktop running on Solaris, so may need fine-tuning " -#~ "on other systems. Alternative prefetchlist files can be contributed to " -#~ "the \"gdm\" category in <ulink type=\"http\" url=\"http://bugzilla.gnome." -#~ "org/\">bugzilla.gnome.org</ulink>, so that they can be included in future " -#~ "GDM releases." -#~ msgstr "" -#~ "To use this feature, configure GDM with the <command>--with-prefetch</" -#~ "command> option. This will cause GDM to install the <command>gdmprefetch</" -#~ "command> program to the <filename>libexecdir</filename> directory, " -#~ "install the <filename>gdmprefetchlist</filename> to the <filename><" -#~ "etc>/gdm</filename> directory, and set the <filename>PreFetchProgram</" -#~ "filename> configuration variable so that the <command>gdmprefetch</" -#~ "command> program is called with the default <filename>gdmprefetchlist</" -#~ "filename> file. The default <filename>gdmprefetchlist</filename> file was " -#~ "optimised for a GNOME desktop running on Solaris, so may need fine-tuning " -#~ "on other systems. Alternative prefetchlist files can be contributed to " -#~ "the \"gdm\" category in <ulink type=\"http\" url=\"http://bugzilla.gnome." -#~ "org/\">bugzilla.gnome.org</ulink>, so that they can be included in future " -#~ "GDM releases." - -#~ msgid "" -#~ "GDM uses PAM for login authentication, though if your machine does not " -#~ "support PAM you can build GDM to work with the password database and the " -#~ "crypt library function." -#~ msgstr "" -#~ "GDM uses PAM for login authentication, though if your machine does not " -#~ "support PAM you can build GDM to work with the password database and the " -#~ "crypt library function." - -#~ msgid "" -#~ "If there is no entry for GDM in your system's PAM configuration file, " -#~ "then features like automatic login may not work. Not having an entry will " -#~ "cause GDM to use default behavior, conservative settings are recommended " -#~ "and probably shipped with your distribution." -#~ msgstr "" -#~ "If there is no entry for GDM in your system's PAM configuration file, " -#~ "then features like automatic login may not work. Not having an entry will " -#~ "cause GDM to use default behavior, conservative settings are recommended " -#~ "and probably shipped with your distribution." - -#~ msgid "" -#~ "For security reasons a dedicated user and group id are required for " -#~ "proper operation! The need to be able to write Xauth files is why user " -#~ "\"nobody\" is not appropriate for gdm." -#~ msgstr "" -#~ "For security reasons a dedicated user and group id are required for " -#~ "proper operation. The user \"nobody\" is not appropiate for gdm as the " -#~ "user needs to be able to write Xauth files." - -#~ msgid "" -#~ "The GDM daemon normally runs as root, as does the slave. However GDM " -#~ "should also have a dedicated user id and a group id which it uses for its " -#~ "graphical interfaces such as <command>gdmgreeter</command> and " -#~ "<command>gdmlogin</command>. These are configured via the <filename>User</" -#~ "filename> and <filename>Group</filename> configuration options in the GDM " -#~ "configuration files. The user and group should be created before running " -#~ "\"make install\". By default GDM assumes the user and the group are " -#~ "called \"gdm\"." -#~ msgstr "" -#~ "The GDM daemon normally runs as root, as does the slave. However GDM " -#~ "should also have a dedicated user id and a group id which it uses for its " -#~ "graphical interfaces such as <command>gdmgreeter</command> and " -#~ "<command>gdmlogin</command>. These are configured via the <filename>User</" -#~ "filename> and <filename>Group</filename> configuration options in the GDM " -#~ "configuration files. The user and group should be created before running " -#~ "\"make install\". By default GDM assumes the user and the group are " -#~ "called \"gdm\"." - -#~ msgid "" -#~ "This userid is used to run the GDM GUI programs required for login. All " -#~ "functionality that requires root authority is done by the GDM daemon " -#~ "process. This design ensures that if the GUI programs are somehow " -#~ "exploited, only the dedicated user privileges are available." -#~ msgstr "" -#~ "This userid is used to run the GDM GUI programs required for login. All " -#~ "functionality that requires root authority is done by the GDM daemon " -#~ "process. This design ensures that if the GUI programs are somehow " -#~ "exploited, only the dedicated user privileges are available." - -#~ msgid "" -#~ "It should however be noted that the GDM user and group have some " -#~ "privileges that make them somewhat dangerous. For one, they have access " -#~ "to the X server authorization directory. It must be able to read and " -#~ "write Xauth keys to <filename><var>/lib/gdm</filename>. This " -#~ "directory should have root:gdm ownership and 1770 permissions. Running " -#~ "\"make install\" will set this directory to these values. The GDM daemon " -#~ "process will reset this directory to proper ownership/permissions if it " -#~ "is somehow not set properly." -#~ msgstr "" -#~ "It should however be noted that the GDM user and group have some " -#~ "privileges that make them somewhat dangerous. For one, they have access " -#~ "to the X server authorisation directory. It must be able to read and " -#~ "write Xauth keys to <filename><var>/lib/gdm</filename>. This " -#~ "directory should have root:gdm ownership and 1770 permissions. Running " -#~ "\"make install\" will set this directory to these values. The GDM daemon " -#~ "process will reset this directory to proper ownership/permissions if it " -#~ "is somehow not set properly." - -#~ msgid "" -#~ "The danger is that someone who gains the GDM user/group privileges can " -#~ "then connect to any session. So you should not, under any circumstances, " -#~ "make this some user/group which may be easy to get access to, such as the " -#~ "user <filename>nobody</filename>. Users who gain access to the \"gdm\" " -#~ "user could also modify the Xauth keys causing Denial-Of-Service attacks. " -#~ "Also if a person gains the ability to run programs as the user \"gdm\", " -#~ "it would be possible to snoop on running GDM processes, including " -#~ "usernames and passwords as they are being typed in." -#~ msgstr "" -#~ "The danger is that someone who gains the GDM user/group privileges can " -#~ "then connect to any session. So you should not, under any circumstances, " -#~ "make this a user/group which may be easily accessed, such as the " -#~ "<filename>nobody</filename> user. Users who gain access to the \"gdm\" " -#~ "user could also modify the Xauth keys causing Denial-Of-Service attacks. " -#~ "If a person gains the ability to run programs as the user \"gdm\", it " -#~ "would be possible to snoop on running GDM processes, including usernames " -#~ "and passwords as they are being typed in." - -#~ msgid "" -#~ "Distributions and system administrators using GDM are expected to setup " -#~ "the dedicated user properly. It is recommended that this userid be " -#~ "configured to disallow login and to not have a default shell. " -#~ "Distributions and system administrators should set up the filesystem to " -#~ "ensure that the GDM user does not have read or write access to sensitive " -#~ "files." -#~ msgstr "" -#~ "Distributions and system administrators using GDM are expected to set up " -#~ "the dedicated user properly. It is recommended that this userid be " -#~ "configured to not have a default shell or be allowed to login. " -#~ "Distributions and system administrators should set up the filesystem to " -#~ "ensure that the GDM user does not have read or write access to sensitive " -#~ "files." - -#~ msgid "" -#~ "The X server authorization directory (the <filename>ServAuthDir</" -#~ "filename>) is used for a host of random internal data in addition to the " -#~ "X server authorization files, and the naming is really a relic of " -#~ "history. GDM daemon enforces this directory to be owned by <filename>root." -#~ "gdm</filename> with the permissions of 1770. This way, only root and the " -#~ "GDM group have write access to this directory, but the GDM group cannot " -#~ "remove the root owned files from this directory, such as the X server " -#~ "authorization files." -#~ msgstr "" -#~ "The X server authorisation directory (the <filename>ServAuthDir</" -#~ "filename>) is used, for legacy reasons, for a host of random internal " -#~ "data in addition to the X server authorisation files. GDM daemon enforces " -#~ "this directory to be owned by <filename>root:gdm</filename> with the " -#~ "permissions of 1770. This way only root and the gdm group have write " -#~ "access to this directory, but the gdm group cannot remove the root owned " -#~ "files from this directory, such as the X server authorisation files." - -#~ msgid "" -#~ "GDM by default doesn't trust the X server authorization directory and " -#~ "treats it in the same way as the temporary directory with respect to " -#~ "creating files. This way someone breaking the GDM user cannot mount " -#~ "attacks by creating links in this directory. Similarly the X server log " -#~ "directory is treated safely, but that directory should really be owned " -#~ "and writable only by root." -#~ msgstr "" -#~ "GDM, by default, doesn't trust the X server authorisation directory and " -#~ "treats it in the same way as the temporary directory with respect to " -#~ "creating files. This way the daemon cannot be attacked by creating links " -#~ "in this directory. Similarly the X server log directory is treated " -#~ "safely, but that directory should be owned and writable only by root." - -#~ msgid "" -#~ "On the upside, GDM's random number generation is very conservative and " -#~ "GDM goes to extraordinary measures to truly get a 128 bit random number, " -#~ "using hardware random number generators (if available), plus the current " -#~ "time (in microsecond precision), a 20 byte array of pseudorandom numbers, " -#~ "process pid's, and other random information (possibly using <filename>/" -#~ "dev/audio</filename> or <filename>/dev/mem</filename> if hardware random " -#~ "generators are not available) to create a large buffer and then run MD5 " -#~ "digest on this. Obviously, all this work is wasted if you send this " -#~ "cookie over an open network or store it on an NFS directory (see " -#~ "<filename>UserAuthDir</filename> configuration key). So be careful about " -#~ "where you use remote X display." -#~ msgstr "" -#~ "On the upside, GDM's random number generation is very conservative and " -#~ "GDM goes to extraordinary measures to get get a truly random 128 bit " -#~ "number, using hardware random number generators (if available), the " -#~ "current time (in microseconds), a 20 byte array of pseudo-random numbers, " -#~ "process pids and other random information (possibly using <filename>/dev/" -#~ "audio</filename> or <filename>/dev/mem</filename> if hardware random " -#~ "generators are not available) to create a large buffer and then runs an " -#~ "MD5 digest on this. Obviously, all this work is wasted if you send this " -#~ "cookie over an open network or store it on an NFS directory (see the " -#~ "<filename>UserAuthDir</filename> configuration key). So be careful about " -#~ "where you use remote X display." - -#~ msgid "GDM Security With NFS" -#~ msgstr "GDM Security With NFS" - -#~ msgid "" -#~ "Note that NFS traffic really goes \"over the wire\" and thus can be " -#~ "snooped. When accessing the user's X authorization file (<filename>~/." -#~ "Xauthority</filename>), GDM will try to open the file for reading as " -#~ "root. If it fails, GDM will conclude that it is on an NFS mount and it " -#~ "will automatically use <filename>UserAuthFBDir</filename>, which by " -#~ "default is set to <filename>/tmp</filename>. This behavior can be changed " -#~ "by setting the <filename>NeverPlaceCookiesOnNFS</filename> in the " -#~ "<filename>[security]</filename> section to false." -#~ msgstr "" -#~ "Note that NFS traffic really goes \"over the wire\" and can be snooped. " -#~ "When accessing the user's X authorisation file (<filename>~/.Xauthority</" -#~ "filename>), GDM will try to open the file for reading as root. If it " -#~ "fails, GDM will conclude that it is on an NFS mount and it will " -#~ "automatically use <filename>UserAuthFBDir</filename>, which by default is " -#~ "set to <filename>/tmp</filename>. This behaviour can be changed by " -#~ "setting the <filename>NeverPlaceCookiesOnNFS</filename> in the <filename>" -#~ "[security]</filename> section to false." - -#~ msgid "" -#~ "The above sections \"X Server Authentication Scheme\" and \"Firewall " -#~ "Security\" also contain important information about using XDMCP securely. " -#~ "The next section also discusses how to set up XDMCP access control." -#~ msgstr "" -#~ "The above sections \"X Server Authentication Scheme\" and \"Firewall " -#~ "Security\" also contain important information about using XDMCP securely. " -#~ "The next section also discusses how to set up XDMCP access control." - -#~ msgid "" -#~ "To workaround the inherent insecurity of XDMCP, gdm proposes a default " -#~ "built-in session that uses SSH to encrypt the remote connection. See the " -#~ "section \"Securing remote connection through SSH\" above." -#~ msgstr "" -#~ "To workaround the inherent insecurity of XDMCP, gdm proposes a default " -#~ "built-in session that uses SSH to encrypt the remote connection. See the " -#~ "section \"Securing remote connection through SSH\" above." - -#~ msgid "Using gdmsetup To Configure GDM" -#~ msgstr "Using gdmsetup To Configure GDM" - -#~ msgid "" -#~ "The <command>gdmsetup</command> application can be used to configure GDM. " -#~ "If you believe running root-owned GUI's causes security risk, then you " -#~ "would want to always edit the files by hand and not use " -#~ "<command>gdmsetup</command>. Editing the files by hand is explained in " -#~ "the \"Configuration\" section of this document. Note that " -#~ "<command>gdmsetup</command> does not support changing of all " -#~ "configuration variables, so it may be necessary to edit the files by hand " -#~ "for some configurations." -#~ msgstr "" -#~ "The <command>gdmsetup</command> application can be used to configure GDM. " -#~ "If you believe running root-owned GUIs causes a security risk, then you " -#~ "would want to always edit the files by hand and not use " -#~ "<command>gdmsetup</command>. Editing the files by hand is explained in " -#~ "the \"Configuration\" section of this document. Note that " -#~ "<command>gdmsetup</command> does not support changing of all " -#~ "configuration variables, so it may be necessary to edit the files by hand " -#~ "for some configurations." - -#~ msgid "" -#~ "The <command>gdmsetup</command> program has five tabs: Local, Remote, " -#~ "Accessibility, Security, and Users, described below. In parenthesis is " -#~ "information about which GDM configuration key is affected by each GUI " -#~ "choice. Refer to the \"Configuration\" section of this manual and the " -#~ "comments in the <share>/gdm/defaults.conf file for additional " -#~ "details about each key." -#~ msgstr "" -#~ "The <command>gdmsetup</command> program has five tabs: Local, Remote, " -#~ "Accessibility, Security, and Users, described below. In parenthesis is " -#~ "information about which GDM configuration key is affected by each GUI " -#~ "choice. Refer to the \"Configuration\" section of this manual and the " -#~ "comments in the <share>/gdm/defaults.conf file for additional " -#~ "details about each key." - -#~ msgid "Local Tab" -#~ msgstr "Local Tab" - -#~ msgid "" -#~ "The Local tab is used for controlling the appearance of GDM for local/" -#~ "static displays (non-XDMCP remote connections). The choices available in " -#~ "this tab depend on the setting of the \"Style\" combobox. This combobox " -#~ "is used to determine whether the \"Plain\" or \"Themed\" greeter GUI is " -#~ "used. The differences between these greeter programs are explained in the " -#~ "\"Overview\" section of this document." -#~ msgstr "" -#~ "The Local tab is used for controlling the appearance of GDM for local/" -#~ "static displays (non-XDMCP remote connections). The choices available in " -#~ "this tab depend on the setting of the \"Style\" combobox. This combobox " -#~ "is used to determine whether the \"Plain\" or \"Themed\" greeter GUI is " -#~ "used. The differences between these greeter programs are explained in the " -#~ "\"Overview\" section of this document." - -#~ msgid "" -#~ "If the \"Style\" choice is \"Plain\", then GDM will use the " -#~ "<command>gdmlogin</command> program as the GUI (daemon/Greeter). When " -#~ "this choice is selected, <command>gdmsetup</command> allows the user to " -#~ "select whether the background is an image or solid color (greeter/" -#~ "BackgroundType). If image is selected, there is a file selection button " -#~ "to pick the image file (greeter/BackgroundImage) and a checkbox to scale " -#~ "the image to fit the screen (greeter/BackgroundImageScaleToFit). If solid " -#~ "color is selected, there is a button available to allow the color " -#~ "selection (greeter/BackgroundColor). Also, the user may select the logo " -#~ "image that appears in gdmlogin (greeter/Logo)." -#~ msgstr "" -#~ "If the \"Style\" choice is \"Plain\", then GDM will use the " -#~ "<command>gdmlogin</command> program as the GUI (daemon/Greeter). When " -#~ "this choice is selected, <command>gdmsetup</command> allows the user to " -#~ "select whether the background is an image or solid colour (greeter/" -#~ "BackgroundType). If image is selected, there is a file selection button " -#~ "to pick the image file (greeter/BackgroundImage) and a checkbox to scale " -#~ "the image to fit the screen (greeter/BackgroundImageScaleToFit). If solid " -#~ "colour is selected, there is a button available to allow the colour " -#~ "selection (greeter/BackgroundColor). Also, the user may select the logo " -#~ "image that appears in gdmlogin (greeter/Logo)." - -#~ msgid "" -#~ "If the \"Style\" choice is \"Plain with face browser\", then the " -#~ "<command>gdmlogin</command> program is used as the GUI (daemon/Greeter) " -#~ "and the face browser is turned on (greeter/Browser). The Face Browser is " -#~ "explained in the Overview section. Otherwise, the choices are the same as " -#~ "when the \"Style\" choice is \"Plain\". Additional setup in the Users tab " -#~ "may be necessary to choose which users appear in the Face Browser." -#~ msgstr "" -#~ "If the \"Style\" choice is \"Plain with face browser\", then the " -#~ "<command>gdmlogin</command> program is used as the GUI (daemon/Greeter) " -#~ "and the face browser is turned on (greeter/Browser). The Face Browser is " -#~ "explained in the Overview section. Otherwise, the choices are the same as " -#~ "when the \"Style\" choice is \"Plain\". Additional setup in the Users tab " -#~ "may be necessary to choose which users appear in the Face Browser." - -#~ msgid "" -#~ "If the \"Style\" choice is \"Themed\", then the <command>gdmgreeter</" -#~ "command> program is used as the GUI (daemon/Greeter). When this choice is " -#~ "selected, <command>gdmsetup</command> allows the user to select the theme " -#~ "to be used (greeter/GraphicalTheme). Note that the checkbox to the left " -#~ "of the theme's name must be checked for a theme to be selected. Clicking " -#~ "on the theme, but not selecting the checkbox will highlight the theme and " -#~ "the \"Remove\" button can be used to delete the theme. Information about " -#~ "the theme's author and copyright are shown for the highlighted theme. The " -#~ "\"Add\" button can be used to add new themes to the system. To turn on " -#~ "the Face Browser, a theme which includes a Face Browser must be selected, " -#~ "such as happygnome-list. The \"Background color\" displayed when GDM " -#~ "starts (and if the theme has transparent elements) can also be selected " -#~ "(greeter/GraphicalThemedColor). The \"Theme\" combo box may be set to " -#~ "\"Random from selected\" if you want a random theme to be used for each " -#~ "login (greeter/GraphicalThemeRand and greeter/GraphicalThemes). To use " -#~ "random themes, select each theme that you wish to be used. By default " -#~ "this combobox is set to \"Selected only\", so that only a single theme " -#~ "can be selected and be used." -#~ msgstr "" -#~ "If the \"Style\" choice is \"Themed\", then the <command>gdmgreeter</" -#~ "command> program is used as the GUI (daemon/Greeter). When this choice is " -#~ "selected, <command>gdmsetup</command> allows the user to select the theme " -#~ "to be used (greeter/GraphicalTheme). Note that the checkbox to the left " -#~ "of the theme's name must be checked for a theme to be selected. Clicking " -#~ "on the theme, but not selecting the checkbox will highlight the theme and " -#~ "the \"Remove\" button can be used to delete the theme. Information about " -#~ "the theme's author and copyright are shown for the highlighted theme. The " -#~ "\"Add\" button can be used to add new themes to the system. To turn on " -#~ "the Face Browser, a theme which includes a Face Browser must be selected, " -#~ "such as happygnome-list. The \"Background colocr\" displayed when GDM " -#~ "starts (and if the theme has transparent elements) can also be selected " -#~ "(greeter/GraphicalThemedColor). The \"Theme\" combo box may be set to " -#~ "\"Random from selected\" if you want a random theme to be used for each " -#~ "login (greeter/GraphicalThemeRand and greeter/GraphicalThemes). To use " -#~ "random themes, select each theme that you wish to be used. By default " -#~ "this combobox is set to \"Selected only\", so that only a single theme " -#~ "can be selected and be used." - -#~ msgid "" -#~ "Regardless of the \"Style\" choice, the user may also select whether the " -#~ "Actions menu is visible (greeter/SystemMenu), whether the Actions menu " -#~ "includes the choice to start <command>gdmsetup</command> (greeter/" -#~ "ConfigAvailable), and whether the Action menu includes the choice to " -#~ "start <command>gdmchooser</command> to run a remote XDMCP login session " -#~ "(greeter/ChooserButton). Note that the root password must be entered to " -#~ "start <command>gdmsetup</command> from the login screen if it is enabled. " -#~ "Also the Welcome message displayed for local sessions may be selected " -#~ "(greeter/DefaultWelcome and greeter/Welcome). The Welcome message can " -#~ "contain the character sequences described in the \"Text Node\" section of " -#~ "the \"Themed Greeter\" section of this manual." -#~ msgstr "" -#~ "Regardless of the \"Style\" choice, the user may also select whether the " -#~ "Actions menu is visible (greeter/SystemMenu), whether the Actions menu " -#~ "includes the choice to start <command>gdmsetup</command> (greeter/" -#~ "ConfigAvailable), and whether the Action menu includes the choice to " -#~ "start <command>gdmchooser</command> to run a remote XDMCP login session " -#~ "(greeter/ChooserButton). Note that the root password must be entered to " -#~ "start <command>gdmsetup</command> from the login screen if it is enabled. " -#~ "Also the Welcome message displayed for local sessions may be selected " -#~ "(greeter/DefaultWelcome and greeter/Welcome). The Welcome message can " -#~ "contain the character sequences described in the \"Text Node\" section of " -#~ "the \"Themed Greeter\" section of this manual." - -#~ msgid "Remote Tab" -#~ msgstr "Remote Tab" - -#~ msgid "" -#~ "The Remote tab controls the appearance of the GDM for users logging in " -#~ "via XDMCP. By default XDMCP is disabled, and users should be comfortable " -#~ "with the XDMCP-related sections of the Security section of this document " -#~ "before enabling it. This tab includes a \"Style\" combobox which can be " -#~ "used to turn on XDMCP and control the appearance of GDM for remote users " -#~ "(gui/RemoteGreeter and xdmcp/Enable). This combobox may be set to " -#~ "\"Remote login disabled\" or \"Same as Local\". If the Local tab is set " -#~ "to \"Plain\" or \"Plain with Face Browser\", then the user may also " -#~ "select \"Themed\". If the Local tab is set to \"Themed\", then the user " -#~ "may also select \"Plain\" or \"Plain with face browser\". It is " -#~ "recommended that the \"Plain\" GUI be used for remote connections since " -#~ "it is more lightweight and tends to have better performance across a " -#~ "network." -#~ msgstr "" -#~ "The Remote tab controls the appearance of the GDM for users logging in " -#~ "via XDMCP. By default XDMCP is disabled, and users should be comfortable " -#~ "with the XDMCP-related sections of the Security section of this document " -#~ "before enabling it. This tab includes a \"Style\" combobox which can be " -#~ "used to turn on XDMCP and control the appearance of GDM for remote users " -#~ "(gui/RemoteGreeter and xdmcp/Enable). This combobox may be set to " -#~ "\"Remote login disabled\" or \"Same as Local\". If the Local tab is set " -#~ "to \"Plain\" or \"Plain with Face Browser\", then the user may also " -#~ "select \"Themed\". If the Local tab is set to \"Themed\", then the user " -#~ "may also select \"Plain\" or \"Plain with face browser\". It is " -#~ "recommended that the \"Plain\" GUI be used for remote connections since " -#~ "it is more lightweight and tends to have better performance across a " -#~ "network." - -#~ msgid "" -#~ "If Remote login is enabled, then the user can specify the remote Welcome " -#~ "Message to be displayed (greeter/DefaultRemoteWelcome and greeter/" -#~ "RemoteWelcome). This welcome message is separate from the Local welcome " -#~ "message and can have a different value. The Welcome message can contain " -#~ "the character sequences described in the \"Text Node\" section of the " -#~ "\"Themed Greeter\" section of this manual." -#~ msgstr "" -#~ "If Remote login is enabled, then the user can specify the remote Welcome " -#~ "Message to be displayed (greeter/DefaultRemoteWelcome and greeter/" -#~ "RemoteWelcome). This welcome message is separate from the Local welcome " -#~ "message and can have a different value. The Welcome message can contain " -#~ "the character sequences described in the \"Text Node\" section of the " -#~ "\"Themed Greeter\" section of this manual." - -#~ msgid "" -#~ "If the \"Style\" choice is \"Same as Local\" and the local selection is " -#~ "\"Plain\" or \"Plain with face browser\", then the user may select " -#~ "whether background images should be displayed for remote logins (greeter/" -#~ "BackgroundRemoteOnlyColor)." -#~ msgstr "" -#~ "If the \"Style\" choice is \"Same as Local\" and the local selection is " -#~ "\"Plain\" or \"Plain with face browser\", then the user may select " -#~ "whether background images should be displayed for remote logins (greeter/" -#~ "BackgroundRemoteOnlyColor)." - -#~ msgid "" -#~ "If the \"Style\" choice is enabled and set to a different value than the " -#~ "Local tab, then the user has the same configuration choices as found on " -#~ "the Local tab except that the System Menu choices are not available since " -#~ "this is never available for remote logins for security purposes." -#~ msgstr "" -#~ "If the \"Style\" choice is enabled and set to a different value than the " -#~ "Local tab, then the user has the same configuration choices as found on " -#~ "the Local tab except that the System Menu choices are not available since " -#~ "this is never available for remote logins for security purposes." - -#~ msgid "" -#~ "If Remote login is enabled, there is a \"Configure XDMCP\" button which " -#~ "displays a dialog allowing the user to set XDMCP configuration, including " -#~ "whether indirect requests are honored (xdmcp/HonorIndirect), UDP port " -#~ "(xdmcp/Port), maximum pending requests (xdmcp/MaxPending), maximum " -#~ "pending indirect requests (xmdcp/MaxPendingIndirect), maximum remote " -#~ "sessions (xdmcp/MaxSessions), maximum wait time (xdmcp/MaxWait), maximum " -#~ "indirect wait time (xdmcp/MaxWaitIndirect), displays per host (xdmcp/" -#~ "DisplaysPerHost), and ping interval (xdmcp/PingIntervalSeconds). The " -#~ "default settings are standard settings and should only be changed by " -#~ "someone who understands the ramifications of the change." -#~ msgstr "" -#~ "If remote login is enabled, there is a \"Configure XDMCP\" button which " -#~ "displays a dialogue allowing the user to set up XDMCP configuration, " -#~ "including whether indirect requests are honoured (xdmcp/HonorIndirect), " -#~ "UDP port (xdmcp/Port), maximum pending requests (xdmcp/MaxPending), " -#~ "maximum pending indirect requests (xmdcp/MaxPendingIndirect), maximum " -#~ "remote sessions (xdmcp/MaxSessions), maximum wait time (xdmcp/MaxWait), " -#~ "maximum indirect wait time (xdmcp/MaxWaitIndirect), displays per host " -#~ "(xdmcp/DisplaysPerHost) and ping interval (xdmcp/PingIntervalSeconds). " -#~ "The default settings are standard settings and should only be changed by " -#~ "someone who understands the ramifications of the change." - -#~ msgid "Accessibility Tab" -#~ msgstr "Accessibility Tab" - -#~ msgid "" -#~ "The Accessibility tab is used to turn on Accessibility features in GDM. " -#~ "\"Enable accessible login\" (daemon/AddGtkModules and daemon/" -#~ "GtkModulesList) turns on GDM's gesture listeners which are explained in " -#~ "the \"Accessibility\" section of this document. There is also a checkbox " -#~ "to allow users to change the theme when using the Plain greeter (gui/" -#~ "AllowGtkThemeChange). This feature allows GDM users to switch the theme " -#~ "to the HighContrast or LowContrast themes if needed. The user may also " -#~ "select whether GDM should play a sound when the login screen is ready, " -#~ "when login is successful and when login has failed. File chooser buttons " -#~ "are used to select the sound file to be played, and the \"Play\" button " -#~ "can be used to sample the sound." -#~ msgstr "" -#~ "The Accessibility tab is used to turn on Accessibility features in GDM. " -#~ "\"Enable accessible login\" (daemon/AddGtkModules and daemon/" -#~ "GtkModulesList) turns on GDM's gesture listeners which are explained in " -#~ "the \"Accessibility\" section of this document. There is also a checkbox " -#~ "to allow users to change the theme when using the Plain greeter (gui/" -#~ "AllowGtkThemeChange). This feature allows GDM users to switch the theme " -#~ "to the HighContrast or LowContrast themes if needed. The user may also " -#~ "select whether GDM should play a sound when the login screen is ready, " -#~ "when login is successful and when login has failed. File chooser buttons " -#~ "are used to select the sound file to be played, and the \"Play\" button " -#~ "can be used to sample the sound." - -#~ msgid "Security Tab" -#~ msgstr "Security Tab" - -#~ msgid "" -#~ "The Security tab allows the user to turn on Automatic and Timed login, " -#~ "which user is logged in via an automatic or timed login, and the timed " -#~ "login delay (daemon/AutomaticLoginEnable, daemon/AutomaticLogin, daemon/" -#~ "TimedLoginEnable, daemon/TimedLogin, and daemon/TimedLoginDelay). If " -#~ "automatic login is turned on, then the specified user will immediately " -#~ "log in on reboot without GDM asking for username/password. If the user " -#~ "logs out of their session, GDM will start and ask for username and " -#~ "password to log back in. If TimedLogin is turned on, then GDM will log in " -#~ "to the specified user after a specified number of seconds. The user may " -#~ "enable Timed Login for remote (XDMCP) connections by checking the \"Allow " -#~ "remote timed logins\" checkbox." -#~ msgstr "" -#~ "The Security tab allows the user to turn on Automatic and Timed login, " -#~ "which user is logged in via an automatic or timed login and the timed " -#~ "login delay (daemon/AutomaticLoginEnable, daemon/AutomaticLogin, daemon/" -#~ "TimedLoginEnable, daemon/TimedLogin and daemon/TimedLoginDelay). If " -#~ "automatic login is turned on, then the specified user will immediately " -#~ "log in on reboot without GDM asking for a username and password. If the " -#~ "user logs out of their session, GDM will start and ask for username and " -#~ "password to log back in. If TimedLogin is turned on, then GDM will log in " -#~ "to the specified user after a specified number of seconds. The user may " -#~ "enable Timed Login for remote (XDMCP) connections by checking the \"Allow " -#~ "remote timed logins\" checkbox." - -#~ msgid "" -#~ "On this tab, the user may select whether the system administrator user " -#~ "can log in, and whether the system administrator user can log in via " -#~ "remote (XDMCP) connections (security/AllowRoot and security/" -#~ "AllowRemoteRoot). The user may turn on GDM debug (debug/Enable) which " -#~ "causes debug messages to be sent to the system log. Debug should only be " -#~ "used when diagnosing a problem and not be left on when not needed. The " -#~ "\"Deny TCP connections to Xserver\" choice will disable X forwarding if " -#~ "selected (security/DisallowTCP). A login retry delay (security/" -#~ "RetryDelay) can be set to cause GDM to wait a number of seconds after a " -#~ "failed login." -#~ msgstr "" -#~ "On this tab, the user may select whether the system administrator user " -#~ "can log in, and whether the system administrator user can log in via " -#~ "remote (XDMCP) connections (security/AllowRoot and security/" -#~ "AllowRemoteRoot). The user may turn on GDM debug (debug/Enable) which " -#~ "causes debug messages to be sent to the system log. Debug should only be " -#~ "used when diagnosing a problem and not be left on when not needed. The " -#~ "\"Deny TCP connections to Xserver\" choice will disable X forwarding if " -#~ "selected (security/DisallowTCP). A login retry delay (security/" -#~ "RetryDelay) can be set to cause GDM to wait a number of seconds after a " -#~ "failed login." - -#~ msgid "" -#~ "The \"Configure X Server\" button can be used to specify how GDM manages " -#~ "each display. The \"Servers\" combobox shows what server definitions are " -#~ "available (Standard, Terminal, and Chooser by default). Refer to the \"X " -#~ "Server Definitions\" section of the \"Configuration\" section for more " -#~ "information about how to create new Server Definitions." -#~ msgstr "" -#~ "The \"Configure X Server\" button can be used to specify how GDM manages " -#~ "each display. The \"Servers\" combobox shows what server definitions are " -#~ "available (Standard, Terminal, and Chooser by default). Refer to the \"X " -#~ "Server Definitions\" section of the \"Configuration\" section for more " -#~ "information about how to create new Server Definitions." - -#~ msgid "" -#~ "For any server type, the user may modify the \"Server Name\" (server/" -#~ "name), the \"Command\" (server/command) to be used to launch the Xserver, " -#~ "whether the server type will \"Launch\" (server/chooser) the greeter or " -#~ "chooser GUI after starting the Xserver, whether GDM handles this type " -#~ "(normally only set to false when logging into a Terminal session type), " -#~ "and whether the session type supports \"Flexible\" (server/flexible) " -#~ "sessions." -#~ msgstr "" -#~ "For any server type, the user may modify the \"Server Name\" (server/" -#~ "name), the \"Command\" (server/command) to be used to launch the Xserver, " -#~ "whether the server type will \"Launch\" (server/chooser) the greeter or " -#~ "chooser GUI after starting the Xserver, whether GDM handles this type " -#~ "(normally only set to false when logging into a Terminal session type), " -#~ "and whether the session type supports \"Flexible\" (server/flexible) " -#~ "sessions." - -#~ msgid "" -#~ "The \"Servers To Start\" section shows what server type is displayed for " -#~ "each display on the machine. Users may click on the \"Add/Modify\" button " -#~ "to add a new display to the list or to modify a selected display. This " -#~ "simply corresponds each physical display with the Server Definition to be " -#~ "used for managing that display. The \"Remove\" button may be used to " -#~ "remove a display from the list." -#~ msgstr "" -#~ "The \"Servers To Start\" section shows what server type is displayed for " -#~ "each display on the machine. Users may click on the \"Add/Modify\" button " -#~ "to add a new display to the list or to modify a selected display. This " -#~ "simply corresponds each physical display with the Server Definition to be " -#~ "used for managing that display. The \"Remove\" button may be used to " -#~ "remove a display from the list." - -#~ msgid "Users Tab" -#~ msgstr "Users Tab" - -#~ msgid "" -#~ "The Users tab controls which users appear in the Face Browser. If the " -#~ "\"Include all users from /etc/password\" checkbox is selected, then all " -#~ "users (with a userid above greeter/MinimalUID and not in the Exclude " -#~ "list) are displayed. If this checkbox is not selected, then users must be " -#~ "added to the \"Include\" list. Users in the \"Exclude\" list are never " -#~ "displayed. The \"Add\" and \"Remove\" buttons are used to add a new user " -#~ "to the list or remove a selected user from the list. The \"Apply User " -#~ "Changes\" button must be pressed after the \"Include\" and \"Exclude\" " -#~ "lists have been modified. The left and right arrow buttons between the " -#~ "\"Include\" and \"Exclude\" lists can be used to move a selected user " -#~ "from one list to the other." -#~ msgstr "" -#~ "The Users tab controls which users appear in the Face Browser. If the " -#~ "\"Include all users from /etc/password\" checkbox is selected, then all " -#~ "users (with a userid above greeter/MinimalUID and not in the Exclude " -#~ "list) are displayed. If this checkbox is not selected, then users must be " -#~ "added to the \"Include\" list. Users in the \"Exclude\" list are never " -#~ "displayed. The \"Add\" and \"Remove\" buttons are used to add a new user " -#~ "to the list or remove a selected user from the list. The \"Apply User " -#~ "Changes\" button must be pressed after the \"Include\" and \"Exclude\" " -#~ "lists have been modified. The left and right arrow buttons between the " -#~ "\"Include\" and \"Exclude\" lists can be used to move a selected user " -#~ "from one list to the other." - -#~ msgid "" -#~ "GDM has powerful configuration management. System configuration is stored " -#~ "in <filename><share>/gdm/defaults.conf</filename> and the intention " -#~ "is that this file can be stored on a shared filesystem so that sysadmins " -#~ "can have a single file to modify to control configuration for multiple " -#~ "machines. Also GDM distributions may patch this file on update to improve " -#~ "usability, improve security, etc. Configuration may be customized for a " -#~ "specific machine by editing the <filename><etc>/gdm/custom.conf</" -#~ "filename> file to include an override for a specific key. Those " -#~ "parameters in the \"gui\", \"greeter\" sections, and the security/" -#~ "PamStack key may be customized per-display by specifying them in a file " -#~ "named <filename><etc>/gdm/custom.conf<display num></" -#~ "filename>. For example, configuration overrides for display \":103\" " -#~ "would be stored in the file <filename><etc>/gdm/custom.conf:0</" -#~ "filename>. Per-display configuration is supported in GDM 2.14.6 and later." -#~ msgstr "" -#~ "GDM has powerful configuration management. System configuration is stored " -#~ "in <filename><share>/gdm/defaults.conf</filename> and the intention " -#~ "is that this file can be stored on a shared filesystem so that sysadmins " -#~ "can have a single file to modify to control configuration for multiple " -#~ "machines. Also GDM distributions may patch this file on update to improve " -#~ "usability, improve security, etc. Configuration may be customised for a " -#~ "specific machine by editing the <filename><etc>/gdm/custom.conf</" -#~ "filename> file to include an override for a specific key. Those " -#~ "parameters in the \"gui\", \"greeter\" sections, and the security/" -#~ "PamStack key may be customised per-display by specifying them in a file " -#~ "named <filename><etc>/gdm/custom.conf<display num></" -#~ "filename>. For example, configuration overrides for display \":103\" " -#~ "would be stored in the file <filename><etc>/gdm/custom.conf:0</" -#~ "filename>. Per-display configuration is supported in GDM 2.14.6 and later." - -#~ msgid "" -#~ "The <command>gdmsetup</command> is a GUI program you can use to edit the " -#~ "GDM configuration. This program may also be launched directly from the " -#~ "login screen if the greeter/ConfigAvailable key is set to \"true\" Not " -#~ "all keys in the GDM configuration file are supported in the GUI, so you " -#~ "may need to edit the configuration files by hand to edit these keys. If " -#~ "you believe running root-owned GUI's causes security risk, then you would " -#~ "want to always edit the files by hand. This program does not support " -#~ "setting per-display configuration, so per-display configuration files " -#~ "must be set up by hand." -#~ msgstr "" -#~ "The <command>gdmsetup</command> is a GUI program you can use to edit the " -#~ "GDM configuration. This program may also be launched directly from the " -#~ "login screen if the greeter/ConfigAvailable key is set to \"true\" Not " -#~ "all keys in the GDM configuration file are supported in the GUI, so you " -#~ "may need to edit the configuration files by hand to edit these keys. If " -#~ "you believe running root-owned GUI's causes security risk, then you would " -#~ "want to always edit the files by hand. This program does not support " -#~ "setting per-display configuration, so per-display configuration files " -#~ "must be set up by hand." - -#~ msgid "" -#~ "Distributions should edit the <filename><share>/gdm/defaults.conf</" -#~ "filename> file to establish the default values so these are preserved as " -#~ "defaults and not modified by users modifying their personal configuration " -#~ "file <filename><etc>/gdm/custom.conf</filename>." -#~ msgstr "" -#~ "Distributions should edit the <filename><share>/gdm/defaults.conf</" -#~ "filename> file to establish the default values so these are preserved as " -#~ "defaults and not modified by users modifying their personal configuration " -#~ "file <filename><etc>/gdm/custom.conf</filename>." - -#~ msgid "" -#~ "If you want to change configuration by hand, edit the <filename><" -#~ "etc>/gdm/custom.conf</filename> file and make sure the keyname=value " -#~ "pair you want is included in the appropriate section. For example, to " -#~ "change the \"Greeter\" key in the \"daemon\" section, make sure the " -#~ "daemon section of the <filename><etc>/gdm/custom.conf</filename> " -#~ "file has the value like in this example." -#~ msgstr "" -#~ "If you want to change configuration by hand, edit the <filename><" -#~ "etc>/gdm/custom.conf</filename> file and make sure the keyname=value " -#~ "pair you want is included in the appropriate section. For example, to " -#~ "change the \"Greeter\" key in the \"daemon\" section, make sure the " -#~ "daemon section of the <filename><etc>/gdm/custom.conf</filename> " -#~ "file has the value like in this example." - -#~ msgid "" -#~ "\n" -#~ "[daemon]\n" -#~ "Greeter=/usr/lib/gdmgreeter\n" -#~ msgstr "" -#~ "\n" -#~ "[daemon]\n" -#~ "Greeter=/usr/lib/gdmgreeter\n" - -#~ msgid "" -#~ "The configuration files (especially the <filename><share>/gdm/" -#~ "defaults.conf</filename> and <filename><etc>/gdm/custom.conf</" -#~ "filename> files) contain useful comments and examples, so read them for " -#~ "more information about changing your configuration. GDM considers lines " -#~ "that start with the \"#\" character a comment, and these lines will be " -#~ "ignored by GDM. Some keys in the <filename><share>/gdm/defaults." -#~ "conf</filename> are commented out while others are set. Commented out " -#~ "values show the default value." -#~ msgstr "" -#~ "The configuration files (especially the <filename><share>/gdm/" -#~ "defaults.conf</filename> and <filename><etc>/gdm/custom.conf</" -#~ "filename> files) contain useful comments and examples, so read them for " -#~ "more information about changing your configuration. GDM considers lines " -#~ "that start with the \"#\" character a comment, and these lines will be " -#~ "ignored by GDM. Some keys in the <filename><share>/gdm/defaults." -#~ "conf</filename> are commented out while others are set. Commented out " -#~ "values show the default value." - -#~ msgid "" -#~ "The <filename><share>/gdm/defaults.conf</filename> file contains " -#~ "the default configuration choices for GDM, and should not be modified by " -#~ "the user. The <filename><etc>/gdm/custom.conf</filename> file is " -#~ "where users may specify their custom configuration choices. Configuration " -#~ "options specified in the <filename><etc>/gdm/custom.conf</filename> " -#~ "file override the values in the main <filename><share>/gdm/defaults." -#~ "conf</filename> file. Running the <command>gdmsetup</command> command " -#~ "will cause the <filename><etc>/gdm/custom.conf</filename> to be " -#~ "modified with the user's configuration choices and will cause any running " -#~ "GDM GUI programs to automatically update. Previous to version 2.13.0.4 " -#~ "GDM only supported the <filename><etc>/gdm/gdm.conf</filename> " -#~ "file, so if using an older version of GDM just edit that file directly." -#~ msgstr "" -#~ "The <filename><share>/gdm/defaults.conf</filename> file contains " -#~ "the default configuration choices for GDM, and should not be modified by " -#~ "the user. The <filename><etc>/gdm/custom.conf</filename> file is " -#~ "where users may specify their custom configuration choices. Configuration " -#~ "options specified in the <filename><etc>/gdm/custom.conf</filename> " -#~ "file override the values in the main <filename><share>/gdm/defaults." -#~ "conf</filename> file. Running the <command>gdmsetup</command> command " -#~ "will cause the <filename><etc>/gdm/custom.conf</filename> to be " -#~ "modified with the user's configuration choices and will cause any running " -#~ "GDM GUI programs to automatically update. Previous to version 2.13.0.4 " -#~ "GDM only supported the <filename><etc>/gdm/gdm.conf</filename> " -#~ "file, so if using an older version of GDM just edit that file directly." - -#~ msgid "" -#~ "The location of the configuration files may be controlled via the " -#~ "<command>--with-defaults-conf</command> and <command>--with-custom-conf</" -#~ "command> configuration options. The GDM daemon --config option may also " -#~ "be used to specify the configuration file location. The GDM daemon must " -#~ "be restarted to change the configuration file being used." -#~ msgstr "" -#~ "The location of the configuration files may be controlled via the " -#~ "<command>--with-defaults-conf</command> and <command>--with-custom-conf</" -#~ "command> configuration options. The GDM daemon --config option may also " -#~ "be used to specify the configuration file location. The GDM daemon must " -#~ "be restarted to change the configuration file being used." - -#~ msgid "" -#~ "<filename><share>/gdm/factory-defaults.conf</filename> is the " -#~ "configuration file as shipped with the daemon. This can be useful for to " -#~ "see if the <filename><share>/gdm/defaults.conf</filename> file has " -#~ "been changed." -#~ msgstr "" -#~ "<filename><share>/gdm/factory-defaults.conf</filename> is the " -#~ "configuration file as shipped with the daemon. This can be useful for to " -#~ "see if the <filename><share>/gdm/defaults.conf</filename> file has " -#~ "been changed." - -#~ msgid "" -#~ "The other GDM configuration files are located, by default, in the " -#~ "<filename><etc>/gdm/</filename> folder or its subdirectories. " -#~ "However, the location of all configuration files are defined in the GDM " -#~ "configuration files, so the sysadmin may choose to locate these files in " -#~ "any location." -#~ msgstr "" -#~ "The other GDM configuration files are located, by default, in the " -#~ "<filename><etc>/gdm/</filename> folder or its subdirectories. " -#~ "However, the location of all configuration files are defined in the GDM " -#~ "configuration files, so the sysadmin may choose to locate these files in " -#~ "any location." - -#~ msgid "This is a listing of the config directory contents:" -#~ msgstr "This is a listing of the config directory contents:" - -#~ msgid "" -#~ "<filename>locale.alias</filename> is a file which looks much like the " -#~ "system locale alias but in fact it is not the same. These are the " -#~ "languages that are available on your system. All the languages are still " -#~ "tested to see if they actually exist before presenting them to the user." -#~ msgstr "" -#~ "<filename>locale.alias</filename> is a file which looks much like the " -#~ "system locale alias but in fact it is not the same. These are the " -#~ "languages that are available on your system. All the languages are still " -#~ "tested to see if they actually exist before presenting them to the user." - -#~ msgid "" -#~ "<filename>Xsession</filename> is a script which sets up a user session " -#~ "and then executes the user's choice of session. Note that the session " -#~ "script is typically started via the <filename>desktop</filename> file " -#~ "associated with the session the user has picked. Some sessions may start " -#~ "the user's session via a different mechanism than the <filename>Xsession</" -#~ "filename> script, so please check the appropriate <filename>desktop</" -#~ "filename> before assuming a session startup issue is being caused by this " -#~ "file." -#~ msgstr "" -#~ "<filename>Xsession</filename> is a script which sets up a user session " -#~ "and then executes the user's choice of session. Note that the session " -#~ "script is typically started via the <filename>desktop</filename> file " -#~ "associated with the session the user has picked. Some sessions may start " -#~ "the user's session via a different mechanism than the <filename>Xsession</" -#~ "filename> script, so please check the appropriate <filename>desktop</" -#~ "filename> before assuming a session startup issue is being caused by this " -#~ "file." - -#~ msgid "" -#~ "<filename>XKeepsCrashing</filename> is a script which gets run when the X " -#~ "server keeps crashing and we cannot recover. The shipped default script " -#~ "will work with most Linux distributions and can run the X configuration " -#~ "application provided the person on the console knows the root password." -#~ msgstr "" -#~ "<filename>XKeepsCrashing</filename> is a script which gets run when the X " -#~ "server keeps crashing and we cannot recover. The shipped default script " -#~ "will work with most Linux distributions and can run the X configuration " -#~ "application provided the person on the console knows the root password." - -#~ msgid "" -#~ "Accessibility modules are configured in the <filename>modules/</filename> " -#~ "subdirectory, and are a separate topic. Read the default files provided, " -#~ "they have adequate documentation. Again normally the default install is " -#~ "given in the files with <filename>factory</filename> in their name, and " -#~ "those files are not read, they are just there for you so you can always " -#~ "revert to default config." -#~ msgstr "" -#~ "Accessibility modules are configured in the <filename>modules/</filename> " -#~ "subdirectory, and are a separate topic. Read the default files provided, " -#~ "they have adequate documentation. Again normally the default install is " -#~ "given in the files with <filename>factory</filename> in their name, and " -#~ "those files are not read, they are just there for you so you can always " -#~ "revert to default config." - -#~ msgid "" -#~ "Files describing available GDM session follow the freedesktop.org desktop " -#~ "file specification and are <filename>.desktop</filename>-style files are " -#~ "installed to <filename><etc>/X11/sessions/</filename>. This " -#~ "directory is also read by the KDE desktop manager (KDM) for common " -#~ "configuration. Next the directory <filename><share>/gdm/" -#~ "BuiltInSessions/</filename> is read for GDM specific built-in sessions " -#~ "(KDM hardcodes these at time of this writing). Lastly the default setup " -#~ "will also read <filename><share>/xsessions/</filename> (which " -#~ "should be <filename><share>/xsessions/</filename> if you really " -#~ "wish to cooperate with KDM) where desktop packages can install their " -#~ "session files. The directories under the <filename><etc></filename> " -#~ "should be reserved for configuration. The desktop file specification " -#~ "approach makes it easy for package management systems to install window " -#~ "managers and different session types without requiring the sysadmin to " -#~ "edit files. See the <filename>SessionDesktopDir</filename> configuration " -#~ "key for changing the paths. It used to be that GDM stored its built in " -#~ "sessions in <filename><etc>/dm/Sessions/</filename> but this is " -#~ "deprecated as of 2.5.90.0. Note that prior to version 2.4.4.2 only the " -#~ "<filename><etc>/dm/Sessions/</filename> was being read." -#~ msgstr "" -#~ "Files describing available GDM session follow the freedesktop.org desktop " -#~ "file specification and are <filename>.desktop</filename>-style files are " -#~ "installed to <filename><etc>/X11/sessions/</filename>. This " -#~ "directory is also read by the KDE desktop manager (KDM) for common " -#~ "configuration. Next the directory <filename><share>/gdm/" -#~ "BuiltInSessions/</filename> is read for GDM specific built-in sessions " -#~ "(KDM hardcodes these at time of this writing). Lastly the default setup " -#~ "will also read <filename><share>/xsessions/</filename> (which " -#~ "should be <filename><share>/xsessions/</filename> if you really " -#~ "wish to cooperate with KDM) where desktop packages can install their " -#~ "session files. The directories under the <filename><etc></filename> " -#~ "should be reserved for configuration. The desktop file specification " -#~ "approach makes it easy for package management systems to install window " -#~ "managers and different session types without requiring the sysadmin to " -#~ "edit files. See the <filename>SessionDesktopDir</filename> configuration " -#~ "key for changing the paths. It used to be that GDM stored its built in " -#~ "sessions in <filename><etc>/dm/Sessions/</filename> but this is " -#~ "deprecated as of 2.5.90.0. Note that prior to version 2.4.4.2 only the " -#~ "<filename><etc>/dm/Sessions/</filename> was being read." - -#~ msgid "" -#~ "A session can be disabled (if it was installed in <filename><share>/" -#~ "xsessions/</filename>) by adding an identically named <filename>.desktop</" -#~ "filename> to one of the directories earlier in the path (likely " -#~ "<filename><etc>/X11/sessions</filename>) and using " -#~ "<filename>Hidden=true</filename> in that file." -#~ msgstr "" -#~ "A session can be disabled (if it was installed in <filename><share>/" -#~ "xsessions/</filename>) by adding an identically named <filename>.desktop</" -#~ "filename> to one of the directories earlier in the path (likely " -#~ "<filename><etc>/X11/sessions</filename>) and using " -#~ "<filename>Hidden=true</filename> in that file." - -#~ msgid "The Script Directories" -#~ msgstr "The Script Directories" - -#~ msgid "" -#~ "When the X server has been successfully started, GDM will try to run the " -#~ "script called <filename>Init/<displayname></filename>. I.e. " -#~ "<filename>Init/:0</filename> for the first local display. If this file is " -#~ "not found, GDM will attempt to to run <filename>Init/<hostname></" -#~ "filename>. I.e. <filename>Init/somehost</filename>. If this still is not " -#~ "found, GDM will try <filename>Init/XDMCP</filename> for all XDMCP logins " -#~ "or <filename>Init/Flexi</filename> for all on demand flexible displays. " -#~ "If none of the above were found, GDM will run <filename>Init/Default</" -#~ "filename>. The script will be run as root and GDM blocks until it " -#~ "terminates. Use the <filename>Init/*</filename> script for applications " -#~ "that are supposed to run alongside with the GDM login window. xconsole " -#~ "for instance. Commands to set the background etc. go in this file too." -#~ msgstr "" -#~ "When the X server has been successfully started, GDM will try to run the " -#~ "script called <filename>Init/<displayname></filename>. I.e. " -#~ "<filename>Init/:0</filename> for the first local display. If this file is " -#~ "not found, GDM will attempt to to run <filename>Init/<hostname></" -#~ "filename>. I.e. <filename>Init/somehost</filename>. If this still is not " -#~ "found, GDM will try <filename>Init/XDMCP</filename> for all XDMCP logins " -#~ "or <filename>Init/Flexi</filename> for all on demand flexible displays. " -#~ "If none of the above were found, GDM will run <filename>Init/Default</" -#~ "filename>. The script will be run as root and GDM blocks until it " -#~ "terminates. Use the <filename>Init/*</filename> script for applications " -#~ "that are supposed to run alongside with the GDM login window. xconsole " -#~ "for instance. Commands to set the background etc. go in this file too." - -#~ msgid "" -#~ "It is up to the sysadmin to decide whether clients started by the Init " -#~ "script should be killed before starting the user session. This is " -#~ "controlled with the <filename>KillInitClients</filename> configuration " -#~ "option." -#~ msgstr "" -#~ "It is up to the sysadmin to decide whether clients started by the Init " -#~ "script should be killed before starting the user session. This is " -#~ "controlled with the <filename>KillInitClients</filename> configuration " -#~ "option." - -#~ msgid "" -#~ "When the user has been successfully authenticated GDM tries the scripts " -#~ "in the <filename>PostLogin</filename> directory in the same manner as for " -#~ "the <filename>Init</filename> directory. This is done before any session " -#~ "setup is done, and so this would be the script where you might setup the " -#~ "home directory if you need to (though you should use the " -#~ "<filename>pam_mount</filename> module if you can for this). You have the " -#~ "<filename>$USER</filename> and <filename>$DISPLAY</filename> environment " -#~ "variables set for this script, and again it is run as root. The script " -#~ "should return 0 on success as otherwise the user won't be logged in. This " -#~ "is not true for failsafe session however." -#~ msgstr "" -#~ "When the user has been successfully authenticated GDM tries the scripts " -#~ "in the <filename>PostLogin</filename> directory in the same manner as for " -#~ "the <filename>Init</filename> directory. This is done before any session " -#~ "setup is done, and so this would be the script where you might setup the " -#~ "home directory if you need to (though you should use the " -#~ "<filename>pam_mount</filename> module if you can for this). You have the " -#~ "<filename>$USER</filename> and <filename>$DISPLAY</filename> environment " -#~ "variables set for this script, and again it is run as root. The script " -#~ "should return 0 on success as otherwise the user won't be logged in. This " -#~ "is not true for failsafe session however." - -#~ msgid "" -#~ "After the user session has been setup from the GDM side of things, GDM " -#~ "will run the scripts in the <filename>PreSession</filename> directory, " -#~ "again in the same manner as the <filename>Init</filename> directory. Use " -#~ "this script for local session management or accounting stuff. The " -#~ "<filename>$USER</filename> environment variable contains the login of the " -#~ "authenticated user and <filename>$DISPLAY</filename> is set to the " -#~ "current display. The script should return 0 on success. Any other value " -#~ "will cause GDM to terminate the current login process. This is not true " -#~ "for failsafe sessions however. Also <filename>$X_SERVERS</filename> " -#~ "environmental variable is set and this points to a fake generated X " -#~ "servers file for use with the sessreg accounting application." -#~ msgstr "" -#~ "After the user session has been setup from the GDM side of things, GDM " -#~ "will run the scripts in the <filename>PreSession</filename> directory, " -#~ "again in the same manner as the <filename>Init</filename> directory. Use " -#~ "this script for local session management or accounting stuff. The " -#~ "<filename>$USER</filename> environment variable contains the login of the " -#~ "authenticated user and <filename>$DISPLAY</filename> is set to the " -#~ "current display. The script should return 0 on success. Any other value " -#~ "will cause GDM to terminate the current login process. This is not true " -#~ "for failsafe sessions however. Also <filename>$X_SERVERS</filename> " -#~ "environmental variable is set and this points to a fake generated X " -#~ "servers file for use with the sessreg accounting application." - -#~ msgid "" -#~ "After this the base <filename>Xsession</filename> script is run with the " -#~ "selected session executable as the first argument. This is run as the " -#~ "user, and really this is the user session. The available session " -#~ "executables are taken from the <filename>Exec=</filename> line in the " -#~ "<filename>.desktop</filename> files in the path specified by " -#~ "<filename>SessionDesktopDir</filename>. Usually this path is " -#~ "<filename><etc>/X11/sessions/:<etc>/dm/Sessions:/usr/share/" -#~ "xsessions/</filename>. The first found file is used. The user either " -#~ "picks from these sessions or GDM will look inside the file <filename>~/." -#~ "dmrc</filename> for the stored preference." -#~ msgstr "" -#~ "After this the base <filename>Xsession</filename> script is run with the " -#~ "selected session executable as the first argument. This is run as the " -#~ "user, and really this is the user session. The available session " -#~ "executables are taken from the <filename>Exec=</filename> line in the " -#~ "<filename>.desktop</filename> files in the path specified by " -#~ "<filename>SessionDesktopDir</filename>. Usually this path is " -#~ "<filename><etc>/X11/sessions/:<etc>/dm/Sessions:/usr/share/" -#~ "xsessions/</filename>. The first found file is used. The user either " -#~ "picks from these sessions or GDM will look inside the file <filename>~/." -#~ "dmrc</filename> for the stored preference." - -#~ msgid "" -#~ "This script should really load the user's profile and generally do all " -#~ "the voodoo that is needed to launch a session. Since many systems reset " -#~ "the language selections done by GDM, GDM will also set the <filename>" -#~ "$GDM_LANG</filename> variable to the selected language. You can use this " -#~ "to reset the language environmental variables after you run the user's " -#~ "profile. If the user elected to use the system language, then <filename>" -#~ "$GDM_LANG</filename> is not set." -#~ msgstr "" -#~ "This script should really load the user's profile and generally do all " -#~ "the voodoo that is needed to launch a session. Since many systems reset " -#~ "the language selections done by GDM, GDM will also set the <filename>" -#~ "$GDM_LANG</filename> variable to the selected language. You can use this " -#~ "to reset the language environmental variables after you run the user's " -#~ "profile. If the user elected to use the system language, then <filename>" -#~ "$GDM_LANG</filename> is not set." - -#~ msgid "" -#~ "When the user terminates his session, the <filename>PostSession</" -#~ "filename> script will be run. Again operation is similar to " -#~ "<filename>Init</filename>, <filename>PostLogin</filename> and " -#~ "<filename>PreSession</filename>. Again the script will be run with root " -#~ "privileges, the slave daemon will block and the <filename>$USER</" -#~ "filename> environment variable will contain the name of the user who just " -#~ "logged out and <filename>$DISPLAY</filename> will be set to the display " -#~ "the user used, however note that the X server for this display may " -#~ "already be dead and so you shouldn't try to access it. Also <filename>" -#~ "$X_SERVERS</filename> environmental variable is set and this points to a " -#~ "fake generated X servers file for use with the sessreg accounting " -#~ "application." -#~ msgstr "" -#~ "When the user terminates his session, the <filename>PostSession</" -#~ "filename> script will be run. Again operation is similar to " -#~ "<filename>Init</filename>, <filename>PostLogin</filename> and " -#~ "<filename>PreSession</filename>. Again the script will be run with root " -#~ "privileges, the slave daemon will block and the <filename>$USER</" -#~ "filename> environment variable will contain the name of the user who just " -#~ "logged out and <filename>$DISPLAY</filename> will be set to the display " -#~ "the user used, however note that the X server for this display may " -#~ "already be dead and so you shouldn't try to access it. Also <filename>" -#~ "$X_SERVERS</filename> environmental variable is set and this points to a " -#~ "fake generated X servers file for use with the sessreg accounting " -#~ "application." - -#~ msgid "" -#~ "Except for the <filename>Xsession</filename> script all of these scripts " -#~ "will also have the environment variable <filename>$RUNNING_UNDER_GDM</" -#~ "filename> set to <filename>yes</filename>, so that you could perhaps use " -#~ "similar scripts for different display managers. The <filename>Xsession</" -#~ "filename> will always have the <filename>$GDMSESSION</filename> set to " -#~ "the basename of the session that the user chose to run without the " -#~ "<filename>.desktop</filename> extension. In addition <filename>" -#~ "$DESKTOP_SESSION</filename> is also set to the same value and in fact " -#~ "this will also be set by KDM in future versions." -#~ msgstr "" -#~ "Except for the <filename>Xsession</filename> script all of these scripts " -#~ "will also have the environment variable <filename>$RUNNING_UNDER_GDM</" -#~ "filename> set to <filename>yes</filename>, so that you could perhaps use " -#~ "similar scripts for different display managers. The <filename>Xsession</" -#~ "filename> will always have the <filename>$GDMSESSION</filename> set to " -#~ "the basename of the session that the user chose to run without the " -#~ "<filename>.desktop</filename> extension. In addition <filename>" -#~ "$DESKTOP_SESSION</filename> is also set to the same value and in fact " -#~ "this will also be set by KDM in future versions." - -#~ msgid "" -#~ "Neither of the <filename>Init</filename>, <filename>PostLogin</filename>, " -#~ "<filename>PreSession</filename> or <filename>PostSession</filename> " -#~ "scripts are necessary and can be left out. The <filename>Xsession</" -#~ "filename> script is however required as well as at least one session " -#~ "<filename>.desktop</filename> file." -#~ msgstr "" -#~ "Neither of the <filename>Init</filename>, <filename>PostLogin</filename>, " -#~ "<filename>PreSession</filename> or <filename>PostSession</filename> " -#~ "scripts are necessary and can be left out. The <filename>Xsession</" -#~ "filename> script is however required as well as at least one session " -#~ "<filename>.desktop</filename> file." - -#~ msgid "" -#~ "The Configuration Files - <filename>defaults.conf</filename> and " -#~ "<filename>custom.conf</filename>" -#~ msgstr "" -#~ "The Configuration Files - <filename>defaults.conf</filename> and " -#~ "<filename>custom.conf</filename>" - -#~ msgid "" -#~ "GDM uses two configuration files: <filename><share>/gdm/defaults." -#~ "conf</filename> and <filename><etc>/gdm/custom.conf</filename>. The " -#~ "<filename><share>/gdm/defaults.conf</filename> file contains the " -#~ "default configuration choices for GDM, and should not be modified by the " -#~ "user. The <filename><etc>/gdm/custom.conf</filename> file is where " -#~ "users may specify their custom configuration choices. Configuration " -#~ "options specified in the <filename><etc>/gdm/custom.conf</filename> " -#~ "file override the values in the <filename><share>/gdm/defaults." -#~ "conf</filename> file. If a configuration option is not defined in either " -#~ "file, GDM will default to the value described in the comments in the " -#~ "<filename><share>/gdm/defaults.conf</filename> file." -#~ msgstr "" -#~ "GDM uses two configuration files: <filename><share>/gdm/defaults." -#~ "conf</filename> and <filename><etc>/gdm/custom.conf</filename>. The " -#~ "<filename><share>/gdm/defaults.conf</filename> file contains the " -#~ "default configuration choices for GDM, and should not be modified by the " -#~ "user. The <filename><etc>/gdm/custom.conf</filename> file is where " -#~ "users may specify their custom configuration choices. Configuration " -#~ "options specified in the <filename><etc>/gdm/custom.conf</filename> " -#~ "file override the values in the <filename><share>/gdm/defaults." -#~ "conf</filename> file. If a configuration option is not defined in either " -#~ "file, GDM will default to the value described in the comments in the " -#~ "<filename><share>/gdm/defaults.conf</filename> file." - -#~ msgid "" -#~ "Running the <command>gdmsetup</command> command will cause the " -#~ "<filename><etc>/gdm/custom.conf</filename> to be modified with the " -#~ "user's configuration choices." -#~ msgstr "" -#~ "Running the <command>gdmsetup</command> command will cause the " -#~ "<filename><etc>/gdm/custom.conf</filename> to be modified with the " -#~ "user's configuration choices." - -#~ msgid "" -#~ "Previous to GDM 2.13.0.4 only the <filename><etc>/gdm/gdm.conf</" -#~ "filename> existed. If upgrading to the new version of GDM, install will " -#~ "check to see if your <filename><etc>/gdm/gdm.conf</filename> file " -#~ "is different than your <filename><etc>/gdm/factory-gdm.conf</" -#~ "filename> file. If so, your <filename><etc>/gdm/gdm.conf</filename> " -#~ "file will be automatically copied to <filename><etc>/gdm/custom." -#~ "conf</filename> to preserve any configuration changes." -#~ msgstr "" -#~ "Previous to GDM 2.13.0.4 only the <filename><etc>/gdm/gdm.conf</" -#~ "filename> existed. If upgrading to the new version of GDM, install will " -#~ "check to see if your <filename><etc>/gdm/gdm.conf</filename> file " -#~ "is different than your <filename><etc>/gdm/factory-gdm.conf</" -#~ "filename> file. If so, your <filename><etc>/gdm/gdm.conf</filename> " -#~ "file will be automatically copied to <filename><etc>/gdm/custom." -#~ "conf</filename> to preserve any configuration changes." - -#~ msgid "" -#~ "The location of the configuration files may be controlled via the " -#~ "<command>--with-defaults-conf</command> and <command>--with-custom-conf</" -#~ "command> configuration options. The GDM daemon --config option may " -#~ "instead be used to specify the configuration file location. The GDM " -#~ "daemon must be restarted to change the configuration file being used." -#~ msgstr "" -#~ "The location of the configuration files may be controlled via the " -#~ "<command>--with-defaults-conf</command> and <command>--with-custom-conf</" -#~ "command> configuration options. The GDM daemon --config option may " -#~ "instead be used to specify the configuration file location. The GDM " -#~ "daemon must be restarted to change the configuration file being used." - -#~ msgid "" -#~ "Both configuration files are divided into sections each containing " -#~ "variables that define the behavior for a specific part of the GDM suite. " -#~ "Refer to the comments in the <filename><share>/gdm/defaults.conf</" -#~ "filename> file for additional information about each configuration " -#~ "setting." -#~ msgstr "" -#~ "Both configuration files are divided into sections each containing " -#~ "variables that define the behavior for a specific part of the GDM suite. " -#~ "Refer to the comments in the <filename><share>/gdm/defaults.conf</" -#~ "filename> file for additional information about each configuration " -#~ "setting." - -#~ msgid "AddGtkModules" -#~ msgstr "AddGtkModules" - -#~ msgid "AddGtkModules=false" -#~ msgstr "AddGtkModules=false" - -#~ msgid "" -#~ "If true, then enables <command>gdmgreeter</command> or <command>gdmlogin</" -#~ "command> to be launched with additional Gtk+ modules. This is useful when " -#~ "extra features are required such as accessible login. Note that only " -#~ "\"trusted\" modules should be used to minimize security issues." -#~ msgstr "" -#~ "If true, then enables <command>gdmgreeter</command> or <command>gdmlogin</" -#~ "command> to be launched with additional Gtk+ modules. This is useful when " -#~ "extra features are required such as accessible login. Note that only " -#~ "\"trusted\" modules should be used to minimise security issues." - -#~ msgid "" -#~ "If true, then the registry daemon <command>at-spi-registryd</command> " -#~ "will be launched by <command>gdmgreeter</command> or <command>gdmlogin</" -#~ "command> starting with version GDM 2.17." -#~ msgstr "" -#~ "If true, then the registry daemon <command>at-spi-registryd</command> " -#~ "will be launched by <command>gdmgreeter</command> or <command>gdmlogin</" -#~ "command> starting with version GDM 2.17." - -#~ msgid "" -#~ "Usually this is used for accessibility modules. The modules which are " -#~ "loaded are specified with the <filename>GtkModulesList</filename> key." -#~ msgstr "" -#~ "Usually this is used for accessibility modules. The modules which are " -#~ "loaded are specified with the <filename>GtkModulesList</filename> key." - -#~ msgid "AlwaysRestartServer" -#~ msgstr "AlwaysRestartServer" - -#~ msgid "AlwaysRestartServer=false" -#~ msgstr "AlwaysRestartServer=false" - -#~ msgid "" -#~ "If true, then gdm never tries to reuse existing X servers by " -#~ "reinitializing them. It will just kill the existing X server and start " -#~ "over. Normally, just reinitializing is a nicer way to go but if the X " -#~ "server memory usage keeps growing this may be a safer option. On Solaris, " -#~ "this value is always true, and this configuration setting is ignored." -#~ msgstr "" -#~ "If true, then gdm never tries to reuse existing X servers by " -#~ "reinitialising them. It will just kill the existing X server and start " -#~ "over. Normally, just reinitialising is a nicer way to go but if the X " -#~ "server memory usage keeps growing this may be a safer option. On Solaris, " -#~ "this value is always true, and this configuration setting is ignored." - -#~ msgid "AlwaysLoginCurrentSession" -#~ msgstr "AlwaysLoginCurrentSession" - -#~ msgid "AlwaysLoginCurrentSession=true" -#~ msgstr "AlwaysLoginCurrentSession=true" - -#~ msgid "" -#~ "If true, then when the user logs in and already has an existing session, " -#~ "then they are connected to that session rather than starting a new " -#~ "session. This only works for sessions running on VTs (Virtual Terminals) " -#~ "started with gdmflexiserver, and not with XDMCP. Note that VTs are not " -#~ "supported on all operating systems." -#~ msgstr "" -#~ "If true, then when the user logs in and already has an existing session, " -#~ "then they are connected to that session rather than starting a new " -#~ "session. This only works for sessions running on VTs (Virtual Terminals) " -#~ "started with gdmflexiserver, and not with XDMCP. Note that VTs are not " -#~ "supported on all operating systems." - -#~ msgid "" -#~ "If the user given in AutomaticLogin should be logged in upon first " -#~ "bootup. No password will be asked. This is useful for single user " -#~ "workstations where local console security is not an issue. Also could be " -#~ "useful for public terminals, although there see <filename>TimedLogin</" -#~ "filename>." -#~ msgstr "" -#~ "If the user given in AutomaticLogin should be logged in upon first " -#~ "bootup. No password will be asked. This is useful for single user " -#~ "workstations where local console security is not an issue. Also could be " -#~ "useful for public terminals, although there see <filename>TimedLogin</" -#~ "filename>." - -#~ msgid "" -#~ "This user should be automatically logged in on first bootup. " -#~ "AutomaticLoginEnable must be true and this must be a valid user for this " -#~ "to happen. \"root\" can never be autologged in however and gdm will just " -#~ "refuse to do it even if you set it up." -#~ msgstr "" -#~ "This user should be automatically logged in on first bootup. " -#~ "AutomaticLoginEnable must be true and this must be a valid user for this " -#~ "to happen. \"root\" can never be autologged in however and gdm will just " -#~ "refuse to do it even if you set it up." - -#~ msgid "" -#~ "The following control chars are recognized within the specified name:" -#~ msgstr "" -#~ "The following control chars are recognised within the specified name:" - -#~ msgid "%%— the `%' character" -#~ msgstr "%%— the `%' character" - -#~ msgid "%d — display's name" -#~ msgstr "%d — display's name" - -#~ msgid "%h — display's hostname" -#~ msgstr "%h — display's hostname" - -#~ msgid "" -#~ "Alternatively, the name may end with a vertical bar |, the pipe symbol. " -#~ "The name is then used as a application to execute which returns the " -#~ "desired username on standard output. If an empty or otherwise invalid " -#~ "username is returned, automatic login is not performed. This feature is " -#~ "typically used when several remote displays are used as internet kiosks, " -#~ "with a specific user to automatically login for each display." -#~ msgstr "" -#~ "Alternatively, the name may end with a vertical bar |, the pipe symbol. " -#~ "The name is then used as a application to execute which returns the " -#~ "desired username on standard output. If an empty or otherwise invalid " -#~ "username is returned, automatic login is not performed. This feature is " -#~ "typically used when several remote displays are used as internet kiosks, " -#~ "with a specific user to automatically login for each display." - -#~ msgid "BaseXsession" -#~ msgstr "BaseXsession" - -#~ msgid "BaseXsession=<etc>/gdm/Xsession" -#~ msgstr "BaseXsession=<etc>/gdm/Xsession" - -#~ msgid "" -#~ "This is the base X session file. When a user logs in, this script will be " -#~ "run with the selected session as the first argument. The selected session " -#~ "will be the <filename>Exec=</filename> from the <filename>.desktop</" -#~ "filename> file of the session." -#~ msgstr "" -#~ "This is the base X session file. When a user logs in, this script will be " -#~ "run with the selected session as the first argument. The selected session " -#~ "will be the <filename>Exec=</filename> from the <filename>.desktop</" -#~ "filename> file of the session." - -#~ msgid "" -#~ "If you wish to use the same script for several different display " -#~ "managers, and wish to have some of the script run only for GDM, then you " -#~ "can check the presence of the <filename>GDMSESSION</filename> " -#~ "environmental variable. This will always be set to the basename of " -#~ "<filename>.desktop</filename> (without the extension) file that is being " -#~ "used for this session, and will only be set for GDM sessions. Previously " -#~ "some scripts were checking for <filename>GDM_LANG</filename>, but that is " -#~ "only set when the user picks a non-system default language." -#~ msgstr "" -#~ "If you wish to use the same script for several different display " -#~ "managers, and wish to have some of the script run only for GDM, then you " -#~ "can check the presence of the <filename>GDMSESSION</filename> " -#~ "environmental variable. This will always be set to the basename of " -#~ "<filename>.desktop</filename> (without the extension) file that is being " -#~ "used for this session, and will only be set for GDM sessions. Previously " -#~ "some scripts were checking for <filename>GDM_LANG</filename>, but that is " -#~ "only set when the user picks a non-system default language." - -#~ msgid "" -#~ "This script should take care of doing the \"login\" for the user and so " -#~ "it should source the <filename><etc>/profile</filename> and " -#~ "friends. The standard script shipped with GDM sources the files in this " -#~ "order: <filename><etc>/profile</filename> then <filename>~/." -#~ "profile</filename> then <filename><etc>/xprofile</filename> and " -#~ "finally <filename>~/.xprofile</filename>. Note that different " -#~ "distributions may change this however. Sometimes users personal setup " -#~ "will be in <filename>~/.bash_profile</filename>, however broken that is." -#~ msgstr "" -#~ "This script should take care of doing the \"login\" for the user and so " -#~ "it should source the <filename><etc>/profile</filename> and " -#~ "friends. The standard script shipped with GDM sources the files in this " -#~ "order: <filename><etc>/profile</filename> then <filename>~/." -#~ "profile</filename> then <filename><etc>/xprofile</filename> and " -#~ "finally <filename>~/.xprofile</filename>. Note that different " -#~ "distributions may change this however. Sometimes users personal setup " -#~ "will be in <filename>~/.bash_profile</filename>, however broken that is." - -#~ msgid "Chooser" -#~ msgstr "Chooser" - -#~ msgid "Chooser=<bin>/gdmchooser" -#~ msgstr "Chooser=<bin>/gdmchooser" - -#~ msgid "" -#~ "Full path and name of the chooser executable followed by optional " -#~ "arguments." -#~ msgstr "" -#~ "Full path and name of the chooser executable followed by optional " -#~ "arguments." - -#~ msgid "Configurator" -#~ msgstr "Configurator" - -#~ msgid "" -#~ "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" -#~ msgstr "" -#~ "Configurator=<bin>/gdmsetup --disable-sound --disable-crash-dialog" - -#~ msgid "" -#~ "The pathname to the configurator binary. If the greeter " -#~ "<filename>ConfigAvailable</filename> option is set to true then run this " -#~ "binary when somebody chooses Configuration from the Actions menu. Of " -#~ "course GDM will first ask for root password however. And it will never " -#~ "allow this to happen from a remote display." -#~ msgstr "" -#~ "The pathname to the configurator binary. If the greeter " -#~ "<filename>ConfigAvailable</filename> option is set to true then run this " -#~ "binary when somebody chooses Configuration from the Actions menu. GDM " -#~ "will first ask for root password however. And it will never allow this to " -#~ "happen from a remote display." - -#~ msgid "ConsoleCannotHandle" -#~ msgstr "ConsoleCannotHandle" - -#~ msgid "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" -#~ msgstr "ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh" - -#~ msgid "" -#~ "These are the languages that the console cannot handle because of font " -#~ "issues. Here we mean the text console, not X. This is only used when " -#~ "there are errors to report and we cannot start X." -#~ msgstr "" -#~ "These are the languages that the console cannot handle because of font " -#~ "issues. Here we mean the text console, not X. This is only used when " -#~ "there are errors to report and we cannot start X." - -#~ msgid "ConsoleNotify" -#~ msgstr "ConsoleNotify" - -#~ msgid "ConsoleNotify=true" -#~ msgstr "ConsoleNotify=true" - -#~ msgid "" -#~ "If false, gdm will not display a message dialog on the console when an " -#~ "error happens." -#~ msgstr "" -#~ "If false, gdm will not display a message dialogue on the console when an " -#~ "error happens." - -#~ msgid "DefaultPath" -#~ msgstr "DefaultPath" - -#~ msgid "DefaultPath=defaultpath (value set by configure)" -#~ msgstr "DefaultPath=defaultpath (value set by configure)" - -#~ msgid "" -#~ "Specifies the path which will be set in the user's session. This value " -#~ "will be overridden with the value from <filename>/etc/default/login</" -#~ "filename> if it contains \"ROOT=<pathname>\". If the <filename>/etc/" -#~ "default/login</filename> file exists, but contains no value for ROOT, the " -#~ "value as defined in the GDM configuration will be be used." -#~ msgstr "" -#~ "Specifies the path which will be set in the user's session. This value " -#~ "will be overridden with the value from <filename>/etc/default/login</" -#~ "filename> if it contains \"ROOT=<pathname>\". If the <filename>/etc/" -#~ "default/login</filename> file exists, but contains no value for ROOT, the " -#~ "value as defined in the GDM configuration will be be used." - -#~ msgid "DefaultSession" -#~ msgstr "DefaultSession" - -#~ msgid "DefaultSession=gnome.desktop" -#~ msgstr "DefaultSession=gnome.desktop" - -#~ msgid "" -#~ "The session that is used by default if the user does not have a saved " -#~ "preference and has picked 'Last' from the list of sessions. Note that " -#~ "'Last' need not be displayed, see the <filename>ShowLastSession</" -#~ "filename> key." -#~ msgstr "" -#~ "The session that is used by default if the user does not have a saved " -#~ "preference and has picked 'Last' from the list of sessions. Note that " -#~ "'Last' need not be displayed, see the <filename>ShowLastSession</" -#~ "filename> key." - -#~ msgid "DisplayInitDir" -#~ msgstr "DisplayInitDir" - -#~ msgid "DisplayInitDir=<etc>/gdm/Init" -#~ msgstr "DisplayInitDir=<etc>/gdm/Init" - -#~ msgid "" -#~ "Directory containing the display init scripts. See the ``The Script " -#~ "Directories'' section for more info." -#~ msgstr "" -#~ "Directory containing the display init scripts. See the ``The Script " -#~ "Directories'' section for more info." - -#~ msgid "DisplayLastLogin" -#~ msgstr "DisplayLastLogin" - -#~ msgid "DisplayLastLogin=true" -#~ msgstr "DisplayLastLogin=true" - -#~ msgid "" -#~ "If true then the last login information is printed to the user before " -#~ "being prompted for password. While this gives away some info on what " -#~ "users are on a system, it on the other hand should give the user an idea " -#~ "of when they logged in and if it doesn't seem kosher to them, they can " -#~ "just abort the login and contact the sysadmin (avoids running malicious " -#~ "startup scripts). This was added in version 2.5.90.0." -#~ msgstr "" -#~ "If true then the last login information is printed to the user before " -#~ "being prompted for password. While this gives away some info on what " -#~ "users are on a system, it on the other hand should give the user an idea " -#~ "of when they logged in and if it doesn't seem kosher to them, they can " -#~ "just abort the login and contact the sysadmin (avoids running malicious " -#~ "startup scripts). This was added in version 2.5.90.0." - -#~ msgid "" -#~ "This is for making GDM conformant to CSC-STD-002-85, although that is " -#~ "purely theoretical now. Someone should read that spec and ensure that " -#~ "this actually conforms (in addition to other places in GDM). See " -#~ "<filename>http://www.radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85." -#~ "html</filename> for more info." -#~ msgstr "" -#~ "This is for making GDM conformant to CSC-STD-002-85, although that is " -#~ "purely theoretical now. Someone should read that spec and ensure that " -#~ "this actually conforms (in addition to other places in GDM). See " -#~ "<filename>http://www.radium.ncsc.mil/tpep/library/rainbow/CSC-STD-002-85." -#~ "html</filename> for more info." - -#~ msgid "DoubleLoginWarning" -#~ msgstr "DoubleLoginWarning" - -#~ msgid "DoubleLoginWarning=true" -#~ msgstr "DoubleLoginWarning=true" - -#~ msgid "" -#~ "If true, GDM will warn the user if they are already logged in on another " -#~ "virtual terminal. On systems where GDM supports checking the X virtual " -#~ "terminals, GDM will let the user switch to the previous login virtual " -#~ "terminal instead of logging in." -#~ msgstr "" -#~ "If true, GDM will warn the user if they are already logged in on another " -#~ "virtual terminal. On systems where GDM supports checking the X virtual " -#~ "terminals, GDM will let the user switch to the previous login virtual " -#~ "terminal instead of logging in." - -#~ msgid "DynamicXServers" -#~ msgstr "DynamicXServers" - -#~ msgid "DynamicXServers=false" -#~ msgstr "DynamicXServers=false" - -#~ msgid "" -#~ "If true, the GDM daemon will honor requests to manage displays via the " -#~ "<filename>/tmp/.gdm_socket</filename> socket connection. Displays can be " -#~ "created, started, and deleted with the appropriate commands. The " -#~ "<filename>gdmdynamic</filename> command is a convenient method to send " -#~ "these messages." -#~ msgstr "" -#~ "If true, the GDM daemon will honour requests to manage displays via the " -#~ "<filename>/tmp/.gdm_socket</filename> socket connection. Displays can be " -#~ "created, started, and deleted with the appropriate commands. The " -#~ "<filename>gdmdynamic</filename> command is a convenient method to send " -#~ "these messages." - -#~ msgid "FailsafeXServer" -#~ msgstr "FailsafeXServer" - -#~ msgid "FailsafeXServer=" -#~ msgstr "FailsafeXServer=" - -#~ msgid "" -#~ "An X command line in case we can't start the normal X server. should " -#~ "probably be some sort of a script that runs an appropriate low resolution " -#~ "X server that will just work. This is tried before the " -#~ "<filename>XKeepsCrashing</filename> script is run." -#~ msgstr "" -#~ "An X command line in case we can't start the normal X server. should " -#~ "probably be some sort of a script that runs an appropriate low resolution " -#~ "X server that will just work. This is tried before the " -#~ "<filename>XKeepsCrashing</filename> script is run." - -#~ msgid "FirstVT" -#~ msgstr "FirstVT" - -#~ msgid "FirstVT=7" -#~ msgstr "FirstVT=7" - -#~ msgid "" -#~ "On systems where GDM supports automatic VT (virtual terminal) allocation, " -#~ "this is the first vt to try. Usually standard text logins are run on the " -#~ "lower vts. See also <filename>VTAllocation</filename>." -#~ msgstr "" -#~ "On systems where GDM supports automatic VT (virtual terminal) allocation, " -#~ "this is the first vt to try. Usually standard text logins are run on the " -#~ "lower vts. See also <filename>VTAllocation</filename>." - -#~ msgid "FlexibleXServers" -#~ msgstr "FlexibleXServers" - -#~ msgid "FlexibleXServers=5" -#~ msgstr "FlexibleXServers=5" - -#~ msgid "" -#~ "The maximum number of allowed flexible displays. These are displays that " -#~ "can be run using the <filename>/tmp/.gdm_socket</filename> socket " -#~ "connection. This is used for both full flexible displays and for Xnest " -#~ "displays." -#~ msgstr "" -#~ "The maximum number of allowed flexible displays. These are displays that " -#~ "can be run using the <filename>/tmp/.gdm_socket</filename> socket " -#~ "connection. This is used for both fully flexible displays and for Xnest " -#~ "displays." - -#~ msgid "FlexiReapDelayMinutes" -#~ msgstr "FlexiReapDelayMinutes" - -#~ msgid "FlexiReapDelayMinutes=5" -#~ msgstr "FlexiReapDelayMinutes=5" - -#~ msgid "" -#~ "After how many minutes of inactivity at the login screen should a flexi " -#~ "display be reaped. This is only in effect before a user logs in. Also it " -#~ "does not affect the Xnest flexiservers. To turn off this behavior set " -#~ "this value to 0. This was added in version 2.5.90.0." -#~ msgstr "" -#~ "After how many minutes of inactivity at the login screen should a flexi " -#~ "display be reaped. This is only in effect before a user logs in. Also it " -#~ "does not affect the Xnest flexiservers. To turn off this behavior set " -#~ "this value to 0. This was added in version 2.5.90.0." - -#~ msgid "Greeter=<bin>/gdmlogin" -#~ msgstr "Greeter=<bin>/gdmlogin" - -#~ msgid "" -#~ "Full path and name of the greeter executable followed by optional " -#~ "arguments. This is the greeter used for all displays except for the XDMCP " -#~ "remote displays. See also <filename>RemoteGreeter</filename>" -#~ msgstr "" -#~ "Full path and name of the greeter executable followed by optional " -#~ "arguments. This is the greeter used for all displays except for the XDMCP " -#~ "remote displays. See also <filename>RemoteGreeter</filename>" - -#~ msgid "" -#~ "The group name under which <command>gdmlogin</command>, " -#~ "<command>gdmgreeter</command>, <command>gdmchooser</command> and the " -#~ "internal failsafe GTK+ dialogs are run. Also see <filename>User</" -#~ "filename>. This user will have access to all the X authorization files, " -#~ "and perhaps to other internal GDM data and it should not therefore be a " -#~ "user such as nobody, but rather a dedicated user. The " -#~ "<filename>ServAuthDir</filename> is owned by this group. The ownership " -#~ "and permissions of <filename>ServAuthDir</filename> should be " -#~ "<filename>root.gdm</filename> and 1770." -#~ msgstr "" -#~ "The group name under which <command>gdmlogin</command>, " -#~ "<command>gdmgreeter</command>, <command>gdmchooser</command> and the " -#~ "internal failsafe GTK+ dialogues are run. Also see <filename>User</" -#~ "filename>. This user will have access to all the X authorisation files, " -#~ "and perhaps to other internal GDM data and it should not be a user such " -#~ "as nobody, but a dedicated user. The <filename>ServAuthDir</filename> is " -#~ "owned by this group. The ownership and permissions of " -#~ "<filename>ServAuthDir</filename> should be <filename>root:gdm</filename> " -#~ "and 1770." - -#~ msgid "GtkModulesList" -#~ msgstr "GtkModulesList" - -#~ msgid "GtkModulesList=module-1:module-2:..." -#~ msgstr "GtkModulesList=module-1:module-2:..." - -#~ msgid "" -#~ "A colon separated list of Gtk+ modules that <command>gdmgreeter</command> " -#~ "or <command>gdmlogin</command> will be invoked with if " -#~ "<filename>AddGtkModules</filename> is true. The format is the same as the " -#~ "standard Gtk+ module interface." -#~ msgstr "" -#~ "A colon separated list of Gtk+ modules that <command>gdmgreeter</command> " -#~ "or <command>gdmlogin</command> will be invoked with if " -#~ "<filename>AddGtkModules</filename> is true. The format is the same as the " -#~ "standard Gtk+ module interface." - -#~ msgid "HaltCommand" -#~ msgstr "HaltCommand" - -#~ msgid "HaltCommand=<sbin>/shutdown -h now" -#~ msgstr "HaltCommand=<sbin>/shutdown -h now" - -#~ msgid "" -#~ "Full path and arguments to command to be executed when user selects " -#~ "\"Shut Down\" from the Actions menu. This can be a ';' separated list of " -#~ "commands to try. If a value is missing, the shut down command is not " -#~ "available. Note that the default for this value is not empty, so to " -#~ "disable \"Shut Down\" it must be set to an empty value." -#~ msgstr "" -#~ "Full path and arguments to command to be executed when user selects " -#~ "\"Shut Down\" from the Actions menu. This can be a ';' separated list of " -#~ "commands to try. If a value is missing, the shut down command is not " -#~ "available. Note that the default for this value is not empty, so to " -#~ "disable \"Shut Down\" it must be set to an empty value." - -#~ msgid "KillInitClients" -#~ msgstr "KillInitClients" - -#~ msgid "KillInitClients=true" -#~ msgstr "KillInitClients=true" - -#~ msgid "" -#~ "Determines whether GDM should kill X clients started by the init scripts " -#~ "when the user logs in." -#~ msgstr "" -#~ "Determines whether GDM should kill X clients started by the init scripts " -#~ "when the user logs in." - -#~ msgid "LogDir" -#~ msgstr "LogDir" - -#~ msgid "LogDir=<var>/log/gdm" -#~ msgstr "LogDir=<var>/log/gdm" - -#~ msgid "" -#~ "Directory containing the log files for the individual displays. By " -#~ "default this is the same as the ServAuthDir." -#~ msgstr "" -#~ "Directory containing the log files for the individual displays. By " -#~ "default this is the same as the ServAuthDir." - -#~ msgid "PidFile" -#~ msgstr "PidFile" - -#~ msgid "PidFile=<var>/run/gdm.pid" -#~ msgstr "PidFile=<var>/run/gdm.pid" - -#~ msgid "Name of the file containing the <filename>gdm</filename> process id." -#~ msgstr "" -#~ "Name of the file containing the <filename>gdm</filename> process id." - -#~ msgid "PreFetchProgram" -#~ msgstr "PreFetchProgram" - -#~ msgid "PreFetchProgram=command" -#~ msgstr "PreFetchProgram=command" - -#~ msgid "" -#~ "Program to be run by the GDM greeter/login program when the initial " -#~ "screen is displayed. The purpose is to provide a hook where files which " -#~ "will be used after login can be preloaded to speed performance for the " -#~ "user. The program will be called once only, the first time a greeter is " -#~ "displayed. The gdmprefetch command may be used. This utility will load " -#~ "any libraries passed in on the command line, or if the argument starts " -#~ "with a \"@\" character, it will process the file assuming it is an ASCII " -#~ "file containing a list of libraries, one per line, and load each library " -#~ "in the file." -#~ msgstr "" -#~ "Program to be run by the GDM greeter/login program when the initial " -#~ "screen is displayed. The purpose is to provide a hook where files which " -#~ "will be used after login can be preloaded to speed performance for the " -#~ "user. The program will be called once only, the first time a greeter is " -#~ "displayed. The gdmprefetch command may be used. This utility will load " -#~ "any libraries passed in on the command line, or if the argument starts " -#~ "with a \"@\" character, it will process the file assuming it is an ASCII " -#~ "file containing a list of libraries, one per line, and load each library " -#~ "in the file." - -#~ msgid "PostLoginScriptDir" -#~ msgstr "PostLoginScriptDir" - -#~ msgid "PostLoginScriptDir=<etc>/gdm/PostLogin" -#~ msgstr "PostLoginScriptDir=<etc>/gdm/PostLogin" - -#~ msgid "" -#~ "Directory containing the scripts run right after the user logs in, but " -#~ "before any session setup is done. See the ``The Script Directories'' " -#~ "section for more info." -#~ msgstr "" -#~ "Directory containing the scripts run right after the user logs in, but " -#~ "before any session setup is done. See the ``The Script Directories'' " -#~ "section for more info." - -#~ msgid "PostSessionScriptDir=<etc>/gdm/PostSession" -#~ msgstr "PostSessionScriptDir=<etc>/gdm/PostSession" - -#~ msgid "" -#~ "Directory containing the scripts run after the user logs out. See the " -#~ "``The Script Directories'' section for more info." -#~ msgstr "" -#~ "Directory containing the scripts run after the user logs out. See the " -#~ "``The Script Directories'' section for more info." - -#~ msgid "PreSessionScriptDir" -#~ msgstr "PreSessionScriptDir" - -#~ msgid "PreSessionScriptDir=<etc>/gdm/PreSession" -#~ msgstr "PreSessionScriptDir=<etc>/gdm/PreSession" - -#~ msgid "" -#~ "Directory containing the scripts run before the user logs in. See the " -#~ "``The Script Directories'' section for more info." -#~ msgstr "" -#~ "Directory containing the scripts run before the user logs in. See the " -#~ "``The Script Directories'' section for more info." - -#~ msgid "RebootCommand" -#~ msgstr "RebootCommand" - -#~ msgid "RebootCommand=<sbin>/shutdown -r now" -#~ msgstr "RebootCommand=<sbin>/shutdown -r now" - -#~ msgid "" -#~ "Full path and optional arguments to the command to be executed when user " -#~ "selects Restart from the Actions menu. This can be a ';' separated list " -#~ "of commands to try. If missing, the restart command is not available. " -#~ "Note that the default for this value is not empty so to disable restart " -#~ "you must set this explicitly to an empty value." -#~ msgstr "" -#~ "Full path and optional arguments to the command to be executed when user " -#~ "selects Restart from the Actions menu. This can be a ';' separated list " -#~ "of commands to try. If missing, the restart command is not available. " -#~ "Note that the default for this value is not empty so to disable restart " -#~ "you must set this explicitly to an empty value." - -#~ msgid "RemoteGreeter" -#~ msgstr "RemoteGreeter" - -#~ msgid "RemoteGreeter=<bin>/gdmlogin" -#~ msgstr "RemoteGreeter=<bin>/gdmlogin" - -#~ msgid "" -#~ "Full path and name of the greeter executable followed by optional " -#~ "arguments. This is used for all remote XDMCP sessions. It is useful to " -#~ "have the less graphically demanding greeter here if you use the Themed " -#~ "Greeter for your main greeter. See also the <filename>Greeter</filename> " -#~ "key." -#~ msgstr "" -#~ "Full path and name of the greeter executable followed by optional " -#~ "arguments. This is used for all remote XDMCP sessions. It is useful to " -#~ "have the less graphically demanding greeter here if you use the Themed " -#~ "Greeter for your main greeter. See also the <filename>Greeter</filename> " -#~ "key." - -#~ msgid "RootPath" -#~ msgstr "RootPath" - -#~ msgid "RootPath=defaultpath (value set by configure)" -#~ msgstr "RootPath=defaultpath (value set by configure)" - -#~ msgid "" -#~ "Specifies the path which will be set in the root's session and the {Init," -#~ "PostLogin,PreSession,PostSession} scripts executed by GDM. This value " -#~ "will be overridden with the value from <filename>/etc/default/login</" -#~ "filename> if it contains \"SUROOT=<pathname>\". If the <filename>/" -#~ "etc/default/login</filename> file exists, but contains no value for " -#~ "SUROOT, the value as defined in the GDM configuration will be used." -#~ msgstr "" -#~ "Specifies the path which will be set in root's session and the {Init," -#~ "PostLogin,PreSession,PostSession} scripts executed by GDM. This value " -#~ "will be overridden with the value from <filename>/etc/default/login</" -#~ "filename> if it contains \"SUROOT=<pathname>\". If the <filename>/" -#~ "etc/default/login</filename> file exists, but contains no value for " -#~ "SUROOT, the value as defined in the GDM configuration will be used." - -#~ msgid "ServAuthDir" -#~ msgstr "ServAuthDir" - -#~ msgid "ServAuthDir=<var>/gdm" -#~ msgstr "ServAuthDir=<var>/gdm" - -#~ msgid "" -#~ "Directory containing the X authentication files for the individual " -#~ "displays. Should be owned by <filename>root.gdm</filename> with " -#~ "permissions 1770, where <filename>gdm</filename> is the GDM group as " -#~ "defined by the <filename>Group</filename> option. That is should be owned " -#~ "by root, with <filename>gdm</filename> group having full write " -#~ "permissions and the directory should be sticky and others should have no " -#~ "permission to the directory. This way the GDM user can't remove files " -#~ "owned by root in that directory, while still being able to write its own " -#~ "files there. GDM will attempt to change permissions for you when it's " -#~ "first run if the permissions are not the above. This directory is also " -#~ "used for other private files that the daemon needs to store. Other users " -#~ "should not have any way to get into this directory and read/change it's " -#~ "contents. Anybody who can read this directory can connect to any display " -#~ "on this computer." -#~ msgstr "" -#~ "Directory containing the X authentication files for the individual " -#~ "displays. Should be owned by <filename>root:gdm</filename> with " -#~ "permissions 1770, where <filename>gdm</filename> is the GDM group as " -#~ "defined by the <filename>Group</filename> option. That is should be owned " -#~ "by root, with <filename>gdm</filename> group having full write " -#~ "permissions and the directory should be sticky and others should have no " -#~ "permission to the directory. This way the GDM user can't remove files " -#~ "owned by root in that directory, while still being able to write its own " -#~ "files there. GDM will attempt to change permissions for you when it's " -#~ "first run if the permissions are not the above. This directory is also " -#~ "used for other private files that the daemon needs to store. Other users " -#~ "should not have any way to get into this directory and read/change it's " -#~ "contents. Anybody who can read this directory can connect to any display " -#~ "on this computer." - -#~ msgid "SessionDesktopDir" -#~ msgstr "SessionDesktopDir" - -#~ msgid "" -#~ "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<" -#~ "share>/xsessions/" -#~ msgstr "" -#~ "SessionDesktopDir=<etc>/X11/sessions/:<etc>/dm/Sessions/:<" -#~ "share>/xsessions/" - -#~ msgid "" -#~ "Directory containing the <filename>.desktop</filename> files which are " -#~ "the available sessions on the system. Since 2.4.4.2 this is treated like " -#~ "a PATH type variable and the first file found is used." -#~ msgstr "" -#~ "Directory containing the <filename>.desktop</filename> files which are " -#~ "the available sessions on the system. Since 2.4.4.2 this is treated like " -#~ "a PATH type variable and the first file found is used." - -#~ msgid "SoundProgram" -#~ msgstr "SoundProgram" - -#~ msgid "<bin>/play" -#~ msgstr "<bin>/play" - -#~ msgid "<bin>/audioplay" -#~ msgstr "<bin>/audioplay" - -#~ msgid "SoundProgram=<placeholder-1/> (or <placeholder-2/> on Solaris)" -#~ msgstr "SoundProgram=<placeholder-1/> (or <placeholder-2/> on Solaris)" - -#~ msgid "" -#~ "Application to use when playing a sound. Currently used for playing the " -#~ "login sound, see the <filename>SoundOnLoginFile</filename> key. Supported " -#~ "since 2.5.90.0." -#~ msgstr "" -#~ "Application to use when playing a sound. Currently used for playing the " -#~ "login sound, see the <filename>SoundOnLoginFile</filename> key. Supported " -#~ "since 2.5.90.0." - -#~ msgid "StandardXServer" -#~ msgstr "StandardXServer" - -#~ msgid "StandardXServer=/dir/to/X (value assigned by configuration file)" -#~ msgstr "StandardXServer=/dir/to/X (value assigned by configuration file)" - -#~ msgid "" -#~ "Full path and arguments to the standard X server command. This is used " -#~ "when gdm cannot find any other definition, and it's used as the default " -#~ "and failsafe fallback in a number of places. This should be able to run " -#~ "some sort of X server." -#~ msgstr "" -#~ "Full path and arguments to the standard X server command. This is used " -#~ "when gdm cannot find any other definition, and it's used as the default " -#~ "and failsafe fallback in a number of places. This should be able to run " -#~ "some sort of X server." - -#~ msgid "SuspendCommand" -#~ msgstr "SuspendCommand" - -#~ msgid "SuspendCommand=" -#~ msgstr "SuspendCommand=" - -#~ msgid "" -#~ "Full path and arguments to command to be executed when user selects " -#~ "Suspend from the Actions menu. If empty there is no such menu item. Note " -#~ "that the default for this value is not empty so to disable suspend you " -#~ "must set this explicitly to an empty value." -#~ msgstr "" -#~ "Full path and arguments to command to be executed when user selects " -#~ "Suspend from the Actions menu. If empty there is no such menu item. Note " -#~ "that the default for this value is not empty so to disable suspend you " -#~ "must set this explicitly to an empty value." - -#~ msgid "" -#~ "This is the user that should be logged in after a specified number of " -#~ "seconds of inactivity. This can never be \"root\" and gdm will refuse to " -#~ "log in root this way. The same features as for <filename>AutomaticLogin</" -#~ "filename> are supported. The same control chars and piping to a " -#~ "application are supported." -#~ msgstr "" -#~ "This is the user that should be logged in after a specified number of " -#~ "seconds of inactivity. This can never be \"root\" and gdm will refuse to " -#~ "log in root this way. The same features as for <filename>AutomaticLogin</" -#~ "filename> are supported. The same control chars and piping to a " -#~ "application are supported." - -#~ msgid "" -#~ "The username under which <command>gdmlogin</command>, " -#~ "<command>gdmgreeter</command>, <command>gdmchooser</command> and the " -#~ "internal failsafe GTK+ dialogs are run. Also see <filename>Group</" -#~ "filename>. This user will have access to all the X authorization files, " -#~ "and perhaps to other internal GDM data and it should not therefore be a " -#~ "user such as nobody, but rather a dedicated user." -#~ msgstr "" -#~ "The username under which <command>gdmlogin</command>, " -#~ "<command>gdmgreeter</command>, <command>gdmchooser</command> and the " -#~ "internal failsafe GTK+ dialogues are run. Also see <filename>Group</" -#~ "filename>. This user will have access to all the X authorisation files, " -#~ "and other internal GDM data; it should not be a user such as nobody, but " -#~ "a dedicated user." - -#~ msgid "UserAuthDir" -#~ msgstr "UserAuthDir" - -#~ msgid "UserAuthDir=" -#~ msgstr "UserAuthDir=" - -#~ msgid "" -#~ "The directory where user's <filename>.Xauthority</filename> file should " -#~ "be saved. When nothing is specified the user's home directory is used. " -#~ "This is tilde expanded so you can set it to things like: <filename>~/" -#~ "authdir/</filename>." -#~ msgstr "" -#~ "The directory where user's <filename>.Xauthority</filename> file should " -#~ "be saved. When nothing is specified the user's home directory is used. " -#~ "This is tilde expanded so you can set it to things like: <filename>~/" -#~ "authdir/</filename>." - -#~ msgid "" -#~ "If you do not use the tilde expansion, then the filename created will be " -#~ "random, like in <filename>UserAuthFBDir</filename>. This way many users " -#~ "can have the same authentication directory. For example you might want to " -#~ "set this to <filename>/tmp</filename> when user has the home directory on " -#~ "NFS, since you really don't want cookie files to go over the wire. The " -#~ "users should really have write privileges to this directory, and this " -#~ "directory should really be sticky and all that, just like the <filename>/" -#~ "tmp</filename> directory." -#~ msgstr "" -#~ "If you do not use the tilde expansion, then the filename created will be " -#~ "random, like in <filename>UserAuthFBDir</filename>. This way many users " -#~ "can have the same authentication directory. For example you might want to " -#~ "set this to <filename>/tmp</filename> when user has the home directory on " -#~ "NFS, since you really don't want cookie files to go over the wire. The " -#~ "users should really have write privileges to this directory, and this " -#~ "directory should really be sticky and all that, just like the <filename>/" -#~ "tmp</filename> directory." - -#~ msgid "" -#~ "Normally if this is the user's home directory GDM will still refuse to " -#~ "put cookies there if it thinks it is NFS (by testing root-squashing). " -#~ "This can be changed by setting <filename>NeverPlaceCookiesOnNFS</" -#~ "filename> in the <filename>[security]</filename> section to false." -#~ msgstr "" -#~ "Normally if this is the user's home directory GDM will still refuse to " -#~ "put cookies there if it thinks it is NFS (by testing root-squashing). " -#~ "This can be changed by setting <filename>NeverPlaceCookiesOnNFS</" -#~ "filename> in the <filename>[security]</filename> section to false." - -#~ msgid "UserAuthFBDir" -#~ msgstr "UserAuthFBDir" - -#~ msgid "UserAuthFBDir=/tmp" -#~ msgstr "UserAuthFBDir=/tmp" - -#~ msgid "" -#~ "If GDM fails to update the user's <filename>.Xauthority</filename> file a " -#~ "fallback cookie is created in this directory." -#~ msgstr "" -#~ "If GDM fails to update the user's <filename>.Xauthority</filename> file a " -#~ "fallback cookie is created in this directory." - -#~ msgid "UserAuthFile" -#~ msgstr "UserAuthFile" - -#~ msgid "UserAuthFile=.Xauthority" -#~ msgstr "UserAuthFile=.Xauthority" - -#~ msgid "Name of the file used for storing user cookies." -#~ msgstr "Name of the file used for storing user cookies." - -#~ msgid "VTAllocation" -#~ msgstr "VTAllocation" - -#~ msgid "VTAllocation=true" -#~ msgstr "VTAllocation=true" - -#~ msgid "" -#~ "On systems where GDM supports automatic VT (virtual terminal) allocation " -#~ "(currently Linux and FreeBSD only), you can have GDM automatically append " -#~ "the vt argument to the X server executable. This way races that come up " -#~ "from each X server managing it's own vt allocation can be avoided. See " -#~ "also <filename>FirstVT</filename>." -#~ msgstr "" -#~ "On systems where GDM supports automatic VT (virtual terminal) allocation " -#~ "(currently Linux and FreeBSD only), you can have GDM automatically append " -#~ "the vt argument to the X server executable. This way races that come up " -#~ "from each X server managing it's own vt allocation can be avoided. See " -#~ "also <filename>FirstVT</filename>." - -#~ msgid "XKeepsCrashing" -#~ msgstr "XKeepsCrashing" - -#~ msgid "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" -#~ msgstr "XKeepsCrashing=<etc>/gdm/XKeepsCrashing" - -#~ msgid "" -#~ "A script to run in case X keeps crashing. This is for running An X " -#~ "configuration or whatever else to make the X configuration work. See the " -#~ "script that came with the distribution for an example. The distributed " -#~ "<filename>XKeepsCrashing</filename> script is tested on Red Hat, but may " -#~ "work elsewhere. Your system integrator should make sure this script is up " -#~ "to date for your particular system." -#~ msgstr "" -#~ "A script to run in case X keeps crashing. This is for running An X " -#~ "configuration or whatever else to make the X configuration work. See the " -#~ "script that came with the distribution for an example. The distributed " -#~ "<filename>XKeepsCrashing</filename> script is tested on Red Hat, but may " -#~ "work elsewhere. Your system integrator should make sure this script is up " -#~ "to date for your particular system." - -#~ msgid "" -#~ "In case <filename>FailsafeXServer</filename> is setup, that will be tried " -#~ "first. and this only used as a backup if even that X server keeps " -#~ "crashing." -#~ msgstr "" -#~ "In case <filename>FailsafeXServer</filename> is setup, that will be tried " -#~ "first. and this only used as a backup if even that X server keeps " -#~ "crashing." - -#~ msgid "Xnest" -#~ msgstr "Xnest" - -#~ msgid "Xnest=<bin>/X11/Xnest (/usr/openwin/bin/Xnest on Solaris)" -#~ msgstr "Xnest=<bin>/X11/Xnest (/usr/openwin/bin/Xnest on Solaris)" - -#~ msgid "" -#~ "The full path and arguments to the Xnest command. This is used for the " -#~ "flexible Xnest displays. This way the user can start new login screens in " -#~ "a nested window. Of course you must have the Xnest display from your X " -#~ "server packages installed for this to work." -#~ msgstr "" -#~ "The full path and arguments to the Xnest command. This is used for the " -#~ "flexible Xnest displays. This way the user can start new login screens in " -#~ "a nested window. Of course you must have the Xnest display from your X " -#~ "server packages installed for this to work." - -#~ msgid "AllowRoot" -#~ msgstr "AllowRoot" - -#~ msgid "AllowRoot=true" -#~ msgstr "AllowRoot=true" - -#~ msgid "" -#~ "Allow root (privileged user) to log in through GDM. Set this to false if " -#~ "you want to disallow such logins." -#~ msgstr "" -#~ "Allow root (privileged user) to log in through GDM. Set this to false if " -#~ "you want to disallow such logins." - -#~ msgid "" -#~ "On systems that support PAM, this parameter is not as useful as you can " -#~ "use PAM to do the same thing, and in fact do even more. However it is " -#~ "still followed, so you should probably leave it true for PAM systems." -#~ msgstr "" -#~ "On systems that support PAM, this parameter is not as useful as you can " -#~ "use PAM to do the same thing, and in fact do even more. However it is " -#~ "still followed, so you should probably leave it true for PAM systems." - -#~ msgid "AllowRemoteRoot" -#~ msgstr "AllowRemoteRoot" - -#~ msgid "AllowRemoteRoot=false" -#~ msgstr "AllowRemoteRoot=false" - -#~ msgid "" -#~ "Allow root (privileged user) to log in remotely through GDM. This value " -#~ "should be set to true to allow such logins. Remote logins are any logins " -#~ "that come in through the XDMCP." -#~ msgstr "" -#~ "Allow root (privileged user) to log in remotely through GDM. This value " -#~ "should be set to true to allow such logins. Remote logins are any logins " -#~ "that come in through the XDMCP." - -#~ msgid "" -#~ "On systems that support PAM, this parameter is not as useful since you " -#~ "can use PAM to do the same thing, and do even more." -#~ msgstr "" -#~ "On systems that support PAM, this parameter is not as useful since you " -#~ "can use PAM to do the same thing, and do even more." - -#~ msgid "" -#~ "This value will be overridden and set to false if the <filename>/etc/" -#~ "default/login</filename> file exists and contains \"CONSOLE=/dev/login\", " -#~ "and set to true if the <filename>/etc/default/login</filename> file " -#~ "exists and contains any other value or no value for CONSOLE." -#~ msgstr "" -#~ "This value will be overridden and set to false if the <filename>/etc/" -#~ "default/login</filename> file exists and contains \"CONSOLE=/dev/login\", " -#~ "and set to true if the <filename>/etc/default/login</filename> file " -#~ "exists and contains any other value or no value for CONSOLE." - -#~ msgid "AllowRemoteAutoLogin" -#~ msgstr "AllowRemoteAutoLogin" - -#~ msgid "AllowRemoteAutoLogin=false" -#~ msgstr "AllowRemoteAutoLogin=false" - -#~ msgid "" -#~ "Allow the timed login to work remotely. That is, remote connections " -#~ "through XDMCP will be allowed to log into the \"TimedLogin\" user by " -#~ "letting the login window time out, just like the local user on the first " -#~ "console." -#~ msgstr "" -#~ "Allow the timed login to work remotely. That is, remote connections " -#~ "through XDMCP will be allowed to log into the \"TimedLogin\" user by " -#~ "letting the login window time out, just like the local user on the first " -#~ "console." - -#~ msgid "" -#~ "Note that this can make a system quite insecure, and thus is off by " -#~ "default." -#~ msgstr "" -#~ "Note that this can make a system quite insecure, and thus is off by " -#~ "default." - -#~ msgid "CheckDirOwner" -#~ msgstr "CheckDirOwner" - -#~ msgid "CheckDirOwner=true" -#~ msgstr "CheckDirOwner=true" - -#~ msgid "" -#~ "By default GDM checks the ownership of the home directories before " -#~ "writing to them, this prevents security issues in case of bad setup. " -#~ "However in some instances home directories will be owned by a different " -#~ "user and in this case it is necessary to turn this option on. You will " -#~ "also most likely have to turn the <filename>RelaxPermissions</filename> " -#~ "key to at least value 1 since in such a scenario home directories are " -#~ "likely to be group writable. Supported since 2.6.0.4." -#~ msgstr "" -#~ "By default GDM checks the ownership of the home directories before " -#~ "writing to them, this prevents security issues in case of bad setup. " -#~ "However in some instances home directories will be owned by a different " -#~ "user and in this case it is necessary to turn this option on. You will " -#~ "also most likely have to turn the <filename>RelaxPermissions</filename> " -#~ "key to at least value 1 since in such a scenario home directories are " -#~ "likely to be group writable. Supported since 2.6.0.4." - -#~ msgid "SupportAutomount" -#~ msgstr "SupportAutomount" - -#~ msgid "SupportAutomount=false" -#~ msgstr "SupportAutomount=false" - -#~ msgid "" -#~ "By default GDM checks the ownership of the home directories before " -#~ "writing to them, this prevents security issues in case of bad setup. " -#~ "However, when home directories are managed by automounter, they are often " -#~ "not mounted before they are accessed. This option works around subtleties " -#~ "of Linux automounter." -#~ msgstr "" -#~ "By default GDM checks the ownership of the home directories before " -#~ "writing to them, this prevents security issues in case of bad setup. " -#~ "However, when home directories are managed by automounter, they are often " -#~ "not mounted before they are accessed. This option works around subtleties " -#~ "of Linux automounter." - -#~ msgid "NeverPlaceCookiesOnNFS" -#~ msgstr "NeverPlaceCookiesOnNFS" - -#~ msgid "NeverPlaceCookiesOnNFS=true" -#~ msgstr "NeverPlaceCookiesOnNFS=true" - -#~ msgid "" -#~ "Normally if this is true (which is by default), GDM will not place " -#~ "cookies into the user's home directory if this directory is on NFS. Well, " -#~ "GDM will consider any filesystem with root-squashing an NFS filesystem. " -#~ "Sometimes however the remote file system can have root squashing and be " -#~ "safe (perhaps by using encryption). In this case set this to 'false'. " -#~ "Note that this option appeared in version 2.4.4.4 and is ignored in " -#~ "previous versions." -#~ msgstr "" -#~ "Normally if this is true (which is by default), GDM will not place " -#~ "cookies into the user's home directory if this directory is on NFS. GDM " -#~ "will consider any filesystem with root-squashing an NFS filesystem. " -#~ "Sometimes however the remote file system can have root squashing and be " -#~ "safe (perhaps by using encryption). In this case set this to 'false'. " -#~ "Note that this option appeared in version 2.4.4.4 and is ignored in " -#~ "previous versions." - -#~ msgid "PasswordRequired" -#~ msgstr "PasswordRequired" - -#~ msgid "PasswordRequired=false" -#~ msgstr "PasswordRequired=false" - -#~ msgid "" -#~ "If true, this will cause PAM_DISALLOW_NULL_AUTHTOK to be passed as a flag " -#~ "to pam_authenticate and pam_acct_mgmt, disallowing NULL password. This " -#~ "setting will only take effect if PAM is being used by GDM. This value " -#~ "will be overridden with the value from <filename>/etc/default/login</" -#~ "filename> if it contains \"PASSREQ=[YES|NO]\". If the <filename>/etc/" -#~ "default/login</filename> file exists, but contains no value for PASSREQ, " -#~ "the value as defined in the GDM configuration will be used." -#~ msgstr "" -#~ "If true, this will cause PAM_DISALLOW_NULL_AUTHTOK to be passed as a flag " -#~ "to pam_authenticate and pam_acct_mgmt, disallowing NULL password. This " -#~ "setting will only take effect if PAM is being used by GDM. This value " -#~ "will be overridden with the value from <filename>/etc/default/login</" -#~ "filename> if it contains \"PASSREQ=[YES|NO]\". If the <filename>/etc/" -#~ "default/login</filename> file exists, but contains no value for PASSREQ, " -#~ "the value as defined in the GDM configuration will be used." - -#~ msgid "RelaxPermissions" -#~ msgstr "RelaxPermissions" - -#~ msgid "RelaxPermissions=0" -#~ msgstr "RelaxPermissions=0" - -#~ msgid "" -#~ "By default GDM ignores files and directories writable to other users than " -#~ "the owner." -#~ msgstr "" -#~ "By default GDM ignores files and directories writable to other users than " -#~ "the owner." - -#~ msgid "" -#~ "Changing the value of RelaxPermissions makes it possible to alter this " -#~ "behavior:" -#~ msgstr "" -#~ "Changing the value of RelaxPermissions makes it possible to alter this " -#~ "behavior:" - -#~ msgid "0 - Paranoia option. Only accepts user owned files and directories." -#~ msgstr "0 - Paranoia option. Only accepts user owned files and directories." - -#~ msgid "1 - Allow group writable files and directories." -#~ msgstr "1 - Allow group writable files and directories." - -#~ msgid "2 - Allow world writable files and directories." -#~ msgstr "2 - Allow world writable files and directories." - -#~ msgid "RetryDelay" -#~ msgstr "RetryDelay" - -#~ msgid "RetryDelay=1" -#~ msgstr "RetryDelay=1" - -#~ msgid "" -#~ "The number of seconds GDM should wait before reactivating the entry field " -#~ "after a failed login." -#~ msgstr "" -#~ "The number of seconds GDM should wait before reactivating the entry field " -#~ "after a failed login." - -#~ msgid "UserMaxFile" -#~ msgstr "UserMaxFile" - -#~ msgid "UserMaxFile=65536" -#~ msgstr "UserMaxFile=65536" - -#~ msgid "" -#~ "GDM will refuse to read/write files bigger than this number (specified in " -#~ "bytes)." -#~ msgstr "" -#~ "GDM will refuse to read/write files bigger than this number (specified in " -#~ "bytes)." - -#~ msgid "" -#~ "In addition to the size check GDM is extremely picky about accessing " -#~ "files in user directories. It will not follow symlinks and can optionally " -#~ "refuse to read files and directories writable by other than the owner. " -#~ "See the <filename>RelaxPermissions</filename> option for more info." -#~ msgstr "" -#~ "In addition to the size check GDM is extremely picky about accessing " -#~ "files in user directories. It will not follow symlinks and can optionally " -#~ "refuse to read files and directories writable by other than the owner. " -#~ "See the <filename>RelaxPermissions</filename> option for more info." - -#~ msgid "EnableProxy" -#~ msgstr "EnableProxy" - -#~ msgid "EnableProxy=false" -#~ msgstr "EnableProxy=false" - -#~ msgid "" -#~ "Setting this to true enables support for running XDMCP sessions on a " -#~ "local proxy X server. This may improve the performance of XDMCP sessions, " -#~ "especially on high latency networks, as many X protocol operations can be " -#~ "completed without going over the network." -#~ msgstr "" -#~ "Setting this to true enables support for running XDMCP sessions on a " -#~ "local proxy X server. This may improve the performance of XDMCP sessions, " -#~ "especially on high latency networks, as many X protocol operations can be " -#~ "completed without going over the network." - -#~ msgid "" -#~ "Note, however, that this mode will significantly increase the burden on " -#~ "the machine hosting the XDMCP sessions" -#~ msgstr "" -#~ "Note, however, that this mode will significantly increase the burden on " -#~ "the machine hosting the XDMCP sessions" - -#~ msgid "" -#~ "See the <filename>FlexiProxy</filename> and " -#~ "<filename>FlexiProxyDisconnect</filename> options for further details on " -#~ "how to configure support for this feature." -#~ msgstr "" -#~ "See the <filename>FlexiProxy</filename> and " -#~ "<filename>FlexiProxyDisconnect</filename> options for further details on " -#~ "how to configure support for this feature." - -#~ msgid "MaxPendingIndirect" -#~ msgstr "MaxPendingIndirect" - -#~ msgid "MaxPendingIndirect=4" -#~ msgstr "MaxPendingIndirect=4" - -#~ msgid "" -#~ "GDM will only provide <filename>MaxPendingIndirect</filename> displays " -#~ "with host choosers simultaneously. If more queries from different hosts " -#~ "come in, the oldest ones will be forgotten." -#~ msgstr "" -#~ "GDM will only provide <filename>MaxPendingIndirect</filename> displays " -#~ "with host choosers simultaneously. If more queries from different hosts " -#~ "come in, the oldest ones will be forgotten." - -#~ msgid "ProxyReconnect" -#~ msgstr "ProxyReconnect" - -#~ msgid "FlexiProxyReconnect=" -#~ msgstr "FlexiProxyReconnect=" - -#~ msgid "" -#~ "Setting this option enables experimental support for session migration " -#~ "with XDMCP sessions. This enables users to disconnect from their session " -#~ "and later reconnect to that same session, possibly from a different " -#~ "terminal." -#~ msgstr "" -#~ "Setting this option enables experimental support for session migration " -#~ "with XDMCP sessions. This enables users to disconnect from their session " -#~ "and later reconnect to that same session, possibly from a different " -#~ "terminal." - -#~ msgid "" -#~ "In order to use this feature, you must have a nested X server available " -#~ "which supports disconnecting from its parent X server and reconnecting to " -#~ "another X server. Currently, the Distributed Multihead X (DMX) server " -#~ "supports this feature to some extent and other projects like NoMachine NX " -#~ "are busy implementing it." -#~ msgstr "" -#~ "In order to use this feature, you must have a nested X server available " -#~ "which supports disconnecting from its parent X server and reconnecting to " -#~ "another X server. Currently, the Distributed Multihead X (DMX) server " -#~ "supports this feature to some extent and other projects like NoMachine NX " -#~ "are busy implementing it." - -#~ msgid "" -#~ "This option should be set to the path of a command which will handle " -#~ "reconnecting the XDMCP proxy to another backend display. A sample " -#~ "implementation for use with DMX is supplied." -#~ msgstr "" -#~ "This option should be set to the path of a command which will handle " -#~ "reconnecting the XDMCP proxy to another backend display. A sample " -#~ "implementation for use with DMX is supplied." - -#~ msgid "ProxyXServer" -#~ msgstr "ProxyXServer" - -#~ msgid "ProxyXServer=" -#~ msgstr "ProxyXServer=" - -#~ msgid "" -#~ "The X server command line for a XDMCP proxy. Any nested X server like " -#~ "Xnest, Xephr or Xdmx should work fairly well." -#~ msgstr "" -#~ "The X server command line for a XDMCP proxy. Any nested X server like " -#~ "Xnest, Xephr or Xdmx should work fairly well." - -#~ msgid "Common GUI Configuration Options" -#~ msgstr "Common GUI Configuration Options" - -#~ msgid "[gui]" -#~ msgstr "[gui]" - -#~ msgid "AllowGtkThemeChange" -#~ msgstr "AllowGtkThemeChange" - -#~ msgid "AllowGtkThemeChange=true" -#~ msgstr "AllowGtkThemeChange=true" - -#~ msgid "" -#~ "If to allow changing the GTK+ (widget) theme from the greeter. Currently " -#~ "this only affects the standard greeter as the graphical greeter does not " -#~ "yet have this ability. The theme will stay in effect on this display " -#~ "until changed and will affect all the other windows that are put up by " -#~ "GDM. Supported since 2.5.90.2." -#~ msgstr "" -#~ "If to allow changing the GTK+ (widget) theme from the greeter. Currently " -#~ "this only affects the standard greeter as the graphical greeter does not " -#~ "yet have this ability. The theme will stay in effect on this display " -#~ "until changed and will affect all the other windows that are put up by " -#~ "GDM. Supported since 2.5.90.2." - -#~ msgid "GtkRC" -#~ msgstr "GtkRC" - -#~ msgid "GtkRC=" -#~ msgstr "GtkRC=" - -#~ msgid "" -#~ "Path to a <filename>gtkrc</filename> to read when GDM puts up a window. " -#~ "You should really now use the <filename>GtkTheme</filename> key for just " -#~ "setting a theme." -#~ msgstr "" -#~ "Path to a <filename>gtkrc</filename> to read when GDM puts up a window. " -#~ "You should really now use the <filename>GtkTheme</filename> key for just " -#~ "setting a theme." - -#~ msgid "GtkTheme" -#~ msgstr "GtkTheme" - -#~ msgid "GtkTheme=Default" -#~ msgstr "GtkTheme=Default" - -#~ msgid "" -#~ "A name of an installed theme to use by default. It will be used in the " -#~ "greeter, chooser and all other GUI windows put up by GDM. Supported since " -#~ "2.5.90.2." -#~ msgstr "" -#~ "A name of an installed theme to use by default. It will be used in the " -#~ "greeter, chooser and all other GUI windows put up by GDM. Supported since " -#~ "2.5.90.2." - -#~ msgid "GtkThemesToAllow" -#~ msgstr "GtkThemesToAllow" - -#~ msgid "GtkThemesToAllow=all" -#~ msgstr "GtkThemesToAllow=all" - -#~ msgid "" -#~ "Comma separated list of themes to allow. These must be the names of the " -#~ "themes installed in the standard locations for GTK+ themes. You can also " -#~ "specify 'all' to allow all installed themes. This is related to the " -#~ "<filename>AllowGtkThemeChange</filename> key. Supported since 2.5.90.2." -#~ msgstr "" -#~ "Comma separated list of themes to allow. These must be the names of the " -#~ "themes installed in the standard locations for GTK+ themes. You can also " -#~ "specify 'all' to allow all installed themes. This is related to the " -#~ "<filename>AllowGtkThemeChange</filename> key. Supported since 2.5.90.2." - -#~ msgid "MaxIconWidth" -#~ msgstr "MaxIconWidth" - -#~ msgid "MaxIconWidth=128" -#~ msgstr "MaxIconWidth=128" - -#~ msgid "" -#~ "Specifies the maximum icon width (in pixels) that the face browser will " -#~ "display. Icons larger than this will be scaled. This also affects icons " -#~ "in the XDMCP chooser." -#~ msgstr "" -#~ "Specifies the maximum icon width (in pixels) that the face browser will " -#~ "display. Icons larger than this will be scaled. This also affects icons " -#~ "in the XDMCP chooser." - -#~ msgid "MaxIconHeight" -#~ msgstr "MaxIconHeight" - -#~ msgid "MaxIconHeight=128" -#~ msgstr "MaxIconHeight=128" - -#~ msgid "" -#~ "Specifies the maximum icon height (in pixels) that the face browser will " -#~ "display. Icons larger than this will be scaled. This also affects icons " -#~ "in the XDMCP chooser." -#~ msgstr "" -#~ "Specifies the maximum icon height (in pixels) that the face browser will " -#~ "display. Icons larger than this will be scaled. This also affects icons " -#~ "in the XDMCP chooser." - -#~ msgid "[greeter]" -#~ msgstr "[greeter]" - -#~ msgid "BackgroundColor" -#~ msgstr "BackgroundColor" - -#~ msgid "BackgroundColor=#76848F" -#~ msgstr "BackgroundColor=#76848F" - -#~ msgid "" -#~ "If the BackgroundType is 2, use this color in the background of the " -#~ "greeter. Also use it as the back of transparent images set on the " -#~ "background and if the BackgroundRemoteOnlyColor is set and this is a " -#~ "remote display. This only affects the GTK+ Greeter." -#~ msgstr "" -#~ "If the BackgroundType is 2, use this colour in the background of the " -#~ "greeter. Also use it as the back of transparent images set on the " -#~ "background and if the BackgroundRemoteOnlyColor is set and this is a " -#~ "remote display. This only affects the GTK+ Greeter." - -#~ msgid "BackgroundProgramInitialDelay" -#~ msgstr "BackgroundProgramInitialDelay" - -#~ msgid "BackgroundProgramInitialDelay=30" -#~ msgstr "BackgroundProgramInitialDelay=30" - -#~ msgid "" -#~ "The background application will be started after at least that many " -#~ "seconds of inactivity." -#~ msgstr "" -#~ "The background application will be started after at least that many " -#~ "seconds of inactivity." - -#~ msgid "RestartBackgroundProgram" -#~ msgstr "RestartBackgroundProgram" - -#~ msgid "RestartBackgroundProgram=true" -#~ msgstr "RestartBackgroundProgram=true" - -#~ msgid "" -#~ "If set the background application will be restarted when it has exited, " -#~ "after the delay described below has elapsed. This option can be useful " -#~ "when you wish to run a screen saver application when no user is using the " -#~ "computer." -#~ msgstr "" -#~ "If set the background application will be restarted when it has exited, " -#~ "after the delay described below has elapsed. This option can be useful " -#~ "when you wish to run a screen saver application when no user is using the " -#~ "computer." - -#~ msgid "BackgroundProgramRestartDelay" -#~ msgstr "BackgroundProgramRestartDelay" - -#~ msgid "BackgroundProgramRestartDelay=30" -#~ msgstr "BackgroundProgramRestartDelay=30" - -#~ msgid "" -#~ "The background application will be restarted after at least that many " -#~ "seconds of inactivity." -#~ msgstr "" -#~ "The background application will be restarted after at least that many " -#~ "seconds of inactivity." - -#~ msgid "BackgroundImage" -#~ msgstr "BackgroundImage" - -#~ msgid "BackgroundImage=somefile.png" -#~ msgstr "BackgroundImage=somefile.png" - -#~ msgid "" -#~ "If the BackgroundType is 1, then display this file as the background in " -#~ "the greeter. This only affects the GTK+ Greeter." -#~ msgstr "" -#~ "If the BackgroundType is 1, then display this file as the background in " -#~ "the greeter. This only affects the GTK+ Greeter." - -#~ msgid "BackgroundProgram" -#~ msgstr "BackgroundProgram" - -#~ msgid "BackgroundProgram=<bin>/xeyes" -#~ msgstr "BackgroundProgram=<bin>/xeyes" - -#~ msgid "" -#~ "If set this command will be run in the background while the login window " -#~ "is being displayed. Note that not all applications will run this way, " -#~ "since GDM does not usually have a home directory. You could set up home " -#~ "directory for the GDM user if you wish to run applications which require " -#~ "it. This only affects the GTK+ Greeter." -#~ msgstr "" -#~ "If set this command will be run in the background while the login window " -#~ "is being displayed. Note that not all applications will run this way, " -#~ "since GDM does not usually have a home directory. You could set up home " -#~ "directory for the GDM user if you wish to run applications which require " -#~ "it. This only affects the GTK+ Greeter." - -#~ msgid "BackgroundRemoteOnlyColor" -#~ msgstr "BackgroundRemoteOnlyColor" - -#~ msgid "BackgroundRemoteOnlyColor=true" -#~ msgstr "BackgroundRemoteOnlyColor=true" - -#~ msgid "" -#~ "On remote displays only set the color background. This is to make network " -#~ "load lighter. The <filename>BackgroundProgram</filename> is also not run. " -#~ "This only affects the GTK+ Greeter." -#~ msgstr "" -#~ "On remote displays only set the colour background. This is to make " -#~ "network load lighter. The <filename>BackgroundProgram</filename> is also " -#~ "not run. This only affects the GTK+ Greeter." - -#~ msgid "BackgroundScaleToFit" -#~ msgstr "BackgroundScaleToFit" - -#~ msgid "BackgroundScaleToFit=true" -#~ msgstr "BackgroundScaleToFit=true" - -#~ msgid "" -#~ "Scale background image to fit the screen. This only affects the GTK+ " -#~ "Greeter." -#~ msgstr "" -#~ "Scale background image to fit the screen. This only affects the GTK+ " -#~ "Greeter." - -#~ msgid "BackgroundType" -#~ msgstr "BackgroundType" - -#~ msgid "BackgroundType=2" -#~ msgstr "BackgroundType=2" - -#~ msgid "" -#~ "The type of background to set. 0 is none, 1 is image and color, 2 is " -#~ "color and 3 is image. This only affects the GTK+ Greeter." -#~ msgstr "" -#~ "The type of background to set. 0 is none, 1 is image and colour, 2 is " -#~ "colour and 3 is image. This only affects the GTK+ Greeter." - -#~ msgid "Browser" -#~ msgstr "Browser" - -#~ msgid "Browser=true" -#~ msgstr "Browser=true" - -#~ msgid "" -#~ "Set to true to enable the face browser. See the ``The GTK+ Greeter'' " -#~ "section for more information on the face browser. This option only works " -#~ "for the GTK+ Greeter. For the Themed Greeter, the face browser is enabled " -#~ "by choosing a theme which includes a face browser" -#~ msgstr "" -#~ "Set to true to enable the face browser. See the ``The GTK+ Greeter'' " -#~ "section for more information on the face browser. This option only works " -#~ "for the GTK+ Greeter. For the Themed Greeter, the face browser is enabled " -#~ "by choosing a theme which includes a face browser" - -#~ msgid "ChooserButton" -#~ msgstr "ChooserButton" - -#~ msgid "ChooserButton=true" -#~ msgstr "ChooserButton=true" - -#~ msgid "" -#~ "If true, add a chooser button to the Actions menu that will restart the " -#~ "current X server with a chooser. XDMCP does not need to be enabled on the " -#~ "local computer for this to work." -#~ msgstr "" -#~ "If true, add a chooser button to the Actions menu that will restart the " -#~ "current X server with a chooser. XDMCP does not need to be enabled on the " -#~ "local computer for this to work." - -#~ msgid "ConfigAvailable" -#~ msgstr "ConfigAvailable" - -#~ msgid "ConfigAvailable=false" -#~ msgstr "ConfigAvailable=false" - -#~ msgid "" -#~ "If true, allows the configurator to be run from the greeter. Note that " -#~ "the user will need to type in the root password before the configurator " -#~ "will be started. This is set to false by default for additional security. " -#~ "See the <filename>Configurator</filename> option in the daemon section." -#~ msgstr "" -#~ "If true, allows the configurator to be run from the greeter. Note that " -#~ "the user will need to type in the root password before the configurator " -#~ "will be started. This is set to false by default for additional security. " -#~ "See the <filename>Configurator</filename> option in the daemon section." - -#~ msgid "DefaultFace" -#~ msgstr "DefaultFace" - -#~ msgid "DefaultFace=<share>/pixmaps/nophoto.png" -#~ msgstr "DefaultFace=<share>/pixmaps/nophoto.png" - -#~ msgid "" -#~ "If a user has no defined face image, GDM will use the \"stock_person\" " -#~ "icon defined in the current GTK+ theme. If no such image is defined, the " -#~ "image specified by <filename>DefaultFace</filename> will be used. The " -#~ "image must be in a gdk-pixbuf supported format and the file must be " -#~ "readable to the GDM user." -#~ msgstr "" -#~ "If a user has no defined face image, GDM will use the \"stock_person\" " -#~ "icon defined in the current GTK+ theme. If no such image is defined, the " -#~ "image specified by <filename>DefaultFace</filename> will be used. The " -#~ "image must be in a gdk-pixbuf supported format and the file must be " -#~ "readable to the GDM user." - -#~ msgid "Include" -#~ msgstr "Include" - -#~ msgid "Include=" -#~ msgstr "Include=" - -#~ msgid "" -#~ "Comma separated list of users to be included in the face browser and in " -#~ "the <command>gdmsetup</command> selection list for Automatic/Timed login. " -#~ "See also <filename>Exclude</filename>, <filename>IncludeAll</filename>, " -#~ "and <filename>MinimalUID</filename>." -#~ msgstr "" -#~ "Comma separated list of users to be included in the face browser and in " -#~ "the <command>gdmsetup</command> selection list for Automatic/Timed login. " -#~ "See also <filename>Exclude</filename>, <filename>IncludeAll</filename>, " -#~ "and <filename>MinimalUID</filename>." - -#~ msgid "Exclude" -#~ msgstr "Exclude" - -#~ msgid "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." -#~ msgstr "Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,..." - -#~ msgid "" -#~ "Comma separated list of users to be excluded from the face browser and " -#~ "from the <command>gdmsetup</command> selection list for Automatic/Timed " -#~ "login. Excluded users will still be able to log in, but will have to type " -#~ "their username. See also <filename>Include</filename>, " -#~ "<filename>IncludeAll</filename>, and <filename>MinimalUID</filename>." -#~ msgstr "" -#~ "Comma separated list of users to be excluded from the face browser and " -#~ "from the <command>gdmsetup</command> selection list for Automatic/Timed " -#~ "login. Excluded users will still be able to log in, but will have to type " -#~ "their username. See also <filename>Include</filename>, " -#~ "<filename>IncludeAll</filename>, and <filename>MinimalUID</filename>." - -#~ msgid "IncludeAll" -#~ msgstr "IncludeAll" - -#~ msgid "IncludeAll=false" -#~ msgstr "IncludeAll=false" - -#~ msgid "" -#~ "By default, an empty include list means display no users. By setting " -#~ "IncludeAll to true, the password file will be scanned and all users will " -#~ "be displayed aside from users excluded via the Exclude setting and user " -#~ "ID's less than MinimalUID. Scanning the password file can be slow on " -#~ "systems with large numbers of users and this feature should not be used " -#~ "in such environments. See also <filename>Include</filename>, " -#~ "<filename>Exclude</filename>, and <filename>MinimalUID</filename>." -#~ msgstr "" -#~ "By default, an empty include list means display no users. By setting " -#~ "IncludeAll to true, the password file will be scanned and all users will " -#~ "be displayed aside from users excluded via the Exclude setting and user " -#~ "ID's less than MinimalUID. Scanning the password file can be slow on " -#~ "systems with large numbers of users and this feature should not be used " -#~ "in such environments. See also <filename>Include</filename>, " -#~ "<filename>Exclude</filename>, and <filename>MinimalUID</filename>." - -#~ msgid "GlobalFaceDir" -#~ msgstr "GlobalFaceDir" - -#~ msgid "GlobalFaceDir=<share>/pixmaps/faces/" -#~ msgstr "GlobalFaceDir=<share>/pixmaps/faces/" - -#~ msgid "" -#~ "Systemwide directory for face files. The sysadmin can place icons for " -#~ "users here without touching their homedirs. Faces are named after their " -#~ "users' logins." -#~ msgstr "" -#~ "Systemwide directory for face files. The sysadmin can place icons for " -#~ "users here without touching their homedirs. Faces are named after their " -#~ "users' logins." - -#~ msgid "" -#~ "I.e. <filename><GlobalFaceDir>/johndoe</filename> would contain the " -#~ "face icon for the user ``johndoe''. No image format extension should be " -#~ "specified." -#~ msgstr "" -#~ "I.e. <filename><GlobalFaceDir>/johndoe</filename> would contain the " -#~ "face icon for the user ``johndoe''. No image format extension should be " -#~ "specified." - -#~ msgid "" -#~ "The face images must be stored in gdk-pixbuf supported formats and they " -#~ "must be readable for the GDM user." -#~ msgstr "" -#~ "The face images must be stored in gdk-pixbuf supported formats and they " -#~ "must be readable for the GDM user." - -#~ msgid "" -#~ "A user's own icon file will always take precedence over the sysadmin " -#~ "provided one." -#~ msgstr "" -#~ "A user's own icon file will always take precedence over the sysadmin " -#~ "provided one." - -#~ msgid "GraphicalTheme" -#~ msgstr "GraphicalTheme" - -#~ msgid "GraphicalTheme=circles" -#~ msgstr "GraphicalTheme=circles" - -#~ msgid "" -#~ "The graphical theme that the Themed Greeter should use. it should refer " -#~ "to a directory in the theme directory set by <filename>GraphicalThemeDir</" -#~ "filename>." -#~ msgstr "" -#~ "The graphical theme that the Themed Greeter should use. it should refer " -#~ "to a directory in the theme directory set by <filename>GraphicalThemeDir</" -#~ "filename>." - -#~ msgid "GraphicalThemes" -#~ msgstr "GraphicalThemes" - -#~ msgid "GraphicalThemes=circles" -#~ msgstr "GraphicalThemes=circles" - -#~ msgid "" -#~ "The graphical themes that the Themed Greeter should use is the Mode is " -#~ "set on Random Themes. This is a \"/:\" delimited list. It should refer to " -#~ "a directory in the theme directory set by <filename>GraphicalThemeDir</" -#~ "filename>. This is only used if <filename>GraphicalThemeRand</filename> " -#~ "is set to true." -#~ msgstr "" -#~ "The graphical themes that the Themed Greeter should use is the Mode is " -#~ "set on Random Themes. This is a \"/:\" delimited list. It should refer to " -#~ "a directory in the theme directory set by <filename>GraphicalThemeDir</" -#~ "filename>. This is only used if <filename>GraphicalThemeRand</filename> " -#~ "is set to true." - -#~ msgid "GraphicalThemeRand" -#~ msgstr "GraphicalThemeRand" - -#~ msgid "GraphicalThemeRand=false" -#~ msgstr "GraphicalThemeRand=false" - -#~ msgid "" -#~ "Whether the graphical greeter will use Only One Theme or Random Theme " -#~ "mode. Only One Theme mode uses themes listed by <filename>GraphicalTheme</" -#~ "filename>, Random Themes mode uses themes listed by " -#~ "<filename>GraphicalThemes</filename>. A value of false sets greeter to " -#~ "use Only One Theme mode, a value of true sets the greeter to use Random " -#~ "Theme mode." -#~ msgstr "" -#~ "Whether the graphical greeter will use Only One Theme or Random Theme " -#~ "mode. Only One Theme mode uses themes listed by <filename>GraphicalTheme</" -#~ "filename>, Random Themes mode uses themes listed by " -#~ "<filename>GraphicalThemes</filename>. A value of false sets greeter to " -#~ "use Only One Theme mode, a value of true sets the greeter to use Random " -#~ "Theme mode." - -#~ msgid "GraphicalThemeDir" -#~ msgstr "GraphicalThemeDir" - -#~ msgid "GraphicalThemeDir=<share>/gdm/themes/" -#~ msgstr "GraphicalThemeDir=<share>/gdm/themes/" - -#~ msgid "The directory where themes for the Themed Greeter are installed." -#~ msgstr "The directory where themes for the Themed Greeter are installed." - -#~ msgid "GraphicalThemedColor" -#~ msgstr "GraphicalThemedColor" - -#~ msgid "GraphicalThemedColor=#76848F" -#~ msgstr "GraphicalThemedColor=#76848F" - -#~ msgid "" -#~ "Use this color in the background of the Themed Greeter. This only affects " -#~ "the Themed Greeter." -#~ msgstr "" -#~ "Use this colour in the background of the Themed Greeter. This only " -#~ "affects the Themed Greeter." - -#~ msgid "InfoMsgFile" -#~ msgstr "InfoMsgFile" - -#~ msgid "InfoMsgFile=/path/to/infofile" -#~ msgstr "InfoMsgFile=/path/to/infofile" - -#~ msgid "" -#~ "If present and /path/to/infofile specifies an existing and readable text " -#~ "file (e.g. <etc>/infomsg.txt) the contents of the file will be " -#~ "displayed in a modal dialog box before the user is allowed to login. This " -#~ "works both with the standard and the themable greeters." -#~ msgstr "" -#~ "If present and /path/to/infofile specifies an existing and readable text " -#~ "file (e.g. <etc>/infomsg.txt) the contents of the file will be " -#~ "displayed in a modal dialogue box before the user is allowed to login. " -#~ "This works both with the standard and the themable greeters." - -#~ msgid "InfoMsgFont" -#~ msgstr "InfoMsgFont" - -#~ msgid "InfoMsgFont=fontspec" -#~ msgstr "InfoMsgFont=fontspec" - -#~ msgid "" -#~ "If present and InfoMsgFile (see above) is used, this specifies the font " -#~ "to use when displaying the contents of the InfoMsgFile text file. For " -#~ "example fontspec could be Sans 24 to get a sans serif font of size 24 " -#~ "points. This works both with the standard and the themable greeters." -#~ msgstr "" -#~ "If present and InfoMsgFile (see above) is used, this specifies the font " -#~ "to use when displaying the contents of the InfoMsgFile text file. For " -#~ "example fontspec could be Sans 24 to get a sans serif font of size 24 " -#~ "points. This works both with the standard and the themable greeters." - -#~ msgid "LocaleFile" -#~ msgstr "LocaleFile" - -#~ msgid "LocaleFile=<etc>/gdm/locale.alias" -#~ msgstr "LocaleFile=<etc>/gdm/locale.alias" - -#~ msgid "" -#~ "File in format similar to the GNU locale format with entries for all " -#~ "supported languages on the system. The format is described above or in a " -#~ "comment inside that file." -#~ msgstr "" -#~ "File in format similar to the GNU locale format with entries for all " -#~ "supported languages on the system. The format is described above or in a " -#~ "comment inside that file." - -#~ msgid "LockPosition" -#~ msgstr "LockPosition" - -#~ msgid "LockPosition=true" -#~ msgstr "LockPosition=true" - -#~ msgid "" -#~ "If true the position of the login window of the GTK+ Greeter cannot be " -#~ "changed even if the title bar is turned on." -#~ msgstr "" -#~ "If true the position of the login window of the GTK+ Greeter cannot be " -#~ "changed even if the title bar is turned on." - -#~ msgid "Logo" -#~ msgstr "Logo" - -#~ msgid "Logo=<share>/pixmaps/gnome-logo-large.png" -#~ msgstr "Logo=<share>/pixmaps/gnome-logo-large.png" - -#~ msgid "" -#~ "Image file to display in the logo box. The file must be in a gdk-pixbuf " -#~ "supported format and it must be readable by the GDM user. If no file is " -#~ "specified the logo feature is disabled. This only affects the GTK+ " -#~ "Greeter." -#~ msgstr "" -#~ "Image file to display in the logo box. The file must be in a gdk-pixbuf " -#~ "supported format and it must be readable by the GDM user. If no file is " -#~ "specified the logo feature is disabled. This only affects the GTK+ " -#~ "Greeter." - -#~ msgid "ChooserButtonLogo" -#~ msgstr "ChooserButtonLogo" - -#~ msgid "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" -#~ msgstr "ChooserButtonLogo=<share>/pixmaps/gnome-logo-large.png" - -#~ msgid "" -#~ "Image file to display in the file chooser button in <command>gdmsetup</" -#~ "command>. This key is modified by <command>gdmsetup</command> and should " -#~ "not be manually modified by the user. This only affects the Login Window " -#~ "Preferences (<command>gdmsetup</command>)." -#~ msgstr "" -#~ "Image file to display in the file chooser button in <command>gdmsetup</" -#~ "command>. This key is modified by <command>gdmsetup</command> and should " -#~ "not be manually modified by the user. This only affects the login window " -#~ "preferences (<command>gdmsetup</command>)." - -#~ msgid "MinimalUID" -#~ msgstr "MinimalUID" - -#~ msgid "MinimalUID=100" -#~ msgstr "MinimalUID=100" - -#~ msgid "" -#~ "The minimal UID that GDM should consider a user. All users with a lower " -#~ "UID will be excluded from the face browser. See also <filename>Include</" -#~ "filename>, <filename>Exclude</filename>, and <filename>IncludeAll</" -#~ "filename>." -#~ msgstr "" -#~ "The minimal UID that GDM should consider a user. All users with a lower " -#~ "UID will be excluded from the face browser. See also <filename>Include</" -#~ "filename>, <filename>Exclude</filename>, and <filename>IncludeAll</" -#~ "filename>." - -#~ msgid "PositionX" -#~ msgstr "PositionX" - -#~ msgid "PositionX=200" -#~ msgstr "PositionX=200" - -#~ msgid "The horizontal position of the login window of the GTK+ Greeter." -#~ msgstr "The horizontal position of the login window of the GTK+ Greeter." - -#~ msgid "PositionY" -#~ msgstr "PositionY" - -#~ msgid "PositionY=100" -#~ msgstr "PositionY=100" - -#~ msgid "The vertical position of the login window of the GTK+ Greeter." -#~ msgstr "The vertical position of the login window of the GTK+ Greeter." - -#~ msgid "Quiver" -#~ msgstr "Quiver" - -#~ msgid "Quiver=true" -#~ msgstr "Quiver=true" - -#~ msgid "" -#~ "Controls whether <command>gdmlogin</command> should shake the display " -#~ "when an incorrect username/password is entered. This only affects the GTK" -#~ "+ Greeter." -#~ msgstr "" -#~ "Controls whether <command>gdmlogin</command> should shake the display " -#~ "when an incorrect username/password is entered. This only affects the GTK" -#~ "+ Greeter." - -#~ msgid "DefaultRemoteWelcome" -#~ msgstr "DefaultRemoteWelcome" - -#~ msgid "DefaultRemoteWelcome=true" -#~ msgstr "DefaultRemoteWelcome=true" - -#~ msgid "" -#~ "If set to true, the value \"Welcome to %n\" is used for the " -#~ "<filename>RemoteWelcome</filename>. This value is translated into the " -#~ "appropriate language for the user. If set to false, the " -#~ "<filename>RemoteWelcome</filename> setting is used. This string can use " -#~ "the same special character sequences as explained in the \"Text Node\" " -#~ "section of the \"Themed Greeter\" chapter. This explains the meaning of " -#~ "\"%n\"." -#~ msgstr "" -#~ "If set to true, the value \"Welcome to %n\" is used for the " -#~ "<filename>RemoteWelcome</filename>. This value is translated into the " -#~ "appropriate language for the user. If set to false, the " -#~ "<filename>RemoteWelcome</filename> setting is used. This string can use " -#~ "the same special character sequences as explained in the \"Text Node\" " -#~ "section of the \"Themed Greeter\" chapter. This explains the meaning of " -#~ "\"%n\"." - -#~ msgid "RemoteWelcome" -#~ msgstr "RemoteWelcome" - -#~ msgid "RemoteWelcome=Welcome to %n" -#~ msgstr "RemoteWelcome=Welcome to %n" - -#~ msgid "" -#~ "Controls which text to display next to the logo image in the greeter for " -#~ "remote XDMCP sessions. The same expansion is done here as in the " -#~ "<filename>Welcome</filename> string. This string can use the same special " -#~ "character sequences as explained in the \"Text Node\" section of the " -#~ "\"Themed Greeter\" chapter. chapter." -#~ msgstr "" -#~ "Controls which text to display next to the logo image in the greeter for " -#~ "remote XDMCP sessions. The same expansion is done here as in the " -#~ "<filename>Welcome</filename> string. This string can use the same special " -#~ "character sequences as explained in the \"Text Node\" section of the " -#~ "\"Themed Greeter\" chapter. chapter." - -#~ msgid "RunBackgroundProgramAlways" -#~ msgstr "RunBackgroundProgramAlways" - -#~ msgid "RunBackgroundProgramAlways=false" -#~ msgstr "RunBackgroundProgramAlways=false" - -#~ msgid "" -#~ "If this is true then the background application is run always, otherwise " -#~ "it is only run when the <filename>BackgroundType</filename> is 0 (None) " -#~ "This only affects the GTK+ Greeter." -#~ msgstr "" -#~ "If this is true then the background application is run always, otherwise " -#~ "it is only run when the <filename>BackgroundType</filename> is 0 (None) " -#~ "This only affects the GTK+ Greeter." - -#~ msgid "SetPosition" -#~ msgstr "SetPosition" - -#~ msgid "SetPosition=true" -#~ msgstr "SetPosition=true" - -#~ msgid "" -#~ "If true the position of the login window of the GTK+ Greeter is " -#~ "determined by <filename>PositionX</filename> / <filename>PositionY</" -#~ "filename>." -#~ msgstr "" -#~ "If true the position of the login window of the GTK+ Greeter is " -#~ "determined by <filename>PositionX</filename> / <filename>PositionY</" -#~ "filename>." - -#~ msgid "ShowGnomeFailsafeSession" -#~ msgstr "ShowGnomeFailsafeSession" - -#~ msgid "ShowGnomeFailsafeSession=true" -#~ msgstr "ShowGnomeFailsafeSession=true" - -#~ msgid "" -#~ "Should the greeter show the Gnome Failsafe session in th sessions list." -#~ msgstr "" -#~ "Should the greeter show the Gnome Failsafe session in th sessions list." - -#~ msgid "ShowLastSession" -#~ msgstr "ShowLastSession" - -#~ msgid "ShowLastSession=true" -#~ msgstr "ShowLastSession=true" - -#~ msgid "" -#~ "Should the greeter show the 'Last' session in the session list. If this " -#~ "is off, then GDM is in the so called 'switchdesk' mode which for example " -#~ "Red Hat uses. That is, the users can't pick the last session and will " -#~ "just then get the default session (see <filename>DefaultSession</" -#~ "filename>) unless then pick something else for this session only. So if " -#~ "this is off, this really circumvents saving of the last session." -#~ msgstr "" -#~ "Should the greeter show the 'Last' session in the session list. If this " -#~ "is off, then GDM is in the so called 'switchdesk' mode which, for " -#~ "example, Red Hat uses. That is, the users can't pick the last session and " -#~ "will just then get the default session (see <filename>DefaultSession</" -#~ "filename>) unless then pick something else for this session only. So if " -#~ "this is off, this really circumvents saving of the last session." - -#~ msgid "ShowXtermFailsafeSession" -#~ msgstr "ShowXtermFailsafeSession" - -#~ msgid "ShowXtermFailsafeSession=true" -#~ msgstr "ShowXtermFailsafeSession=true" - -#~ msgid "" -#~ "Should the greeter show the Xterm Failsafe session in the sessions list." -#~ msgstr "" -#~ "Should the greeter show the Xterm Failsafe session in the sessions list." - -#~ msgid "SoundOnLogin" -#~ msgstr "SoundOnLogin" - -#~ msgid "SoundOnLogin=true" -#~ msgstr "SoundOnLogin=true" - -#~ msgid "" -#~ "If true, the greeter will play a sound or beep when it is ready for a " -#~ "login. See also the <filename>SoundOnLoginFile</filename> key. Supported " -#~ "since 2.5.90.0." -#~ msgstr "" -#~ "If true, the greeter will play a sound or beep when it is ready for a " -#~ "login. See also the <filename>SoundOnLoginFile</filename> key. Supported " -#~ "since 2.5.90.0." - -#~ msgid "SoundOnLoginSuccess" -#~ msgstr "SoundOnLoginSuccess" - -#~ msgid "SoundOnLoginSuccess=true" -#~ msgstr "SoundOnLoginSuccess=true" - -#~ msgid "" -#~ "If true, the greeter will play a sound after a successful login attempt. " -#~ "See also the <filename>SoundOnLoginSuccessFile</filename> key." -#~ msgstr "" -#~ "If true, the greeter will play a sound after a successful login attempt. " -#~ "See also the <filename>SoundOnLoginSuccessFile</filename> key." - -#~ msgid "SoundOnLoginFailure" -#~ msgstr "SoundOnLoginFailure" - -#~ msgid "SoundOnLoginFailure=true" -#~ msgstr "SoundOnLoginFailure=true" - -#~ msgid "" -#~ "If true, the greeter will play a sound after a failed login attempt. See " -#~ "also the <filename>SoundOnLoginFailureFile</filename> key." -#~ msgstr "" -#~ "If true, the greeter will play a sound after a failed login attempt. See " -#~ "also the <filename>SoundOnLoginFailureFile</filename> key." - -#~ msgid "SoundOnLoginFile" -#~ msgstr "SoundOnLoginFile" - -#~ msgid "SoundOnLoginFile=/path/to/sound.wav" -#~ msgstr "SoundOnLoginFile=/path/to/sound.wav" - -#~ msgid "" -#~ "The file that will be played using the specified sound application (by " -#~ "default that is <filename>/usr/bin/play</filename>) instead of a beep " -#~ "when the greeter is ready for a login. See also the " -#~ "<filename>SoundOnLogin</filename> key and the <filename>SoundProgram</" -#~ "filename> key. Supported since 2.5.90.0." -#~ msgstr "" -#~ "The file that will be played using the specified sound application (by " -#~ "default that is <filename>/usr/bin/play</filename>) instead of a beep " -#~ "when the greeter is ready for a login. See also the " -#~ "<filename>SoundOnLogin</filename> key and the <filename>SoundProgram</" -#~ "filename> key. Supported since 2.5.90.0." - -#~ msgid "SoundOnLoginSuccessFile" -#~ msgstr "SoundOnLoginSuccessFile" - -#~ msgid "SoundOnLoginSuccessFile=/path/to/sound.wav" -#~ msgstr "SoundOnLoginSuccessFile=/path/to/sound.wav" - -#~ msgid "" -#~ "The file that will be played using the specified sound application (by " -#~ "default that is <filename>/usr/bin/play</filename>) after a successful " -#~ "login attempt. See also the <filename>SoundOnLoginSuccess</filename> key " -#~ "and the <filename>SoundProgram</filename> key." -#~ msgstr "" -#~ "The file that will be played using the specified sound application (by " -#~ "default that is <filename>/usr/bin/play</filename>) after a successful " -#~ "login attempt. See also the <filename>SoundOnLoginSuccess</filename> key " -#~ "and the <filename>SoundProgram</filename> key." - -#~ msgid "SoundOnLoginFailureFile" -#~ msgstr "SoundOnLoginFailureFile" - -#~ msgid "SoundOnLoginFailureFile=/path/to/sound.wav" -#~ msgstr "SoundOnLoginFailureFile=/path/to/sound.wav" - -#~ msgid "" -#~ "The file that will be played using the specified sound application (by " -#~ "default that is <filename>/usr/bin/play</filename>) after a failed login " -#~ "attempt. See also the <filename>SoundOnLoginFailure</filename> key and " -#~ "the <filename>SoundProgram</filename> key." -#~ msgstr "" -#~ "The file that will be played using the specified sound application (by " -#~ "default that is <filename>/usr/bin/play</filename>) after a failed login " -#~ "attempt. See also the <filename>SoundOnLoginFailure</filename> key and " -#~ "the <filename>SoundProgram</filename> key." - -#~ msgid "SystemMenu" -#~ msgstr "SystemMenu" - -#~ msgid "SystemMenu=true" -#~ msgstr "SystemMenu=true" - -#~ msgid "" -#~ "Turns the Actions menu (which used to be called System menu) on or off. " -#~ "If this is off then one of the actions will be available anywhere. These " -#~ "actions include Shutdown, Restart, Configure, XDMCP chooser and such. All " -#~ "of those can however be turned off individually. Shutdown, Restart and " -#~ "Suspend can be turned off by just setting the corresponding keys to " -#~ "empty. Note that the actions menu is only shown on local logins as it " -#~ "would not be safe or even desirable on remote logins, so you don't have " -#~ "to worry about remote users having any sort of console privileges." -#~ msgstr "" -#~ "Turns the Actions menu (which used to be called System menu) on or off. " -#~ "If this is off then one of the actions will be available anywhere. These " -#~ "actions include Shutdown, Restart, Configure, XDMCP chooser etc. All of " -#~ "those can be turned off individually. Shutdown, Restart and Suspend can " -#~ "be turned off by just setting the corresponding keys to empty. Note that " -#~ "the actions menu is only shown on local logins as it would not be safe or " -#~ "even desirable on remote logins, so you don't have to worry about remote " -#~ "users having any sort of console privileges." - -#~ msgid "" -#~ "Note that if this is off none of the actions will be available even if a " -#~ "theme for a graphical greeter mistakenly shows them. Also note that " -#~ "sometimes a graphical theme may not show all the available actions as " -#~ "buttons and you may have to press F10 to see the menu." -#~ msgstr "" -#~ "Note that if this is off none of the actions will be available even if a " -#~ "theme for a graphical greeter mistakenly shows them. Also note that " -#~ "sometimes a graphical theme may not show all the available actions as " -#~ "buttons and you may have to press F10 to see the menu." - -#~ msgid "TitleBar" -#~ msgstr "TitleBar" - -#~ msgid "TitleBar=true" -#~ msgstr "TitleBar=true" - -#~ msgid "" -#~ "Display the title bar in the greeter. This only affects the GTK+ Greeter." -#~ msgstr "" -#~ "Display the title bar in the greeter. This only affects the GTK+ Greeter." - -#~ msgid "Use24Clock" -#~ msgstr "Use24Clock" - -#~ msgid "Use24Clock=auto" -#~ msgstr "Use24Clock=auto" - -#~ msgid "" -#~ "Select the use of 24 hour clock. Some locales do not support 12 hour " -#~ "format (like Finnish, that is <filename>fi_FI</filename>), and in those " -#~ "locales this setting has no effect at all." -#~ msgstr "" -#~ "Select the use of 24 hour clock. Some locales do not support 12 hour " -#~ "format (like Finnish, that is <filename>fi_FI</filename>), and in those " -#~ "locales this setting has no effect at all." - -#~ msgid "" -#~ "Possible values are \"auto\" (default), \"true\", and \"false\". If this " -#~ "is set to \"auto\" or left empty, then time format is chosen from locale " -#~ "settings. Locale settings are based on the language in use, thus it is " -#~ "changed by setting environment variables LANGUAGE (GNU extension), LANG, " -#~ "LC_MESSAGES or LC_ALL in the GDM's runtime environment. Priorities " -#~ "between the mentioned environment variables can be found from your " -#~ "system's C library manual." -#~ msgstr "" -#~ "Possible values are \"auto\" (default), \"true\", and \"false\". If this " -#~ "is set to \"auto\" or left empty, then time format is chosen from locale " -#~ "settings. Locale settings are based on the language in use, thus it is " -#~ "changed by setting environment variables LANGUAGE (GNU extension), LANG, " -#~ "LC_MESSAGES or LC_ALL in the GDM's runtime environment. Priorities " -#~ "between the mentioned environment variables can be found from your " -#~ "system's C library manual." - -#~ msgid "UseCirclesInEntry" -#~ msgstr "UseCirclesInEntry" - -#~ msgid "UseCirclesInEntry=false" -#~ msgstr "UseCirclesInEntry=false" - -#~ msgid "" -#~ "Use circles instead of asterisks in the password entry. This may not work " -#~ "with all fonts however." -#~ msgstr "" -#~ "Use circles instead of asterisks in the password entry. This may not work " -#~ "with all fonts however." - -#~ msgid "UseInvisibleInEntry" -#~ msgstr "UseInvisibleInEntry" - -#~ msgid "UseInvisibleInEntry=false" -#~ msgstr "UseInvisibleInEntry=false" - -#~ msgid "" -#~ "Do not show any visual feedback is the password entry. This is the " -#~ "standard in console and xdm. Settings this option discards the " -#~ "<filename>UseCirclesInEntry</filename> option." -#~ msgstr "" -#~ "Do not show any visual feedback is the password entry. This is the " -#~ "standard in console and xdm. Settings this option discards the " -#~ "<filename>UseCirclesInEntry</filename> option." - -#~ msgid "DefaultWelcome" -#~ msgstr "DefaultWelcome" - -#~ msgid "DefaultWelcome=true" -#~ msgstr "DefaultWelcome=true" - -#~ msgid "" -#~ "If set to true, the value \"Welcome\" is used for the <filename>Welcome</" -#~ "filename>. This value is translated into the appropriate language for the " -#~ "user. If set to false, the <filename>Welcome</filename> setting is used." -#~ msgstr "" -#~ "If set to true, the value \"Welcome\" is used for the <filename>Welcome</" -#~ "filename>. This value is translated into the appropriate language for the " -#~ "user. If set to false, the <filename>Welcome</filename> setting is used." - -#~ msgid "Welcome" -#~ msgstr "Welcome" - -#~ msgid "Welcome=Welcome" -#~ msgstr "Welcome=Welcome" - -#~ msgid "" -#~ "Controls which text to display next to the logo image in the standard " -#~ "greeter. The following control chars are supported:" -#~ msgstr "" -#~ "Controls which text to display next to the logo image in the standard " -#~ "greeter. The following control chars are supported:" - -#~ msgid "%d — display's hostname" -#~ msgstr "%d — display's hostname" - -#~ msgid "%h — Fully qualified hostname" -#~ msgstr "%h — Fully qualified hostname" - -#~ msgid "%m — machine (processor type)" -#~ msgstr "%m — machine (processor type)" - -#~ msgid "%n — Nodename (i.e. hostname without .domain)" -#~ msgstr "%n — Nodename (i.e. hostname without .domain)" - -#~ msgid "%r — release (OS version)" -#~ msgstr "%r — release (OS version)" - -#~ msgid "%s — sysname (i.e. OS)" -#~ msgstr "%s — sysname (i.e. OS)" - -#~ msgid "" -#~ "This string is only used for local logins. For remote XDMCP logins we use " -#~ "<filename>RemoteWelcome</filename>." -#~ msgstr "" -#~ "This string is only used for local logins. For remote XDMCP logins we use " -#~ "<filename>RemoteWelcome</filename>." - -#~ msgid "" -#~ "In the Themed Greeter the location of this text depends on the theme. " -#~ "Unless the theme uses the stock welcome string somewhere this string will " -#~ "not be displayed at all." -#~ msgstr "" -#~ "In the Themed Greeter the location of this text depends on the theme. " -#~ "Unless the theme uses the stock welcome string somewhere this string will " -#~ "not be displayed at all." - -#~ msgid "XineramaScreen" -#~ msgstr "XineramaScreen" - -#~ msgid "XineramaScreen=0" -#~ msgstr "XineramaScreen=0" - -#~ msgid "" -#~ "If the Xinerama extension is active the login window will be centered on " -#~ "this physical screen (use 0 for the first screen, 1 for the second...)." -#~ msgstr "" -#~ "If the Xinerama extension is active the login window will be centered on " -#~ "this physical screen (use 0 for the first screen, 1 for the second...)." - -#~ msgid "XDCMP Chooser Options" -#~ msgstr "XDCMP Chooser Options" - -#~ msgid "AllowAdd" -#~ msgstr "AllowAdd" - -#~ msgid "AllowAdd=true" -#~ msgstr "AllowAdd=true" - -#~ msgid "" -#~ "If true, allow the user to add arbitrary hosts to the chooser. This way " -#~ "the user could connect to any host that responds to XDMCP queries from " -#~ "the chooser." -#~ msgstr "" -#~ "If true, allow the user to add arbitrary hosts to the chooser. This way " -#~ "the user could connect to any host that responds to XDMCP queries from " -#~ "the chooser." - -#~ msgid "Broadcast" -#~ msgstr "Broadcast" - -#~ msgid "Broadcast=true" -#~ msgstr "Broadcast=true" - -#~ msgid "" -#~ "If true, the chooser will broadcast a query to the local network and " -#~ "collect responses. This way the chooser will always show all available " -#~ "managers on the network. If you need to add some hosts not local to this " -#~ "network, or if you don't want to use a broadcast, you can list them " -#~ "explicitly in the <filename>Hosts</filename> key." -#~ msgstr "" -#~ "If true, the chooser will broadcast a query to the local network and " -#~ "collect responses. This way the chooser will always show all available " -#~ "managers on the network. If you need to add some hosts not local to this " -#~ "network, or if you don't want to use a broadcast, you can list them " -#~ "explicitly in the <filename>Hosts</filename> key." - -#~ msgid "DefaultHostImage" -#~ msgstr "DefaultHostImage" - -#~ msgid "DefaultHostImage=<share>/pixmaps/nohost.png" -#~ msgstr "DefaultHostImage=<share>/pixmaps/nohost.png" - -#~ msgid "" -#~ "File name for the default host icon. This image will be displayed if no " -#~ "icon is specified for a given host. The file must be in a gdk-pixbuf " -#~ "supported format and it must be readable for the GDM user." -#~ msgstr "" -#~ "File name for the default host icon. This image will be displayed if no " -#~ "icon is specified for a given host. The file must be in a gdk-pixbuf " -#~ "supported format and it must be readable for the GDM user." - -#~ msgid "HostImageDir" -#~ msgstr "HostImageDir" - -#~ msgid "HostImageDir=<share>/hosts" -#~ msgstr "HostImageDir=<share>/hosts" - -#~ msgid "" -#~ "Repository for host icon files. The sysadmin can place icons for remote " -#~ "hosts here and they will appear in <filename>gdmchooser</filename>." -#~ msgstr "" -#~ "Repository for host icon files. The sysadmin can place icons for remote " -#~ "hosts here and they will appear in <filename>gdmchooser</filename>." - -#~ msgid "" -#~ "The file name must match the fully qualified name (FQDN) for the host. " -#~ "The icons must be stored in gdk-pixbuf supported formats and they must be " -#~ "readable to the GDM user." -#~ msgstr "" -#~ "The file name must match the fully qualified name (FQDN) for the host. " -#~ "The icons must be stored in gdk-pixbuf supported formats and they must be " -#~ "readable to the GDM user." - -#~ msgid "Hosts" -#~ msgstr "Hosts" - -#~ msgid "Hosts=host1,host2" -#~ msgstr "Hosts=host1,host2" - -#~ msgid "" -#~ "The hosts which should be listed in the chooser. The chooser will only " -#~ "list them if they respond. This is done in addition to broadcast (if " -#~ "<filename>Broadcast</filename> is set), so you need not list hosts on the " -#~ "local network. This is useful if your networking setup doesn't allow all " -#~ "hosts to be reachable by a broadcast packet." -#~ msgstr "" -#~ "The hosts which should be listed in the chooser. The chooser will only " -#~ "list them if they respond. This is done in addition to broadcast (if " -#~ "<filename>Broadcast</filename> is set), so you need not list hosts on the " -#~ "local network. This is useful if your networking setup doesn't allow all " -#~ "hosts to be reachable by a broadcast packet." - -#~ msgid "ScanTime" -#~ msgstr "ScanTime" - -#~ msgid "ScanTime=4" -#~ msgstr "ScanTime=4" - -#~ msgid "" -#~ "Specifies how many seconds the chooser should wait for replies to its " -#~ "BROADCAST_QUERY. Really this is only the time in which we expect a reply. " -#~ "We will still add hosts to the list even if they reply after this time." -#~ msgstr "" -#~ "Specifies how many seconds the chooser should wait for replies to its " -#~ "BROADCAST_QUERY. Really this is only the time in which we expect a reply. " -#~ "We will still add hosts to the list even if they reply after this time." - -#~ msgid "Debug Configuration" -#~ msgstr "Debug Configuration" - -#~ msgid "[debug]" -#~ msgstr "[debug]" - -#~ msgid "" -#~ "Setting to true sends debug ouput to the syslog. This can be useful for " -#~ "tracking down problems with GDM. This output tends to be verbose so " -#~ "should not be turned on for general use." -#~ msgstr "" -#~ "Setting to true sends debug ouput to the syslog. This can be useful for " -#~ "tracking down problems with GDM. This output tends to be verbose so " -#~ "should not be turned on for general use." - -#~ msgid "Gestures" -#~ msgstr "Gestures" - -#~ msgid "Gestures=false" -#~ msgstr "Gestures=false" - -#~ msgid "" -#~ "Setting to true sends debug ouput concerning the accessibility gesture " -#~ "listeners to the syslog. This can be useful for tracking down problems " -#~ "with them not working properly. This output tends to be verbose so should " -#~ "not be turned on for general use." -#~ msgstr "" -#~ "Setting to true sends debug ouput concerning the accessibility gesture " -#~ "listeners to the syslog. This can be useful for tracking down problems " -#~ "with them not working properly. This output tends to be verbose so should " -#~ "not be turned on for general use." - -#~ msgid "Custom Commands" -#~ msgstr "Custom Commands" - -#~ msgid "" -#~ "You can create up to 10 different commands. Gaps between command numbers " -#~ "are allowed and their relative positioning within the section and with " -#~ "respect to each other is not important as long as they conform to the " -#~ "permitted range of [0-9]." -#~ msgstr "" -#~ "You can create up to 10 different commands. Gaps between command numbers " -#~ "are allowed and their relative positioning within the section and with " -#~ "respect to each other is not important as long as they conform to the " -#~ "permitted range of [0-9]." - -#~ msgid "[customcommand]" -#~ msgstr "[customcommand]" - -#~ msgid "CustomCommand[0-9]" -#~ msgstr "CustomCommand[0-9]" - -#~ msgid "CustomCommand[0-9]=" -#~ msgstr "CustomCommand[0-9]=" - -#~ msgid "" -#~ "Full path and arguments to command to be executed when user selects " -#~ "<filename>n-th</filename> \"Custom Command\" from the Actions menu. This " -#~ "can be a ';' separated list of commands to try. If the value is empty or " -#~ "missing, then the custom command is not available. By default this value " -#~ "is not enabled, so to enable \"Custom Command\" it must be set to a " -#~ "nonempty value. [0-9] represents the <filename>CustomCommand</filename> " -#~ "suffix and can be an integer between 0 and 9." -#~ msgstr "" -#~ "Full path and arguments to command to be executed when user selects the " -#~ "<filename>n-th</filename> \"Custom Command\" from the Actions menu. This " -#~ "can be a ';' separated list of commands to try. If the value is empty or " -#~ "missing, then the custom command is not available. By default this value " -#~ "is not enabled, so to enable \"Custom Command\" it must be set to a " -#~ "nonempty value. [0-9] represents the <filename>CustomCommand</filename> " -#~ "suffix and can be an integer between 0 and 9." - -#~ msgid "CustomCommandIsPersistent[0-9]" -#~ msgstr "CustomCommandIsPersistent[0-9]" - -#~ msgid "CustomCommandIsPersistent[0-9]=" -#~ msgstr "CustomCommandIsPersistent[0-9]=" - -#~ msgid "" -#~ "Specifies if <filename>n-th</filename> \"Custom Command\" will appear " -#~ "outside the login manager, for example on the desktop through the Log Out/" -#~ "Shut Down dialogs. If not specified the default value is \"false\". This " -#~ "option is only valid if corresponding <filename>CustomCommand</filename> " -#~ "is defined. [0-9] represents <filename>CustomCommand</filename> suffix " -#~ "and can be an integer between 0 and 9." -#~ msgstr "" -#~ "Specifies if the <filename>n-th</filename> \"Custom Command\" will appear " -#~ "outside the login manager, for example on the desktop through the Log Out/" -#~ "Shut Down dialogues. If not specified the default value is \"false\". " -#~ "This option is only valid if corresponding <filename>CustomCommand</" -#~ "filename> is defined. [0-9] represents <filename>CustomCommand</filename> " -#~ "suffix and can be an integer between 0 and 9." - -#~ msgid "CustomCommandLabel[0-9]" -#~ msgstr "CustomCommandLabel[0-9]" - -#~ msgid "CustomCommandLabel[0-9]=" -#~ msgstr "CustomCommandLabel[0-9]=" - -#~ msgid "" -#~ "Specifies the stock label that will be displayed on the <filename>n-th</" -#~ "filename> \"Custom Command\" buttons and menu items. If not specified the " -#~ "default value is \"Custom_[0-9]\". This option is only valid if " -#~ "corresponding <filename>CustomCommand</filename> is defined. [0-9] " -#~ "represents <filename>CustomCommand</filename> suffix and can be an " -#~ "integer between 0 and 9. This option can't contain any semicolon " -#~ "characters (i.e. \";\")." -#~ msgstr "" -#~ "Specifies the stock label that will be displayed on the <filename>n-th</" -#~ "filename> \"Custom Command\" buttons and menu items. If not specified the " -#~ "default value is \"Custom_[0-9]\". This option is only valid if the " -#~ "corresponding <filename>CustomCommand</filename> is defined. [0-9] " -#~ "represents the <filename>CustomCommand</filename> suffix and can be an " -#~ "integer between 0 and 9. This option can't contain any semicolon " -#~ "characters (i.e. \";\")." - -#~ msgid "CustomCommandLRLabel[0-9]" -#~ msgstr "CustomCommandLRLabel[0-9]" - -#~ msgid "CustomCommandLRLabel[0-9]=" -#~ msgstr "CustomCommandLRLabel[0-9]=" - -#~ msgid "" -#~ "Specifies the stock label that will be displayed on the <filename>n-th</" -#~ "filename> \"Custom Command\" list items and radio buttons. If not " -#~ "specified the default value is \"Execute custom command _[0-9]\". This " -#~ "option is only valid if corresponding <filename>CustomCommand</filename> " -#~ "is defined. [0-9] represents <filename>CustomCommand</filename> suffix " -#~ "and can be an integer between 0 and 9." -#~ msgstr "" -#~ "Specifies the stock label that will be displayed on the <filename>n-th</" -#~ "filename> \"Custom Command\" list items and radio buttons. If not " -#~ "specified the default value is \"Execute custom command _[0-9]\". This " -#~ "option is only valid if the corresponding <filename>CustomCommand</" -#~ "filename> is defined. [0-9] represents the <filename>CustomCommand</" -#~ "filename> suffix and can be an integer between 0 and 9." - -#~ msgid "CustomCommandNoRestart[0-9]" -#~ msgstr "CustomCommandNoRestart[0-9]" - -#~ msgid "CustomCommandNoRestart[0-9]=" -#~ msgstr "CustomCommandNoRestart[0-9]=" - -#~ msgid "" -#~ "Specifies if gdm will be stopped/restarted once <filename>n-th</filename> " -#~ "\"Custom Command\" has been executed. If not specified the default value " -#~ "is \"false\". This option is only valid if corresponding " -#~ "<filename>CustomCommand</filename> is defined. [0-9] represents " -#~ "<filename>CustomCommand</filename> suffix and can be an integer between 0 " -#~ "and 9. In addition when corresponding " -#~ "<filename>CustomCommandIsPersistent</filename> is set to true, setting " -#~ "CustomCommandNoRestart to false will place corresponding " -#~ "<filename>CustomCommand</filename> in the Shut Down dialog set of " -#~ "actions, setting it to true will place corresponding " -#~ "<filename>CustomCommand</filename> in the Log Out dialog set of actions." -#~ msgstr "" -#~ "Specifies if gdm will be stopped/restarted once the <filename>n-th</" -#~ "filename> \"Custom Command\" has been executed. If not specified the " -#~ "default value is \"false\". This option is only valid if the " -#~ "corresponding <filename>CustomCommand</filename> is defined. [0-9] " -#~ "represents the <filename>CustomCommand</filename> suffix and can be an " -#~ "integer between 0 and 9. When the corresponding " -#~ "<filename>CustomCommandIsPersistent</filename> is set to true, setting " -#~ "CustomCommandNoRestart to false will place the corresponding " -#~ "<filename>CustomCommand</filename> in the Shut Down dialogue set of " -#~ "actions. Setting it to true will place the corresponding " -#~ "<filename>CustomCommand</filename> in the Log Out dialogue set of actions." - -#~ msgid "CustomCommandText[0-9]" -#~ msgstr "CustomCommandText[0-9]" - -#~ msgid "CustomCommandText[0-9]=" -#~ msgstr "CustomCommandText[0-9]=" - -#~ msgid "" -#~ "Specifies the message that will be displayed on the warning dialog box " -#~ "once <filename>n-th</filename> \"Custom Command\" button/menu item/radio " -#~ "button/list item has been activated. If not specified the default value " -#~ "is \"Are you sure?\". This option is only valid if corresponding " -#~ "<filename>CustomCommand</filename> is defined. [0-9] represents " -#~ "<filename>CustomCommand</filename> suffix and can be an integer between 0 " -#~ "and 9." -#~ msgstr "" -#~ "Specifies the message that will be displayed on the warning dialogue box " -#~ "once the <filename>n-th</filename> \"Custom Command\" button/menu item/" -#~ "radio button/list item has been activated. If not specified the default " -#~ "value is \"Are you sure?\". This option is only valid if the " -#~ "corresponding <filename>CustomCommand</filename> is defined. [0-9] " -#~ "represents the <filename>CustomCommand</filename> suffix and can be an " -#~ "integer between 0 and 9." - -#~ msgid "CustomCommandTooltip[0-9]" -#~ msgstr "CustomCommandTooltip[0-9]" - -#~ msgid "CustomCommandTooltip[0-9]=" -#~ msgstr "CustomCommandTooltip[0-9]=" - -#~ msgid "" -#~ "Specifies the message that will be displayed on tooltips for <filename>n-" -#~ "th</filename> \"Custom Command\" entries. If not specified the default " -#~ "value is \"Execute custom command [0-9]\". This option is only valid if " -#~ "corresponding <filename>CustomCommand</filename> is defined. [0-9] " -#~ "represents <filename>CustomCommand</filename> suffix and can be an " -#~ "integer between 0 and 9." -#~ msgstr "" -#~ "Specifies the message that will be displayed on tooltips for <filename>n-" -#~ "th</filename> \"Custom Command\" entries. If not specified the default " -#~ "value is \"Execute custom command [0-9]\". This option is only valid if " -#~ "corresponding <filename>CustomCommand</filename> is defined. [0-9] " -#~ "represents <filename>CustomCommand</filename> suffix and can be an " -#~ "integer between 0 and 9." - -#~ msgid "X Server Definitions" -#~ msgstr "X Server Definitions" - -#~ msgid "" -#~ "To set up X servers, you need to provide GDM with information about the " -#~ "installed X servers. You can have as many different definitions as you " -#~ "wish, each identified with a unique name. The name <filename>Standard</" -#~ "filename> is required. If you do not specify this server, GDM will assume " -#~ "default values for a 'Standard' server and the path given by " -#~ "<filename>daemon/StandardXServer</filename>. <filename>Standard</" -#~ "filename> is used as the default, in situations when no other server has " -#~ "been defined." -#~ msgstr "" -#~ "To set up X servers, you need to provide GDM with information about the " -#~ "installed X servers. You can have as many different definitions as you " -#~ "wish, each identified with a unique name. The name <filename>Standard</" -#~ "filename> is required. If you do not specify this server, GDM will assume " -#~ "default values for a 'Standard' server and the path given by " -#~ "<filename>daemon/StandardXServer</filename>. <filename>Standard</" -#~ "filename> is used as the default, in situations when no other server has " -#~ "been defined." - -#~ msgid "" -#~ "Servers are defined by sections named <filename>server-</filename> " -#~ "followed by the identifier of this server. This should be a simple ASCII " -#~ "string with no spaces. The GUI configuration program allows users to edit " -#~ "the servers defined in the GDM configuration files but currently does not " -#~ "allow adding or deleting entries. Like normal configuration options, " -#~ "<filename>server-</filename> sections in the <filename><etc>/gdm/" -#~ "custom.conf</filename> file override values in the <filename><" -#~ "share>/gdm/defaults.conf</filename> file. In other words, if a " -#~ "<filename>server-Standard</filename> section is defined in <filename><" -#~ "etc>/gdm/custom.conf</filename>, then that will be used and the " -#~ "section in the <filename><share>/gdm/defaults.conf</filename> file " -#~ "will be ignored." -#~ msgstr "" -#~ "Servers are defined by sections named <filename>server-</filename> " -#~ "followed by the identifier of this server. This should be a simple ASCII " -#~ "string with no spaces. The GUI configuration program allows users to edit " -#~ "the servers defined in the GDM configuration files but currently does not " -#~ "allow adding or deleting entries. Like normal configuration options, " -#~ "<filename>server-</filename> sections in the <filename><etc>/gdm/" -#~ "custom.conf</filename> file override values in the <filename><" -#~ "share>/gdm/defaults.conf</filename> file. In other words, if a " -#~ "<filename>server-Standard</filename> section is defined in <filename><" -#~ "etc>/gdm/custom.conf</filename>, then that will be used and the " -#~ "section in the <filename><share>/gdm/defaults.conf</filename> file " -#~ "will be ignored." - -#~ msgid "[server-Standard]" -#~ msgstr "[server-Standard]" - -#~ msgid "name" -#~ msgstr "name" - -#~ msgid "name=Standard server" -#~ msgstr "name=Standard server" - -#~ msgid "The name that will be displayed to the user." -#~ msgstr "The name that will be displayed to the user." - -#~ msgid "command" -#~ msgstr "command" - -#~ msgid "command=/path/to/X" -#~ msgstr "command=/path/to/X" - -#~ msgid "" -#~ "The command to execute, with full path to the binary of the X server, and " -#~ "any extra arguments needed." -#~ msgstr "" -#~ "The command to execute, with full path to the binary of the X server, and " -#~ "any extra arguments needed." - -#~ msgid "flexible" -#~ msgstr "flexible" - -#~ msgid "flexible=true" -#~ msgstr "flexible=true" - -#~ msgid "" -#~ "Indicates if this server is available as a choice when a user wishes to " -#~ "run a flexible, on demand server." -#~ msgstr "" -#~ "Indicates if this server is available as a choice when a user wishes to " -#~ "run a flexible, on demand server." - -#~ msgid "handled" -#~ msgstr "handled" - -#~ msgid "handled=true" -#~ msgstr "handled=true" - -#~ msgid "" -#~ "Indicates that GDM should run the login window on this server and allow a " -#~ "user to log in. If set to false, then GDM will just run this server and " -#~ "wait for it to terminate. This can be useful to run an X terminal using " -#~ "GDM. When this is done you should normally also add <filename>-terminate</" -#~ "filename> to the command line of the server to make the server terminate " -#~ "after each session. Otherwise the control of the slave will never come " -#~ "back to GDM and, for example, soft restarts won't work. This is because " -#~ "GDM assumes there is a login in progress for the entire time this server " -#~ "is active." -#~ msgstr "" -#~ "Indicates that GDM should run the login window on this server and allow a " -#~ "user to log in. If set to false, then GDM will just run this server and " -#~ "wait for it to terminate. This can be useful to run an X terminal using " -#~ "GDM. When this is done you should normally also add <filename>-terminate</" -#~ "filename> to the command line of the server to make the server terminate " -#~ "after each session. Otherwise the control of the slave will never come " -#~ "back to GDM and, for example, soft restarts won't work. This is because " -#~ "GDM assumes there is a login in progress for the entire time this server " -#~ "is active." - -#~ msgid "chooser" -#~ msgstr "chooser" - -#~ msgid "chooser=false" -#~ msgstr "chooser=false" - -#~ msgid "" -#~ "Indicates that GDM should instead of a login window run a chooser on this " -#~ "window and allow the user to choose which server to log into." -#~ msgstr "" -#~ "Indicates that GDM should run a chooser on this window, instead of a " -#~ "login window, and allow the user to choose which server to log into." - -#~ msgid "Local Static X Display Configuration" -#~ msgstr "Local Static X Display Configuration" - -#~ msgid "" -#~ "The static display configuration specifies what displays should be always " -#~ "managed by GDM. GDM will restart the X server on the display if it dies, " -#~ "for example. There may be as many static displays that are managed as you " -#~ "wish, although typically each display is associated with a real display. " -#~ "For example, if a machine has two displays (say display \":0\" and " -#~ "display \":1\"), then this section can be used to specify that a separate " -#~ "login screen be managed for each screen. Each key in the <filename>" -#~ "[servers]</filename> section corresponds to the display number to be " -#~ "managed. Normally there is only one key, which is the key <filename>0</" -#~ "filename>, which corresponds to the display <filename>:0</filename>." -#~ msgstr "" -#~ "The static display configuration specifies what displays should be always " -#~ "managed by GDM. GDM will restart the X server on the display if it dies, " -#~ "for example. There may be as many static displays that are managed as you " -#~ "wish, although typically each display is associated with a real display. " -#~ "For example, if a machine has two displays (say display \":0\" and " -#~ "display \":1\"), then this section can be used to specify that a separate " -#~ "login screen be managed for each screen. Each key in the <filename>" -#~ "[servers]</filename> section corresponds to the display number to be " -#~ "managed. Normally there is only one key, which is the key <filename>0</" -#~ "filename>, which corresponds to the display <filename>:0</filename>." - -#~ msgid "" -#~ "The GUI configuration program allows users to edit the static display " -#~ "configuration defined in the GDM configuration files and allows the user " -#~ "to add or delete entries. Like normal configuration options, the " -#~ "<filename>[servers]</filename> section in the <filename><etc>/gdm/" -#~ "custom.conf</filename> file overrides values in the <filename><" -#~ "share>/gdm/defaults.conf</filename> file." -#~ msgstr "" -#~ "The GUI configuration program allows users to edit the static display " -#~ "configuration defined in the GDM configuration files and allows the user " -#~ "to add or delete entries. Like normal configuration options, the " -#~ "<filename>[servers]</filename> section in the <filename><etc>/gdm/" -#~ "custom.conf</filename> file overrides values in the <filename><" -#~ "share>/gdm/defaults.conf</filename> file." - -#~ msgid "[servers]" -#~ msgstr "[servers]" - -#~ msgid "<display number>" -#~ msgstr "<display number>" - -#~ msgid "0=Standard" -#~ msgstr "0=Standard" - -#~ msgid "" -#~ "Control section for local displays. Each line indicates the local display " -#~ "number and the command that needs to be run to start the X server(s)." -#~ msgstr "" -#~ "Control section for local displays. Each line indicates the local display " -#~ "number and the command that needs to be run to start the X server(s)." - -#~ msgid "" -#~ "The command can either be a path to an X executable, or a name of one of " -#~ "the server definitions. This can be followed by some arguments that " -#~ "should be passed to the X server when executed. The gdm daemon doesn't " -#~ "enforce the numbers to be in order or for them to be \"packed\". They " -#~ "keyword \"inactive\" can be used instead of a command to specify that the " -#~ "display should be not managed. This can be used in the <filename><" -#~ "etc>/gdm/custom.conf</filename> to turn off a display that is defined " -#~ "in the <filename><share>/gdm/defaults.conf</filename> file." -#~ msgstr "" -#~ "The command can either be a path to an X executable or a name of one of " -#~ "the server definitions. This can be followed by some arguments that " -#~ "should be passed to the X server when executed. The gdm daemon doesn't " -#~ "enforce the numbers to be in order or for them to be \"packed\". They " -#~ "keyword \"inactive\" can be used instead of a command to specify that the " -#~ "display should be not managed. This can be used in the <filename><" -#~ "etc>/gdm/custom.conf</filename> to turn off a display that is defined " -#~ "in the <filename><share>/gdm/defaults.conf</filename> file." - -#~ msgid "" -#~ "GDM will splice \"<filename>-auth <ServAuthDir>/:n.Xauth :n</" -#~ "filename>\", where n is the display number. Inside the command line " -#~ "before all other arguments before running the X server." -#~ msgstr "" -#~ "GDM will splice \"<filename>-auth <ServAuthDir>/:n.Xauth :n</" -#~ "filename>\" (where n is the display number) inside the command line " -#~ "before all other arguments before running the X server." - -#~ msgid "" -#~ "On some systems it is necessary for GDM to know on which virtual consoles " -#~ "to run the X server. In this case, (if running XFree86) add \"vt7\" to " -#~ "the command line, for example, to run on virtual console 7. However on " -#~ "Linux and FreeBSD this is normally done automatically if the " -#~ "<filename>VTAllocation</filename> key is set." -#~ msgstr "" -#~ "On some systems it is necessary for GDM to know on which virtual consoles " -#~ "to run the X server. In this case, (if running XFree86) add \"vt7\" to " -#~ "the command line, for example, to run on virtual console 7. However on " -#~ "Linux and FreeBSD this is normally done automatically if the " -#~ "<filename>VTAllocation</filename> key is set." - -#~ msgid "" -#~ "Normally you do not need to add a <filename>-nolisten tcp</filename> flag " -#~ "as this is added automatically for local X servers when the " -#~ "<filename>DisallowTCP</filename> option is set." -#~ msgstr "" -#~ "Normally you do not need to add a <filename>-nolisten tcp</filename> flag " -#~ "as this is added automatically for local X servers when the " -#~ "<filename>DisallowTCP</filename> option is set." - -#~ msgid "priority" -#~ msgstr "priority" - -#~ msgid "priority=0" -#~ msgstr "priority=0" - -#~ msgid "" -#~ "Indicates that the X server should be started at a different process " -#~ "priority. Values can be any integer value accepted by the setpriority C " -#~ "library function (normally between -20 and 20) with 0 being the default. " -#~ "For highly interactive applications, -5 yields good responsiveness. The " -#~ "default value is 0 and the setpriority function is not called if the " -#~ "value is 0." -#~ msgstr "" -#~ "Indicates that the X server should be started at a different process " -#~ "priority. Values can be any integer value accepted by the setpriority C " -#~ "library function (normally between -20 and 20) with 0 being the default. " -#~ "For highly interactive applications, -5 yields good responsiveness. The " -#~ "default value is 0 and the setpriority function is not called if the " -#~ "value is 0." - -#~ msgid "Per User Configuration" -#~ msgstr "Per User Configuration" - -#~ msgid "" -#~ "There are some per user configuration settings that control how GDM " -#~ "behaves. GDM is picky about the file ownership and permissions of the " -#~ "user files it will access, and will ignore files if they are not owned by " -#~ "the user or files that have group/world write permission. It will also " -#~ "ignore the user if the user's $HOME directory is not owned by the user or " -#~ "if the user's $HOME directory has group/world write permission. files " -#~ "must also be smaller than the <filename>UserMaxFile</filename> value as " -#~ "defined in the GDM configuration. If it seems that GDM is not properly " -#~ "accessing user configuration settings, the problem is most likely caused " -#~ "by one of these checks failing." -#~ msgstr "" -#~ "There are some per user configuration settings that control how GDM " -#~ "behaves. GDM is picky about the file ownership and permissions of the " -#~ "user files it will access, and will ignore files if they are not owned by " -#~ "the user or files that have group/world write permissions. It will also " -#~ "ignore the user if the user's $HOME directory is not owned by the user or " -#~ "if the user's $HOME directory has group/world write permissions. Files " -#~ "must also be smaller than the <filename>UserMaxFile</filename> value as " -#~ "defined in the GDM configuration. If GDM is not properly accessing user " -#~ "configuration settings, the problem is most likely caused by one of these " -#~ "checks failing." - -#~ msgid "" -#~ "Normally GDM will write this file when the user logs in for the first " -#~ "time, and rewrite it if the user chooses to change their default values " -#~ "on a subsequent login." -#~ msgstr "" -#~ "Normally GDM will write this file when the user logs in for the first " -#~ "time, and rewrite it if the user chooses to change their default values " -#~ "on a subsequent login." - -#~ msgid "" -#~ "If the GDM Face Browser is turned, then the file <filename>$HOME/.face</" -#~ "filename> is accessed. This file should be a standard image that GTK+ can " -#~ "read, such as PNG or JPEG. It also must be smaller than the " -#~ "<filename>MaxIconWidth</filename> and <filename>MaxIconHeight</filename> " -#~ "values defined in the GDM configuration or it will be ignored. Users can " -#~ "run the <command>gdmphotosetup</command> program to specify a face image " -#~ "and it will copy the file to the <filename>$HOME/.face</filename> " -#~ "location and scale it so its longest dimension is not larger than the " -#~ "<filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> " -#~ "values. <command>gdmphotosetup</command> takes care to not change the " -#~ "aspect ratio of the image." -#~ msgstr "" -#~ "If the GDM Face Browser is enabled, then the file <filename>$HOME/.face</" -#~ "filename> is accessed. This file should be in a standard image format " -#~ "that GTK+ can read, such as PNG or JPEG. It also must be smaller than the " -#~ "<filename>MaxIconWidth</filename> and <filename>MaxIconHeight</filename> " -#~ "values defined in the GDM configuration or it will be ignored. Users can " -#~ "run the <command>gdmphotosetup</command> program to specify a face image " -#~ "and it will copy the file to the <filename>$HOME/.face</filename> " -#~ "location and scale it so its longest dimension is not larger than the " -#~ "<filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> " -#~ "values. <command>gdmphotosetup</command> takes care to not change the " -#~ "aspect ratio of the image." - -#~ msgid "" -#~ "Face images can also be placed in the global face directory, which is " -#~ "specified by the <filename>GlobalFaceDir</filename> configuration option " -#~ "( normally <filename><share>/pixmaps/faces/</filename>) and the " -#~ "filename should be the name of the user, optionally with a <filename>." -#~ "png</filename>, <filename>.jpg</filename>, etc. appended." -#~ msgstr "" -#~ "Face images can also be placed in the global face directory, which is " -#~ "specified by the <filename>GlobalFaceDir</filename> configuration option " -#~ "( normally <filename><share>/pixmaps/faces/</filename>) and the " -#~ "filename should be the name of the user, optionally with a <filename>." -#~ "png</filename>, <filename>.jpg</filename>, etc. appended." - -#~ msgid "Controlling GDM" -#~ msgstr "Controlling GDM" - -#~ msgid "" -#~ "You can control GDM behavior during runtime in several different ways. " -#~ "You can either run certain commands, or you can talk to GDM using either " -#~ "a unix socket protocol, or a FIFO protocol." -#~ msgstr "" -#~ "You can control GDM behaviour during runtime in several different ways: " -#~ "you can run certain commands or you can talk to GDM using either a unix " -#~ "socket protocol or a FIFO protocol." - -#~ msgid "Commands" -#~ msgstr "Commands" - -#~ msgid "" -#~ "To stop GDM, you can either send the TERM signal to the main daemon or " -#~ "run the <command>gdm-stop</command> command which is in the <filename><" -#~ "sbin>/</filename> directory. To restart GDM, you can either send the " -#~ "HUP signal to the main daemon or run the <command>gdm-restart</command> " -#~ "command which is also in the <filename><sbin>/</filename> " -#~ "directory. To restart GDM but only after all the users have logged out, " -#~ "you can either send the USR1 signal to the main daemon or run the " -#~ "<command>gdm-safe-restart</command> command which is in the <filename><" -#~ "sbin>/</filename> directory as well." -#~ msgstr "" -#~ "To stop GDM, you can either send the TERM signal to the main daemon or " -#~ "run the <command>gdm-stop</command> command which is in the <filename><" -#~ "sbin>/</filename> directory. To restart GDM, you can either send the " -#~ "HUP signal to the main daemon or run the <command>gdm-restart</command> " -#~ "command which is also in the <filename><sbin>/</filename> " -#~ "directory. To restart GDM only after all the users have logged out, you " -#~ "can either send the USR1 signal to the main daemon or run the " -#~ "<command>gdm-safe-restart</command> command which is in the <filename><" -#~ "sbin>/</filename> directory as well." - -#~ msgid "" -#~ "The <command>gdmflexiserver</command> command can be used to start new " -#~ "flexible (on demand) displays if your system supports virtual terminals. " -#~ "This command will normally lock the current session with a screensaver so " -#~ "that the user can safely walk away from the computer and let someone else " -#~ "log in. If more that two flexible displays have started " -#~ "<command>gdmflexiserver</command> will display a pop-up dialog allowing " -#~ "the user to select which session to continue. The user will normally have " -#~ "to enter a password to return to the session. On session exit the system " -#~ "will return to the previous virtual terminal. Run <command>gdmflexiserver " -#~ "--help</command> to get a listing of possible options." -#~ msgstr "" -#~ "The <command>gdmflexiserver</command> command can be used to start new " -#~ "flexible (on demand) displays if your system supports virtual terminals. " -#~ "This command will normally lock the current session with a screensaver so " -#~ "that the user can safely walk away from the computer and let someone else " -#~ "log in. If more that two flexible displays have been started " -#~ "<command>gdmflexiserver</command> will display a pop-up dialogue allowing " -#~ "the user to select which session to continue. The user will normally have " -#~ "to enter a password to return to the session. On session exit, the system " -#~ "will return to the previous virtual terminal. Run <command>gdmflexiserver " -#~ "--help</command> to get a listing of possible options." - -#~ msgid "The FIFO protocol" -#~ msgstr "The FIFO protocol" - -#~ msgid "" -#~ "GDM also provides a FIFO called <filename>.gdmfifo</filename> in the " -#~ "<filename>ServAuthDir</filename> directory (usually <filename><var>/" -#~ "gdm/.gdmfifo</filename>). You must be root to use this protocol, and it " -#~ "is mostly used for internal GDM chatter. It is a very simple protocol " -#~ "where you just echo a command on a single line to this file. It can be " -#~ "used to tell GDM things such as restart, suspend the computer, or restart " -#~ "all X servers next time it has a chance (which would be useful from an X " -#~ "configuration application)." -#~ msgstr "" -#~ "GDM also provides a FIFO called <filename>.gdmfifo</filename> in the " -#~ "<filename>ServAuthDir</filename> directory (usually <filename><var>/" -#~ "gdm/.gdmfifo</filename>). You must be root to use this protocol, and it " -#~ "is mostly used for internal GDM chatter. It is a very simple protocol " -#~ "where you just echo a command on a single line to this file. It can be " -#~ "used to tell GDM things such as restart, suspend the computer, or restart " -#~ "all X servers next time it has a chance (which would be useful from an X " -#~ "configuration application)." - -#~ msgid "" -#~ "Full and up to date documentation of the commands and their use is " -#~ "contained in the GDM source tree in the file <filename>daemon/gdm.h</" -#~ "filename>. Look for the defines starting with <filename>GDM_SOP_</" -#~ "filename>. The commands which require the pid of the slave as an argument " -#~ "are the ones that are really used for internal communication of the slave " -#~ "with the master and should not be used." -#~ msgstr "" -#~ "Full and up to date documentation of the commands and their use is " -#~ "contained in the GDM source tree in the file <filename>daemon/gdm.h</" -#~ "filename>. Look for the defines starting with <filename>GDM_SOP_</" -#~ "filename>. The commands which require the pid of the slave as an argument " -#~ "are the ones that are really used for internal communication of the slave " -#~ "with the master and should not be used." - -#~ msgid "Socket Protocol" -#~ msgstr "Socket Protocol" - -#~ msgid "" -#~ "GDM provides a unix domain socket for communication at <filename>/tmp/." -#~ "gdm_socket</filename>. Using this you can check if GDM is running, the " -#~ "version of the daemon, the current displays that are running and who is " -#~ "logged in on them, and if GDM supports it on your operating system, also " -#~ "the virtual terminals of all the console logins. The " -#~ "<command>gdmflexiserver</command> command uses this protocol, for " -#~ "example, to launch flexible (on-demand) displays." -#~ msgstr "" -#~ "GDM provides a unix domain socket for communication at <filename>/tmp/." -#~ "gdm_socket</filename>. Using this you can check if GDM is running, the " -#~ "version of the daemon, the current displays that are running and who is " -#~ "logged in on them, and if GDM supports it on your operating system, also " -#~ "the virtual terminals of all the console logins. The " -#~ "<command>gdmflexiserver</command> command uses this protocol, for " -#~ "example, to launch flexible (on-demand) displays." - -#~ msgid "" -#~ "gdmflexiserver accepts the following commands with the --command option:" -#~ msgstr "" -#~ "gdmflexiserver accepts the following commands with the --command option:" - -#~ msgid "" -#~ "\n" -#~ "ADD_DYNAMIC_DISPLAY\n" -#~ "ALL_SERVERS\n" -#~ "ATTACHED_SERVERS\n" -#~ "AUTH_LOCAL\n" -#~ "CLOSE\n" -#~ "FLEXI_XNEST\n" -#~ "FLEXI_XNEST_USER\n" -#~ "FLEXI_XSERVER\n" -#~ "FLEXI_XSERVER_USER\n" -#~ "GET_CONFIG\n" -#~ "GET_CONFIG_FILE\n" -#~ "GET_CUSTOM_CONFIG_FILE\n" -#~ "GET_SERVER_LIST\n" -#~ "GET_SERVER_DETAILS\n" -#~ "GREETERPIDS\n" -#~ "QUERY_LOGOUT_ACTION\n" -#~ "QUERY_VT\n" -#~ "RELEASE_DYNAMIC_DISPLAYS\n" -#~ "REMOVE_DYNAMIC_DISPLAY\n" -#~ "SERVER_BUSY\n" -#~ "SET_LOGOUT_ACTION\n" -#~ "SET_SAFE_LOGOUT_ACTION\n" -#~ "SET_VT\n" -#~ "UPDATE_CONFIG\n" -#~ "VERSION\n" -#~ msgstr "" -#~ "\n" -#~ "ADD_DYNAMIC_DISPLAY\n" -#~ "ALL_SERVERS\n" -#~ "ATTACHED_SERVERS\n" -#~ "AUTH_LOCAL\n" -#~ "CLOSE\n" -#~ "FLEXI_XNEST\n" -#~ "FLEXI_XNEST_USER\n" -#~ "FLEXI_XSERVER\n" -#~ "FLEXI_XSERVER_USER\n" -#~ "GET_CONFIG\n" -#~ "GET_CONFIG_FILE\n" -#~ "GET_CUSTOM_CONFIG_FILE\n" -#~ "GET_SERVER_LIST\n" -#~ "GET_SERVER_DETAILS\n" -#~ "GREETERPIDS\n" -#~ "QUERY_LOGOUT_ACTION\n" -#~ "QUERY_VT\n" -#~ "RELEASE_DYNAMIC_DISPLAYS\n" -#~ "REMOVE_DYNAMIC_DISPLAY\n" -#~ "SERVER_BUSY\n" -#~ "SET_LOGOUT_ACTION\n" -#~ "SET_SAFE_LOGOUT_ACTION\n" -#~ "SET_VT\n" -#~ "UPDATE_CONFIG\n" -#~ "VERSION\n" - -#~ msgid "" -#~ "These are described in detail below, including required arguments, " -#~ "response format, and return codes." -#~ msgstr "" -#~ "These are described in detail below, including required arguments, " -#~ "response format, and return codes." - -#~ msgid "ADD_DYNAMIC_DISPLAY" -#~ msgstr "ADD_DYNAMIC_DISPLAY" - -#~ msgid "" -#~ "\n" -#~ "ADD_DYNAMIC_DISPLAY: Create a new server definition that will\n" -#~ " run on the specified display leaving, it\n" -#~ " in DISPLAY_CONFIG state.\n" -#~ "Supported since: 2.8.0.0\n" -#~ "Arguments: <display to run on>=<server>\n" -#~ " Where <server> is either a configuration named in the\n" -#~ " GDM configuration or a literal command name.\n" -#~ "Answers:\n" -#~ " OK <display>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 2 = Existing display\n" -#~ " 3 = No server string\n" -#~ " 4 = Display startup failure\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Dynamic Displays not allowed\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "ADD_DYNAMIC_DISPLAY: Create a new server definition that will\n" -#~ " run on the specified display leaving, it\n" -#~ " in DISPLAY_CONFIG state.\n" -#~ "Supported since: 2.8.0.0\n" -#~ "Arguments: <display to run on>=<server>\n" -#~ " Where <server> is either a configuration named in the\n" -#~ " GDM configuration or a literal command name.\n" -#~ "Answers:\n" -#~ " OK <display>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 2 = Existing display\n" -#~ " 3 = No server string\n" -#~ " 4 = Display startup failure\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Dynamic Displays not allowed\n" -#~ " 999 = Unknown error\n" - -#~ msgid "ALL_SERVERS" -#~ msgstr "ALL_SERVERS" - -#~ msgid "" -#~ "\n" -#~ "ALL_SERVERS: List all displays, including console, remote, xnest.\n" -#~ " This can, for example, be useful to figure out if\n" -#~ " the display you are on is managed by the gdm daemon,\n" -#~ " by seeing if it is in the list. It is also somewhat\n" -#~ " like the 'w' command but for graphical sessions.\n" -#~ "Supported since: 2.4.2.96\n" -#~ "Arguments: None\n" -#~ "Answers:\n" -#~ " OK <server>;<server>;...\n" -#~ "\n" -#~ " <server> is <display>,<logged in user>\n" -#~ "\n" -#~ " <logged in user> can be empty in case no one logged in yet\n" -#~ "\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "ALL_SERVERS: List all displays, including console, remote, xnest.\n" -#~ " This can, for example, be useful to figure out if\n" -#~ " the display you are on is managed by the gdm daemon,\n" -#~ " by seeing if it is in the list. It is also somewhat\n" -#~ " like the 'w' command but for graphical sessions.\n" -#~ "Supported since: 2.4.2.96\n" -#~ "Arguments: None\n" -#~ "Answers:\n" -#~ " OK <server>;<server>;...\n" -#~ "\n" -#~ " <server> is <display>,<logged in user>\n" -#~ "\n" -#~ " <logged in user> can be empty in case no one logged in yet\n" -#~ "\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "ATTACHED_SERVERS" -#~ msgstr "ATTACHED_SERVERS" - -#~ msgid "" -#~ "\n" -#~ "ATTACHED_SERVERS: List all attached displays. Doesn't list XDMCP\n" -#~ " and xnest non-attached displays.\n" -#~ "Note: This command used to be named CONSOLE_SERVERS,\n" -#~ " which is still recognized for backwards\n" -#~ " compatibility. The optional pattern argument\n" -#~ " is supported as of version 2.8.0.0.\n" -#~ "Supported since: 2.2.4.0\n" -#~ "Arguments: <pattern> (optional)\n" -#~ " With no argument, all attached displays are returned. The optional\n" -#~ " <pattern> is a string that may contain glob characters '*', '?', " -#~ "and\n" -#~ " '[]'. Only displays that match the pattern will be returned.\n" -#~ "Answers:\n" -#~ " OK <server>;<server>;...\n" -#~ "\n" -#~ " <server> is <display>,<logged in user>,<vt or " -#~ "xnest display>\n" -#~ "\n" -#~ " <logged in user> can be empty in case no one logged\n" -#~ " in yet, and <vt> can be -1 if it's not known or not\n" -#~ " supported (on non-Linux for example). If the display is an\n" -#~ " xnest display and is a console one (that is, it is an xnest\n" -#~ " inside another console display) it is listed and instead of\n" -#~ " vt, it lists the parent display in standard form.\n" -#~ "\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "ATTACHED_SERVERS: List all attached displays. Doesn't list XDMCP\n" -#~ " and xnest non-attached displays.\n" -#~ "Note: This command used to be named CONSOLE_SERVERS,\n" -#~ " which is still recognized for backwards\n" -#~ " compatibility. The optional pattern argument\n" -#~ " is supported as of version 2.8.0.0.\n" -#~ "Supported since: 2.2.4.0\n" -#~ "Arguments: <pattern> (optional)\n" -#~ " With no argument, all attached displays are returned. The optional\n" -#~ " <pattern> is a string that may contain glob characters '*', '?', " -#~ "and\n" -#~ " '[]'. Only displays that match the pattern will be returned.\n" -#~ "Answers:\n" -#~ " OK <server>;<server>;...\n" -#~ "\n" -#~ " <server> is <display>,<logged in user>,<vt or " -#~ "xnest display>\n" -#~ "\n" -#~ " <logged in user> can be empty in case no one logged\n" -#~ " in yet, and <vt> can be -1 if it's not known or not\n" -#~ " supported (on non-Linux for example). If the display is an\n" -#~ " xnest display and is a console one (that is, it is an xnest\n" -#~ " inside another console display) it is listed and instead of\n" -#~ " vt, it lists the parent display in standard form.\n" -#~ "\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "AUTH_LOCAL" -#~ msgstr "AUTH_LOCAL" - -#~ msgid "" -#~ "\n" -#~ "AUTH_LOCAL: Setup this connection as authenticated for\n" -#~ " FLEXI_SERVER. Because all full blown (non-Xnest)\n" -#~ " displays can be started only from users logged in\n" -#~ " locally, and here GDM assumes only users logged\n" -#~ " in from GDM. They must pass the xauth\n" -#~ " MIT-MAGIC-COOKIE-1 that they were passed before\n" -#~ " the connection is authenticated.\n" -#~ "Note: The AUTH LOCAL command requires the\n" -#~ " --authenticate option, although only\n" -#~ " FLEXI XSERVER uses this currently.\n" -#~ "Note: Since 2.6.0.6 you can also use a global\n" -#~ " <ServAuthDir>/.cookie, which works for all\n" -#~ " authentication except for SET_LOGOUT_ACTION and\n" -#~ " QUERY_LOGOUT_ACTION and SET_SAFE_LOGOUT_ACTION\n" -#~ " which require a logged in display.\n" -#~ "Supported since: 2.2.4.0\n" -#~ "Arguments: <xauth cookie>\n" -#~ " <xauth cookie> is in hex form with no 0x prefix\n" -#~ "Answers:\n" -#~ " OK\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "AUTH_LOCAL: Setup this connection as authenticated for\n" -#~ " FLEXI_SERVER. Because all full blown (non-Xnest)\n" -#~ " displays can be started only from users logged in\n" -#~ " locally, and here GDM assumes only users logged\n" -#~ " in from GDM. They must pass the xauth\n" -#~ " MIT-MAGIC-COOKIE-1 that they were passed before\n" -#~ " the connection is authenticated.\n" -#~ "Note: The AUTH LOCAL command requires the\n" -#~ " --authenticate option, although only\n" -#~ " FLEXI XSERVER uses this currently.\n" -#~ "Note: Since 2.6.0.6 you can also use a global\n" -#~ " <ServAuthDir>/.cookie, which works for all\n" -#~ " authentication except for SET_LOGOUT_ACTION and\n" -#~ " QUERY_LOGOUT_ACTION and SET_SAFE_LOGOUT_ACTION\n" -#~ " which require a logged in display.\n" -#~ "Supported since: 2.2.4.0\n" -#~ "Arguments: <xauth cookie>\n" -#~ " <xauth cookie> is in hex form with no 0x prefix\n" -#~ "Answers:\n" -#~ " OK\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "CLOSE" -#~ msgstr "CLOSE" - -#~ msgid "" -#~ "\n" -#~ "CLOSE: Close sockets connection\n" -#~ "Supported since: 2.2.4.0\n" -#~ "Arguments: None\n" -#~ "Answers: None\n" -#~ msgstr "" -#~ "\n" -#~ "CLOSE: Close sockets connection\n" -#~ "Supported since: 2.2.4.0\n" -#~ "Arguments: None\n" -#~ "Answers: None\n" - -#~ msgid "FLEXI_XNEST" -#~ msgstr "FLEXI_XNEST" - -#~ msgid "" -#~ "\n" -#~ "FLEXI_XNEXT: Start a new flexible Xnest display.\n" -#~ "Note: Supported on older version from 2.2.4.0, later\n" -#~ " 2.2.4.2, but since 2.3.90.4 you must supply 4\n" -#~ " arguments or ERROR 100 will be returned. This\n" -#~ " will start Xnest using the XAUTHORITY file\n" -#~ " supplied and as the uid same as the owner of\n" -#~ " that file (and same as you supply). You must\n" -#~ " also supply the cookie as the third argument\n" -#~ " for this display, to prove that you indeed are\n" -#~ " this user. Also this file must be readable\n" -#~ " ONLY by this user, that is have a mode of 0600.\n" -#~ " If this all is not met, ERROR 100 is returned.\n" -#~ "Note: The cookie should be the MIT-MAGIC-COOKIE-1,\n" -#~ " the first one GDM can find in the XAUTHORITY\n" -#~ " file for this display. If that's not what you\n" -#~ " use you should generate one first. The cookie\n" -#~ " should be in hex form.\n" -#~ "Supported since: 2.3.90.4\n" -#~ "Arguments: <display to run on> <uid of requesting user>\n" -#~ " <xauth cookie for the display> <xauth file>\n" -#~ "Answers:\n" -#~ " OK <display>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = No more flexi servers\n" -#~ " 2 = Startup errors\n" -#~ " 3 = X failed\n" -#~ " 4 = X too busy\n" -#~ " 5 = Xnest can't connect\n" -#~ " 6 = No server binary\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "FLEXI_XNEXT: Start a new flexible Xnest display.\n" -#~ "Note: Supported on older version from 2.2.4.0, later\n" -#~ " 2.2.4.2, but since 2.3.90.4 you must supply 4\n" -#~ " arguments or ERROR 100 will be returned. This\n" -#~ " will start Xnest using the XAUTHORITY file\n" -#~ " supplied and as the uid same as the owner of\n" -#~ " that file (and same as you supply). You must\n" -#~ " also supply the cookie as the third argument\n" -#~ " for this display, to prove that you indeed are\n" -#~ " this user. Also this file must be readable\n" -#~ " ONLY by this user, that is have a mode of 0600.\n" -#~ " If this all is not met, ERROR 100 is returned.\n" -#~ "Note: The cookie should be the MIT-MAGIC-COOKIE-1,\n" -#~ " the first one GDM can find in the XAUTHORITY\n" -#~ " file for this display. If that's not what you\n" -#~ " use you should generate one first. The cookie\n" -#~ " should be in hex form.\n" -#~ "Supported since: 2.3.90.4\n" -#~ "Arguments: <display to run on> <uid of requesting user>\n" -#~ " <xauth cookie for the display> <xauth file>\n" -#~ "Answers:\n" -#~ " OK <display>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = No more flexi servers\n" -#~ " 2 = Startup errors\n" -#~ " 3 = X failed\n" -#~ " 4 = X too busy\n" -#~ " 5 = Xnest can't connect\n" -#~ " 6 = No server binary\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "FLEXI_XNEST_USER" -#~ msgstr "FLEXI_XNEST_USER" - -#~ msgid "" -#~ "\n" -#~ "FLEXI_XNEST_USER: Start a new flexible Xnest display and\n" -#~ " initialize the greeter with the given username.\n" -#~ "Note: This is a variant of the FLEXI_XNEST command.\n" -#~ "Note: The cookie should be the MIT-MAGIC-COOKIE-1,\n" -#~ " the first one GDM can find in the XAUTHORITY\n" -#~ " file for this display. If that's not what you\n" -#~ " use you should generate one first. The cookie\n" -#~ " should be in hex form.\n" -#~ "Supported since: 2.17.7\n" -#~ "Arguments: <username> <display to run on> <uid of " -#~ "requesting user>\n" -#~ " <xauth cookie for the display> <xauth file>\n" -#~ "Answers:\n" -#~ " OK <display>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = No more flexi servers\n" -#~ " 2 = Startup errors\n" -#~ " 3 = X failed\n" -#~ " 4 = X too busy\n" -#~ " 5 = Xnest can't connect\n" -#~ " 6 = No server binary\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "FLEXI_XNEST_USER: Start a new flexible Xnest display and\n" -#~ " initialize the greeter with the given username.\n" -#~ "Note: This is a variant of the FLEXI_XNEST command.\n" -#~ "Note: The cookie should be the MIT-MAGIC-COOKIE-1,\n" -#~ " the first one GDM can find in the XAUTHORITY\n" -#~ " file for this display. If that's not what you\n" -#~ " use you should generate one first. The cookie\n" -#~ " should be in hex form.\n" -#~ "Supported since: 2.17.7\n" -#~ "Arguments: <username> <display to run on> <uid of " -#~ "requesting user>\n" -#~ " <xauth cookie for the display> <xauth file>\n" -#~ "Answers:\n" -#~ " OK <display>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = No more flexi servers\n" -#~ " 2 = Startup errors\n" -#~ " 3 = X failed\n" -#~ " 4 = X too busy\n" -#~ " 5 = Xnest can't connect\n" -#~ " 6 = No server binary\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "FLEXI_XSERVER" -#~ msgstr "FLEXI_XSERVER" - -#~ msgid "" -#~ "\n" -#~ "FLEXI_XSERVER: Start a new X flexible display. Only supported on\n" -#~ " connection that passed AUTH_LOCAL\n" -#~ "Supported since: 2.2.4.0\n" -#~ "Arguments: <xserver type>\n" -#~ " If no arguments, starts the standard X server\n" -#~ "Answers:\n" -#~ " OK <display>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = No more flexi servers\n" -#~ " 2 = Startup errors\n" -#~ " 3 = X failed\n" -#~ " 4 = X too busy\n" -#~ " 6 = No server binary\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "FLEXI_XSERVER: Start a new X flexible display. Only supported on\n" -#~ " connection that passed AUTH_LOCAL\n" -#~ "Supported since: 2.2.4.0\n" -#~ "Arguments: <xserver type>\n" -#~ " If no arguments, starts the standard X server\n" -#~ "Answers:\n" -#~ " OK <display>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = No more flexi servers\n" -#~ " 2 = Startup errors\n" -#~ " 3 = X failed\n" -#~ " 4 = X too busy\n" -#~ " 6 = No server binary\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "FLEXI_XSERVER_USER" -#~ msgstr "FLEXI_XSERVER_USER" - -#~ msgid "" -#~ "\n" -#~ "FLEXI_XSERVER_USER: Start a new X flexible display and initialize the\n" -#~ " greeter with the given username. Only supported on\n" -#~ " connection that passed AUTH_LOCAL\n" -#~ "Supported since: 2.17.7 \n" -#~ "Arguments: <username> <xserver type>\n" -#~ " If no server type specified, starts the standard X server\n" -#~ "Answers:\n" -#~ " OK <display>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = No more flexi servers\n" -#~ " 2 = Startup errors\n" -#~ " 3 = X failed\n" -#~ " 4 = X too busy\n" -#~ " 6 = No server binary\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "FLEXI_XSERVER_USER: Start a new X flexible display and initialise the\n" -#~ " greeter with the given username. Only supported on\n" -#~ " connection that passed AUTH_LOCAL\n" -#~ "Supported since: 2.17.7 \n" -#~ "Arguments: <username> <xserver type>\n" -#~ " If no server type specified, starts the standard X server\n" -#~ "Answers:\n" -#~ " OK <display>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = No more flexi servers\n" -#~ " 2 = Startup errors\n" -#~ " 3 = X failed\n" -#~ " 4 = X too busy\n" -#~ " 6 = No server binary\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "GET_CONFIG" -#~ msgstr "GET_CONFIG" - -#~ msgid "" -#~ "\n" -#~ "GET_CONFIG: Get configuration value for key. Useful so\n" -#~ " that other applications can request configuration\n" -#~ " information from GDM. Any key defined as GDM_KEY_*\n" -#~ " in gdm.h is supported. Starting with version 2.13.0.2\n" -#~ " translated keys (such as \"greeter/GdmWelcome[cs]\" are\n" -#~ " supported via GET_CONFIG. Also starting with version\n" -#~ " 2.13.0.2 it is no longer necessary to include the\n" -#~ " default value (i.e. you can use key \"greeter/IncludeAll\"\n" -#~ " instead of having to use \"greeter/IncludeAll=false\". \n" -#~ "Supported since: 2.6.0.9\n" -#~ "Arguments: <key>\n" -#~ "Answers:\n" -#~ " OK <value>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 50 = Unsupported key\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "GET_CONFIG: Get configuration value for key. Useful so\n" -#~ " that other applications can request configuration\n" -#~ " information from GDM. Any key defined as GDM_KEY_*\n" -#~ " in gdm.h is supported. Starting with version 2.13.0.2\n" -#~ " translated keys (such as \"greeter/GdmWelcome[cs]\" are\n" -#~ " supported via GET_CONFIG. Also starting with version\n" -#~ " 2.13.0.2 it is no longer necessary to include the\n" -#~ " default value (i.e. you can use key \"greeter/IncludeAll\"\n" -#~ " instead of having to use \"greeter/IncludeAll=false\". \n" -#~ "Supported since: 2.6.0.9\n" -#~ "Arguments: <key>\n" -#~ "Answers:\n" -#~ " OK <value>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 50 = Unsupported key\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "GET_CONFIG_FILE" -#~ msgstr "GET_CONFIG_FILE" - -#~ msgid "" -#~ "\n" -#~ "GET_CONFIG_FILE: Get config file location being used by\n" -#~ " the daemon. If the GDM daemon was started\n" -#~ " with the --config option, it will return\n" -#~ " the value passed in via the argument.\n" -#~ "Supported since: 2.8.0.2\n" -#~ "Arguments: None\n" -#~ "Answers:\n" -#~ " OK <full path to GDM configuration file>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "GET_CONFIG_FILE: Get configuration file location being used by\n" -#~ " the daemon. If the GDM daemon was started\n" -#~ " with the --config option, it will return\n" -#~ " the value passed in via the argument.\n" -#~ "Supported since: 2.8.0.2\n" -#~ "Arguments: None\n" -#~ "Answers:\n" -#~ " OK <full path to GDM configuration file>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "GET_CUSTOM_CONFIG_FILE" -#~ msgstr "GET_CUSTOM_CONFIG_FILE" - -#~ msgid "" -#~ "\n" -#~ "GET_CUSTOM_CONFIG_FILE: Get custom config file location being\n" -#~ " used by the daemon.\n" -#~ "Supported since: 2.14.0.0\n" -#~ "Arguments: None\n" -#~ "Answers:\n" -#~ " OK <full path to GDM custom configuration file>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = File not found\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "GET_CUSTOM_CONFIG_FILE: Get custom configuration file location being\n" -#~ " used by the daemon.\n" -#~ "Supported since: 2.14.0.0\n" -#~ "Arguments: None\n" -#~ "Answers:\n" -#~ " OK <full path to GDM custom configuration file>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = File not found\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "GET_SERVER_DETAILS" -#~ msgstr "GET_SERVER_DETAILS" - -#~ msgid "" -#~ "\n" -#~ "GET_SERVER_DETAILS: Get detail information for a specific server.\n" -#~ "Supported since: 2.13.0.4\n" -#~ "Arguments: <server> <key>\n" -#~ " Key values include:\n" -#~ " NAME - Returns the server name\n" -#~ " COMMAND - Returns the server command\n" -#~ " FLEXIBLE - Returns \"true\" if flexible, \"false\"\n" -#~ " otherwise\n" -#~ " CHOOSABLE - Returns \"true\" if choosable, \"false\"\n" -#~ " otherwise\n" -#~ " HANDLED - Returns \"true\" if handled, \"false\"\n" -#~ " otherwise\n" -#~ " CHOOSER - Returns \"true\" if chooser, \"false\"\n" -#~ " otherwise\n" -#~ " PRIORITY - Returns process priority\n" -#~ "Answers:\n" -#~ " OK <value>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = Server not found\n" -#~ " 2 = Key not valid\n" -#~ " 50 = Unsupported key\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "GET_SERVER_DETAILS: Get detail information for a specific server.\n" -#~ "Supported since: 2.13.0.4\n" -#~ "Arguments: <server> <key>\n" -#~ " Key values include:\n" -#~ " NAME - Returns the server name\n" -#~ " COMMAND - Returns the server command\n" -#~ " FLEXIBLE - Returns \"true\" if flexible, \"false\"\n" -#~ " otherwise\n" -#~ " CHOOSABLE - Returns \"true\" if choosable, \"false\"\n" -#~ " otherwise\n" -#~ " HANDLED - Returns \"true\" if handled, \"false\"\n" -#~ " otherwise\n" -#~ " CHOOSER - Returns \"true\" if chooser, \"false\"\n" -#~ " otherwise\n" -#~ " PRIORITY - Returns process priority\n" -#~ "Answers:\n" -#~ " OK <value>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = Server not found\n" -#~ " 2 = Key not valid\n" -#~ " 50 = Unsupported key\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "GET_SERVER_LIST" -#~ msgstr "GET_SERVER_LIST" - -#~ msgid "" -#~ "\n" -#~ "GET_SERVER_LIST: Get a list of the server sections from\n" -#~ " the configuration file.\n" -#~ "Supported since: 2.13.0.4\n" -#~ "Arguments: None\n" -#~ "Answers:\n" -#~ " OK <value>;<value>;...\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = No servers found\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "GET_SERVER_LIST: Get a list of the server sections from\n" -#~ " the configuration file.\n" -#~ "Supported since: 2.13.0.4\n" -#~ "Arguments: None\n" -#~ "Answers:\n" -#~ " OK <value>;<value>;...\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = No servers found\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "GREETERPIDS" -#~ msgstr "GREETERPIDS" - -#~ msgid "" -#~ "\n" -#~ "GREETERPIDS: List all greeter pids so that one can send HUP\n" -#~ " to them for config rereading. Of course one\n" -#~ " must be root to do that.\n" -#~ "Supported since: 2.3.90.2\n" -#~ "Arguments: None\n" -#~ "Answers:\n" -#~ " OK <pid>;<pid>;...\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "GREETERPIDS: List all greeter pids so that one can send HUP\n" -#~ " to them for config re-reading. Of course one\n" -#~ " must be root to do that.\n" -#~ "Supported since: 2.3.90.2\n" -#~ "Arguments: None\n" -#~ "Answers:\n" -#~ " OK <pid>;<pid>;...\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "QUERY_LOGOUT_ACTION" -#~ msgstr "QUERY_LOGOUT_ACTION" - -#~ msgid "" -#~ "\n" -#~ "QUERY_LOGOUT_ACTION: Query which logout actions are possible\n" -#~ " Only supported on connections that passed\n" -#~ " AUTH_LOCAL.\n" -#~ "Supported since: 2.5.90.0\n" -#~ "Answers:\n" -#~ " OK <action>;<action>;...\n" -#~ " Where action is one of HALT, REBOOT, SUSPEND or CUSTOM_CMD[0-9].\n" -#~ " An empty list can also be returned if no action is possible.\n" -#~ " A '!' is appended to an action if it was already set with\n" -#~ " SET_LOGOUT_ACTION or SET_SAFE_LOGOUT_ACTION. Note that\n" -#~ " SET_LOGOUT_ACTION has precedence over\n" -#~ " SET_SAFE_LOGOUT_ACTION.\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "QUERY_LOGOUT_ACTION: Query which logout actions are possible\n" -#~ " Only supported on connections that passed\n" -#~ " AUTH_LOCAL.\n" -#~ "Supported since: 2.5.90.0\n" -#~ "Answers:\n" -#~ " OK <action>;<action>;...\n" -#~ " Where action is one of HALT, REBOOT, SUSPEND or CUSTOM_CMD[0-9].\n" -#~ " An empty list can also be returned if no action is possible.\n" -#~ " A '!' is appended to an action if it was already set with\n" -#~ " SET_LOGOUT_ACTION or SET_SAFE_LOGOUT_ACTION. Note that\n" -#~ " SET_LOGOUT_ACTION has precedence over\n" -#~ " SET_SAFE_LOGOUT_ACTION.\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "QUERY_CUSTOM_CMD_LABELS" -#~ msgstr "QUERY_CUSTOM_CMD_LABELS" - -#~ msgid "" -#~ "\n" -#~ " QUERY_CUSTOM_CMD_LABELS: Query labels belonging to exported custom\n" -#~ " commands Only supported on connections that\n" -#~ " passed AUTH_LOCAL.\n" -#~ " Supported since: 2.5.90.0\n" -#~ " Answers:\n" -#~ " OK <label1>;<label2>;...\n" -#~ " Where labelX is one of the labels belonging to CUSTOM_CMDX\n" -#~ " (where X in [0,GDM_CUSTOM_COMMAND_MAX)). An empty list can\n" -#~ " also be returned if none of the custom commands are exported\n" -#~ " outside login manager (no CustomCommandIsPersistent options\n" -#~ " are set to true). \n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ " QUERY_CUSTOM_CMD_LABELS: Query labels belonging to exported custom\n" -#~ " commands Only supported on connections that\n" -#~ " passed AUTH_LOCAL.\n" -#~ " Supported since: 2.5.90.0\n" -#~ " Answers:\n" -#~ " OK <label1>;<label2>;...\n" -#~ " Where labelX is one of the labels belonging to CUSTOM_CMDX\n" -#~ " (where X in [0,GDM_CUSTOM_COMMAND_MAX)). An empty list can\n" -#~ " also be returned if none of the custom commands are exported\n" -#~ " outside login manager (no CustomCommandIsPersistent options\n" -#~ " are set to true). \n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "QUERY_CUSTOM_CMD_NO_RESTART_STATUS" -#~ msgstr "QUERY_CUSTOM_CMD_NO_RESTART_STATUS" - -#~ msgid "" -#~ "\n" -#~ "QUERY_CUSTOM_CMD_NO_RESTART_STATUS: Query NoRestart config options\n" -#~ " for each of custom commands Only\n" -#~ " supported on connections that\n" -#~ " passed AUTH_LOCAL.\n" -#~ "Supported since: 2.5.90.0\n" -#~ "Answers:\n" -#~ " OK <status>\n" -#~ " Where each bit of the status represents NoRestart value for\n" -#~ " each of the custom commands.\n" -#~ " bit on (1): NoRestart = true, \n" -#~ " bit off (0): NoRestart = false.\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "QUERY_CUSTOM_CMD_NO_RESTART_STATUS: Query NoRestart config options\n" -#~ " for each of custom commands Only\n" -#~ " supported on connections that\n" -#~ " passed AUTH_LOCAL.\n" -#~ "Supported since: 2.5.90.0\n" -#~ "Answers:\n" -#~ " OK <status>\n" -#~ " Where each bit of the status represents NoRestart value for\n" -#~ " each of the custom commands.\n" -#~ " bit on (1): NoRestart = true, \n" -#~ " bit off (0): NoRestart = false.\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "QUERY_VT" -#~ msgstr "QUERY_VT" - -#~ msgid "" -#~ "\n" -#~ "QUERY_VT: Ask the daemon about which VT we are currently on.\n" -#~ " This is useful for logins which don't own\n" -#~ " /dev/console but are still console logins. Only\n" -#~ " supported on Linux currently, other places will\n" -#~ " just get ERROR 8. This is also the way to query\n" -#~ " if VT support is available in the daemon in the\n" -#~ " first place. Only supported on connections that\n" -#~ " passed AUTH_LOCAL.\n" -#~ "Supported since: 2.5.90.0\n" -#~ "Arguments: None\n" -#~ "Answers:\n" -#~ " OK <vt number>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 8 = Virtual terminals not supported\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "QUERY_VT: Ask the daemon about which VT we are currently on.\n" -#~ " This is useful for logins which don't own\n" -#~ " /dev/console but are still console logins. Only\n" -#~ " supported on Linux currently, other places will\n" -#~ " just get ERROR 8. This is also the way to query\n" -#~ " if VT support is available in the daemon in the\n" -#~ " first place. Only supported on connections that\n" -#~ " passed AUTH_LOCAL.\n" -#~ "Supported since: 2.5.90.0\n" -#~ "Arguments: None\n" -#~ "Answers:\n" -#~ " OK <vt number>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 8 = Virtual terminals not supported\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "RELEASE_DYNAMIC_DISPLAYS" -#~ msgstr "RELEASE_DYNAMIC_DISPLAYS" - -#~ msgid "" -#~ "\n" -#~ "RELEASE_DYNAMIC_DISPLAYS: Release dynamic displays currently in \n" -#~ " DISPLAY_CONFIG state\n" -#~ "Supported since: 2.8.0.0\n" -#~ "Arguments: <display to release>\n" -#~ "Answers:\n" -#~ " OK <display>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = Bad display number\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Dynamic Displays not allowed\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "RELEASE_DYNAMIC_DISPLAYS: Release dynamic displays currently in \n" -#~ " DISPLAY_CONFIG state\n" -#~ "Supported since: 2.8.0.0\n" -#~ "Arguments: <display to release>\n" -#~ "Answers:\n" -#~ " OK <display>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = Bad display number\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Dynamic Displays not allowed\n" -#~ " 999 = Unknown error\n" - -#~ msgid "REMOVE_DYNAMIC_DISPLAY" -#~ msgstr "REMOVE_DYNAMIC_DISPLAY" - -#~ msgid "" -#~ "\n" -#~ "REMOVE_DYNAMIC_DISPLAY: Remove a dynamic display, killing the server\n" -#~ " and purging the display configuration\n" -#~ "Supported since: 2.8.0.0\n" -#~ "Arguments: <display to remove>\n" -#~ "Answers:\n" -#~ " OK <display>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = Bad display number\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Dynamic Displays not allowed\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "REMOVE_DYNAMIC_DISPLAY: Remove a dynamic display, killing the server\n" -#~ " and purging the display configuration\n" -#~ "Supported since: 2.8.0.0\n" -#~ "Arguments: <display to remove>\n" -#~ "Answers:\n" -#~ " OK <display>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 1 = Bad display number\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Dynamic Displays not allowed\n" -#~ " 999 = Unknown error\n" - -#~ msgid "SERVER_BUSY" -#~ msgstr "SERVER_BUSY" - -#~ msgid "" -#~ "\n" -#~ "SERVER_BUSY: Returns true if half or more of the daemon's sockets\n" -#~ " are busy, false otherwise. Used by slave programs\n" -#~ " which want to ensure they do not overwhelm the \n" -#~ " sever.\n" -#~ "Supported since: 2.13.0.8\n" -#~ "Arguments: None\n" -#~ "Answers:\n" -#~ " OK <value>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "SERVER_BUSY: Returns true if half or more of the daemon's sockets\n" -#~ " are busy, false otherwise. Used by slave programs\n" -#~ " which want to ensure they do not overwhelm the \n" -#~ " sever.\n" -#~ "Supported since: 2.13.0.8\n" -#~ "Arguments: None\n" -#~ "Answers:\n" -#~ " OK <value>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "SET_LOGOUT_ACTION" -#~ msgstr "SET_LOGOUT_ACTION" - -#~ msgid "" -#~ "\n" -#~ "SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n" -#~ " slave process exits. Only supported on\n" -#~ " connections that passed AUTH_LOCAL.\n" -#~ "Supported since: 2.5.90.0\n" -#~ "Arguments: <action>\n" -#~ " NONE Set exit action to 'none'\n" -#~ " HALT Set exit action to 'halt'\n" -#~ " REBOOT Set exit action to 'reboot'\n" -#~ " SUSPEND Set exit action to 'suspend'\n" -#~ " CUSTOM_CMD[0-9] Set exit action to 'custom command [0-9]'\n" -#~ "Answers:\n" -#~ " OK\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 7 = Unknown logout action, or not available\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n" -#~ " slave process exits. Only supported on\n" -#~ " connections that passed AUTH_LOCAL.\n" -#~ "Supported since: 2.5.90.0\n" -#~ "Arguments: <action>\n" -#~ " NONE Set exit action to 'none'\n" -#~ " HALT Set exit action to 'halt'\n" -#~ " REBOOT Set exit action to 'reboot'\n" -#~ " SUSPEND Set exit action to 'suspend'\n" -#~ " CUSTOM_CMD[0-9] Set exit action to 'custom command [0-9]'\n" -#~ "Answers:\n" -#~ " OK\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 7 = Unknown logout action, or not available\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "SET_SAFE_LOGOUT_ACTION" -#~ msgstr "SET_SAFE_LOGOUT_ACTION" - -#~ msgid "" -#~ "\n" -#~ "SET_SAFE_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend\n" -#~ " after everybody logs out. If only one\n" -#~ " person logs out, then this is obviously\n" -#~ " the same as the SET_LOGOUT_ACTION. Note\n" -#~ " that SET_LOGOUT_ACTION has precedence\n" -#~ " over SET_SAFE_LOGOUT_ACTION if it is set\n" -#~ " to something other then NONE. If no one\n" -#~ " is logged in, then the action takes effect\n" -#~ " effect immediately. Only supported on\n" -#~ " connections that passed AUTH_LOCAL.\n" -#~ "Supported since: 2.5.90.0\n" -#~ "Arguments: <action>\n" -#~ " NONE Set exit action to 'none'\n" -#~ " HALT Set exit action to 'halt'\n" -#~ " REBOOT Set exit action to 'reboot'\n" -#~ " SUSPEND Set exit action to 'suspend'\n" -#~ " CUSTOM_CMD[0-9] Set exit action to 'custom command [0-9]'\n" -#~ "Answers:\n" -#~ " OK\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 7 = Unknown logout action, or not available\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "SET_SAFE_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend\n" -#~ " after everybody logs out. If only one\n" -#~ " person logs out, then this is obviously\n" -#~ " the same as the SET_LOGOUT_ACTION. Note\n" -#~ " that SET_LOGOUT_ACTION has precedence\n" -#~ " over SET_SAFE_LOGOUT_ACTION if it is set\n" -#~ " to something other then NONE. If no one\n" -#~ " is logged in, then the action takes effect\n" -#~ " effect immediately. Only supported on\n" -#~ " connections that passed AUTH_LOCAL.\n" -#~ "Supported since: 2.5.90.0\n" -#~ "Arguments: <action>\n" -#~ " NONE Set exit action to 'none'\n" -#~ " HALT Set exit action to 'halt'\n" -#~ " REBOOT Set exit action to 'reboot'\n" -#~ " SUSPEND Set exit action to 'suspend'\n" -#~ " CUSTOM_CMD[0-9] Set exit action to 'custom command [0-9]'\n" -#~ "Answers:\n" -#~ " OK\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 7 = Unknown logout action, or not available\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "SET_VT" -#~ msgstr "SET_VT" - -#~ msgid "" -#~ "\n" -#~ "SET_VT: Change to the specified virtual terminal.\n" -#~ " This is useful for logins which don't own /dev/console\n" -#~ " but are still console logins. Only supported on Linux\n" -#~ " currently, other places will just get ERROR 8.\n" -#~ " Only supported on connections that passed AUTH_LOCAL.\n" -#~ "Supported since: 2.5.90.0\n" -#~ "Arguments: <vt>\n" -#~ "Answers:\n" -#~ " OK\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 8 = Virtual terminals not supported\n" -#~ " 9 = Invalid virtual terminal number\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "SET_VT: Change to the specified virtual terminal.\n" -#~ " This is useful for logins which don't own /dev/console\n" -#~ " but are still console logins. Only currently supported\n" -#~ " on Linux, other systems will just get ERROR 8.\n" -#~ " Only supported on connections that passed AUTH_LOCAL.\n" -#~ "Supported since: 2.5.90.0\n" -#~ "Arguments: <vt>\n" -#~ "Answers:\n" -#~ " OK\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 8 = Virtual terminals not supported\n" -#~ " 9 = Invalid virtual terminal number\n" -#~ " 100 = Not authenticated\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "UPDATE_CONFIG" -#~ msgstr "UPDATE_CONFIG" - -#~ msgid "" -#~ "\n" -#~ "UPDATE_CONFIG: Tell the daemon to re-read a key from the \n" -#~ " GDM configuration file. Any user can request\n" -#~ " that values are re-read but the daemon will\n" -#~ " only do so if the file has been modified\n" -#~ " since GDM first read the file. Only users\n" -#~ " who can change the GDM configuration file\n" -#~ " (normally writable only by the root user) can\n" -#~ " actually modify the GDM configuration. This\n" -#~ " command is useful to cause the GDM to update\n" -#~ " itself to recognize a change made to the GDM\n" -#~ " configuration file by the root user.\n" -#~ "\n" -#~ " Starting with version 2.13.0.0, all GDM keys are\n" -#~ " supported except for the following:\n" -#~ "\n" -#~ " daemon/PidFile\n" -#~ " daemon/ConsoleNotify\n" -#~ " daemon/User\n" -#~ " daemon/Group\n" -#~ " daemon/LogDir\n" -#~ " daemon/ServAuthDir\n" -#~ " daemon/UserAuthDir\n" -#~ " daemon/UserAuthFile\n" -#~ " daemon/UserAuthFBDir\n" -#~ "\n" -#~ " GDM also supports the following Psuedokeys:\n" -#~ "\n" -#~ " xdmcp/PARAMETERS (2.3.90.2) updates the following:\n" -#~ " xdmcp/MaxPending\n" -#~ " xdmcp/MaxSessions\n" -#~ " xdmcp/MaxWait\n" -#~ " xdmcp/DisplaysPerHost\n" -#~ " xdmcp/HonorIndirect\n" -#~ " xdmcp/MaxPendingIndirect\n" -#~ " xdmcp/MaxWaitIndirect\n" -#~ " xdmcp/PingIntervalSeconds (only affects new " -#~ "connections)\n" -#~ "\n" -#~ " xservers/PARAMETERS (2.13.0.4) updates the following:\n" -#~ " all [server-foo] sections.\n" -#~ "\n" -#~ " Supported keys for previous versions of GDM:\n" -#~ "\n" -#~ " security/AllowRoot (2.3.90.2)\n" -#~ " security/AllowRemoteRoot (2.3.90.2)\n" -#~ " security/AllowRemoteAutoLogin (2.3.90.2)\n" -#~ " security/RetryDelay (2.3.90.2)\n" -#~ " security/DisallowTCP (2.4.2.0)\n" -#~ " daemon/Greeter (2.3.90.2)\n" -#~ " daemon/RemoteGreeter (2.3.90.2)\n" -#~ " xdmcp/Enable (2.3.90.2)\n" -#~ " xdmcp/Port (2.3.90.2)\n" -#~ " daemon/TimedLogin (2.3.90.3)\n" -#~ " daemon/TimedLoginEnable (2.3.90.3)\n" -#~ " daemon/TimedLoginDelay (2.3.90.3)\n" -#~ " greeter/SystemMenu (2.3.90.3)\n" -#~ " greeter/ConfigAvailable (2.3.90.3)\n" -#~ " greeter/ChooserButton (2.4.2.0)\n" -#~ " greeter/SoundOnLoginFile (2.5.90.0)\n" -#~ " daemon/AddGtkModules (2.5.90.0)\n" -#~ " daemon/GtkModulesList (2.5.90.0)\n" -#~ "Supported since: 2.3.90.2\n" -#~ "Arguments: <key>\n" -#~ " <key> is just the base part of the key such as\n" -#~ " \"security/AllowRemoteRoot\"\n" -#~ "Answers:\n" -#~ " OK\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 50 = Unsupported key\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "UPDATE_CONFIG: Tell the daemon to re-read a key from the \n" -#~ " GDM configuration file. Any user can request\n" -#~ " that values are re-read but the daemon will\n" -#~ " only do so if the file has been modified\n" -#~ " since GDM first read the file. Only users\n" -#~ " who can change the GDM configuration file\n" -#~ " (normally writable only by the root user) can\n" -#~ " actually modify the GDM configuration. This\n" -#~ " command is useful to cause the GDM to update\n" -#~ " itself to recognise a change made to the GDM\n" -#~ " configuration file by the root user.\n" -#~ "\n" -#~ " Starting with version 2.13.0.0, all GDM keys are\n" -#~ " supported except for the following:\n" -#~ "\n" -#~ " daemon/PidFile\n" -#~ " daemon/ConsoleNotify\n" -#~ " daemon/User\n" -#~ " daemon/Group\n" -#~ " daemon/LogDir\n" -#~ " daemon/ServAuthDir\n" -#~ " daemon/UserAuthDir\n" -#~ " daemon/UserAuthFile\n" -#~ " daemon/UserAuthFBDir\n" -#~ "\n" -#~ " GDM also supports the following Psuedokeys:\n" -#~ "\n" -#~ " xdmcp/PARAMETERS (2.3.90.2) updates the following:\n" -#~ " xdmcp/MaxPending\n" -#~ " xdmcp/MaxSessions\n" -#~ " xdmcp/MaxWait\n" -#~ " xdmcp/DisplaysPerHost\n" -#~ " xdmcp/HonorIndirect\n" -#~ " xdmcp/MaxPendingIndirect\n" -#~ " xdmcp/MaxWaitIndirect\n" -#~ " xdmcp/PingIntervalSeconds (only affects new " -#~ "connections)\n" -#~ "\n" -#~ " xservers/PARAMETERS (2.13.0.4) updates the following:\n" -#~ " all [server-foo] sections.\n" -#~ "\n" -#~ " Supported keys for previous versions of GDM:\n" -#~ "\n" -#~ " security/AllowRoot (2.3.90.2)\n" -#~ " security/AllowRemoteRoot (2.3.90.2)\n" -#~ " security/AllowRemoteAutoLogin (2.3.90.2)\n" -#~ " security/RetryDelay (2.3.90.2)\n" -#~ " security/DisallowTCP (2.4.2.0)\n" -#~ " daemon/Greeter (2.3.90.2)\n" -#~ " daemon/RemoteGreeter (2.3.90.2)\n" -#~ " xdmcp/Enable (2.3.90.2)\n" -#~ " xdmcp/Port (2.3.90.2)\n" -#~ " daemon/TimedLogin (2.3.90.3)\n" -#~ " daemon/TimedLoginEnable (2.3.90.3)\n" -#~ " daemon/TimedLoginDelay (2.3.90.3)\n" -#~ " greeter/SystemMenu (2.3.90.3)\n" -#~ " greeter/ConfigAvailable (2.3.90.3)\n" -#~ " greeter/ChooserButton (2.4.2.0)\n" -#~ " greeter/SoundOnLoginFile (2.5.90.0)\n" -#~ " daemon/AddGtkModules (2.5.90.0)\n" -#~ " daemon/GtkModulesList (2.5.90.0)\n" -#~ "Supported since: 2.3.90.2\n" -#~ "Arguments: <key>\n" -#~ " <key> is just the base part of the key such as\n" -#~ " \"security/AllowRemoteRoot\"\n" -#~ "Answers:\n" -#~ " OK\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 0 = Not implemented\n" -#~ " 50 = Unsupported key\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "VERSION" -#~ msgstr "VERSION" - -#~ msgid "" -#~ "\n" -#~ "VERSION: Query GDM version\n" -#~ "Supported since: 2.2.4.0\n" -#~ "Arguments: None\n" -#~ "Answers:\n" -#~ " GDM <gdm version>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" -#~ msgstr "" -#~ "\n" -#~ "VERSION: Query GDM version\n" -#~ "Supported since: 2.2.4.0\n" -#~ "Arguments: None\n" -#~ "Answers:\n" -#~ " GDM <gdm version>\n" -#~ " ERROR <err number> <english error description>\n" -#~ " 200 = Too many messages\n" -#~ " 999 = Unknown error\n" - -#~ msgid "GDM User Commands" -#~ msgstr "GDM User Commands" - -#~ msgid "" -#~ "The GDM package provides the following different commands in " -#~ "<filename>bindir</filename> intended to be used by the end-user:" -#~ msgstr "" -#~ "The GDM package provides the following different commands in " -#~ "<filename>bindir</filename> intended to be used by the end-user:" - -#~ msgid "" -#~ "<command>gdmXnestchooser</command> and <command>gdmXnest</command> " -#~ "Command Line Options" -#~ msgstr "" -#~ "<command>gdmXnestchooser</command> and <command>gdmXnest</command> " -#~ "Command Line Options" - -#~ msgid "" -#~ "The <command>gdmXnestchooser</command> command automatically gets the " -#~ "correct display number, sets up access, and runs <command>Xnest</command> " -#~ "with -indirect localhost. This way you get an XDMCP chooser provided by " -#~ "your computer. You can also supply as an argument the hostname whose " -#~ "chooser should be displayed, so <command>gdmXnestchooser somehost</" -#~ "command> will run the XDMCP chooser from host <command>somehost</command> " -#~ "inside an Xnest session. You can make this command do a direct query " -#~ "instead by passing the <command>-d</command> option as well. In addition " -#~ "to the following options, this command also supports standard GNOME " -#~ "options." -#~ msgstr "" -#~ "The <command>gdmXnestchooser</command> command automatically gets the " -#~ "correct display number, sets up access and runs <command>Xnest</command> " -#~ "with -indirect localhost. This way you get an XDMCP chooser provided by " -#~ "your computer. You can also supply as an argument the hostname whose " -#~ "chooser should be displayed, so <command>gdmXnestchooser somehost</" -#~ "command> will run the XDMCP chooser from host <command>somehost</command> " -#~ "inside an Xnest session. You can make this command do a direct query " -#~ "instead by passing the <command>-d</command> option as well. In addition " -#~ "to the following options, this command also supports standard GNOME " -#~ "options." - -#~ msgid "<command>gdmXnestchooser</command> Command Line Options" -#~ msgstr "<command>gdmXnestchooser</command> Command Line Options" - -#~ msgid "-x, --xnest=STRING" -#~ msgstr "-x, --xnest=STRING" - -#~ msgid "Xnest command line, default is \"Xnest\"" -#~ msgstr "Xnest command line, default is \"Xnest\"" - -#~ msgid "-o, --xnest-extra-options=OPTIONS" -#~ msgstr "-o, --xnest-extra-options=OPTIONS" - -#~ msgid "Extra options for Xnest, default is no options." -#~ msgstr "Extra options for Xnest, default is no options." - -#~ msgid "-n, --no-query" -#~ msgstr "-n, --no-query" - -#~ msgid "Just run Xnest, no query (no chooser)" -#~ msgstr "Just run Xnest, no query (no chooser)" - -#~ msgid "-d, --direct" -#~ msgstr "-d, --direct" - -#~ msgid "Do direct query instead of indirect (chooser)" -#~ msgstr "Do direct query instead of indirect (chooser)" - -#~ msgid "-B, --broadcast" -#~ msgstr "-B, --broadcast" - -#~ msgid "Run broadcast instead of indirect (chooser)" -#~ msgstr "Run broadcast instead of indirect (chooser)" - -#~ msgid "-b, --background" -#~ msgstr "-b, --background" - -#~ msgid "Run in background" -#~ msgstr "Run in background" - -#~ msgid "--no-gdm-check" -#~ msgstr "--no-gdm-check" - -#~ msgid "Don't check for running GDM" -#~ msgstr "Don't check for running GDM" - -#~ msgid "<command>gdmflexichooser</command> Command Line Options" -#~ msgstr "<command>gdmflexichooser</command> Command Line Options" - -#~ msgid "" -#~ "The <command>gdmflexiserver</command> command provides three features. It " -#~ "can be used to run flexible (on demand) X displays, to run a flexible " -#~ "display via Xnest, and to send commands to the GDM daemon process." -#~ msgstr "" -#~ "The <command>gdmflexiserver</command> command provides three features. It " -#~ "can be used to run flexible (on demand) X displays, to run a flexible " -#~ "display via Xnest, and to send commands to the GDM daemon process." - -#~ msgid "" -#~ "Starting a flexible X display will normally lock the current session with " -#~ "a screensaver and will redisplay the GDM login screen so a second user " -#~ "can log in. This feature is only available on systems that support " -#~ "virtual terminals and have them enabled. This feature is useful if you " -#~ "are logged in as user A, and user B wants to log in quickly but user A " -#~ "does not wish to log out. The X server takes care of the virtual terminal " -#~ "switching so it works transparently. If there is more than one running " -#~ "display defined with flexible=true, then the user is shown a dialog that " -#~ "displays the currently running sessions. The user can then pick which " -#~ "session to continue and will normally have to enter the password to " -#~ "unlock the screen." -#~ msgstr "" -#~ "Starting a flexible X display will normally lock the current session with " -#~ "a screensaver and will redisplay the GDM login screen so a second user " -#~ "can log in. This feature is only available on systems that support " -#~ "virtual terminals and have them enabled. This feature is useful if you " -#~ "are logged in as user A and user B wants to log in quickly but user A " -#~ "does not wish to log out. The X server takes care of the virtual terminal " -#~ "switching so it works transparently. If there is more than one running " -#~ "display defined with flexible=true, then the user is shown a dialogue " -#~ "that displays the currently running sessions. The user can then pick " -#~ "which session to continue and will normally have to enter the password to " -#~ "unlock the screen." - -#~ msgid "" -#~ "Flexible displays started via Xnest works on systems that do not support " -#~ "virtual terminals. This option starts a flexible display in a window in " -#~ "the current session. This does not lock the current session, so is not as " -#~ "secure as a flexible server started via virtual terminals." -#~ msgstr "" -#~ "Flexible displays started via Xnest works on systems that do not support " -#~ "virtual terminals. This option starts a flexible display in a window in " -#~ "the current session. This does not lock the current session, so is not as " -#~ "secure as a flexible server started via virtual terminals." - -#~ msgid "" -#~ "The <command>gdmflexiserver --command</command> option provides a way to " -#~ "send commands to the GDM daemon and can be used to debug problems or to " -#~ "change the GDM configuration." -#~ msgstr "" -#~ "The <command>gdmflexiserver --command</command> option provides a way to " -#~ "send commands to the GDM daemon and can be used to debug problems or to " -#~ "change the GDM configuration." - -#~ msgid "" -#~ "In addition to the following options, <command>gdmflexiserver</command> " -#~ "also supports standard GNOME options." -#~ msgstr "" -#~ "In addition to the following options, <command>gdmflexiserver</command> " -#~ "also supports standard GNOME options." - -#~ msgid "-c, --command=COMMAND" -#~ msgstr "-c, --command=COMMAND" - -#~ msgid "Send the specified protocol command to GDM" -#~ msgstr "Send the specified protocol command to GDM" - -#~ msgid "-n, --xnest" -#~ msgstr "-n, --xnest" - -#~ msgid "Start a flexible X display in Xnest mode" -#~ msgstr "Start a flexible X display in Xnest mode" - -#~ msgid "-l, --no-lock" -#~ msgstr "-l, --no-lock" - -#~ msgid "Do not lock current screen" -#~ msgstr "Do not lock current screen" - -#~ msgid "" -#~ "Turns on debugging output which gets sent to syslog. Same as turning on " -#~ "debug in the configuration file." -#~ msgstr "" -#~ "Turns on debugging output which gets sent to syslog. Same as turning on " -#~ "debug in the configuration file." - -#~ msgid "-a, --authenticate" -#~ msgstr "-a, --authenticate" - -#~ msgid "Authenticate before running --command" -#~ msgstr "Authenticate before running --command" - -#~ msgid "-s, --startnew" -#~ msgstr "-s, --startnew" - -#~ msgid "" -#~ "Starts a new flexible display without displaying a dialog asking the user " -#~ "if they wish to continue any existing sessions." -#~ msgstr "" -#~ "Starts a new flexible display without displaying a dialogue asking the " -#~ "user if they wish to continue any existing sessions." - -#~ msgid "<command>gdmdynamic</command> Command Line Options" -#~ msgstr "<command>gdmdynamic</command> Command Line Options" - -#~ msgid "" -#~ "The <command>gdmdynamic</command> command which creates, runs, and " -#~ "removes displays (X servers) on demand." -#~ msgstr "" -#~ "The <command>gdmdynamic</command> command which creates, runs, and " -#~ "removes displays (X servers) on demand." - -#~ msgid "" -#~ "<command>gdmdynamic</command> allows the management of displays in a " -#~ "dynamic fashion. It is typically used in environments where it is not " -#~ "possible to list the possible displays in the GDM configuration files. " -#~ "The <command>gdmdynamic</command> command can be used to create a new " -#~ "display on a particular display number, run all newly created displays, " -#~ "or remove a display. The <command>gdmdynamic</command> command can also " -#~ "be used to list all attached displays, or only attached displays that " -#~ "match a pattern." -#~ msgstr "" -#~ "<command>gdmdynamic</command> allows the management of displays in a " -#~ "dynamic fashion. It is typically used in environments where it is not " -#~ "possible to list the possible displays in the GDM configuration files. " -#~ "The <command>gdmdynamic</command> command can be used to create a new " -#~ "display on a particular display number, run all newly created displays, " -#~ "or remove a display. The <command>gdmdynamic</command> command can also " -#~ "be used to list all attached displays, or only attached displays that " -#~ "match a pattern." - -#~ msgid "" -#~ "This program is designed to manage multiple simultaneous requests and " -#~ "works to avoid flooding the daemon with requests. If the sockets " -#~ "connection is busy, it will sleep and retry a certain number of times " -#~ "that can be tuned with the -s and -t options." -#~ msgstr "" -#~ "This program is designed to manage multiple simultaneous requests and " -#~ "works to avoid flooding the daemon with requests. If the sockets " -#~ "connection is busy, it will sleep and retry a certain number of times " -#~ "that can be tuned with the -s and -t options." - -#~ msgid "One of the following options can be used per instance:" -#~ msgstr "One of the following options can be used per instance:" - -#~ msgid "-a display=server" -#~ msgstr "-a display=server" - -#~ msgid "" -#~ "Add a new display configuration, leaving it in the DISPLAY_CONFIG state. " -#~ "For example, <command>\"-a 2=StandardServerTwo\"</command><command>\"-a " -#~ "3=/usr/X11R6/bin/X -dev /dev/fb2\"</command>" -#~ msgstr "" -#~ "Add a new display configuration, leaving it in the DISPLAY_CONFIG state. " -#~ "For example, <command>\"-a 2=StandardServerTwo\"</command><command>\"-a " -#~ "3=/usr/X11R6/bin/X -dev /dev/fb2\"</command>" - -#~ msgid "" -#~ "The display will not actually be started until the display is released by " -#~ "calling <command>gdmdynamic</command> again with the -r option." -#~ msgstr "" -#~ "The display will not actually be started until the display is released by " -#~ "calling <command>gdmdynamic</command> again with the -r option." - -#~ msgid "-r" -#~ msgstr "-r" - -#~ msgid "Release (run) all displays waiting in the DISPLAY_CONFIG state." -#~ msgstr "Release (run) all displays waiting in the DISPLAY_CONFIG state." - -#~ msgid "-d display" -#~ msgstr "-d display" - -#~ msgid "" -#~ "Delete a display, killing the X server and purging the display " -#~ "configuration. For example, \"-d 3\"." -#~ msgstr "" -#~ "Delete a display, killing the X server and purging the display " -#~ "configuration. For example, \"-d 3\"." - -#~ msgid "-l [pattern]" -#~ msgstr "-l [pattern]" - -#~ msgid "" -#~ "List displays via the ATTACHED_SERVERS <command>gdmflexiserver</command> " -#~ "command. Without a pattern lists all attached displays. With a pattern " -#~ "will match using glob characters '*', '?', and '[]'. For example: " -#~ "<command>\"-l Standard*\"</command><command>\"-l *Xorg*\"</command>" -#~ msgstr "" -#~ "List displays via the ATTACHED_SERVERS <command>gdmflexiserver</command> " -#~ "command. Without a pattern lists all attached displays. With a pattern " -#~ "will match using glob characters '*', '?', and '[]'. For example: " -#~ "<command>\"-l Standard*\"</command><command>\"-l *Xorg*\"</command>" - -#~ msgid "These options can be added to the above:" -#~ msgstr "These options can be added to the above:" - -#~ msgid "-v" -#~ msgstr "-v" - -#~ msgid "" -#~ "Verbose mode. Prinr diagnostic messages about each message sent to GDM." -#~ msgstr "" -#~ "Verbose mode. Print diagnostic messages about each message sent to GDM." - -#~ msgid "-b" -#~ msgstr "-b" - -#~ msgid "Background mode. Fork child to do the work and return immediately." -#~ msgstr "Background mode. Fork child to do the work and return immediately." - -#~ msgid "-t RETRY" -#~ msgstr "-t RETRY" - -#~ msgid "" -#~ "If the daemon socket is busy, <command>gdmdynamic</command> will retry to " -#~ "open the connection the specified RETRY number of times. Default value is " -#~ "15." -#~ msgstr "" -#~ "If the daemon socket is busy, <command>gdmdynamic</command> will retry to " -#~ "open the connection the specified RETRY number of times. The default " -#~ "value is 15." - -#~ msgid "-s SLEEP" -#~ msgstr "-s SLEEP" - -#~ msgid "" -#~ "If the daemon socket is busy, <command>gdmdynamic</command> will sleep an " -#~ "amount of time between retries. A random number of seconds 0-5 is added " -#~ "to the SLEEP value to help ensure that multiple calls to gdmdynamic do " -#~ "not all try to restart at the same time. A SLEEP value of zero causes the " -#~ "sleep time to be 1 second. Default value is 8 seconds." -#~ msgstr "" -#~ "If the daemon socket is busy, <command>gdmdynamic</command> will sleep an " -#~ "amount of time between retries. A random number of seconds between 0 and " -#~ "5 is added to the SLEEP value to help ensure that multiple calls to " -#~ "gdmdynamic do not all try to restart at the same time. A SLEEP value of " -#~ "zero causes the sleep time to be 1 second. The default value is 8 seconds." - -#~ msgid "<command>gdmphotosetup</command> Command Line Options" -#~ msgstr "<command>gdmphotosetup</command> Command Line Options" - -#~ msgid "" -#~ "Allows the user to select an image that will be used as the user's photo " -#~ "by GDM's face browser, if enabled by GDM. The selected file is stored as " -#~ "<filename>~/.face</filename>. This command accepts standard GNOME options." -#~ msgstr "" -#~ "Allows the user to select an image that will be used as the user's photo " -#~ "by GDM's face browser, if enabled by GDM. The selected file is stored as " -#~ "<filename>~/.face</filename>. This command accepts the standard GNOME " -#~ "options." - -#~ msgid "<command>gdmthemetester</command> Command Line Options" -#~ msgstr "<command>gdmthemetester</command> Command Line Options" - -#~ msgid "" -#~ "<command>gdmthemetester</command> takes two parameters. The first " -#~ "parameter specifies the environment and the second parameter specifies " -#~ "the path name or the name of a theme to view. This is a tool for viewing " -#~ "a theme outside of GDM. It is useful for testing or viewing themes. " -#~ "<command>gdmthemetester</command> requires that the system support " -#~ "<command>gdmXnest</command>. Note that themes can display differently " -#~ "depending on the theme's \"Show mode\". <command>gdmthemetester</command> " -#~ "allows viewing the themes in different modes via the environment option. " -#~ "Valid environment values and their meanings follow: <screen>\n" -#~ "console - In console mode.\n" -#~ "console-timed - In console non-flexi mode.\n" -#~ "flexi - In flexi mode.\n" -#~ "xdmcp - In remote (XDMCP) mode.\n" -#~ "remote-flexi - In remote (XDMCP) & flexi mode.\n" -#~ "</screen>" -#~ msgstr "" -#~ "<command>gdmthemetester</command> takes two parameters. The first " -#~ "parameter specifies the environment and the second parameter specifies " -#~ "the path name or the name of a theme to view. This is a tool for viewing " -#~ "a theme outside of GDM. It is useful for testing or viewing themes. " -#~ "<command>gdmthemetester</command> requires that the system support " -#~ "<command>gdmXnest</command>. Note that themes can display differently " -#~ "depending on the theme's \"Show mode\". <command>gdmthemetester</command> " -#~ "allows viewing the themes in different modes via the environment option. " -#~ "Valid environment values and their meanings follow: <screen>\n" -#~ "console - In console mode.\n" -#~ "console-timed - In console non-flexi mode.\n" -#~ "flexi - In flexi mode.\n" -#~ "xdmcp - In remote (XDMCP) mode.\n" -#~ "remote-flexi - In remote (XDMCP) & flexi mode.\n" -#~ "</screen>" - -#~ msgid "--nodaemon" -#~ msgstr "--nodaemon" - -#~ msgid "" -#~ "If this option is specified, then GDM does not fork into the background " -#~ "when run. You can also use a single-dash version, \"-nodaemon\" for " -#~ "compatibility with other display managers." -#~ msgstr "" -#~ "If this option is specified, then GDM does not fork into the background " -#~ "when run. You can also use a single-dash version, \"-nodaemon\" for " -#~ "compatibility with other display managers." - -#~ msgid "--no-console" -#~ msgstr "--no-console" - -#~ msgid "" -#~ "Tell the daemon that it should not run anything on the console. This " -#~ "means that none of the local servers from the <filename>[servers]</" -#~ "filename> section will be run, and the console will not be used for " -#~ "communicating errors to the user. An empty <filename>[servers]</filename> " -#~ "section automatically implies this option." -#~ msgstr "" -#~ "Tell the daemon that it should not run anything on the console. This " -#~ "means that none of the local servers from the <filename>[servers]</" -#~ "filename> section will be run, and the console will not be used for " -#~ "communicating errors to the user. An empty <filename>[servers]</filename> " -#~ "section automatically implies this option." - -#~ msgid "--config=CONFIGFILE" -#~ msgstr "--config=CONFIGFILE" - -#~ msgid "Specify an alternative configuration file." -#~ msgstr "Specify an alternative configuration file." - -#~ msgid "--preserve-ld-vars" -#~ msgstr "--preserve-ld-vars" - -#~ msgid "" -#~ "When clearing the environment internally, preserve all variables starting " -#~ "with LD_. This is mostly for debugging purposes." -#~ msgstr "" -#~ "When clearing the environment internally, preserve all variables starting " -#~ "with LD_. This is mostly for debugging purposes." - -#~ msgid "--wait-for-go" -#~ msgstr "--wait-for-go" - -#~ msgid "" -#~ "If started with this option, gdm will init, but only start the first " -#~ "local display and then wait for a GO message in the fifo protocol. No " -#~ "greeter will be shown until the GO message is sent. Also flexiserver " -#~ "requests will be denied and XDMCP will not be started until GO is given. " -#~ "This is useful for initialization scripts which wish to start X early, " -#~ "but where you don't yet want the user to start logging in. So the script " -#~ "would send the GO to the fifo once it is ready and GDM will then " -#~ "continue. This functionality was added in version 2.5.90.0." -#~ msgstr "" -#~ "If started with this option, gdm will init, but only start the first " -#~ "local display and then wait for a GO message in the fifo protocol. No " -#~ "greeter will be shown until the GO message is sent. Also flexiserver " -#~ "requests will be denied and XDMCP will not be started until GO is given. " -#~ "This is useful for initialisation scripts which wish to start X early, " -#~ "but where you don't yet want the user to start logging in. So the script " -#~ "would send the GO to the fifo once it is ready and GDM will then " -#~ "continue. This functionality was added in version 2.5.90.0." - -#~ msgid "<command>gdmsetup</command> Command Line Options" -#~ msgstr "<command>gdmsetup</command> Command Line Options" - -#~ msgid "" -#~ "<command>gdmsetup</command> runs a graphical application for modifying " -#~ "the GDM configuration file. Normally on systems that support the PAM " -#~ "userhelper, this is setup such that when you run <command>gdmsetup</" -#~ "command> as an ordinary user, it will first ask you for your root " -#~ "password before starting. Otherwise, this application may only be run as " -#~ "root. This application supports standard GNOME options." -#~ msgstr "" -#~ "<command>gdmsetup</command> runs a graphical application for modifying " -#~ "the GDM configuration file. Normally on systems that support the PAM user " -#~ "helper, this is set up such that when you run <command>gdmsetup</command> " -#~ "as an ordinary user, it will first ask you for your root password before " -#~ "starting. Otherwise, this application may only be run as root. This " -#~ "application supports standard GNOME options." - -#~ msgid "GDM Internal Commands" -#~ msgstr "GDM Internal Commands" - -#~ msgid "" -#~ "The GDM package provides the following different commands in " -#~ "<filename>libexecdir</filename> intended to be used by the gdm daemon " -#~ "process." -#~ msgstr "" -#~ "The GDM package provides the following different commands in " -#~ "<filename>libexecdir</filename> intended to be used by the gdm daemon " -#~ "process." - -#~ msgid "" -#~ "<command>gdmchooser</command> and <command>gdmlogin</command> Command " -#~ "Line Options" -#~ msgstr "" -#~ "<command>gdmchooser</command> and <command>gdmlogin</command> Command " -#~ "Line Options" - -#~ msgid "" -#~ "The <command>gdmgreeter</command> and <command>gdmlogin</command> are two " -#~ "different login applications, either can be used by GDM. " -#~ "<command>gdmgreeter</command> is themeable with GDM themes while " -#~ "<command>gdmlogin</command> is themable with GTK+ themes. These " -#~ "applications are normally executed by the GDM daemon. Both commands " -#~ "support standard GNOME options." -#~ msgstr "" -#~ "The <command>gdmgreeter</command> and <command>gdmlogin</command> are two " -#~ "different login applications, either can be used by GDM. " -#~ "<command>gdmgreeter</command> is themeable with GDM themes while " -#~ "<command>gdmlogin</command> is themable with GTK+ themes. These " -#~ "applications are normally executed by the GDM daemon. Both commands " -#~ "support standard GNOME options." - -#~ msgid "<command>gdmchooser</command> Command Line Options" -#~ msgstr "<command>gdmchooser</command> Command Line Options" - -#~ msgid "" -#~ "The <command>gdmchooser</command> is the XDMCP chooser application. The " -#~ "<command>gdmchooser</command> is normally executed by the GDM daemon. It " -#~ "supports the following options for XDM compatibility. This command " -#~ "supports standard GNOME options and is found in support standard GNOME " -#~ "options." -#~ msgstr "" -#~ "The <command>gdmchooser</command> is the XDMCP chooser application. The " -#~ "<command>gdmchooser</command> is normally executed by the GDM daemon. It " -#~ "supports the following options for XDM compatibility. This command " -#~ "supports standard GNOME options and is found in support standard GNOME " -#~ "options." - -#~ msgid "--xdmaddress=SOCKET" -#~ msgstr "--xdmaddress=SOCKET" - -#~ msgid "Socket for XDM communication." -#~ msgstr "Socket for XDM communication." - -#~ msgid "--clientaddress=ADDRESS" -#~ msgstr "--clientaddress=ADDRESS" - -#~ msgid "" -#~ "Client address to return in response to XDM. This option is for running " -#~ "gdmchooser with XDM, and is not used within GDM." -#~ msgstr "" -#~ "Client address to return in response to XDM. This option is for running " -#~ "gdmchooser with XDM, and is not used within GDM." - -#~ msgid "--connectionType=TYPE" -#~ msgstr "--connectionType=TYPE" - -#~ msgid "" -#~ "Connection type to return in response to XDM. This option is for running " -#~ "gdmchooser with XDM, and is not used within GDM." -#~ msgstr "" -#~ "Connection type to return in response to XDM. This option is for running " -#~ "gdmchooser with XDM, and is not used within GDM." - -#~ msgid "gdm-ssh-session" -#~ msgstr "gdm-ssh-session" - -#~ msgid "" -#~ "The <command>gdm-ssh-session</command> is normally executed by the GDM " -#~ "daemon when starting a secure remote connection through ssh. It does not " -#~ "take any options." -#~ msgstr "" -#~ "The <command>gdm-ssh-session</command> is normally executed by the GDM " -#~ "daemon when starting a secure remote connection through ssh. It does not " -#~ "take any options." - -#~ msgid "Themed Greeter" -#~ msgstr "Themed Greeter" - -#~ msgid "" -#~ "This section describes the creation of themes for the Themed Greeter. For " -#~ "examples including screenshots, see the standard installed themes and the " -#~ "themes from <ulink type=\"http\" url=\"http://art.gnome.org/themes/" -#~ "gdm_greeter/\"> the theme website</ulink>." -#~ msgstr "" -#~ "This section describes the creation of themes for the Themed Greeter. For " -#~ "examples including screenshots, see the standard installed themes and the " -#~ "themes from <ulink type=\"http\" url=\"http://art.gnome.org/themes/" -#~ "gdm_greeter/\"> the theme website</ulink>." - -#~ msgid "Theme Overview" -#~ msgstr "Theme Overview" - -#~ msgid "" -#~ "GDM Themes can be created by creating an XML file that follows the " -#~ "specification in gui/greeter/greeter.dtd. Theme files are stored in the " -#~ "directory <filename><share>/gdm/themes/<theme_name></" -#~ "filename>. Usually this would be under <filename>/usr/share</filename>. " -#~ "The theme directory should contain a file called " -#~ "<filename>GdmGreeterTheme.desktop</filename> which has similar format to " -#~ "other .desktop files and looks like:" -#~ msgstr "" -#~ "GDM Themes can be created by creating an XML file that follows the " -#~ "specification in gui/greeter/greeter.dtd. Theme files are stored in the " -#~ "directory <filename><share>/gdm/themes/<theme_name></" -#~ "filename>. Usually this would be under <filename>/usr/share</filename>. " -#~ "The theme directory should contain a file called " -#~ "<filename>GdmGreeterTheme.desktop</filename> which has similar format to " -#~ "other .desktop files and looks like:" - -#~ msgid "" -#~ "\n" -#~ "[GdmGreeterTheme]\n" -#~ "Encoding=UTF-8\n" -#~ "Greeter=circles.xml\n" -#~ "Name=Circles\n" -#~ "Description=Theme with blue circles\n" -#~ "Author=Bond, James Bond\n" -#~ "Copyright=(c) 2002 Bond, James Bond\n" -#~ "Screenshot=screenshot.png\n" -#~ msgstr "" -#~ "\n" -#~ "[GdmGreeterTheme]\n" -#~ "Encoding=UTF-8\n" -#~ "Greeter=circles.xml\n" -#~ "Name=Circles\n" -#~ "Description=Theme with blue circles\n" -#~ "Author=Bond, James Bond\n" -#~ "Copyright=(c) 2002 Bond, James Bond\n" -#~ "Screenshot=screenshot.png\n" - -#~ msgid "" -#~ "The Name, Description, Author and Copyright fields can be translated just " -#~ "like the other <filename>.desktop</filename>files. All the files that are " -#~ "mentioned should be in the theme directory itself. The Screenshot field " -#~ "points to a file which should be a 200x150 screenshot of the theme in " -#~ "action (it is OK not to have one, but it makes it nicer for user). The " -#~ "Greeter field points to an XML file that contains the description of the " -#~ "theme. The description will be given later." -#~ msgstr "" -#~ "The Name, Description, Author and Copyright fields can be translated just " -#~ "like the other <filename>.desktop</filename>files. All the files that are " -#~ "mentioned should be in the theme directory itself. The Screenshot field " -#~ "points to a file which should be a 200x150 screenshot of the theme in " -#~ "action (it is OK not to have one, but it makes it nicer for user). The " -#~ "Greeter field points to an XML file that contains the description of the " -#~ "theme. The description will be given later." - -#~ msgid "" -#~ "Once you have theme ready and installed you can test it with the " -#~ "installed <command>gdmthemetester</command> script. This script assumes " -#~ "that the X server supports Xnest. This command takes two arguments, first " -#~ "the environment that should be used. This is one of console, console-" -#~ "timed, flexi, remote-flexi, xdmcp. Where console is a standard console " -#~ "login, console-timed is a console login with a timed login going on, " -#~ "flexi is for any local flexible display, remote-flexi is for flexi " -#~ "displays that are not local (such as an Xnest flexiserver run from a " -#~ "remote display) and xdmcp is for remote XDMCP connections. The second " -#~ "argument is the theme name. So for example to test how things look in the " -#~ "XDMCP mode with the circles theme you would run:" -#~ msgstr "" -#~ "Once you have theme ready and installed you can test it with the " -#~ "installed <command>gdmthemetester</command> script. This script assumes " -#~ "that the X server supports Xnest. This command takes two arguments, first " -#~ "the environment that should be used. This is one of console, console-" -#~ "timed, flexi, remote-flexi, xdmcp. Where console is a standard console " -#~ "login, console-timed is a console login with a timed login going on, " -#~ "flexi is for any local flexible display, remote-flexi is for flexi " -#~ "displays that are not local (such as an Xnest flexiserver run from a " -#~ "remote display) and xdmcp is for remote XDMCP connections. The second " -#~ "argument is the theme name. So for example to test how things look in the " -#~ "XDMCP mode with the circles theme you would run:" - -#~ msgid "gdmthemetester xdmcp circles" -#~ msgstr "gdmthemetester xdmcp circles" - -#~ msgid "" -#~ "Be sure to test all the environments with your theme, and make sure to " -#~ "test how the caps lock warning looks by pressing caps lock. This is also " -#~ "a good way to take screenshots, just take a screenshot of the Xnest " -#~ "window. This can be done in GNOME by focusing the Xnest window and " -#~ "pressing Alt-PrintScreen." -#~ msgstr "" -#~ "Be sure to test all the environments with your theme, and make sure to " -#~ "test how the caps lock warning looks by pressing caps lock. This is also " -#~ "a good way to take screenshots, just take a screenshot of the Xnest " -#~ "window. This can be done in GNOME by focusing the Xnest window and " -#~ "pressing Alt-PrintScreen." - -#~ msgid "" -#~ "Once you have all this done, then make a tarball that contains the " -#~ "directory name (so that you could just untar it in the <filename><" -#~ "share>/gdm/themes</filename> directory). And this is the tarball you " -#~ "distribute and people can install from the graphical configuration " -#~ "application. You can do this with the commands: <screen>\n" -#~ "cd <share>/gdm/themes\n" -#~ "tar czvf <theme_name>.tar.gz <theme_name>/\n" -#~ "</screen>" -#~ msgstr "" -#~ "Once you have all this done, then make a tarball that contains the " -#~ "directory name (so that you could just untar it in the <filename><" -#~ "share>/gdm/themes</filename> directory). And this is the tarball you " -#~ "distribute and people can install from the graphical configuration " -#~ "application. You can do this with the commands: <screen>\n" -#~ "cd <share>/gdm/themes\n" -#~ "tar czvf <theme_name>.tar.gz <theme_name>/\n" -#~ "</screen>" - -#~ msgid "Detailed Description of Theme XML format" -#~ msgstr "Detailed Description of Theme XML format" - -#~ msgid "greeter tag" -#~ msgstr "greeter tag" - -#~ msgid "" -#~ "The GDM theme format is specified in XML format contained within a <" -#~ "greeter> tag. You may specify a GTK+ theme to be used with this theme " -#~ "by using the gtk-theme element in the greeter tag as in the following " -#~ "example." -#~ msgstr "" -#~ "The GDM theme format is specified in XML format contained within a <" -#~ "greeter> tag. You may specify a GTK+ theme to be used with this theme " -#~ "by using the gtk-theme element in the greeter tag as in the following " -#~ "example." - -#~ msgid "" -#~ "\n" -#~ "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" -#~ "<!DOCTYPE greeter SYSTEM \"greeter.dtd\">\n" -#~ "<greeter gtk-theme=\"Crux\">\n" -#~ "[...]\n" -#~ "</greeter>\n" -#~ msgstr "" -#~ "\n" -#~ "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" -#~ "<!DOCTYPE greeter SYSTEM \"greeter.dtd\">\n" -#~ "<greeter gtk-theme=\"Crux\">\n" -#~ "[...]\n" -#~ "</greeter>\n" - -#~ msgid "" -#~ "Contained within the greeter tag can be the nodes described in the next " -#~ "sections of this document. Some of these nodes are containers (box nodes, " -#~ "rect item nodes) which can be used to organize how to display the nodes " -#~ "that the user sees and interacts with (such as button, pixmap and entry " -#~ "item nodes)." -#~ msgstr "" -#~ "Contained within the greeter tag can be the nodes described in the next " -#~ "sections of this document. Some of these nodes are containers (box nodes, " -#~ "rect item nodes) which can be used to organize how to display the nodes " -#~ "that the user sees and interacts with (such as button, pixmap and entry " -#~ "item nodes)." - -#~ msgid "Box Nodes" -#~ msgstr "Box Nodes" - -#~ msgid "" -#~ "Box nodes are container nodes for item nodes. Box nodes are specified as " -#~ "follows: <screen>\n" -#~ "<box orientation=\"alignment\" min-width=\"num\"\n" -#~ "xpadding=\"num\" ypadding=\"num\" spacing=\"num\"\n" -#~ "homogeneous=\"bool\">\n" -#~ "</screen> Where \"num\" means number and bool means either \"true\" or " -#~ "\"false\" The alignment value can be either \"horizontal\" or \"vertical" -#~ "\". If you leave any property off it will default to zero or \"false\" in " -#~ "case of \"homogeneous\" and \"vertical\" for the orientation." -#~ msgstr "" -#~ "Box nodes are container nodes for item nodes. Box nodes are specified as " -#~ "follows: <screen>\n" -#~ "<box orientation=\"alignment\" min-width=\"num\"\n" -#~ "xpadding=\"num\" ypadding=\"num\" spacing=\"num\"\n" -#~ "homogeneous=\"bool\">\n" -#~ "</screen> Where \"num\" means number and bool means either \"true\" or " -#~ "\"false\" The alignment value can be either \"horizontal\" or \"vertical" -#~ "\". If you leave any property off it will default to zero or \"false\" in " -#~ "case of \"homogeneous\" and \"vertical\" for the orientation." - -#~ msgid "" -#~ "If the box is homogeneous then the children are allocated equal amount of " -#~ "space." -#~ msgstr "" -#~ "If the box is homogeneous then the children are allocated equal amount of " -#~ "space." - -#~ msgid "" -#~ "The \"min-width\" must be specified in pixels. Obviously there is also a " -#~ "corresponding \"min-height\" property as well." -#~ msgstr "" -#~ "The \"min-width\" must be specified in pixels. Obviously there is also a " -#~ "corresponding \"min-height\" property as well." - -#~ msgid "Fixed Nodes" -#~ msgstr "Fixed Nodes" - -#~ msgid "" -#~ "Fixed is a container that has its children scattered about laid out with " -#~ "precise coordinates. The size of this container is the biggest rectangle " -#~ "that contains all the children. Fixed has no extra properties and so you " -#~ "just use: <screen>\n" -#~ "<fixed>\n" -#~ "</screen> Then you put other items with proper position nodes inside this." -#~ msgstr "" -#~ "Fixed is a container that has its children scattered about laid out with " -#~ "precise co-ordinates. The size of this container is the largest rectangle " -#~ "that contains all the children. Fixed has no extra properties and so you " -#~ "just use: <screen>\n" -#~ "<fixed>\n" -#~ "</screen> Then you put other items with proper position nodes inside this." - -#~ msgid "The \"toplevel\" node is really just like a fixed node." -#~ msgstr "The \"toplevel\" node is really just like a fixed node." - -#~ msgid "Item Nodes" -#~ msgstr "Item Nodes" - -#~ msgid "" -#~ "A GDM Theme is created by specifying a hierarchy of item and box nodes. " -#~ "Item nodes can have the following value for \"type\":" -#~ msgstr "" -#~ "A GDM Theme is created by specifying a hierarchy of item and box nodes. " -#~ "Item nodes can have the following value for \"type\":" - -#~ msgid "button" -#~ msgstr "button" - -#~ msgid "" -#~ "A button field. This field uses a GTK+ button. It is also possible to " -#~ "make a \"rect\" item act like a button by setting its button element to " -#~ "true. However it is better to use GTK+ buttons in GDM themes since these " -#~ "are accessible to users with disabilities. Also, GTK+ buttons can be " -#~ "themed. This feature is supported in GDM 2.14.6 and later." -#~ msgstr "" -#~ "A button field. This field uses a GTK+ button. It is also possible to " -#~ "make a \"rect\" item act like a button by setting its button element to " -#~ "true. However it is better to use GTK+ buttons in GDM themes since these " -#~ "are accessible to users with disabilities. Also, GTK+ buttons can be " -#~ "themed. This feature is supported in GDM 2.14.6 and later." - -#~ msgid "entry" -#~ msgstr "entry" - -#~ msgid "Text entry field." -#~ msgstr "Text entry field." - -#~ msgid "label" -#~ msgstr "label" - -#~ msgid "A text label. Must have a \"text\" node to specify the text." -#~ msgstr "A text label. Must have a \"text\" node to specify the text." - -#~ msgid "list" -#~ msgstr "list" - -#~ msgid "" -#~ "A face browser widget. Only useful if the face browser is enabled via the " -#~ "configuration." -#~ msgstr "" -#~ "A face browser widget. Only useful if the face browser is enabled via the " -#~ "configuration." - -#~ msgid "pixmap" -#~ msgstr "pixmap" - -#~ msgid "" -#~ "An pixmap image in a format that gdk-pixbuf supports like PNG, JPEG, " -#~ "Tiff, etc...)" -#~ msgstr "" -#~ "An pixmap image in a format that gdk-pixbuf supports like PNG, JPEG, " -#~ "Tiff, etc...)" - -#~ msgid "rect" -#~ msgstr "rect" - -#~ msgid "Rectangle." -#~ msgstr "Rectangle." - -#~ msgid "svg" -#~ msgstr "svg" - -#~ msgid "Scaled Vector Graphic image." -#~ msgstr "Scaled Vector Graphic image." - -#~ msgid "" -#~ "For example: <screen>\n" -#~ "<item type=\"label\">\n" -#~ "</screen> Items can specify ID values which gives them a specific look " -#~ "and feel or formatting. Furthermore you can customize the login process " -#~ "by adding custom widgets with custom id's for some items (currently only " -#~ "the list item)" -#~ msgstr "" -#~ "For example: <screen>\n" -#~ "<item type=\"label\">\n" -#~ "</screen> Items can specify ID values which gives them a specific look " -#~ "and feel or formatting. Furthermore you can customise the login process " -#~ "by adding custom widgets with custom id's for some items (currently only " -#~ "the list item)" - -#~ msgid "Entry items can have id values as follows:" -#~ msgstr "Entry items can have id values as follows:" - -#~ msgid "user-pw-entry" -#~ msgstr "user-pw-entry" - -#~ msgid "" -#~ "Entry field for userid and password entry. This is the field used for " -#~ "responses for the PAM/GDM questions (Username, Password, etc..)." -#~ msgstr "" -#~ "Entry field for userid and password entry. This is the field used for " -#~ "responses for the PAM/GDM questions (Username, Password, etc..)." - -#~ msgid "" -#~ "List items by default display as lists, but the combo=\"true\" attribute " -#~ "can be used to specify combo box style (combo style supported since GDM " -#~ "2.16.2). Some predefined lists may be included in a theme by using the " -#~ "following id values. Customized lists may also be defined, which are " -#~ "explained below." -#~ msgstr "" -#~ "List items by default display as lists, but the combo=\"true\" attribute " -#~ "can be used to specify combo box style (combo style supported since GDM " -#~ "2.16.2). Some predefined lists may be included in a theme by using the " -#~ "following id values. Customised lists may also be defined, which are " -#~ "explained below." - -#~ msgid "session" -#~ msgstr "session" - -#~ msgid "" -#~ "A list of available sessions, which allows the user to pick the session " -#~ "to use. Supported since GDM 2.16.2." -#~ msgstr "" -#~ "A list of available sessions, which allows the user to pick the session " -#~ "to use. Supported since GDM 2.16.2." - -#~ msgid "language" -#~ msgstr "language" - -#~ msgid "" -#~ "A list of available languages, which allows the user to pick the language " -#~ "to use. Supported since GDM 2.16.2." -#~ msgstr "" -#~ "A list of available languages, which allows the user to pick the language " -#~ "to use. Supported since GDM 2.16.2." - -#~ msgid "userlist" -#~ msgstr "userlist" - -#~ msgid "" -#~ "A Face Browser list, so that users can pick their username by clicking on " -#~ "this instead of typing. This obviously exposes the usernames to viewers " -#~ "of the login screen, and is not recommended for users who feel that this " -#~ "reduces security. The face browser does not support combo box style." -#~ msgstr "" -#~ "A Face Browser list, so that users can pick their username by clicking on " -#~ "this instead of typing. This obviously exposes the usernames to viewers " -#~ "of the login screen, and is not recommended for users who feel that this " -#~ "reduces security. The face browser does not support combo box style." - -#~ msgid "userlist-rect" -#~ msgstr "userlist-rect" - -#~ msgid "" -#~ "This id can be specified for the <rect> object containing the " -#~ "userlist and if the userlist is empty then this rectangle will not be " -#~ "shown. This allows the theme to define something like an area with a " -#~ "different color and/or alpha to surround the userlist, but only if there " -#~ "are users to display. Supported since 2.16.2." -#~ msgstr "" -#~ "This id can be specified for the <rect> object containing the " -#~ "userlist and if the userlist is empty then this rectangle will not be " -#~ "shown. This allows the theme to define something like an area with a " -#~ "different colour and/or alpha to surround the userlist, but only if there " -#~ "are users to display. Supported since 2.16.2." - -#~ msgid "" -#~ "Furthermore, you can have an arbitrary id (I'd recommend starting the id " -#~ "with 'custom' not to conflict with future additions to this spec) and ask " -#~ "extra information of the user. See the section 'Custom Widgetry'" -#~ msgstr "" -#~ "Furthermore, you can have an arbitrary id (I'd recommend starting the id " -#~ "with 'custom' not to conflict with future additions to this spec) and ask " -#~ "extra information of the user. See the section 'Custom Widgetry'" - -#~ msgid "Label items can have id values as follows:" -#~ msgstr "Label items can have id values as follows:" - -#~ msgid "clock" -#~ msgstr "clock" - -#~ msgid "Label that displays the date and time." -#~ msgstr "Label that displays the date and time." - -#~ msgid "pam-prompt" -#~ msgstr "pam-prompt" - -#~ msgid "" -#~ "Label that displays the PAM prompt. This is the prompt that PAM uses to " -#~ "ask for username, password, etc..." -#~ msgstr "" -#~ "Label that displays the PAM prompt. This is the prompt that PAM uses to " -#~ "ask for username, password, etc..." - -#~ msgid "pam-error" -#~ msgstr "pam-error" - -#~ msgid "" -#~ "Label that displayst PAM/GDM error messages. Such as when user can't log " -#~ "in." -#~ msgstr "" -#~ "Label that displayst PAM/GDM error messages. Such as when user can't log " -#~ "in." - -#~ msgid "pam-error-logo" -#~ msgstr "pam-error-logo" - -#~ msgid "" -#~ "An image that will be displayed only when a pam-error message is being " -#~ "displayed. This is useful for displaying an \"Attention\" icon, for " -#~ "example. This feature is supported in GDM 2.14.6 and later." -#~ msgstr "" -#~ "An image that will be displayed only when a pam-error message is being " -#~ "displayed. This is useful for displaying an \"Attention\" icon, for " -#~ "example. This feature is supported in GDM 2.14.6 and later." - -#~ msgid "pam-message" -#~ msgstr "pam-message" - -#~ msgid "" -#~ "Label that displays the PAM message. These are messages that PAM/GDM " -#~ "gives about state of the account, help about the prompts and other " -#~ "information." -#~ msgstr "" -#~ "Label that displays the PAM message. These are messages that PAM/GDM " -#~ "gives about state of the account, help about the prompts and other " -#~ "information." - -#~ msgid "Label that displays timed login information." -#~ msgstr "Label that displays timed login information." - -#~ msgid "Rectangles can have id values as follows:" -#~ msgstr "Rectangles can have id values as follows:" - -#~ msgid "" -#~ "Displays an icon that shows if the CAPS LOCK key is depressed. This " -#~ "rectangle will be hidden/shown appropriately" -#~ msgstr "" -#~ "Displays an icon that shows if the CAPS LOCK key is depressed. This " -#~ "rectangle will be hidden/shown appropriately" - -#~ msgid "" -#~ "If an item is of type rect, the item can be a button. Buttons must also " -#~ "include a \"button\" value as follows: <screen>\n" -#~ "<item type=\"rect\" id=\"disconnect_button\" button=\"true\">.\n" -#~ "</screen>" -#~ msgstr "" -#~ "If an item is of type rect, the item can be a button. Buttons must also " -#~ "include a \"button\" value as follows: <screen>\n" -#~ "<item type=\"rect\" id=\"disconnect_button\" button=\"true\">.\n" -#~ "</screen>" - -#~ msgid "Possible values for button ids are as follows." -#~ msgstr "Possible values for button ids are as follows." - -#~ msgid "chooser_button" -#~ msgstr "chooser_button" - -#~ msgid "Runs the XDMCP chooser." -#~ msgstr "Runs the XDMCP chooser." - -#~ msgid "config_button" -#~ msgstr "config_button" - -#~ msgid "Runs the GDM configuration application." -#~ msgstr "Runs the GDM configuration application." - -#~ msgid "custom_cmd_button[0-9]" -#~ msgstr "custom_cmd_button[0-9]" - -#~ msgid "Runs the <filename>n-th</filename> custom command." -#~ msgstr "Runs the <filename>n-th</filename> custom command." - -#~ msgid "disconnect_button" -#~ msgstr "disconnect_button" - -#~ msgid "Disconnect from remote session." -#~ msgstr "Disconnect from remote session." - -#~ msgid "language_button" -#~ msgstr "language_button" - -#~ msgid "Displays the language selection dialog." -#~ msgstr "Displays the language selection dialogue." - -#~ msgid "halt_button" -#~ msgstr "halt_button" - -#~ msgid "Halt (shuts down) the system." -#~ msgstr "Halt (shuts down) the system." - -#~ msgid "reboot_button" -#~ msgstr "reboot_button" - -#~ msgid "Restart the system." -#~ msgstr "Restart the system." - -#~ msgid "session_button" -#~ msgstr "session_button" - -#~ msgid "List and select from available sessions." -#~ msgstr "List and select from available sessions." - -#~ msgid "suspend_button" -#~ msgstr "suspend_button" - -#~ msgid "Suspend the system." -#~ msgstr "Suspend the system." - -#~ msgid "system_button" -#~ msgstr "system_button" - -#~ msgid "" -#~ "Perform halt/restart/suspend/etc. options (if allowed by GDM " -#~ "configuration). Also allows user to run configurator if user enters root " -#~ "password (again if allowed by GDM configuration). This is usually now " -#~ "labeled Actions, and referred to as the Actions menu." -#~ msgstr "" -#~ "Perform halt/restart/suspend/etc. options (if allowed by GDM " -#~ "configuration). Also allows the user to run configurator if the user " -#~ "enters the root password (if allowed by the GDM configuration). This is " -#~ "labelled Actions, and referred to as the Actions menu." - -#~ msgid "Position Node" -#~ msgstr "Position Node" - -#~ msgid "" -#~ "Each item can specify its position and size via the \"pos\" node. For " -#~ "example: <screen>\n" -#~ "<pos x=\"0\" y=\"4\" width=\"100%\" height=\"100%\"/>\n" -#~ "</screen>" -#~ msgstr "" -#~ "Each item can specify its position and size via the \"pos\" node. For " -#~ "example: <screen>\n" -#~ "<pos x=\"0\" y=\"4\" width=\"100%\" height=\"100%\"/>\n" -#~ "</screen>" - -#~ msgid "" -#~ "Both position and size can be given in percent and it will be taken as " -#~ "the percentage of the size of the current container. For toplevel items " -#~ "it's the percentage of the whole screen." -#~ msgstr "" -#~ "Both position and size can be given in percent and it will be taken as " -#~ "the percentage of the size of the current container. For toplevel items " -#~ "it's the percentage of the whole screen." - -#~ msgid "" -#~ "For x and y, you can also specify a negative position which means " -#~ "position from the right or bottom edge. But this only applies with " -#~ "absolute coordinates. With percentage you can specify negative position " -#~ "and it will be still from the same edge." -#~ msgstr "" -#~ "For x and y, you can also specify a negative position which means " -#~ "position from the right or bottom edge. But this only applies with " -#~ "absolute coordinates. With percentage you can specify negative position " -#~ "and it will be still from the same edge." - -#~ msgid "" -#~ "The position also specifies the anchor of the item, this can be \"n\" \"ne" -#~ "\" \"e\" \"se\" \"s\" \"sw\" \"w\" and \"nw\" or \"center\" which stand " -#~ "for the different edges/corners or \"center\" for center. For example: " -#~ "<screen>\n" -#~ "<pos x=\"10%\" y=\"50%\" anchor=\"w\" width=\"80%\" height=\"95\"/" -#~ ">\n" -#~ "</screen>" -#~ msgstr "" -#~ "The position also specifies the anchor of the item, this can be \"n\" \"ne" -#~ "\" \"e\" \"se\" \"s\" \"sw\" \"w\" and \"nw\" or \"center\" which stand " -#~ "for the different edges/corners or \"center\" for centre. For example: " -#~ "<screen>\n" -#~ "<pos x=\"10%\" y=\"50%\" anchor=\"w\" width=\"80%\" height=\"95\"/" -#~ ">\n" -#~ "</screen>" - -#~ msgid "" -#~ "If the item contains a box, you can specify width and height to be \"box" -#~ "\" to mean that they are supposed to be the width and height of the box, " -#~ "that is the items in the box plus the padding." -#~ msgstr "" -#~ "If the item contains a box, you can specify width and height to be \"box" -#~ "\" to mean that they are supposed to be the width and height of the box, " -#~ "that is the items in the box plus the padding." - -#~ msgid "" -#~ "If the item contains an SVG image, you can specify width and height to be " -#~ "\"scale\" to mean that the SVG image should be scaled to fit the " -#~ "requested area." -#~ msgstr "" -#~ "If the item contains an SVG image, you can specify width and height to be " -#~ "\"scale\" to mean that the SVG image should be scaled to fit the " -#~ "requested area." - -#~ msgid "" -#~ "You can also specify an \"expand\" property to either be \"true\" or " -#~ "false. If true then the child will be expanded in the box as much as " -#~ "possible (that is it will be given more space if available)." -#~ msgstr "" -#~ "You can also specify an \"expand\" property to either be \"true\" or " -#~ "false. If true then the child will be expanded in the box as much as " -#~ "possible (that is it will be given more space if available)." - -#~ msgid "" -#~ "There are two extra properties you can specify (as of 2.4.4.3) for labels " -#~ "(and labels only). The first is \"max-width\" which will specify the " -#~ "maximum width of the label in pixels. And the second is \"max-screen-" -#~ "percent-width\" which specifies the maximum percentage of the screen " -#~ "width that the label can occupy. By default no label will occupy more " -#~ "then 90% of the screen by width. An example may be: <screen>\n" -#~ "<item type=\"label\">\n" -#~ "<pos x=\"10%\" max-screen-percent-width=\"50%\"/>\n" -#~ "</screen>" -#~ msgstr "" -#~ "There are two extra properties you can specify (as of 2.4.4.3) for labels " -#~ "(and labels only). The first is \"max-width\" which will specify the " -#~ "maximum width of the label in pixels. And the second is \"max-screen-" -#~ "percent-width\" which specifies the maximum percentage of the screen " -#~ "width that the label can occupy. By default no label will occupy more " -#~ "then 90% of the screen by width. An example may be: <screen>\n" -#~ "<item type=\"label\">\n" -#~ "<pos x=\"10%\" max-screen-percent-width=\"50%\"/>\n" -#~ "</screen>" - -#~ msgid "Show Node" -#~ msgstr "Show Node" - -#~ msgid "" -#~ "Some items may only display in certain modes, like when doing a remote " -#~ "display. Multiple values can be specified and must be separated with " -#~ "commas. The following values are possible:" -#~ msgstr "" -#~ "Some items may only display in certain modes, like when doing a remote " -#~ "display. Multiple values can be specified and must be separated with " -#~ "commas. The following values are possible:" - -#~ msgid "<filename>console</filename> - In console mode." -#~ msgstr "<filename>console</filename> - In console mode." - -#~ msgid "<filename>console-fixed</filename> - In console non-flexi mode." -#~ msgstr "<filename>console-fixed</filename> - In console non-flexi mode." - -#~ msgid "<filename>console-flexi</filename> - In console & flexi mode." -#~ msgstr "<filename>console-flexi</filename> - In console & flexi mode." - -#~ msgid "<filename>flexi</filename> - In flexi mode." -#~ msgstr "<filename>flexi</filename> - In flexi mode." - -#~ msgid "<filename>remote</filename> - In remote mode." -#~ msgstr "<filename>remote</filename> - In remote mode." - -#~ msgid "<filename>remote-flexi</filename> - In remote & flexi mode." -#~ msgstr "<filename>remote-flexi</filename> - In remote & flexi mode." - -#~ msgid "" -#~ "For example: <screen>\n" -#~ "<show modes=\"flexi,remote\"/>\n" -#~ "</screen>" -#~ msgstr "" -#~ "For example: <screen>\n" -#~ "<show modes=\"flexi,remote\"/>\n" -#~ "</screen>" - -#~ msgid "" -#~ "You can also specify the \"type\" value to indicate that certain items " -#~ "should only be displayed if the type is true. Valid values include the " -#~ "following:" -#~ msgstr "" -#~ "You can also specify the \"type\" value to indicate that certain items " -#~ "should only be displayed if the type is true. Valid values include the " -#~ "following:" - -#~ msgid "" -#~ "<filename>chooser</filename>, if ChooserButton is set to \"true\" in the " -#~ "GDM configuration." -#~ msgstr "" -#~ "<filename>chooser</filename>, if ChooserButton is set to \"true\" in the " -#~ "GDM configuration." - -#~ msgid "" -#~ "<filename>config</filename>, if ConfigAvailable is set to \"true\" in the " -#~ "GDM configuration." -#~ msgstr "" -#~ "<filename>config</filename>, if ConfigAvailable is set to \"true\" in the " -#~ "GDM configuration." - -#~ msgid "" -#~ "<filename>custom_cmd[0-9]</filename>, if <filename>n-th</filename> " -#~ "CustomCommand is specified in the GDM configuration." -#~ msgstr "" -#~ "<filename>custom_cmd[0-9]</filename>, if <filename>n-th</filename> " -#~ "CustomCommand is specified in the GDM configuration." - -#~ msgid "" -#~ "<filename>halt</filename>, if HaltDaemon is specified in the GDM " -#~ "configuration." -#~ msgstr "" -#~ "<filename>halt</filename>, if HaltDaemon is specified in the GDM " -#~ "configuration." - -#~ msgid "" -#~ "<filename>reboot</filename>, if RebootCommand is specified in the GDM " -#~ "configuration." -#~ msgstr "" -#~ "<filename>reboot</filename>, if RebootCommand is specified in the GDM " -#~ "configuration." - -#~ msgid "" -#~ "<filename>suspend</filename>, if SuspendCommand is specified in the GDM " -#~ "configuration." -#~ msgstr "" -#~ "<filename>suspend</filename>, if SuspendCommand is specified in the GDM " -#~ "configuration." - -#~ msgid "" -#~ "<filename>system</filename>, if SystemMenu is specified in the GDM " -#~ "configuration." -#~ msgstr "" -#~ "<filename>system</filename>, if SystemMenu is specified in the GDM " -#~ "configuration." - -#~ msgid "" -#~ "<filename>timed</filename>, if TimedLoginEnabled is set to \"true\" in " -#~ "the GDM configuration." -#~ msgstr "" -#~ "<filename>timed</filename>, if TimedLoginEnabled is set to \"true\" in " -#~ "the GDM configuration." - -#~ msgid "" -#~ "For example: <screen>\n" -#~ "<show modes=\"console\" type=\"system\"/>\n" -#~ "</screen>" -#~ msgstr "" -#~ "For example: <screen>\n" -#~ "<show modes=\"console\" type=\"system\"/>\n" -#~ "</screen>" - -#~ msgid "" -#~ "Note that if SystemMenu is off then the halt, restart, suspend, chooser " -#~ "and config choices will not be shown, so this is a global toggle for them " -#~ "all. See some of the standard themes for how the show modes are used." -#~ msgstr "" -#~ "Note that if SystemMenu is off then the halt, restart, suspend, chooser " -#~ "and config choices will not be shown, so this is a global toggle for them " -#~ "all. See some of the standard themes for how the show modes are used." - -#~ msgid "Normal/Active/Prelight Nodes" -#~ msgstr "Normal/Active/Prelight Nodes" - -#~ msgid "" -#~ "Depending on the item type (except for userlist - refer to Color node " -#~ "below), it can specify its color, font, or image via the following tags:" -#~ msgstr "" -#~ "Depending on the item type (except for userlist - refer to colour node " -#~ "below), it can specify its colour, font or image via the following tags:" - -#~ msgid "<filename>normal</filename> - normal state." -#~ msgstr "<filename>normal</filename> - normal state." - -#~ msgid "<filename>active</filename> - when the item has active focus." -#~ msgstr "<filename>active</filename> - when the item has active focus." - -#~ msgid "" -#~ "<filename>prelight</filename> - when the mouse is hovering over the item." -#~ msgstr "" -#~ "<filename>prelight</filename> - when the mouse is hovering over the item." - -#~ msgid "" -#~ "When item is \"rect\" (alpha can be omitted and defaults to 0.0): " -#~ "<screen>\n" -#~ "<normal color=\"#ffffff\" alpha=\"0.0\">\n" -#~ "</screen>" -#~ msgstr "" -#~ "When item is \"rect\" (alpha can be omitted and defaults to 0.0): " -#~ "<screen>\n" -#~ "<normal colour=\"#ffffff\" alpha=\"0.0\">\n" -#~ "</screen>" - -#~ msgid "" -#~ "When item is \"label\" <screen>\n" -#~ "<normal color=\"#ffffff\" font=\"Sans 14\"/>\n" -#~ "</screen>" -#~ msgstr "" -#~ "When item is \"label\" <screen>\n" -#~ "<normal colour=\"#ffffff\" font=\"Sans 14\"/>\n" -#~ "</screen>" - -#~ msgid "" -#~ "When the item type is \"pixmap\" or \"SVG\", then the normal, active, and " -#~ "prelight tags specify the images to use as follows: <screen>\n" -#~ "<normal file=\"picture.png\" tint=\"#dddddd\"/>\n" -#~ "</screen>" -#~ msgstr "" -#~ "When the item type is \"pixmap\" or \"SVG\", then the normal, active, and " -#~ "prelight tags specify the images to use as follows: <screen>\n" -#~ "<normal file=\"picture.png\" tint=\"#dddddd\"/>\n" -#~ "</screen>" - -#~ msgid "" -#~ "Note that relative pathnames are assumed to be in the same directory as " -#~ "the theme <filename>.xml</filename> file in <filename><share>/gdm/" -#~ "themes/<theme_name></filename>." -#~ msgstr "" -#~ "Note that relative pathnames are assumed to be in the same directory as " -#~ "the theme <filename>.xml</filename> file in <filename><share>/gdm/" -#~ "themes/<theme_name></filename>." - -#~ msgid "" -#~ "Note that alternative image file can be specified using the altfile[n] " -#~ "property. GDM will use the last valid image filename specified. For " -#~ "example: <screen>\n" -#~ "<normal file=\"picture.png\" altfile1=\"distribution-blah-image.png\" " -#~ "altfile2=\"distribution-foo-image.png\"/>\n" -#~ "</screen> If <filename>distribution-foo-image.png</filename> is a valid " -#~ "image filename it will be used. Otherwise distribution-blah-image.png " -#~ "will be used if valid. This feature supported since 2.16.3." -#~ msgstr "" -#~ "Note that alternative image file can be specified using the altfile[n] " -#~ "property. GDM will use the last valid image filename specified. For " -#~ "example: <screen>\n" -#~ "<normal file=\"picture.png\" altfile1=\"distribution-blah-image.png\" " -#~ "altfile2=\"distribution-foo-image.png\"/>\n" -#~ "</screen> If <filename>distribution-foo-image.png</filename> is a valid " -#~ "image filename it will be used. Otherwise distribution-blah-image.png " -#~ "will be used if valid. This feature supported since 2.16.3." - -#~ msgid "Face Browser Icon/Label Color Nodes" -#~ msgstr "Face Browser Icon/Label Colour Nodes" - -#~ msgid "" -#~ "If the item type is of userlist, then the background color for the icon " -#~ "and label can be set separately via the the following tag:" -#~ msgstr "" -#~ "If the item type is of userlist, then the background colour for the icon " -#~ "and label can be set separately via the the following tag:" - -#~ msgid "" -#~ "\n" -#~ "<color iconcolor=\"#dddddd\" labelcolor=\"#ffffff\"/>\n" -#~ msgstr "" -#~ "\n" -#~ "<color iconcolor=\"#dddddd\" labelcolor=\"#ffffff\"/>\n" - -#~ msgid "Text Node" -#~ msgstr "Text Node" - -#~ msgid "" -#~ "Text tags are used by labels. They can be used to display localized text " -#~ "as follows (if the \"xml:lang\" attribute is omitted, the C locale is " -#~ "assumed): <screen>\n" -#~ "<text xml:lang=\"fr\">Option</text>\n" -#~ "</screen>" -#~ msgstr "" -#~ "Text tags are used by labels. They can be used to display localised text " -#~ "as follows (if the \"xml:lang\" attribute is omitted, the C locale is " -#~ "assumed): <screen>\n" -#~ "<text xml:lang=\"fr\">Option</text>\n" -#~ "</screen>" - -#~ msgid "" -#~ "You can include pango markup in the text nodes for labels, however you " -#~ "must encode it. So for example to have the label of \"foo<sup>" -#~ "bar</sup>\", you must type: <screen>\n" -#~ "<text>\"foo<sup>bar</sup>\"</text>\n" -#~ "</screen>" -#~ msgstr "" -#~ "You can include pango markup in the text nodes for labels, however you " -#~ "must encode it. So for example to have the label of \"foo<sup>" -#~ "bar</sup>\", you must type: <screen>\n" -#~ "<text>\"foo<sup>bar</sup>\"</text>\n" -#~ "</screen>" - -#~ msgid "" -#~ "Text nodes can contain the following special character sequences which " -#~ "will be translated as follows:" -#~ msgstr "" -#~ "Text nodes can contain the following special character sequences which " -#~ "will be translated as follows:" - -#~ msgid "%% - A literal % character" -#~ msgstr "%% - A literal % character" - -#~ msgid "" -#~ "%c - Clock time. Only labels with the \"clock\" id will update " -#~ "automatically every second. Other labels will contain a static timestamp." -#~ msgstr "" -#~ "%c - Clock time. Only labels with the \"clock\" id will update " -#~ "automatically every second. Other labels will contain a static timestamp." - -#~ msgid "%d - Display name (DISPLAY environment variable)" -#~ msgstr "%d - Display name (DISPLAY environment variable)" - -#~ msgid "%h - Hostname (gethostname output)" -#~ msgstr "%h - Hostname (gethostname output)" - -#~ msgid "%m - Machine name (uname.machine output)" -#~ msgstr "%m - Machine name (uname.machine output)" - -#~ msgid "%n - Node name (uname.nodename output)" -#~ msgstr "%n - Node name (uname.nodename output)" - -#~ msgid "%o - Domain name (getdomainname output)" -#~ msgstr "%o - Domain name (getdomainname output)" - -#~ msgid "%r - Release name (uname.release output)" -#~ msgstr "%r - Release name (uname.release output)" - -#~ msgid "%s - System name (uname.sysname output)" -#~ msgstr "%s - System name (uname.sysname output)" - -#~ msgid "" -#~ "%t - Current timed delay value from configuration file (0 if off) " -#~ "followed by the word \"seconds\" if value is greater than 1 or the word " -#~ "\"second\" if the value is 1. This character sequence is intended to be " -#~ "only used internally to display the \"timed-label\" message, which is " -#~ "automatically updated every second." -#~ msgstr "" -#~ "%t - Current timed delay value from configuration file (0 if off) " -#~ "followed by the word \"seconds\" if value is greater than 1 or the word " -#~ "\"second\" if the value is 1. This character sequence is intended to be " -#~ "only used internally to display the \"timed-label\" message, which is " -#~ "automatically updated every second." - -#~ msgid "" -#~ "%u - Timed username value from configuration file (empty if off) This " -#~ "character sequence is intended to be only used internally to display the " -#~ "\"timed-label\" message, which is automatically updated every second." -#~ msgstr "" -#~ "%u - Timed username value from configuration file (empty if off) This " -#~ "character sequence is intended to be only used internally to display the " -#~ "\"timed-label\" message, which is automatically updated every second." - -#~ msgid "\\n - Carriage return" -#~ msgstr "\\n - Carriage return" - -#~ msgid "" -#~ "_ - An underscore causes the following character to be underlined. If it " -#~ "precedes a % character sequence, the string that replaces the character " -#~ "sequence is underlined." -#~ msgstr "" -#~ "_ - An underscore causes the following character to be underlined. If it " -#~ "precedes a % character sequence, the string that replaces the character " -#~ "sequence is underlined." - -#~ msgid "Stock" -#~ msgstr "Stock" - -#~ msgid "" -#~ "Certain common localized labels can be specified via the stock tags. The " -#~ "\"text\" tag is ignored if the \"stock\" tag is used. You should really " -#~ "use the stock labels rather then just putting all the translations into " -#~ "the themes. This gives faster load times and likely better translations. " -#~ "The following values are valid:" -#~ msgstr "" -#~ "Certain common localised labels can be specified via the stock tags. The " -#~ "\"text\" tag is ignored if the \"stock\" tag is used. You should really " -#~ "use the stock labels rather then just putting all the translations into " -#~ "the themes. This gives faster load times and likely better translations. " -#~ "The following values are valid:" - -#~ msgid "<filename>cancel</filename>, _(\"_Cancel\"" -#~ msgstr "<filename>cancel</filename>, _(\"_Cancel\"" - -#~ msgid "<filename>caps-lock-warning</filename>, _(\"Caps Lock key is on.\"" -#~ msgstr "<filename>caps-lock-warning</filename>, _(\"Caps Lock key is on.\"" - -#~ msgid "<filename>chooser</filename>, _(\"Remote Login via _XDMCP\"" -#~ msgstr "<filename>chooser</filename>, _(\"Remote Login via _XDMCP\"" - -#~ msgid "<filename>config</filename>, _(\"_Configure\"" -#~ msgstr "<filename>config</filename>, _(\"_Configure\"" - -#~ msgid "<filename>custom_cmd[0-9]</filename>, _(\"Custom_[0-9]\"" -#~ msgstr "<filename>custom_cmd[0-9]</filename>, _(\"Custom_[0-9]\"" - -#~ msgid "<filename>disconnect</filename>, _(\"D_isconnect\"" -#~ msgstr "<filename>disconnect</filename>, _(\"D_isconnect\"" - -#~ msgid "<filename>halt</filename>, _(\"Shut _Down\"" -#~ msgstr "<filename>halt</filename>, _(\"Shut _Down\"" - -#~ msgid "<filename>language</filename>, _(\"_Language\"" -#~ msgstr "<filename>language</filename>, _(\"_Language\"" - -#~ msgid "<filename>ok</filename>, _(\"_OK\"" -#~ msgstr "<filename>ok</filename>, _(\"_OK\"" - -#~ msgid "<filename>quit</filename>, _(\"_Quit\"" -#~ msgstr "<filename>quit</filename>, _(\"_Quit\"" - -#~ msgid "<filename>reboot</filename>, _(\"_Restart\"" -#~ msgstr "<filename>reboot</filename>, _(\"_Restart\"" - -#~ msgid "<filename>session</filename>, _(\"_Session\"" -#~ msgstr "<filename>session</filename>, _(\"_Session\"" - -#~ msgid "<filename>startover</filename>, _(\"_Start Over\"" -#~ msgstr "<filename>startover</filename>, _(\"_Start Over\"" - -#~ msgid "<filename>suspend</filename>, _(\"Sus_pend\"" -#~ msgstr "<filename>suspend</filename>, _(\"Sus_pend\"" - -#~ msgid "<filename>system</filename>, _(\"_Actions\" (Formerly \"S_ystem\"" -#~ msgstr "<filename>system</filename>, _(\"_Actions\" (Formerly \"S_ystem\"" - -#~ msgid "<filename>timed-label</filename>, _(\"User %u will login in %t\"" -#~ msgstr "<filename>timed-label</filename>, _(\"User %u will login in %t\"" - -#~ msgid "<filename>username-label</filename>, _(\"Username:\"" -#~ msgstr "<filename>username-label</filename>, _(\"Username:\"" - -#~ msgid "<filename>welcome-label</filename>, _(\"Welcome to %n\"" -#~ msgstr "<filename>welcome-label</filename>, _(\"Welcome to %n\"" - -#~ msgid "" -#~ "For example: <screen>\n" -#~ "<stock type=\"welcome-label\">\n" -#~ "</screen>" -#~ msgstr "" -#~ "For example: <screen>\n" -#~ "<stock type=\"welcome-label\">\n" -#~ "</screen>" - -#~ msgid "Custom Widgetry" -#~ msgstr "Custom Widgetry" - -#~ msgid "" -#~ "Currently there is one item which is customizable and this is the list " -#~ "item. If you need to ask the user extra things, such as to pick from a " -#~ "list of places to log into, or set of custom login sessions you can setup " -#~ "the list item and add listitem children that describe the choices. Each " -#~ "listitem must have an id and a text child. The choice will be recorded in " -#~ "the file <filename><ServAuthDir>/<display>.GreeterInfo</" -#~ "filename> as <filename><list id>=<listitem id></filename>." -#~ msgstr "" -#~ "Currently there is one item which is customisable and this is the list " -#~ "item. If you need to ask the user extra things, such as to pick from a " -#~ "list of places to log into, or set of custom login sessions you can set " -#~ "up the list item and add list item children that describe the choices. " -#~ "Each list item must have an id and a text child. The choice will be " -#~ "recorded in the file <filename><ServAuthDir>/<display>." -#~ "GreeterInfo</filename> as <filename><list id>=<listitem id></" -#~ "filename>." - -#~ msgid "" -#~ "For example suppose we are on display :0, <filename>ServAuthDir</" -#~ "filename> is <filename><var>/lib/gdm</filename> and we have the " -#~ "following in the theme:" -#~ msgstr "" -#~ "For example, suppose we are on display :0, <filename>ServAuthDir</" -#~ "filename> is <filename><var>/lib/gdm</filename> and we have the " -#~ "following in the theme:" - -#~ msgid "" -#~ "\n" -#~ "<item type=\"list\" id=\"custom-config\">\n" -#~ "<pos anchor=\"nw\" x=\"1\" y=\"1\" height=\"200\" width=\"100\">\n" -#~ "<listitem id=\"foo\">\n" -#~ "<text>Foo</text>\n" -#~ "</listitem>\n" -#~ "<listitem id=\"bar\">\n" -#~ "<text>Bar</text>\n" -#~ "</listitem>\n" -#~ "</item>\n" -#~ msgstr "" -#~ "\n" -#~ "<item type=\"list\" id=\"custom-config\">\n" -#~ "<pos anchor=\"nw\" x=\"1\" y=\"1\" height=\"200\" width=\"100\">\n" -#~ "<listitem id=\"foo\">\n" -#~ "<text>Foo</text>\n" -#~ "</listitem>\n" -#~ "<listitem id=\"bar\">\n" -#~ "<text>Bar</text>\n" -#~ "</listitem>\n" -#~ "</item>\n" - -#~ msgid "" -#~ "Then if the user chooses 'Foo' then <filename><var>/lib/gdm/:0." -#~ "GreeterInfo</filename> will contain: <screen>\n" -#~ "custom-config=foo\n" -#~ "</screen>" -#~ msgstr "" -#~ "Then if the user chooses 'Foo' then <filename><var>/lib/gdm/:0." -#~ "GreeterInfo</filename> will contain: <screen>\n" -#~ "custom-config=foo\n" -#~ "</screen>" - -#~ msgid "" -#~ "GDM supports \"Accessible Login\" to allow users to log in to their " -#~ "desktop session even if they cannot easily use the screen, mouse, or " -#~ "keyboard in the usual way. Only the \"Standard Greeter\" supports " -#~ "accessibility, so use this login GUI for accessibility support. This is " -#~ "done by specifying the \"Standard Greeter\" in the \"Local\" tab for the " -#~ "console display and specifying the \"Standard Greeter\" in the \"Remote\" " -#~ "tab for remote displays. Or you can modify the <filename>Greeter</" -#~ "filename> configuration option by hand to be <command>gdmlogin</command>." -#~ msgstr "" -#~ "GDM supports \"Accessible Login\" to allow users to log in to their " -#~ "desktop session even if they cannot easily use the screen, mouse or " -#~ "keyboard in the usual way. Only the \"Standard Greeter\" supports " -#~ "accessibility, so use this login GUI for accessibility support. This is " -#~ "done by specifying the \"Standard Greeter\" in the \"Local\" tab for the " -#~ "console display and specifying the \"Standard Greeter\" in the \"Remote\" " -#~ "tab for remote displays. Or you can modify the <filename>Greeter</" -#~ "filename> configuration option by hand to be <command>gdmlogin</command>." - -#~ msgid "" -#~ "The Standard Greeter supports the ability to launch assistive " -#~ "technologies at login time via configurable \"gestures\" from the " -#~ "standard keyboard, pointing device, or switch device attached to the USB " -#~ "or PS/2 mouse port. Also the user can change the visual appearance of the " -#~ "login UI before logging in, for instance to use a higher-contrast color " -#~ "scheme for better visibility." -#~ msgstr "" -#~ "The Standard Greeter supports the ability to launch assistive " -#~ "technologies at login time via configurable \"gestures\" from the " -#~ "standard keyboard, pointing device or switch device attached to the USB " -#~ "or PS/2 mouse port. Also the user can change the visual appearance of the " -#~ "login user interface before logging in, for instance to use a higher-" -#~ "contrast colour scheme for better visibility." - -#~ msgid "" -#~ "In order to enable Accessible Login, the system administrator must make " -#~ "some changes to the default login configuration by manually modifying " -#~ "three human-readable configuration files, stored in the GDM " -#~ "configuration, AccessKeyMouseEvents and AccessDwellMouseEvents." -#~ msgstr "" -#~ "In order to enable Accessible Login, the system administrator must make " -#~ "some changes to the default login configuration by manually modifying " -#~ "three human-readable configuration files, stored in the GDM " -#~ "configuration, AccessKeyMouseEvents and AccessDwellMouseEvents." - -#~ msgid "" -#~ "In order to allow users to change the color and contrast scheme of the " -#~ "login dialog, make sure the <filename>AllowThemeChange</filename> " -#~ "parameter in the GDM configuration is set to \"true\"." -#~ msgstr "" -#~ "In order to allow users to change the colour and contrast scheme of the " -#~ "login dialogue, make sure the <filename>AllowThemeChange</filename> " -#~ "parameter in the GDM configuration is set to \"true\"." - -#~ msgid "" -#~ "To restrict user changes to the visual appearance to a subset of " -#~ "available themes, the <filename>GtkThemesToAllow</filename> parameter in " -#~ "the GDM configuration can be set to a list of acceptable themes separated " -#~ "by commas. For example:" -#~ msgstr "" -#~ "To restrict user changes to the visual appearance to a subset of " -#~ "available themes, the <filename>GtkThemesToAllow</filename> parameter in " -#~ "the GDM configuration can be set to a list of acceptable themes separated " -#~ "by commas. For example:" - -#~ msgid "" -#~ "\n" -#~ "GtkThemesToAllow=HighContrast,HighContrastInverse\n" -#~ msgstr "" -#~ "\n" -#~ "GtkThemesToAllow=HighContrast,HighContrastInverse\n" - -#~ msgid "" -#~ "To enable the use of assistive technologies such as the Onscreen " -#~ "Keyboard, Screen Reader, or Magnifier, the <filename>AddGtkModules</" -#~ "filename> parameter in the GDM configuration must be uncommented and set " -#~ "to \"true\". Also the <filename>GtkModulesList</filename> parameter must " -#~ "be uncommented and set as follows:" -#~ msgstr "" -#~ "To enable the use of assistive technologies such as the Onscreen " -#~ "Keyboard, Screen Reader, or Magnifier, the <filename>AddGtkModules</" -#~ "filename> parameter in the GDM configuration must be uncommented and set " -#~ "to \"true\". Also the <filename>GtkModulesList</filename> parameter must " -#~ "be uncommented and set as follows:" - -#~ msgid "" -#~ "\n" -#~ "GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener\n" -#~ msgstr "" -#~ "\n" -#~ "GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener\n" - -#~ msgid "" -#~ "The use of assistive technologies and the atk-bridge module requires the " -#~ "registry daemon, <command>at-spi-registryd</command>, to be running. This " -#~ "is handled by the GDM GUI starting with version 2.17." -#~ msgstr "" -#~ "The use of assistive technologies and the atk-bridge module requires the " -#~ "registry daemon, <command>at-spi-registryd</command>, to be running. This " -#~ "is handled by the GDM GUI starting with version 2.17." - -#~ msgid "" -#~ "System administrators may wish to load only the minimum subset of these " -#~ "modules which is required to support their user base. Depending on the " -#~ "end-user needs, not all of the above GtkModules may need to be loaded. If " -#~ "your end-users need the integrated Screen Reader and Magnifier, you must " -#~ "include \"gail\" and \"atk-bridge\". If your end-users will be using a " -#~ "pointing device without buttons or switches, include \"dwellmouselistener" -#~ "\". If some of your users will use pointing devices with switches, " -#~ "alternative physical keyboards, or switch/button devices, include " -#~ "\"keymouselistener\". Including all four is suitable for most system " -#~ "configurations. The Onscreen Keyboard can operate without gail and atk-" -#~ "bridge, but with a reduced feature set; for optimum accessibility we " -#~ "recommend including both gail and atk-bridge." -#~ msgstr "" -#~ "System administrators may wish to load only the minimum subset of these " -#~ "modules which is required to support their user base. Depending on the " -#~ "end-user needs, not all of the above GtkModules may need to be loaded. If " -#~ "your end-users need the integrated Screen Reader and Magnifier, you must " -#~ "include \"gail\" and \"atk-bridge\". If your end-users will be using a " -#~ "pointing device without buttons or switches, include \"dwellmouselistener" -#~ "\". If some of your users will use pointing devices with switches, " -#~ "alternative physical keyboards, or switch/button devices, include " -#~ "\"keymouselistener\". Including all four is suitable for most system " -#~ "configurations. The Onscreen Keyboard can operate without gail and atk-" -#~ "bridge, but with a reduced feature set; for optimum accessibility we " -#~ "recommend including both gail and atk-bridge." - -#~ msgid "" -#~ "Once \"keymouselistener\" and/or \"dwellmouselistener\" have been added " -#~ "to the GtkModules loaded by GDM, you can assign end-user actions with the " -#~ "launching of specific assistive technologies. These gesture associations " -#~ "are contained in files AccessKeyMouseEvents and AccessDwellMouseEvents, " -#~ "respectively. Both files are located in the <etc>/gdm/modules " -#~ "directory. The gesture format is described in the two configuration files." -#~ msgstr "" -#~ "Once \"keymouselistener\" and/or \"dwellmouselistener\" have been added " -#~ "to the GtkModules loaded by GDM, you can assign end-user actions with the " -#~ "launching of specific assistive technologies. These gesture associations " -#~ "are contained in files AccessKeyMouseEvents and AccessDwellMouseEvents, " -#~ "respectively. Both files are located in the <etc>/gdm/modules " -#~ "directory. The gesture format is described in the two configuration files." - -#~ msgid "" -#~ "The AccessKeyMouseEvents file controls the keymouselistener Gesture " -#~ "Listener and is used to define key-press, mouse button, or XInput device " -#~ "sequences that can be used to launch applications needed for " -#~ "accessibility. In order to reduce the likelihood of unintentional launch, " -#~ "these \"gestures\" may be associated with multiple switch presses and/or " -#~ "minimum durations. Note that the XKB extension is needed for key gestures " -#~ "to work, so you may need to add +xkb to your Xserver command line for " -#~ "gestures to work properly." -#~ msgstr "" -#~ "The AccessKeyMouseEvents file controls the keymouselistener Gesture " -#~ "Listener and is used to define key-press, mouse button, or XInput device " -#~ "sequences that can be used to launch applications needed for " -#~ "accessibility. In order to reduce the likelihood of unintentional launch, " -#~ "these \"gestures\" may be associated with multiple switch presses and/or " -#~ "minimum durations. Note that the XKB extension is needed for key gestures " -#~ "to work, so you may need to add +xkb to your Xserver command line for " -#~ "gestures to work properly." - -#~ msgid "" -#~ "The DwellKeyMouseEvents file controls the dwellmouselistner and supports " -#~ "gestures that involve only motion of a pointing device such as the system " -#~ "mouse of an alternative pointing device such as a head pointer or " -#~ "trackball may also be defined. All gestures are specified by the same " -#~ "syntax; that is, there is no distinction between a \"core mouse\" gesture " -#~ "and motion from an alternate input device." -#~ msgstr "" -#~ "The DwellKeyMouseEvents file controls the dwellmouselistner and supports " -#~ "gestures that involve only motion of a pointing device such as the system " -#~ "mouse of an alternative pointing device such as a head pointer or " -#~ "trackball may also be defined. All gestures are specified by the same " -#~ "syntax; that is, there is no distinction between a \"core mouse\" gesture " -#~ "and motion from an alternate input device." - -#~ msgid "" -#~ "Motion gestures are defined as \"crossing events\" into and out of the " -#~ "login dialog window. If the \"dwellmouselistener\" GtkModule is loaded, " -#~ "alternative pointing devices are temporarily \"latched\" to the core " -#~ "pointer, such that motion from alternative devices results in movement of " -#~ "the onscreen pointer." -#~ msgstr "" -#~ "Motion gestures are defined as \"crossing events\" into and out of the " -#~ "login dialogue window. If the \"dwellmouselistener\" GtkModule is loaded, " -#~ "alternative pointing devices are temporarily \"latched\" to the core " -#~ "pointer, such that motion from alternative devices results in movement of " -#~ "the on screen pointer." - -#~ msgid "" -#~ "In order to use text-to-speech services at login time (for instance, when " -#~ "using the Screen Reader in speech mode) on some operating systems, the " -#~ "GDM user must be made a member of the \"audio\" group" -#~ msgstr "" -#~ "In order to use text-to-speech services at login time (for instance, when " -#~ "using the Screen Reader in speech mode) on some operating systems, the " -#~ "GDM user must be made a member of the \"audio\" group" - -#~ msgid "" -#~ "Currently GDM does not remember what accessible technology programs have " -#~ "been started when switching applications. So if the user switches between " -#~ "the login program and the chooser, for example, then it is necessary for " -#~ "the user to redo the gesture. Users may need to also set up their default " -#~ "session so that the assistive technologies required are started " -#~ "automatically (or have appropriate key-bindings defined to start them) " -#~ "after the user session has started." -#~ msgstr "" -#~ "Currently GDM does not remember what accessible technology programs have " -#~ "been started when switching applications. So if the user switches between " -#~ "the login program and the chooser, for example, then it is necessary for " -#~ "the user to redo the gesture. Users may need to also set up their default " -#~ "session so that the assistive technologies required are started " -#~ "automatically (or have appropriate key-bindings defined to start them) " -#~ "after the user session has started." - -#~ msgid "" -#~ "There are some issues that cause users to have problems getting the " -#~ "gesture listeners to work. It is recommended that people use GDM version " -#~ "2.8.0.5 or later for best results. Some X servers have a bug which causes " -#~ "detectable autorepeat to fail when XEVIE is enabled (which happens when " -#~ "atk-bridge is included as a GTK Module). This bug causes key gestures " -#~ "with a duration greater than 0 to always fail. A workaround is to simply " -#~ "redefine all key gestures so they have zero length duration. Some " -#~ "versions of GOK and gnopernicus will not launch unless the \"gdm\" user " -#~ "has a writable home directory. If you see an hourglass cursor when you " -#~ "complete a gesture but the program does not start, then you are likely " -#~ "having this problem. It should be considered a bug for AT programs to " -#~ "require having a writable home directory, so please file a bug with the " -#~ "AT program if you encounter this problem. Also note that some input " -#~ "devices require X server configuration before GDM will recognize them." -#~ msgstr "" -#~ "There are some issues that cause users to have problems getting the " -#~ "gesture listeners to work. It is recommended that people use GDM version " -#~ "2.8.0.5 or later for best results. Some X servers have a bug which causes " -#~ "detectable autorepeat to fail when XEVIE is enabled (which happens when " -#~ "atk-bridge is included as a GTK Module). This bug causes key gestures " -#~ "with a duration greater than 0 to always fail. A workaround is to simply " -#~ "redefine all key gestures so they have zero length duration. Some " -#~ "versions of GOK and gnopernicus will not launch unless the \"gdm\" user " -#~ "has a writable home directory. If you see an hourglass cursor when you " -#~ "complete a gesture but the program does not start, then you are likely " -#~ "having this problem. It should be considered a bug for AT programs to " -#~ "require having a writable home directory, so please file a bug with the " -#~ "AT program if you encounter this problem. Also note that some input " -#~ "devices require X server configuration before GDM will recognise them." - -#~ msgid "Accessibility Login Sound Configuration" -#~ msgstr "Accessibility Login Sound Configuration" - -#~ msgid "" -#~ "By default, GDM requires a media application such as \"sox\" to be " -#~ "present to play sounds for successful or failed login. GDM defaults the " -#~ "location of this application to <filename><bin>/play</filename> (or " -#~ "<filename><bin>/audioplay</filename> on Solaris. This can be " -#~ "changed via the SoundProgram GDM configuration option. Typically most " -#~ "text-to-speech programs (such as ORCA or Gnopernicus) use a separate " -#~ "mechanism to play audio." -#~ msgstr "" -#~ "By default, GDM requires a media application such as \"sox\" to be " -#~ "present to play sounds for successful or failed login. GDM defaults the " -#~ "location of this application to <filename><bin>/play</filename> (or " -#~ "<filename><bin>/audioplay</filename> on Solaris. This can be " -#~ "changed via the SoundProgram GDM configuration option. Typically most " -#~ "text-to-speech programs (such as ORCA or Gnopernicus) use a separate " -#~ "mechanism to play audio." - -#~ msgid "Solaris Specific Features" -#~ msgstr "Solaris Specific Features" - -#~ msgid "" -#~ "On Solaris, the following configuration is recommended. This turns on " -#~ "IPv6 and also turns on PreFetch for performance benefit. <screen>\n" -#~ "./autogen.sh --prefix=/usr --sysconfdir=/etc/X11 --localstatedir=/var\n" -#~ " --libexecdir=/usr/lib --enable-ipv6=yes --with-at-bindir=/usr/sfw/bin\n" -#~ " --with-prefetch --with-post-path=/usr/openwin/bin\n" -#~ "</screen>" -#~ msgstr "" -#~ "On Solaris, the following configuration is recommended. This turns on " -#~ "IPv6 and also turns on PreFetch for performance benefit. <screen>\n" -#~ "./autogen.sh --prefix=/usr --sysconfdir=/etc/X11 --localstatedir=/var\n" -#~ " --libexecdir=/usr/lib --enable-ipv6=yes --with-at-bindir=/usr/sfw/bin\n" -#~ " --with-prefetch --with-post-path=/usr/openwin/bin\n" -#~ "</screen>" - -#~ msgid "" -#~ "Configuring GDM with the \"--with-post-path=/usr/openwin/bin\" on Solaris " -#~ "is recommended for access to programs like Xnest." -#~ msgstr "" -#~ "Configuring GDM with the \"--with-post-path=/usr/openwin/bin\" on Solaris " -#~ "is recommended for access to programs like Xnest." - -#~ msgid "Solaris /etc/logindevperm" -#~ msgstr "Solaris /etc/logindevperm" - -#~ msgid "" -#~ "GDM supports /etc/logindevperm, but only on Solaris 10 and higher. Refer " -#~ "to the logindevperm.4 man page for more information." -#~ msgstr "" -#~ "GDM supports /etc/logindevperm, but only on Solaris 10 and higher. Refer " -#~ "to the logindevperm.4 man page for more information." - -#~ msgid "" -#~ "To make /etc/logindevperm functionality work on Solaris 9 or earlier you " -#~ "would have to hack the GDM PreSession and PostSession script to chmod the " -#~ "device permissions directly. In other words, if /etc/logindevperm had a " -#~ "listing like this:" -#~ msgstr "" -#~ "To make /etc/logindevperm functionality work on Solaris 9 or earlier you " -#~ "would have to hack the GDM PreSession and PostSession script to chmod the " -#~ "device permissions directly. In other words, if /etc/logindevperm had a " -#~ "listing like this:" - -#~ msgid "" -#~ "\n" -#~ "/dev/console 0600 /dev/sound/* # audio devices\n" -#~ msgstr "" -#~ "\n" -#~ "/dev/console 0600 /dev/sound/* # audio devices\n" - -#~ msgid "" -#~ "The PreSession script would need to be modified to chown /dev/console to " -#~ "the user:group who is logging into the console and ensure whatever " -#~ "permissions is specified in /etc/logindevperm (0600 for the line above). " -#~ "Then in the PostSession script chmod the device back to root:root and " -#~ "ensure 0600 this time (do not use the value in the /etc/logindevperm " -#~ "file). Linux uses a different mechanism for managing device permissions, " -#~ "so this extra scripting is not needed." -#~ msgstr "" -#~ "The PreSession script would need to be modified to chown /dev/console to " -#~ "the user:group who is logging into the console and ensure whatever " -#~ "permissions is specified in /etc/logindevperm (0600 for the line above). " -#~ "Then in the PostSession script chmod the device back to root:root and " -#~ "ensure 0600 this time (do not use the value in the /etc/logindevperm " -#~ "file). Linux uses a different mechanism for managing device permissions, " -#~ "so this extra scripting is not needed." - -#~ msgid "Solaris Automatic Login" -#~ msgstr "Solaris Automatic Login" - -#~ msgid "" -#~ "Automatic login does not work on Solaris because PAM is not configured to " -#~ "support this feature by default. Automatic login is a GDM feature that is " -#~ "not enabled by default, so you would only notice this problem if you try " -#~ "to make use of it. Turning this feature on causes your computer to login " -#~ "to a specified username on startup without asking for username and " -#~ "password. This is an insecure way to set up your computer." -#~ msgstr "" -#~ "Automatic login does not work on Solaris because PAM is not configured to " -#~ "support this feature by default. Automatic login is a GDM feature that is " -#~ "not enabled by default, so you would only notice this problem if you try " -#~ "to make use of it. Turning this feature on causes your computer to log in " -#~ "to a specified username on startup without asking for username and " -#~ "password. This is an insecure way to set up your computer." - -#~ msgid "" -#~ "If using Solaris 10 or lower, then you need to compile the pam_allow.c " -#~ "code provided with the GDM release and install it to /usr/lib/security " -#~ "(or provide the full path in /etc/pam.conf) and ensure it is owned by uid " -#~ "0 and not group or world writable." -#~ msgstr "" -#~ "If using Solaris 10 or lower, then you need to compile the pam_allow.c " -#~ "code provided with the GDM release and install it to /usr/lib/security " -#~ "(or provide the full path in /etc/pam.conf) and ensure it is owned by uid " -#~ "0 and not group or world writable." - -#~ msgid "" -#~ "The following are reasonable pam.conf values for turning on automatic " -#~ "login in GDM. Make sure to read the PAM documentation (e.g. pam.d/pam." -#~ "conf man page) and be comfortable with the security implications of any " -#~ "changes you intend to make to your configuration." -#~ msgstr "" -#~ "The following are reasonable pam.conf values for turning on automatic " -#~ "login in GDM. Make sure to read the PAM documentation (e.g. pam.d/pam." -#~ "conf man page) and be comfortable with the security implications of any " -#~ "changes you intend to make to your configuration." - -#~ msgid "Other Solaris Features" -#~ msgstr "Other Solaris Features" - -#~ msgid "GDM supports a few features specific to Solaris, as follows:" -#~ msgstr "GDM supports a few features specific to Solaris, as follows:" - -#~ msgid "" -#~ "GDM supports Solaris Auditing if running on Solaris 10 or higher. GDM " -#~ "should not be used if auditing is needed and running Solaris 9 or older." -#~ msgstr "" -#~ "GDM supports Solaris Auditing if running on Solaris 10 or higher. GDM " -#~ "should not be used if auditing is needed and running Solaris 9 or older." - -#~ msgid "" -#~ "GDM supports a security feature which causes the X server to run as the " -#~ "user instead of as the root user. GDM must be using PAM for this feature " -#~ "to be enabled, which is the normal case for Solaris. This second feature " -#~ "has the side-effect of causing the X server to always restart between " -#~ "sessions, which disables the AlwaysRestartServer configuration option." -#~ msgstr "" -#~ "GDM supports a security feature which causes the X server to run as the " -#~ "user instead of as the root user. GDM must be using PAM for this feature " -#~ "to be enabled, which is the normal case for Solaris. This second feature " -#~ "has the side-effect of causing the X server to always restart between " -#~ "sessions, which disables the AlwaysRestartServer configuration option." - -#~ msgid "" -#~ "Solaris supports the <filename>/etc/default/login</filename> interface, " -#~ "which affects the <filename>DefaultPath</filename>, <filename>RootPath</" -#~ "filename>, <filename>PasswordRequired</filename>, and " -#~ "<filename>AllowRemoteRoot</filename> options as described in the " -#~ "\"Configuration\" section." -#~ msgstr "" -#~ "Solaris supports the <filename>/etc/default/login</filename> interface, " -#~ "which affects the <filename>DefaultPath</filename>, <filename>RootPath</" -#~ "filename>, <filename>PasswordRequired</filename>, and " -#~ "<filename>AllowRemoteRoot</filename> options as described in the " -#~ "\"Configuration\" section." - -#~ msgid "Example Configurations" -#~ msgstr "Example Configurations" - -#~ msgid "" -#~ "This section has some example configurations that are useful for various " -#~ "setups." -#~ msgstr "" -#~ "This section has some example configurations that are useful for various " -#~ "setups." - -#~ msgid "Terminal Lab With One Server" -#~ msgstr "Terminal Lab With One Server" - -#~ msgid "" -#~ "Suppose you want to make a lab full of X terminals that all connect to " -#~ "one server machine. So let's call one X terminal <filename>xterminal</" -#~ "filename> and let's call the server machine <filename>appserver</" -#~ "filename>. You install GDM on both." -#~ msgstr "" -#~ "Suppose you want to make a lab full of X terminals that all connect to " -#~ "one server machine. So let's call one X terminal <filename>xterminal</" -#~ "filename> and let's call the server machine <filename>appserver</" -#~ "filename>. You install GDM on both." - -#~ msgid "" -#~ "On <filename>appserver</filename> you enable XDMCP, so you have <screen>\n" -#~ "[xdmcp]\n" -#~ "Enable=true\n" -#~ "</screen> If you want no local screens here, you can then make the " -#~ "<filename>[servers]</filename> section empty." -#~ msgstr "" -#~ "On <filename>appserver</filename> you enable XDMCP, so you have <screen>\n" -#~ "[xdmcp]\n" -#~ "Enable=true\n" -#~ "</screen> If you want no local screens here, you can then make the " -#~ "<filename>[servers]</filename> section empty." - -#~ msgid "" -#~ "On the <filename>xterminal</filename> you disable XDMCP (you don't want " -#~ "anyone to connect to the xterminal really). You will add a server type " -#~ "perhaps called <filename>Terminal</filename> as follows: <screen>\n" -#~ "[server-Terminal]\n" -#~ "name=Terminal server\n" -#~ "command=/path/to/X -terminate\n" -#~ "flexible=false\n" -#~ "handled=false\n" -#~ "</screen> This definition should in fact be included in the standard " -#~ "configuration file. Notice that we made the <filename>handled</filename> " -#~ "key false since we don't want GDM to handle this server localy. Also note " -#~ "that we have not yet added the <filename>-query</filename> argument, you " -#~ "can add that here, or in the <filename>[servers]</filename> section. " -#~ "We'll define our local servers as follows: <screen>\n" -#~ "[servers]\n" -#~ "0=Terminal -query appserver\n" -#~ "</screen> This will run a direct XDMCP query to the server named " -#~ "<filename>appserver</filename>." -#~ msgstr "" -#~ "On the <filename>xterminal</filename> you disable XDMCP (you don't want " -#~ "anyone to connect to the xterminal really). You will add a server type " -#~ "perhaps called <filename>Terminal</filename> as follows: <screen>\n" -#~ "[server-Terminal]\n" -#~ "name=Terminal server\n" -#~ "command=/path/to/X -terminate\n" -#~ "flexible=false\n" -#~ "handled=false\n" -#~ "</screen> This definition should in fact be included in the standard " -#~ "configuration file. Notice that we made the <filename>handled</filename> " -#~ "key false since we don't want GDM to handle this server localy. Also note " -#~ "that we have not yet added the <filename>-query</filename> argument, you " -#~ "can add that here, or in the <filename>[servers]</filename> section. " -#~ "We'll define our local servers as follows: <screen>\n" -#~ "[servers]\n" -#~ "0=Terminal -query appserver\n" -#~ "</screen> This will run a direct XDMCP query to the server named " -#~ "<filename>appserver</filename>." - -#~ msgid "Terminal Lab With Two Or More Servers" -#~ msgstr "Terminal Lab With Two Or More Servers" - -#~ msgid "" -#~ "Suppose you want to make a lab full of X terminals that all connect to " -#~ "some choice of servers. For now let's make it <filename>appserverone</" -#~ "filename> and <filename>appservertwo</filename>. Again we'll call our " -#~ "example X terminal server <filename>xterminal</filename>. The setup on " -#~ "both servers is the same as with the case of one server in the previous " -#~ "section. You do not need to explicitly enable indirect queries on the " -#~ "server since we'll run the choosers locally on the X terminals." -#~ msgstr "" -#~ "Suppose you want to make a lab full of X terminals that all connect to " -#~ "some choice of servers. For now let's make it <filename>appserverone</" -#~ "filename> and <filename>appservertwo</filename>. Again we'll call our " -#~ "example X terminal server <filename>xterminal</filename>. The setup on " -#~ "both servers is the same as with the case of one server in the previous " -#~ "section. You do not need to explicitly enable indirect queries on the " -#~ "server since we'll run the choosers locally on the X terminals." - -#~ msgid "" -#~ "So on the <filename>xterminal</filename> you again disable XDMCP. You " -#~ "will add a server type perhaps called <filename>Chooser</filename> as " -#~ "follows: <screen>\n" -#~ "[server-Chooser]\n" -#~ "name=Chooser server\n" -#~ "command=/path/to/X\n" -#~ "flexible=false\n" -#~ "chooser=true\n" -#~ "</screen> And again this definition should in fact be included in the " -#~ "standard configuration file. Notice that we made the <filename>chooser</" -#~ "filename> key true here. This will run the XDMCP chooser for this server, " -#~ "and when the user chooses a host GDM will run a query for that host. Then " -#~ "we will define our local servers as follows: <screen>\n" -#~ "[servers]\n" -#~ "0=Chooser\n" -#~ "</screen>" -#~ msgstr "" -#~ "So on the <filename>xterminal</filename> you again disable XDMCP. You " -#~ "will add a server type perhaps called <filename>Chooser</filename> as " -#~ "follows: <screen>\n" -#~ "[server-Chooser]\n" -#~ "name=Chooser server\n" -#~ "command=/path/to/X\n" -#~ "flexible=false\n" -#~ "chooser=true\n" -#~ "</screen> And again this definition should in fact be included in the " -#~ "standard configuration file. Notice that we made the <filename>chooser</" -#~ "filename> key true here. This will run the XDMCP chooser for this server, " -#~ "and when the user chooses a host GDM will run a query for that host. Then " -#~ "we will define our local servers as follows: <screen>\n" -#~ "[servers]\n" -#~ "0=Chooser\n" -#~ "</screen>" - -#~ msgid "" -#~ "The XDMCP chooser on the X terminal will normally give a broadcast query " -#~ "to see which servers exist on the network. If the two servers are not " -#~ "reachable by a broadcast query, you must add them by hand to the " -#~ "configuration file. So in the <filename>[chooser]</filename> section you " -#~ "would have: <screen>\n" -#~ "Hosts=appserverone,appservertwo\n" -#~ "</screen> and any other servers you wish the users to be able to connect " -#~ "to." -#~ msgstr "" -#~ "The XDMCP chooser on the X terminal will normally give a broadcast query " -#~ "to see which servers exist on the network. If the two servers are not " -#~ "reachable by a broadcast query, you must add them by hand to the " -#~ "configuration file. So in the <filename>[chooser]</filename> section you " -#~ "would have: <screen>\n" -#~ "Hosts=appserverone,appservertwo\n" -#~ "</screen> and any other servers you wish the users to be able to connect " -#~ "to." - -#~ msgid "" -#~ "Sometimes you may want to run the chooser on the server side however. " -#~ "Then what you want to do is to run a configuration similar to the " -#~ "previous section about the one server configuration with XDMCP indirect " -#~ "queries enabled on <filename>appserver</filename> and on the X terminals " -#~ "you'd have <screen>\n" -#~ "[servers]\n" -#~ "0=Terminal -indirect appserver\n" -#~ "</screen> This way for example you only have to maintain one " -#~ "<filename>Hosts</filename> entry. However as a disadvantage then, the " -#~ "<filename>appserver</filename> must then always be available. So it's not " -#~ "good for situations where you want to have several servers and not all of " -#~ "them have to be on all the time. You could also have one of the X " -#~ "terminals handle indirect XDMCP queries and serve up the chooser to the " -#~ "other X terminals." -#~ msgstr "" -#~ "Sometimes you may want to run the chooser on the server side however. " -#~ "Then what you want to do is to run a configuration similar to the " -#~ "previous section about the one server configuration with XDMCP indirect " -#~ "queries enabled on <filename>appserver</filename> and on the X terminals " -#~ "you'd have <screen>\n" -#~ "[servers]\n" -#~ "0=Terminal -indirect appserver\n" -#~ "</screen> This way for example you only have to maintain one " -#~ "<filename>Hosts</filename> entry. However as a disadvantage then, the " -#~ "<filename>appserver</filename> must then always be available. So it's not " -#~ "good for situations where you want to have several servers and not all of " -#~ "them have to be on all the time. You could also have one of the X " -#~ "terminals handle indirect XDMCP queries and serve up the chooser to the " -#~ "other X terminals." - -#~ msgid "Defining Custom Commands" -#~ msgstr "Defining Custom Commands" - -#~ msgid "" -#~ "Suppose you want to add a custom command to the GDM menu that will give " -#~ "you the oportunity to boot into other operating system such as Windoze. " -#~ "Jsut add the following options into the <filename>[customcommand]</" -#~ "filename> section of the GDM configuration file. <screen>\n" -#~ " [customcommand]\n" -#~ " CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/" -#~ "rebootwindoze\n" -#~ " CustomCommandLabel0=_Windoze\n" -#~ " CustomCommandLRLabel0=Reboot into _Windoze\n" -#~ " CustomCommandText0=Are you sure you want to restart the " -#~ "computer into Windoze?\n" -#~ " CustomCommandTooltip0=Restarts the computer into Windoze\n" -#~ " CustomCommandIsPersistent0=true\n" -#~ " </screen> CustomCommand0 specifies two commands separated by a " -#~ "semicolon: <filename>/sbin/rebootwindoze</filename> and <filename>/usr/" -#~ "local/sbin/rebootwindoze</filename>. GDM will use the first valid command " -#~ "in the list. This allows different commands for different operating " -#~ "systems to be included." -#~ msgstr "" -#~ "Suppose you want to add a custom command to the GDM menu that will give " -#~ "you the oportunity to boot into another operating system such as Windoze. " -#~ "Just add the following options into the <filename>[customcommand]</" -#~ "filename> section of the GDM configuration file. <screen>\n" -#~ " [customcommand]\n" -#~ " CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/" -#~ "rebootwindoze\n" -#~ " CustomCommandLabel0=_Windoze\n" -#~ " CustomCommandLRLabel0=Reboot into _Windoze\n" -#~ " CustomCommandText0=Are you sure you want to restart the " -#~ "computer into Windoze?\n" -#~ " CustomCommandTooltip0=Restarts the computer into Windoze\n" -#~ " CustomCommandIsPersistent0=true\n" -#~ " </screen> CustomCommand0 specifies two commands separated by a " -#~ "semicolon: <filename>/sbin/rebootwindoze</filename> and <filename>/usr/" -#~ "local/sbin/rebootwindoze</filename>. GDM will use the first valid command " -#~ "in the list. This allows different commands for different operating " -#~ "systems to be included." - -#~ msgid "" -#~ "Note, that besides being able to customise this option to reboot into " -#~ "different operating systems you can also use it to define your own custom " -#~ "behaviours that you wish to run from the GDM menu. Suppose you want to " -#~ "give users the oportunity to run system update scripts from the login " -#~ "screen. Add the following options into the <filename>[customcommand]</" -#~ "filename> section of your GDM configuration file. <screen>\n" -#~ " [customcommand]\n" -#~ " CustomCommand0=/sbin/updatesystem;/usr/local/sbin/updatesystem\n" -#~ " CustomCommandLabel0=_Update Me\n" -#~ " CustomCommandLRLabel0=Update the system\n" -#~ " CustomCommandText0=Are you sure you want to update the system " -#~ "software?\n" -#~ " CustomCommandTooltip0=Updates the system\n" -#~ " CustomCommandNoRestart0=true\n" -#~ " </screen>" -#~ msgstr "" -#~ "Note, that besides being able to customise this option to reboot into " -#~ "different operating systems you can also use it to define your own custom " -#~ "behaviours that you wish to run from the GDM menu. Suppose you want to " -#~ "give users the oportunity to run system update scripts from the login " -#~ "screen. Add the following options into the <filename>[customcommand]</" -#~ "filename> section of your GDM configuration file. <screen>\n" -#~ " [customcommand]\n" -#~ " CustomCommand0=/sbin/updatesystem;/usr/local/sbin/updatesystem\n" -#~ " CustomCommandLabel0=_Update Me\n" -#~ " CustomCommandLRLabel0=Update the system\n" -#~ " CustomCommandText0=Are you sure you want to update the system " -#~ "software?\n" -#~ " CustomCommandTooltip0=Updates the system\n" -#~ " CustomCommandNoRestart0=true\n" -#~ " </screen>" - -#~ msgid "" -#~ "Both custom commands could be defined as follows. <screen>\n" -#~ " [customcommand]\n" -#~ " CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/" -#~ "rebootwindoze\n" -#~ " CustomCommandLabel0=_Windoze\n" -#~ " CustomCommandLRLabel0=Reboot into _Windoze\n" -#~ " CustomCommandText0=Are you sure you want to restart the " -#~ "computer into Windoze?\n" -#~ " CustomCommandTooltip0=Restarts the computer into Windoze\n" -#~ " CustomCommandIsPersistent0=true\n" -#~ " \n" -#~ " CustomCommand1=/sbin/updatesystem;/usr/local/sbin/updatesystem\n" -#~ " CustomCommandLabel1=_Update Me\n" -#~ " CustomCommandLRLabel1=Update the system\n" -#~ " CustomCommandText1=Are you sure you want to update the system " -#~ "software?\n" -#~ " CustomCommandTooltip1=Updates the system\n" -#~ " CustomCommandNoRestart1=true\n" -#~ " </screen>" -#~ msgstr "" -#~ "Both custom commands could be defined as follows. <screen>\n" -#~ " [customcommand]\n" -#~ " CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/" -#~ "rebootwindoze\n" -#~ " CustomCommandLabel0=_Windoze\n" -#~ " CustomCommandLRLabel0=Reboot into _Windoze\n" -#~ " CustomCommandText0=Are you sure you want to restart the " -#~ "computer into Windoze?\n" -#~ " CustomCommandTooltip0=Restarts the computer into Windoze\n" -#~ " CustomCommandIsPersistent0=true\n" -#~ " \n" -#~ " CustomCommand1=/sbin/updatesystem;/usr/local/sbin/updatesystem\n" -#~ " CustomCommandLabel1=_Update Me\n" -#~ " CustomCommandLRLabel1=Update the system\n" -#~ " CustomCommandText1=Are you sure you want to update the system " -#~ "software?\n" -#~ " CustomCommandTooltip1=Updates the system\n" -#~ " CustomCommandNoRestart1=true\n" -#~ " </screen>" - -#~ msgid "" -#~ "There can be up to 10 custom commands numbered 0-9. <screen>\n" -#~ " [customcommand]\n" -#~ " CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/" -#~ "rebootwindoze\n" -#~ " CustomCommandLabel0=_Windoze\n" -#~ " CustomCommandLRLabel0=Reboot into _Windoze\n" -#~ " CustomCommandText0=Are you sure you want to restart the " -#~ "computer into Windoze?\n" -#~ " CustomCommandTooltip0=Restarts the computer into Windoze\n" -#~ " CustomCommandIsPersistent0=true\n" -#~ " \n" -#~ " CustomCommand1=/sbin/updatesystem;/usr/local/sbin/updatesystem\n" -#~ " CustomCommandLabel1=_Update Me\n" -#~ " CustomCommandLRLabel1=Update the system\n" -#~ " CustomCommandText1=Are you sure you want to update the system " -#~ "software?\n" -#~ " CustomCommandTooltip1=Updates the system\n" -#~ " CustomCommandNoRestart1=true\n" -#~ " \n" -#~ " CustomCommand3=/sbin/do_something\n" -#~ " .\n" -#~ " .\n" -#~ " .\n" -#~ " \n" -#~ " CustomCommand4=/sbin/do_something_else\n" -#~ " .\n" -#~ " .\n" -#~ " .\n" -#~ " </screen>" -#~ msgstr "" -#~ "There can be up to 10 custom commands numbered 0-9. <screen>\n" -#~ " [customcommand]\n" -#~ " CustomCommand0=/sbin/rebootwindoze;/usr/local/sbin/" -#~ "rebootwindoze\n" -#~ " CustomCommandLabel0=_Windoze\n" -#~ " CustomCommandLRLabel0=Reboot into _Windoze\n" -#~ " CustomCommandText0=Are you sure you want to restart the " -#~ "computer into Windoze?\n" -#~ " CustomCommandTooltip0=Restarts the computer into Windoze\n" -#~ " CustomCommandIsPersistent0=true\n" -#~ " \n" -#~ " CustomCommand1=/sbin/updatesystem;/usr/local/sbin/updatesystem\n" -#~ " CustomCommandLabel1=_Update Me\n" -#~ " CustomCommandLRLabel1=Update the system\n" -#~ " CustomCommandText1=Are you sure you want to update the system " -#~ "software?\n" -#~ " CustomCommandTooltip1=Updates the system\n" -#~ " CustomCommandNoRestart1=true\n" -#~ " \n" -#~ " CustomCommand3=/sbin/do_something\n" -#~ " .\n" -#~ " .\n" -#~ " .\n" -#~ " \n" -#~ " CustomCommand4=/sbin/do_something_else\n" -#~ " .\n" -#~ " .\n" -#~ " .\n" -#~ " </screen>" - -#~ msgid "" -#~ "You should not leave debug on after collecting data. It will clutter your " -#~ "syslog and slow system performance." -#~ msgstr "" -#~ "You should not leave debugging on after collecting data. It will clutter " -#~ "your syslog and slow system performance." - -#~ msgid "" -#~ "Another common problem is that the GDM greeter program is having trouble " -#~ "starting. This can happen, for example, if GDM cannot find a needed " -#~ "library or other resource. Try starting the Xserver and a terminal " -#~ "program, set the shell environment variable DOING_GDM_DEVELOPMENT=1 and " -#~ "run <command><lib>/gdmlogin</command> or <command><lib>/" -#~ "gdmgreeter</command>. Any error messages echoed to the terminal will " -#~ "likely highlight the problem. Also, turning on debug and checking the " -#~ "output sent to the system log will often highlight the problem." -#~ msgstr "" -#~ "Another common problem is that the GDM greeter program is having trouble " -#~ "starting. This can happen, for example, if GDM cannot find a needed " -#~ "library or other resource. Try starting the Xserver and a terminal " -#~ "program, set the shell environment variable DOING_GDM_DEVELOPMENT=1 and " -#~ "run <command><lib>/gdmlogin</command> or <command><lib>/" -#~ "gdmgreeter</command>. Any error messages echoed to the terminal will " -#~ "likely highlight the problem. Also, turning on debug and checking the " -#~ "output sent to the system log will often highlight the problem." - -#~ msgid "GDM Will Not Access User Settings" -#~ msgstr "GDM Will Not Access User Settings" - -#~ msgid "" -#~ "GDM saves user settings, such as your default session and default " -#~ "language, in the <filename>~/.dmrc</filename>. Other files, such as the " -#~ "user's <filename>~/.Xauthority</filename> file will also affect login. " -#~ "GDM, by default, is strict about how it tries to access files in the " -#~ "user's home directory, and will ignore the file if they do not conform to " -#~ "certain rules. You can use the <filename>RelaxPermissions</filename> " -#~ "configuration option to make GDM less strict about how it accesses files " -#~ "in the user's home directory, or correct the permissions issues that " -#~ "cause GDM to ignore the file. This is discussed in detail described in " -#~ "the \"File Access\" section of the \"Overview\"." -#~ msgstr "" -#~ "GDM saves user settings, such as your default session and default " -#~ "language, in the <filename>~/.dmrc</filename>. Other files, such as the " -#~ "user's <filename>~/.Xauthority</filename> file will also affect login. " -#~ "GDM, by default, is strict about how it tries to access files in the " -#~ "user's home directory, and will ignore the file if they do not conform to " -#~ "certain rules. You can use the <filename>RelaxPermissions</filename> " -#~ "configuration option to make GDM less strict about how it accesses files " -#~ "in the user's home directory, or correct the permissions issues that " -#~ "cause GDM to ignore the file. This is discussed in detail described in " -#~ "the \"File Access\" section of the \"Overview\"." diff --git a/docs/es/es.po b/docs/es/es.po index 3b13f6f3..a42b623c 100644 --- a/docs/es/es.po +++ b/docs/es/es.po @@ -2712,7 +2712,7 @@ msgstr "PingIntervalSeconds=60" #: C/index.docbook:1551 msgid "" "If the Xserver does not respond in the specified number of seconds, then the " -"connection is stopped and the session ended. When this happens the slave " +"connection is stopped and the session ended. When this happens the " "daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied " "this setting by 2, so it may be necessary to increase the timeout if " "upgrading from GDM 2.20 and earlier to a newer version." diff --git a/docs/fr/fr.po b/docs/fr/fr.po index 6fd3d5df..8cbc5274 100644 --- a/docs/fr/fr.po +++ b/docs/fr/fr.po @@ -2745,7 +2745,7 @@ msgstr "PingIntervalSeconds=60" #: C/index.docbook:1551 msgid "" "If the Xserver does not respond in the specified number of seconds, then the " -"connection is stopped and the session ended. When this happens the slave " +"connection is stopped and the session ended. When this happens the " "daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied " "this setting by 2, so it may be necessary to increase the timeout if " "upgrading from GDM 2.20 and earlier to a newer version." diff --git a/docs/gl/gl.po b/docs/gl/gl.po index 1fd4fb59..125a01e6 100644 --- a/docs/gl/gl.po +++ b/docs/gl/gl.po @@ -2351,7 +2351,7 @@ msgstr "PingIntervalSeconds=60" #: C/index.docbook:1553 msgid "" "If the Xserver does not respond in the specified number of seconds, then the " -"connection is stopped and the session ended. When this happens the slave " +"connection is stopped and the session ended. When this happens the " "daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied " "this setting by 2, so it may be necessary to increase the timeout if " "upgrading from GDM 2.20 and earlier to a newer version." diff --git a/docs/hu/hu.po b/docs/hu/hu.po index fe692936..d703269c 100644 --- a/docs/hu/hu.po +++ b/docs/hu/hu.po @@ -1999,7 +1999,7 @@ msgstr "" #: C/index.docbook:1551 msgid "" "If the Xserver does not respond in the specified number of seconds, then the " -"connection is stopped and the session ended. When this happens the slave " +"connection is stopped and the session ended. When this happens the " "daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied " "this setting by 2, so it may be necessary to increase the timeout if " "upgrading from GDM 2.20 and earlier to a newer version." diff --git a/docs/id/id.po b/docs/id/id.po index 4b0bcbdf..77ed676c 100644 --- a/docs/id/id.po +++ b/docs/id/id.po @@ -2666,13 +2666,13 @@ msgstr "PingIntervalSeconds=60" #: C/index.docbook:1551 msgid "" "If the Xserver does not respond in the specified number of seconds, then the " -"connection is stopped and the session ended. When this happens the slave " +"connection is stopped and the session ended. When this happens the " "daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied " "this setting by 2, so it may be necessary to increase the timeout if " "upgrading from GDM 2.20 and earlier to a newer version." msgstr "" "Bila Xserver tak merespon dalam sekian detik yang dinyatakan, maka koneksi " -"dihentikan dan sesi diakhiri. Ketika ini terjadi daemon slave mati dengan " +"dihentikan dan sesi diakhiri. Ketika ini terjadi daemon mati dengan " "sinyal ALARM. Perhatikan bahwa GDM 2.20 dan sebelumnya mengalikan 2 " "pengaturan ini, sehingga mungkin perlu menaikkan tenggang waktu bila " "meningkatkan dari GDM 2.20 dan sebelumnya ke versi yang lebih baru." diff --git a/docs/ko/ko.po b/docs/ko/ko.po index 5a63279d..a481e139 100644 --- a/docs/ko/ko.po +++ b/docs/ko/ko.po @@ -244,17 +244,11 @@ msgstr "" msgid "GDM can be asked to manage a display a number of ways. Local displays are always managed when GDM starts and will be restarted when a user's session is finished. Displays can be requested via XDMCP, flexible displays can be requested by running the <command>gdmflexiserver</command> command. Displays that are started on request are not restarted on session exit. GDM also provides the <command>gdmdynamic</command> command to allow easier management of displays on a multi-user server. These display types are discussed further in the next section." msgstr "" -#: ../C/gdm.xml:246(para) -msgid "When the GDM daemon is asked to manage a display, it will fork an X server process, then run the <filename>Init</filename> script as the root user, and start the login GUI dialog as a slave process on the display. GDM can be configured to use either <command>gdmgreeter</command> (the default) or <command>gdmlogin</command> as the GUI dialog program. The <command>gdmlogin</command> program supports accessibility while the <command>gdmgreeter</command> program supports greater themeability. The GUI dialog is run as the unpriviledged \"gdm\" user/group which is described in the \"Security\" section below. The GUI dialog communicates with the daemon via a sockets protocol and via standard input/output. The slave, for example passes the username and password information to the GDM daemon via standard input/output so the daemon can handle the actual authentication." -msgstr "" #: ../C/gdm.xml:263(para) msgid "The login GUI dialog screen allows the user to select which session they wish to start and which language they wish to use. Sessions are defined by files that end in the .desktop extension and more information about these files can be found in the \"Configuration\" section. The user enters their name and password and if these successfully authenticate, GDM will start the requested session for the user. It is possible to configure GDM to avoid the authentication process by turning on the Automatic or Timed Login features in the GDM configuration. The login GUI can also be configured to provide additional features to the user, such as the Face Browser; the ability to halt, restart, or suspend the system; and/or edit the login configuration (after entering the root password)." msgstr "" -#: ../C/gdm.xml:278(para) -msgid "GDM, by default, will use Pluggable Authentication Modules (PAM) for authentication, but can also support regular crypt and shadow passwords on legacy systems. After authenticating a user, the daemon runs the <filename>PostLogin</filename> script as root, and forks a slave process to start the requested session. This slave process runs the <filename>PreSession</filename> script as root, sets up the user's environment, and starts the requested session. GDM keeps track of the user's default session and language in the user's <filename>~/.dmrc</filename> and will use these defaults if the user did not pick a session or language in the login GUI. On Solaris, GDM (since version 2.8.0.3) uses the SDTLOGIN interface after user authentication to tell the X server to be restarted as the user instead of as root for added security. When the user's session exits, the GDM daemon will run the <filename>PostSession</filename> script as root." -msgstr "" #: ../C/gdm.xml:295(para) msgid "Note that, by default, GDM uses the \"gdm\" service name for normal login and the \"gdm-autologin\" service name for automatic login. The <filename>PamStack</filename> configuration option can be used to specify a different service name. For example, if \"foo\" is specified, then GDM will use the \"foo\" service name for normal login and \"foo-autologin\" for automatic login." @@ -524,9 +518,6 @@ msgstr "" msgid "For security reasons a dedicated user and group id are required for proper operation! The need to be able to write Xauth files is why user \"nobody\" is not appropriate for gdm." msgstr "" -#: ../C/gdm.xml:877(para) -msgid "The GDM daemon normally runs as root, as does the slave. However GDM should also have a dedicated user id and a group id which it uses for its graphical interfaces such as <command>gdmgreeter</command> and <command>gdmlogin</command>. These are configured via the <filename>User</filename> and <filename>Group</filename> configuration options in the GDM configuration files. The user and group should be created before running \"make install\". By default GDM assumes the user and the group are called \"gdm\"." -msgstr "" #: ../C/gdm.xml:888(para) msgid "This userid is used to run the GDM GUI programs required for login. All functionality that requires root authority is done by the GDM daemon process. This design ensures that if the GUI programs are somehow exploited, only the dedicated user privileges are available." @@ -847,9 +838,6 @@ msgstr "" msgid "This script should really load the user's profile and generally do all the voodoo that is needed to launch a session. Since many systems reset the language selections done by GDM, GDM will also set the <filename>$GDM_LANG</filename> variable to the selected language. You can use this to reset the language environmental variables after you run the user's profile. If the user elected to use the system language, then <filename>$GDM_LANG</filename> is not set." msgstr "" -#: ../C/gdm.xml:1610(para) -msgid "When the user terminates his session, the <filename>PostSession</filename> script will be run. Again operation is similar to <filename>Init</filename>, <filename>PostLogin</filename> and <filename>PreSession</filename>. Again the script will be run with root privileges, the slave daemon will block and the <filename>$USER</filename> environment variable will contain the name of the user who just logged out and <filename>$DISPLAY</filename> will be set to the display the user used, however note that the X server for this display may already be dead and so you shouldn't try to access it. Also <filename>$X_SERVERS</filename> environmental variable is set and this points to a fake generated X servers file for use with the sessreg accounting application." -msgstr "" #: ../C/gdm.xml:1625(para) msgid "Note that the <filename>PostSession</filename> script will be run even when the display fails to respond due to an I/O error or similar. Thus, there is no guarantee that X applications will work during script execution." @@ -3176,9 +3164,6 @@ msgstr "handled" msgid "handled=true" msgstr "handled=true" -#: ../C/gdm.xml:4276(para) -msgid "Indicates that GDM should run the login window on this server and allow a user to log in. If set to false, then GDM will just run this server and wait for it to terminate. This can be useful to run an X terminal using GDM. When this is done you should normally also add <filename>-terminate</filename> to the command line of the server to make the server terminate after each session. Otherwise the control of the slave will never come back to GDM and, for example, soft restarts won't work. This is because GDM assumes there is a login in progress for the entire time this server is active." -msgstr "" #: ../C/gdm.xml:4292(term) msgid "chooser" @@ -3313,9 +3298,6 @@ msgstr "" msgid "GDM also provides a FIFO called <filename>.gdmfifo</filename> in the <filename>ServAuthDir</filename> directory (usually <filename><var>/gdm/.gdmfifo</filename>). You must be root to use this protocol, and it is mostly used for internal GDM chatter. It is a very simple protocol where you just echo a command on a single line to this file. It can be used to tell GDM things such as restart, suspend the computer, or restart all X servers next time it has a chance (which would be useful from an X configuration application)." msgstr "" -#: ../C/gdm.xml:4529(para) -msgid "Full and up to date documentation of the commands and their use is contained in the GDM source tree in the file <filename>daemon/gdm.h</filename>. Look for the defines starting with <filename>GDM_SOP_</filename>. The commands which require the pid of the slave as an argument are the ones that are really used for internal communication of the slave with the master and should not be used." -msgstr "" #: ../C/gdm.xml:4541(title) msgid "Socket Protocol" @@ -3531,20 +3513,10 @@ msgstr "" msgid "SERVER_BUSY" msgstr "SERVER_BUSY" -#: ../C/gdm.xml:5083(screen) -#, no-wrap -msgid "\nSERVER_BUSY: Returns true if half or more of the daemon's sockets\n are busy, false otherwise. Used by slave programs\n which want to ensure they do not overwhelm the \n sever.\nSupported since: 2.13.0.8\nArguments: None\nAnswers:\n OK <value>\n ERROR <err number> <english error description>\n 0 = Not implemented\n 200 = Too many messages\n 999 = Unknown error\n" -msgstr "" - #: ../C/gdm.xml:5100(title) msgid "SET_LOGOUT_ACTION" msgstr "SET_LOGOUT_ACTION" -#: ../C/gdm.xml:5101(screen) -#, no-wrap -msgid "\nSET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n slave process exits. Only supported on\n connections that passed AUTH_LOCAL.\nSupported since: 2.5.90.0\nArguments: <action>\n NONE Set exit action to 'none'\n HALT Set exit action to 'halt'\n REBOOT Set exit action to 'reboot'\n SUSPEND Set exit action to 'suspend'\n CUSTOM_CMD[0-9] Set exit action to 'custom command [0-9]'\nAnswers:\n OK\n ERROR <err number> <english error description>\n 0 = Not implemented\n 7 = Unknown logout action, or not available\n 100 = Not authenticated\n 200 = Too many messages\n 999 = Unknown error\n" -msgstr "" - #: ../C/gdm.xml:5124(title) msgid "SET_SAFE_LOGOUT_ACTION" msgstr "SET_SAFE_LOGOUT_ACTION" diff --git a/docs/oc/oc.po b/docs/oc/oc.po index f6e0f88d..e0234621 100644 --- a/docs/oc/oc.po +++ b/docs/oc/oc.po @@ -356,22 +356,6 @@ msgid "" "discussed further in the next section." msgstr "" -#: ../C/gdm.xml:248(para) -msgid "" -"When the GDM daemon is asked to manage a display, it will fork an X server " -"process, then run the <filename>Init</filename> script as the root user, and " -"start the login GUI dialog as a slave process on the display. GDM can be " -"configured to use either <command>gdmgreeter</command> (the default) or " -"<command>gdmlogin</command> as the GUI dialog program. The " -"<command>gdmlogin</command> program supports accessibility while the " -"<command>gdmgreeter</command> program supports greater themeability. The GUI " -"dialog is run as the unpriviledged \"gdm\" user/group which is described in " -"the \"Security\" section below. The GUI dialog communicates with the daemon " -"via a sockets protocol and via standard input/output. The slave, for example " -"passes the username and password information to the GDM daemon via standard " -"input/output so the daemon can handle the actual authentication." -msgstr "" - #: ../C/gdm.xml:265(para) msgid "" "The login GUI dialog screen allows the user to select which session they " @@ -387,23 +371,6 @@ msgid "" "(after entering the root password)." msgstr "" -#: ../C/gdm.xml:280(para) -msgid "" -"GDM, by default, will use Pluggable Authentication Modules (PAM) for " -"authentication, but can also support regular crypt and shadow passwords on " -"legacy systems. After authenticating a user, the daemon runs the " -"<filename>PostLogin</filename> script as root, and forks a slave process to " -"start the requested session. This slave process runs the " -"<filename>PreSession</filename> script as root, sets up the user's " -"environment, and starts the requested session. GDM keeps track of the user's " -"default session and language in the user's <filename>~/.dmrc</filename> and " -"will use these defaults if the user did not pick a session or language in " -"the login GUI. On Solaris, GDM (since version 2.8.0.3) uses the SDTLOGIN " -"interface after user authentication to tell the X server to be restarted as " -"the user instead of as root for added security. When the user's session " -"exits, the GDM daemon will run the <filename>PostSession</filename> script " -"as root." -msgstr "" #: ../C/gdm.xml:297(para) msgid "" @@ -994,16 +961,6 @@ msgid "" "is not appropriate for gdm." msgstr "" -#: ../C/gdm.xml:879(para) -msgid "" -"The GDM daemon normally runs as root, as does the slave. However GDM should " -"also have a dedicated user id and a group id which it uses for its graphical " -"interfaces such as <command>gdmgreeter</command> and <command>gdmlogin</" -"command>. These are configured via the <filename>User</filename> and " -"<filename>Group</filename> configuration options in the GDM configuration " -"files. The user and group should be created before running \"make install\". " -"By default GDM assumes the user and the group are called \"gdm\"." -msgstr "" #: ../C/gdm.xml:890(para) msgid "" @@ -1778,20 +1735,6 @@ msgid "" "is not set." msgstr "" -#: ../C/gdm.xml:1641(para) -msgid "" -"When the user terminates his session, the <filename>PostSession</filename> " -"script will be run. Again operation is similar to <filename>Init</filename>, " -"<filename>PostLogin</filename> and <filename>PreSession</filename>. Again " -"the script will be run with root privileges, the slave daemon will block and " -"the <filename>$USER</filename> environment variable will contain the name of " -"the user who just logged out and <filename>$DISPLAY</filename> will be set " -"to the display the user used, however note that the X server for this " -"display may already be dead and so you shouldn't try to access it. Also " -"<filename>$X_SERVERS</filename> environmental variable is set and this " -"points to a fake generated X servers file for use with the sessreg " -"accounting application." -msgstr "" #: ../C/gdm.xml:1656(para) msgid "" @@ -4989,18 +4932,6 @@ msgstr "" msgid "handled=true" msgstr "" -#: ../C/gdm.xml:4376(para) -msgid "" -"Indicates that GDM should run the login window on this server and allow a " -"user to log in. If set to false, then GDM will just run this server and wait " -"for it to terminate. This can be useful to run an X terminal using GDM. When " -"this is done you should normally also add <filename>-terminate</filename> to " -"the command line of the server to make the server terminate after each " -"session. Otherwise the control of the slave will never come back to GDM and, " -"for example, soft restarts won't work. This is because GDM assumes there is " -"a login in progress for the entire time this server is active." -msgstr "" - #: ../C/gdm.xml:4392(term) msgid "chooser" msgstr "" @@ -5249,16 +5180,6 @@ msgid "" "application)." msgstr "" -#: ../C/gdm.xml:4629(para) -msgid "" -"Full and up to date documentation of the commands and their use is contained " -"in the GDM source tree in the file <filename>daemon/gdm.h</filename>. Look " -"for the defines starting with <filename>GDM_SOP_</filename>. The commands " -"which require the pid of the slave as an argument are the ones that are " -"really used for internal communication of the slave with the master and " -"should not be used." -msgstr "" - #: ../C/gdm.xml:4641(title) msgid "Socket Protocol" msgstr "" @@ -5895,52 +5816,10 @@ msgstr "" msgid "SERVER_BUSY" msgstr "" -#: ../C/gdm.xml:5185(screen) -#, no-wrap -msgid "" -"\n" -"SERVER_BUSY: Returns true if half or more of the daemon's sockets\n" -" are busy, false otherwise. Used by slave programs\n" -" which want to ensure they do not overwhelm the \n" -" sever.\n" -"Supported since: 2.13.0.8\n" -"Arguments: None\n" -"Answers:\n" -" OK <value>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -msgstr "" - #: ../C/gdm.xml:5202(title) msgid "SET_LOGOUT_ACTION" msgstr "" -#: ../C/gdm.xml:5203(screen) -#, no-wrap -msgid "" -"\n" -"SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n" -" slave process exits. Only supported on\n" -" connections that passed AUTH_LOCAL.\n" -"Supported since: 2.5.90.0\n" -"Arguments: <action>\n" -" NONE Set exit action to 'none'\n" -" HALT Set exit action to 'halt'\n" -" REBOOT Set exit action to 'reboot'\n" -" SUSPEND Set exit action to 'suspend'\n" -" CUSTOM_CMD[0-9] Set exit action to 'custom command [0-9]'\n" -"Answers:\n" -" OK\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 7 = Unknown logout action, or not available\n" -" 100 = Not authenticated\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -msgstr "" - #: ../C/gdm.xml:5226(title) msgid "SET_SAFE_LOGOUT_ACTION" msgstr "" diff --git a/docs/pt_BR/pt_BR.po b/docs/pt_BR/pt_BR.po index 87dd1af8..182ae78d 100644 --- a/docs/pt_BR/pt_BR.po +++ b/docs/pt_BR/pt_BR.po @@ -1962,16 +1962,6 @@ msgid "PingIntervalSeconds=60" msgstr "" #. (itstool) path: listitem/para -#: C/index.docbook:1553 -msgid "" -"If the Xserver does not respond in the specified number of seconds, then the " -"connection is stopped and the session ended. When this happens the slave " -"daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied " -"this setting by 2, so it may be necessary to increase the timeout if " -"upgrading from GDM 2.20 and earlier to a newer version." -msgstr "" - -#. (itstool) path: listitem/para #: C/index.docbook:1562 msgid "" "Note that GDM in the past used to have a <filename>PingInterval</filename> " diff --git a/docs/ro/ro.po b/docs/ro/ro.po index 444e41b1..0d3b5e04 100644 --- a/docs/ro/ro.po +++ b/docs/ro/ro.po @@ -2793,7 +2793,7 @@ msgstr "PingIntervalSeconds=60" #: C/index.docbook:1551 msgid "" "If the Xserver does not respond in the specified number of seconds, then the " -"connection is stopped and the session ended. When this happens the slave " +"connection is stopped and the session ended. When this happens the " "daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied " "this setting by 2, so it may be necessary to increase the timeout if " "upgrading from GDM 2.20 and earlier to a newer version." diff --git a/docs/ru/ru.po b/docs/ru/ru.po index 5df0ff85..db028412 100644 --- a/docs/ru/ru.po +++ b/docs/ru/ru.po @@ -2730,16 +2730,6 @@ msgid "PingIntervalSeconds=60" msgstr "PingIntervalSeconds=60" #. (itstool) path: listitem/para -#: C/index.docbook:1551 -msgid "" -"If the Xserver does not respond in the specified number of seconds, then the " -"connection is stopped and the session ended. When this happens the slave " -"daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied " -"this setting by 2, so it may be necessary to increase the timeout if " -"upgrading from GDM 2.20 and earlier to a newer version." -msgstr "" - -#. (itstool) path: listitem/para #: C/index.docbook:1560 msgid "" "Note that GDM in the past used to have a <filename>PingInterval</filename> " diff --git a/docs/sl/sl.po b/docs/sl/sl.po index 1bd858c9..37fa4139 100644 --- a/docs/sl/sl.po +++ b/docs/sl/sl.po @@ -1139,10 +1139,6 @@ msgstr "" msgid "PingIntervalSeconds=60" msgstr "" -#: C/gdm.xml:1532(para) -msgid "If the Xserver does not respond in the specified number of seconds, then the connection is stopped and the session ended. When this happens the slave daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied this setting by 2, so it may be necessary to increase the timeout if upgrading from GDM 2.20 and earlier to a newer version." -msgstr "" - #: C/gdm.xml:1541(para) msgid "Note that GDM in the past used to have a <filename>PingInterval</filename> configuration key which was also in minutes. For most purposes you'd want this setting to be lower than one minute. However since in most cases where XDMCP would be used (such as terminal labs), a lag of more than 15 or so seconds would really mean that the terminal was turned off or restarted and you would want to end the session." msgstr "" diff --git a/docs/sv/sv.po b/docs/sv/sv.po index a7fa9b84..941f5f94 100644 --- a/docs/sv/sv.po +++ b/docs/sv/sv.po @@ -2075,17 +2075,6 @@ msgid "PingIntervalSeconds=60" msgstr "PingIntervalSeconds=60" #. (itstool) path: listitem/para -#: C/index.docbook:1551 -msgid "" -"If the Xserver does not respond in the specified number of seconds, then the connection is stopped and the session ended. When this " -"happens the slave daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied this setting by 2, so it may be necessary " -"to increase the timeout if upgrading from GDM 2.20 and earlier to a newer version." -msgstr "" -"Om Xservern inte svarar inom det angivna antalet sekunder kommer anslutningen att stoppas och sessionen att avslutas. När detta händer " -"kommer slavdemonen att dö med en ALARM-signal. Notera att GDM 2.20 och tidigare multiplicerade denna inställning med 2 så det kan vara " -"nödvändigt att öka tidsbegränsningen om du uppgraderar från GDM 2.20 och tidigare till en nyare version." - -#. (itstool) path: listitem/para #: C/index.docbook:1560 msgid "" "Note that GDM in the past used to have a <filename>PingInterval</filename> configuration key which was also in minutes. For most " diff --git a/docs/te/te.po b/docs/te/te.po index f46acaf8..7ee9aede 100644 --- a/docs/te/te.po +++ b/docs/te/te.po @@ -1773,15 +1773,6 @@ msgstr "" msgid "PingIntervalSeconds=60" msgstr "" -#: C/gdm.xml:1551(para) -msgid "" -"If the Xserver does not respond in the specified number of seconds, then the " -"connection is stopped and the session ended. When this happens the slave " -"daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied " -"this setting by 2, so it may be necessary to increase the timeout if " -"upgrading from GDM 2.20 and earlier to a newer version." -msgstr "" - #: C/gdm.xml:1560(para) msgid "" "Note that GDM in the past used to have a <filename>PingInterval</filename> " diff --git a/docs/uk/uk.po b/docs/uk/uk.po index 0cf15160..16cbfe83 100644 --- a/docs/uk/uk.po +++ b/docs/uk/uk.po @@ -233,18 +233,10 @@ msgstr "" msgid "GDM can be asked to manage a display a number of ways. Local displays are always managed when GDM starts and will be restarted when a user's session is finished. Displays can be requested via XDMCP, flexible displays can be requested by running the <command>gdmflexiserver</command> command. Displays that are started on request are not restarted on session exit. GDM also provides the <command>gdmdynamic</command> command to allow easier management of displays on a multi-user server. These display types are discussed further in the next section." msgstr "" -#: ../C/gdm.xml:225(para) -msgid "When the GDM daemon is asked to manage a display, it will fork an X server process, then run the <filename>Init</filename> script as the root user, and start the login GUI dialog as a slave process on the display. GDM can be configured to use either <command>gdmgreeter</command> (the default) or <command>gdmlogin</command> as the GUI dialog program. The <command>gdmlogin</command> program supports accessibility while the <command>gdmgreeter</command> program supports greater themeability. The GUI dialog is run as the unpriviledged \"gdm\" user/group which is described in the \"Security\" section below. The GUI dialog communicates with the daemon via a sockets protocol and via standard input/output. The slave, for example passes the username and password information to the GDM daemon via standard input/output so the daemon can handle the actual authentication." -msgstr "" - #: ../C/gdm.xml:242(para) msgid "The login GUI dialog screen allows the user to select which session they wish to start and which language they wish to use. Sessions are defined by files that end in the .desktop extension and more information about these files can be found in the \"Configuration\" section. The user enters their name and password and if these successfully authenticate, GDM will start the requested session for the user. It is possible to configure GDM to avoid the authentication process by turning on the Automatic or Timed Login features in the GDM configuration. The login GUI can also be configured to provide additional features to the user, such as the Face Browser; the ability to halt, restart, or suspend the system; and/or edit the login configuration (after entering the root password)." msgstr "" -#: ../C/gdm.xml:257(para) -msgid "GDM, by default, will use Pluggable Authentication Modules (PAM) for authentication, but can also support regular crypt and shadow passwords on legacy systems. After authenticating a user, the daemon runs the <filename>PostLogin</filename> script as root, and forks a slave process to start the requested session. This slave process runs the <filename>PreSession</filename> script as root, sets up the users environment, and starts the requested session. GDM keeps track of the user's default session and language in the user's <filename>~/.dmrc</filename> and will use these defaults if the user did not pick a session or language in the login GUI. On Solaris, GDM (since version 2.8.0.3) uses the SDTLOGIN interface after user authentication to tell the X server to be restarted as the user instead of as root for added security. When the users session exits, the GDM daemon will run the <filename>PostSession</filename> script as root." -msgstr "" - #: ../C/gdm.xml:276(title) msgid "Different Display Types" msgstr "Різні типи дисплеїв" @@ -485,10 +477,6 @@ msgstr "Користувач GDM" msgid "For security reasons a dedicated user and group id are required for proper operation! The need to be able to write Xauth files is why user \"nobody\" is not appropriate for gdm." msgstr "" -#: ../C/gdm.xml:785(para) -msgid "The GDM daemon normally runs as root, as does the slave. However GDM should also have a dedicated user id and a group id which it uses for its graphical interfaces such as <command>gdmgreeter</command> and <command>gdmlogin</command>. These are configured via the <filename>User</filename> and <filename>Group</filename> configuration options in the GDM configuration files. The user and group should be created before running \"make install\". By default GDM assumes the user and the group are called \"gdm\"." -msgstr "Зазвичай GDM сервер запускається від імені адміністратора (root). Але GDM також має призначені ідентифікатори користувача (uid) та групи (gid), якими він користується для запуску графічного інтерфейсу, тобто <command>gdmgreeter</command> та <command>gdmlogin</command>. Вона налаштовуються у параметрах <filename>User</filename> та <filename>Group</filename> у файлі конфігурації GDM. Користувач та група мають існувати перед запуском \"make install\". Зазвичай користувач та група GDM називається \"gdm\". " - #: ../C/gdm.xml:796(para) msgid "This userid is used to run the GDM GUI programs required for login. All functionality that requires root authority is done by the GDM daemon process. This design ensures that if the GUI programs are somehow exploited, only the dedicated user privileges are available." msgstr "" @@ -736,10 +724,6 @@ msgstr "Після цього запускається основний сцен msgid "This script should really load the users profile and generally do all the voodoo that is needed to launch a session. Since many systems reset the language selections done by GDM, GDM will also set the <filename>$GDM_LANG</filename> variable to the selected language. You can use this to reset the language environmental variables after you run the users profile. If the user elected to use the system language, then <filename>$GDM_LANG</filename> is not set." msgstr "Цей сценарій повинен зчитати профіль користувача та виконати всю роботу, необхідну для встановлення сеансу. Через те, що у деяких системах скидається вибране користувачем у GDM значення мови, GDM також встановлює змінну оточення <filename>$GDM_LANG</filename> у вибране значення мови. Можна її використовувати для встановлення змінних оточення після запуску профілю, які відповідають за вибір мови. Якщо користувач вибрав системну мову, тоді <filename>$GDM_LANG</filename> не встановлюється." -#: ../C/gdm.xml:1266(para) -msgid "When the user terminates his session, the <filename>PostSession</filename> script will be run. Again operation is similar to <filename>Init</filename>, <filename>PostLogin</filename> and <filename>PreSession</filename>. Again the script will be run with root privileges, the slave daemon will block and the <filename>$USER</filename> environment variable will contain the name of the user who just logged out and <filename>$DISPLAY</filename> will be set to the display the user used, however note that the X server for this display may already be dead and so you shouldn't try to access it. Also <filename>$X_SERVERS</filename> environmental variable is set and this points to a fake generated X servers file for use with the sessreg accounting application." -msgstr "Коли користувач завершує сеанс, знову виконується сценарій з <filename>PostSession</filename>. Всі дії такі самі як і у <filename>Init</filename>, <filename>PostLogin</filename> та <filename>PreSession</filename>. Знову ж таки сценарій запускається з правами адміністратора (root), допоміжний процес сервера блокується. Змінна оточення <filename>$USER</filename> містить ім'я користувача, який завершує сеанс, змінна оточення <filename>$DISPLAY</filename> буде встановлена у значення дисплею, але зверніть увагу, що X-сервер для цього дисплею може бути вже завершений, тому не слід намагатись отримати до нього доступ. Тут встановлена змінна оточення <filename>$X_SERVERS</filename>, вона має значення фальшивого згенерованого файлу x-сервера для використання з програмою обліку sessreg." - #: ../C/gdm.xml:1281(para) msgid "Note that the <filename>PostSession</filename> script will be run even when the display fails to respond due to an I/O error or similar. Thus, there is no guarantee that X applications will work during script execution." msgstr "Зверніть увагу, сценарій <filename>PostSession</filename> запускається навіть якщо дисплей завершився аварійно через помилку вводу/виводу або щось подібне. Тому, не гарантується, що X-програми працюватимуть при його виконанні." @@ -2933,10 +2917,6 @@ msgstr "handled" msgid "handled=true" msgstr "handled=true" -#: ../C/gdm.xml:3723(para) -msgid "Indicates that GDM should run the login window on this server and allow a user to log in. If set to false, then GDM will just run this server and wait for it to terminate. This can be useful to run an X terminal using GDM. When this is done you should normally also add <filename>-terminate</filename> to the command line of the server to make the server terminate after each session. Otherwise the control of the slave will never come back to GDM and, for example, soft restarts won't work. This is because GDM assumes there is a login in progress for the entire time this server is active." -msgstr "Означає, що GDM має виводити вікно запрошення до входу на цьому сервері. Якщо значення false, тоді GDM просто запускає цей сервер та очікує завершення. Це корисно для запуску X-терміналів через GDM. Також звичайно можна додати до командного рядка сервера <filename>-terminate</filename>, щоб сервер завершувався після завершення кожного сеансу. У іншому випадку керування над породженим процесом ніколи не повернеться до GDM та, наприклад, не працюватиме м'який перезапуск, бо GDM вважатиме, що сеанс триває весь час активності сервера." - #: ../C/gdm.xml:3739(term) msgid "chooser" msgstr "chooser" @@ -3086,10 +3066,6 @@ msgstr "Протокол роботи з FIFO" msgid "GDM also provides a FIFO called <filename>.gdmfifo</filename> in the <filename>ServAuthDir</filename> directory (usually <filename><var>/gdm/.gdmfifo</filename>). You must be root to use this protocol, and it is mostly used for internal GDM chatter. It is a very simple protocol where you just echo a command on a single line to this file. It can be used to tell GDM things such as restart, suspend the computer, or restart all X servers next time it has a chance (which would be useful from an X configuration application)." msgstr "GDM також має канал FIFO з назвою <filename>.gdmfifo</filename> у каталозі <filename>ServAuthDir</filename> (зазвичай <filename><var>/gdm/.gdmfifo</filename>). Користуватись цим протоколом може лише root, і він здебільшого використовується для внутрішнього обміну GDM. Це дуже простий протокол. Ви надсилаєте команди через echo по одній команді на рядок. Він може використовуватись, щоб змусити GDM виконати перезавантаження, призупинення комп'ютера чи перезапустити усі X-сервери одразу коли буде можливість (це корисно для програми налаштовування X-сервера)." -#: ../C/gdm.xml:3978(para) -msgid "Full and up to date documentation of the commands and their use is contained in the GDM source tree in the file <filename>daemon/gdm.h</filename>. Look for the defines starting with <filename>GDM_SOP_</filename>. The commands which require the pid of the slave as an argument are the ones that are really used for internal communication of the slave with the master and should not be used." -msgstr "Повна та оновлена документація з команд та їх використання міститься у програмному коді GDM у файлі <filename>daemon/gdm.h</filename>. Шукайте визначення, що починаються з <filename>GDM_SOP_</filename>. Команди, яким у аргументі слід вказувати pid дочірнього процесу, - це команди які справді використовуються для внутрішнього зв'язку дочірнього процесу з головним процесом. Такі команди не слід використовувати." - #: ../C/gdm.xml:3990(title) msgid "Socket Protocol" msgstr "Протокол роботи з сокетом" @@ -3885,84 +3861,10 @@ msgstr "" msgid "SERVER_BUSY" msgstr "SERVER_BUSY" -#: ../C/gdm.xml:4411(screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"SERVER_BUSY: Returns true if half or more of the daemon's sockets\n" -" are busy, false otherwise. Used by slave programs\n" -" which want to ensure they do not overwhelm the \n" -" sever.\n" -"Supported since: 2.13.0.8\n" -"Arguments: None\n" -"Answers:\n" -" OK <value>\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -msgstr "" -"\n" -"GREETERPIDS: Список усіх ідентифікаторів процесів програм привітання.\n" -" З його допомогою можна надіслати сигнал HUP усім процесам\n" -" для повторного зчитування конфігурації. Це може робити лише root.\n" -"Підтримується з: 2.3.90.2\n" -"Аргументи: Немає\n" -"Відповідь:\n" -" OK <номер процесу>;<номер процесу>;...\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" -" " - #: ../C/gdm.xml:4428(title) msgid "SET_LOGOUT_ACTION" msgstr "SET_LOGOUT_ACTION" -#: ../C/gdm.xml:4429(screen) -#, fuzzy, no-wrap -msgid "" -"\n" -"SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n" -" slave process exits. Only supported on\n" -" connections that passed AUTH_LOCAL.\n" -"Supported since: 2.5.90.0\n" -"Arguments: <action>\n" -" NONE Set exit action to 'none'\n" -" HALT Set exit action to 'halt'\n" -" REBOOT Set exit action to 'reboot'\n" -" SUSPEND Set exit action to 'suspend'\n" -"Answers:\n" -" OK\n" -" ERROR <err number> <english error description>\n" -" 0 = Not implemented\n" -" 7 = Unknown logout action, or not available\n" -" 100 = Not authenticated\n" -" 200 = Too many messages\n" -" 999 = Unknown error\n" -msgstr "" -"\n" -"SET_LOGOUT_ACTION: Вказує службі вимкнути/перезапустити/призупинити\n" -" комп'ютер після завершення підлеглого процесу. \n" -"Підтримується лише для з'єднань, які пройшли AUTH_LOCAL.\n" -"Підтримується з: 2.5.90.0\n" -"Аргументи: <дія>\n" -" NONE Встановити дію при виході у 'none'\n" -" HALT Встановити дію при виході у 'halt'\n" -" REBOOT Встановити дію при виході у 'reboot'\n" -" SUSPEND Встановити дію при виході у 'suspend'\n" -"\n" -"Відповідь:\n" -" OK\n" -" ERROR <код помилки> <опис помилки англійською>\n" -" 0 = Не реалізовано\n" -" 7 = Невідома дія при виході, або дія недоступна\n" -" 100 = Немає автентифікації\n" -" 200 = Надто багато повідомлень\n" -" 999 = Невідома помилка\n" -" " - #: ../C/gdm.xml:4451(title) msgid "SET_SAFE_LOGOUT_ACTION" msgstr "SET_SAFE_LOGOUT_ACTION" diff --git a/docs/zh_CN/zh_CN.po b/docs/zh_CN/zh_CN.po index 8b2991d7..b6d22c36 100644 --- a/docs/zh_CN/zh_CN.po +++ b/docs/zh_CN/zh_CN.po @@ -2404,7 +2404,7 @@ msgstr "PingIntervalSeconds=60" #: C/index.docbook:1551 msgid "" "If the Xserver does not respond in the specified number of seconds, then the " -"connection is stopped and the session ended. When this happens the slave " +"connection is stopped and the session ended. When this happens the " "daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied " "this setting by 2, so it may be necessary to increase the timeout if " "upgrading from GDM 2.20 and earlier to a newer version." |