Translations by Chao-Hsiung Liao

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

Line %d character %d: %s

Attribute "%s" is invalid on <%s> element in this context

Unknown value "%s" for "%s" attribute on element <%s>

No "%s" attribute on element <%s>

Two <default> elements below a <local_schema>

Two <longdesc> elements below a <local_schema>

Element <%s> is not allowed below <%s>

<%s> provided but current element does not have type %s

Two <car> elements given for same pair

Two <cdr> elements given for same pair

<%s> provided but parent <entry> does not have a value

Element <%s> is not allowed inside current element

Outermost element in menu file must be <gconf> not <%s>

Element <%s> is not allowed inside a <%s> element

No text is allowed inside element <%s>

Could not flush file '%s' to disk: %s

Failed to delete "%s": %s

Change GConf mandatory values

Change GConf system values

Privileges are required to change GConf mandatory values

Privileges are required to change GConf system values

`%c' is an invalid character in a configuration storage address

Backend `%s' failed to return a vtable

Expected `%s' got `%s' for key %s

Failed to log addition of listener %s (%s); will not be able to restore this listener on gconfd restart, resulting in unreliable notification of configuration changes.

Failed to log removal of listener to logfile (most likely harmless, may result in a notification weirdly reappearing): %s

Error unsetting "%s": %s

Error getting new value for "%s": %s

Error removing directory "%s": %s

Configuration server couldn't be contacted

Operation not allowed without configuration server

No '/' in key "%s"

Not running within active session

Failed to get connection to session: %s

Could not send message to GConf daemon: %s

daemon gave erroneous reply: %s

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - %s)

- Sanity checks for GConf

Error while parsing options: %s. Run '%s --help' to see a full list of available command line options.

Schema specifies type pair but doesn't specify the type of the car/cdr elements

Failed to load source "%s": %s

Resolved address "%s" to a partially writable configuration source at position %d

Unable to store a value at key '%s', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file %s/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf

Key `%s' listed as schema for key `%s' actually stores type `%s'

Didn't understand `%s' (list must start with a '[')

Didn't understand `%s' (list must end with a ']')

Didn't understand `%s' (extra unescaped ']' found inside list)

Didn't understand `%s' (extra trailing characters)