Translations by David Lodge
David Lodge has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
| 1. |
Didn't understand `%s' (expected integer)
|
|
| 2007-06-03 |
Didn't understand `%s' (expected integer)
|
|
| 2. |
Integer `%s' is too large or small
|
|
| 2007-06-03 |
Integer `%s' is too large or small
|
|
| 3. |
Didn't understand `%s' (expected true or false)
|
|
| 2007-06-03 |
Didn't understand `%s' (expected true or false)
|
|
| 4. |
Text contains invalid UTF-8
|
|
| 2007-06-03 |
Text contains invalid UTF-8
|
|
| 5. |
Common Desktop Environment (CDE)
|
|
| 2007-06-03 |
Common Desktop Environment (CDE)
|
|
| 9. |
Failed to start the X server (your graphical interface). It is likely that it is not set up correctly. You will need to log in on a console and reconfigure the X server. Then restart GDM.
|
|
| 2006-10-06 |
Failed to start the X server (your graphical interface). It is likely that it is not set up correctly. You will need to log in on a console and reconfigure the X server. Then restart GDM.
|
|
| 10. |
Would you like to try to configure the X server? Note that you will need the root password for this.
|
|
| 2006-10-06 |
Would you like to try to configure the X server? Note that you will need the root password for this.
|
|
| 13. |
The X server is now disabled. Restart GDM when it is configured correctly.
|
|
| 2006-10-06 |
The X server is now disabled. Restart GDM when it is configured correctly.
|
|
| 14. |
Failed to start the X server (your graphical interface). It is likely that it is not set up correctly. Would you like to view the X server output to diagnose the problem?
|
|
| 2006-10-06 |
Failed to start the X server (your graphical interface). It is likely that it is not set up correctly. Would you like to view the X server output to diagnose the problem?
|
|
| 16. |
Failed to start the X server (your graphical interface). It seems that the pointer device (your mouse) is not set up correctly. Would you like to view the X server output to diagnose the problem?
|
|
| 2006-10-06 |
Failed to start the X server (your graphical interface). It seems that the pointer device (your mouse) is not set up correctly. Would you like to view the X server output to diagnose the problem?
|
|
| 17. |
Would you like to try to configure the mouse? Note that you will need the root password for this.
|
|
| 2006-10-06 |
Would you like to try to configure the mouse? Note that you will need the root password for this.
|
|
| 18. |
System has no Xclients file, so starting a failsafe xterm session. Windows will have focus only if the mouse pointer is above them. To get out of this mode type 'exit' in the window.
|
|
| 2007-06-14 |
System has no Xclients file, so starting a failsafe xterm session. Windows will have focus only if the mouse pointer is above them. To get out of this mode type 'exit' in the window.
|
|
| 19. |
Failed to start the session, so starting a failsafe xterm session. Windows will have focus only if the mouse pointer is above them. To get out of this mode type 'exit' in the window.
|
|
| 2007-06-14 |
Failed to start the session, so starting a failsafe xterm session. Windows will have focus only if the mouse pointer is above them. To get out of this mode type 'exit' in the window.
|
|
| 25. |
%s: Could not write new authorization entry. Possibly out of diskspace
|
|
| 2009-07-03 |
%s: Could not write new authorization entry. Possibly out of diskspace
|
|
| 26. |
GDM could not write a new authorization entry to disk. Possibly out of diskspace.%s%s
|
|
| 2009-07-03 |
GDM could not write a new authorization entry to disk. Possibly out of diskspace.%s%s
|
|
| 46. |
Server Authorization directory (daemon/ServAuthDir) is set to %s but this does not exist. Please correct GDM configuration and restart GDM.
|
|
| 2009-07-03 |
Server Authorization directory (daemon/ServAuthDir) is set to %s but this does not exist. Please correct GDM configuration and restart GDM.
|
|
| 48. |
Server Authorization directory (daemon/ServAuthDir) is set to %s but this is not a directory. Please correct GDM configuration and restart GDM.
|
|
| 2009-07-03 |
Server Authorization directory (daemon/ServAuthDir) is set to %s but this is not a directory. Please correct GDM configuration and restart GDM.
|
|
| 50. |
%s: BaseXsession empty; using %s
|
|
| 2007-06-03 |
%s: BaseXsession empty; using %s
|
|
| 58. |
XDMCP is disabled and GDM cannot find any static server to start. Aborting! Please correct the configuration and restart GDM.
|
|
| 2009-07-03 |
XDMCP is disabled and GDM cannot find any static server to start. Aborting! Please correct the configuration and restart GDM.
|
|
| 61. |
The GDM user is set to be root, but this is not allowed since it can pose a security risk. Please correct GDM configuration and restart GDM.
|
|
| 2006-10-06 |
The GDM user is set to be root, but this is not allowed since it can pose a security risk. Please correct GDM configuration and restart GDM.
|
|
| 67. |
Server Authorization directory (daemon/ServAuthDir) is set to %s but is not owned by user %d and group %d. Please correct the ownership or GDM configuration and restart GDM.
|
|
| 2007-06-03 |
Server Authorisation directory (daemon/ServAuthDir) is set to %s but is not owned by user %d and group %d. Please correct the ownership or GDM configuration and restart GDM.
|
|
| 68. |
%s: Authdir %s is not owned by user %d, group %d. Aborting.
|
|
| 2007-06-03 |
%s: Authdir %s is not owned by user %d, group %d. Aborting.
|
|
| 69. |
Server Authorization directory (daemon/ServAuthDir) is set to %s but has the wrong permissions: it should have permissions of %o. Please correct the permissions or the GDM configuration and restart GDM.
|
|
| 2009-07-03 |
Server Authorization directory (daemon/ServAuthDir) is set to %s but has the wrong permissions: it should have permissions of %o. Please correct the permissions or the GDM configuration and restart GDM.
|
|
| 76. |
Cannot write PID file %s: possibly out of diskspace. Error: %s
|
|
| 2009-07-03 |
Cannot write PID file %s: possibly out of diskspace. Error: %s
|
|
| 82. |
The X server (your graphical interface) cannot be started. It is likely that it is not set up correctly. You will need to log in on a console and rerun the X configuration application, then restart GDM.
|
|
| 2006-10-06 |
The X server (your graphical interface) cannot be started. It is likely that it is not set up correctly. You will need to log in on a console and rerun the X configuration application, then restart GDM.
|
|
| 104. |
Alternative GDM System Defaults configuration file
|
|
| 2007-06-03 |
Alternative GDM System Defaults configuration file
|
|
| 128. |
Display '%s' cannot be opened by nested display
|
|
| 2007-06-03 |
Display '%s' cannot be opened by nested display
|
|
| 158. |
Could not execute the configuration application. Make sure its path is set correctly in the configuration file. Attempting to start it from the default location.
|
|
| 2006-10-06 |
Could not execute the configuration application. Make sure its path is set correctly in the configuration file. Attempting to start it from the default location.
|
|
| 159. |
Could not execute the configuration application. Make sure its path is set correctly in the configuration file.
|
|
| 2006-10-06 |
Could not execute the configuration application. Make sure its path is set correctly in the configuration file.
|
|
| 169. |
Cannot start the greeter application; you will not be able to log in. This display will be disabled. Try logging in by other means and editing the configuration file
|
|
| 2006-10-06 |
Cannot start the greeter application; you will not be able to log in. This display will be disabled. Try logging in by other means and editing the configuration file
|
|
| 174. |
Cannot start the chooser application. You will probably not be able to log in. Please contact the system administrator.
|
|
| 2006-10-06 |
Cannot start the chooser application. You will probably not be able to log in. Please contact the system administrator.
|
|
| 184. |
No Exec line in the session file: %s. Running the GNOME failsafe session instead
|
|
| 2006-10-06 |
No Exec line in the session file: %s. Running the GNOME failsafe session instead
|
|
| 186. |
%s: Cannot find or run the base Xsession script. Running the GNOME failsafe session instead.
|
|
| 2009-07-03 |
%s: Cannot find or run the base session script. Running the GNOME failsafe session insteae.
|
|
| 193. |
This is the Failsafe xterm session. You will be logged into a terminal console and be prompted to enter the password for root so that you may fix your system if you cannot log in any other way. To exit the terminal emulator, type 'exit' and an enter into the window.
|
|
| 2009-07-03 |
This is the Failsafe xterm session. You will be logged into a terminal console and be prompted to enter the password for root so that you may fix your system if you cannot log in any other way. To exit the terminal emulator, type 'exit' and an enter into the window.
|
|
| 198. |
%s: Could not exec %s
|
|
| 2007-06-14 |
%s: Could not exec %s
|
|
| 204. |
User's $HOME/.dmrc file is being ignored. This prevents the default session and language from being saved. File should be owned by user and have 644 permissions. User's $HOME directory must be owned by user and not writable by other users.
|
|
| 2006-10-06 |
User's $HOME/.dmrc file is being ignored. This prevents the default session and language from being saved. File should be owned by user and have 644 permissions. User's $HOME directory must be owned by user and not writable by other users.
|
|
| 205. |
GDM could not write to your authorization file. This could mean that you are out of disk space or that your home directory could not be opened for writing. In any case, it is not possible to log in. Please contact your system administrator
|
|
| 2009-07-03 |
GDM could not write to your authorization file. This could mean that you are out of disk space or that your home directory could not be opened for writing. In any case, it is not possible to log in. Please contact your system administrator
|
|
| 207. |
Your session only lasted less than 10 seconds. If you have not logged out yourself, this could mean that there is some installation problem or that you may be out of diskspace. Try logging in with one of the failsafe sessions to see if you can fix this problem.
|
|
| 2009-07-03 |
Your session only lasted less than 10 seconds. If you have not logged out yourself, this could mean that there is some installation problem or that you may be out of diskspace. Try logging in with one of the failsafe sessions to see if you can fix this problem.
|
|
| 226. |
Your password has been changed but you may have to change it again. Please try again later or contact your system administrator.
|
|
| 2009-07-03 |
Your password has been changed but you may have to change it again. Please try again later or contact your system administrator.
|
|
| 228. |
An internal error occurred. You will not be able to log in.
Please try again later or contact your system administrator.
|
|
| 2009-07-03 |
An internal error occured. You will not be able to log in.
Please try again later or contact your system administrator.
|
|
| 294. |
The main area of this application shows the hosts on the local network that have "XDMCP" enabled. This allows users to login remotely to other computers as if they were logged on using the console.
You can rescan the network for new hosts by clicking "Refresh". When you have selected a host click "Connect" to open a session to that computer.
|
|
| 2006-10-06 |
The main area of this application shows the hosts on the local network that have "XDMCP" enabled. This allows users to login remotely to other computers as if they were logged on using the console.
You can rescan the network for new hosts by clicking "Refresh". When you have selected a host click "Connect" to open a session to that computer.
|
|
| 302. |
The chooser version (%s) does not match the daemon version (%s). You have probably just upgraded GDM. Please restart the GDM daemon or the computer.
|
|
| 2006-10-06 |
The chooser version (%s) does not match the daemon version (%s). You have probably just upgraded GDM. Please restart the GDM daemon or the computer.
|
|
| 314. |
GDM (GNOME Display Manager) is not running.
|
|
| 2007-06-03 |
GDM (GNOME Display Manager) is not running.
|
|
| 315. |
You might be using a different display manager, such as KDM (KDE Display Manager), CDE login (dtlogin), or xdm. If you wish to use this feature, then your system will need to be configured to use GDM instead.
|
|
| 2007-06-03 |
You might be using a different display manager, such as KDM (KDE Display Manager), CDE login (dtlogin), or xdm. If you wish to use this feature, then your system will need to be configured to use GDM instead.
|
|
| 323. |
The nested X server cannot connect to your current X server. You may be missing an X authorization file.
|
|
| 2007-06-03 |
The nested X server cannot connect to your current X server. You may be missing an X authorisation file.
|
|
| 324. |
The nested X server is not available, or GDM is badly configured.
Please install the Xnest package in order to use the nested login.
|
|
| 2007-06-03 |
The nested X server is not available, or GDM is badly configured.
Please install the Xnest package in order to use the nested login.
|
|
| 325. |
The X server is not available. GDM may be misconfigured.
|
|
| 2009-07-03 |
The X server is not available. GDM may be misconfigured.
|
|
| 346. |
Connection to daemon failed, sleeping for %d seconds. Retry %d of %d
|
|
| 2006-10-06 |
Connection to daemon failed, sleeping for %d seconds. Retry %d of %d
|
|
| 370. |
Error: GDM (GNOME Display Manager) is not running.
|
|
| 2007-06-03 |
Error: GDM (GNOME Display Manager) is not running.
|
|
| 371. |
You might be using a different display manager.
|
|
| 2007-06-03 |
You might be using a different display manager.
|
|
