Translations by A S Alam

Error reading the file:

%s Continue (y/n)?

The files that contain your preference settings are currently in use. You might be logged in to a session from another computer, and the other login session is using your preference settings files. You can continue to use the current session, but this might cause temporary problems with the preference settings in the other session. Do you want to continue?

Please contact your system administrator to resolve the following problem: Could not lock the file "%s"; this indicates that there may be a problem with your operating system configuration. If you have an NFS-mounted home directory, either the client or the server may be set up incorrectly. See the rpc.statd and rpc.lockd documentation. A common cause of this error is that the "nfslock" service has been disabled.The error was "%s" (errno = %d).

_Log Out

Please contact your system administrator to resolve the following problem: Could not lock the file "%s"; this indicates that there may be a problem with your operating system configuration. If you have an NFS-mounted home directory, either the client or the server may be set up incorrectly. See the rpc.statd and rpc.lockd documentation. A common cause of this error is that the "nfslock" service has been disabled.The error was "%s" (errno = %d).

_Continue

Error reading the file:

Please contact your system administrator to resolve the following problem: Could not resolve the address "%s" in the configuration file "%s": %s

Please contact your system administrator to resolve the following problem: Could not open or create the file "%s"; this indicates that there may be a problem with your configuration, as many programs will need to create files in your home directory. The error was "%s" (errno = %d).

_Log Out

Please contact your system administrator to resolve the following problem: No configuration sources in the configuration file "%s"; this means that preferences and other settings can't be saved. %s%s

%s Continue (y/n)?

Can't remove file %s: %s

Please contact your system administrator to resolve the following problem: Could not lock the file "%s"; this indicates that there may be a problem with your operating system configuration. If you have an NFS-mounted home directory, either the client or the server may be set up incorrectly. See the rpc.statd and rpc.lockd documentation. A common cause of this error is that the "nfslock" service has been disabled.The error was "%s" (errno = %d).

Failed to get configuration file path from '%s'

Created Evolution/LDAP source using configuration file '%s'

Unable to parse XML file '%s'

Config file '%s' is empty

Root node of '%s' must be <evoldap>, not <%s>

No <template> specified in '%s'

No "filter" attribute specified on <template> in '%s'

No LDAP server or base DN specified in '%s'

Contacting LDAP server: host '%s', port '%d', base DN '%s'

Failed to contact LDAP server: %s

Searching for entries using filter: %s

Error querying LDAP server: %s

Got %d entries using filter: %s

Cannot find directory %s

Error saving GConf tree to '%s': %s

Usage: %s <dir>

Usage: %s <dir> Merges a markup backend filesystem hierarchy like: dir/%%gconf.xml subdir1/%%gconf.xml subdir2/%%gconf.xml to: dir/%%gconf-tree.xml

Unloading text markup backend module.

Couldn't find the XML root directory in the address `%s'

Could not make directory `%s': %s

Can't read from or write to the XML root directory in the address "%s"

Directory/file permissions for XML source at root %s are: %o/%o

Remove directory operation is no longer supported, just remove all the values in the directory

Could not open lock directory for %s to remove locks: %s

Could not remove file %s: %s

Initializing Markup backend module

Failed to give up lock on XML directory "%s": %s