After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 318600 - Use "configuration" instead of "config" in gconf messages
Use "configuration" instead of "config" in gconf messages
Status: RESOLVED FIXED
Product: GConf
Classification: Deprecated
Component: gconf
CVS HEAD
Other All
: Normal normal
: ---
Assigned To: GConf Maintainers
GConf Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-10-11 19:11 UTC by Christian Rose
Modified: 2008-01-08 14:32 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christian Rose 2005-10-11 19:11:56 UTC
#: ../backends/evoldap-backend.c:453
#, c-format
msgid "Config file '%s' is empty"

#: ../gconf/gconf.c:3025
#, c-format
msgid "Failure shutting down config server: %s"

#: ../gconf/gconfd.c:354
#, c-format
msgid ""
"No configuration files found, trying to use the default config source `%s'"

#: ../gconf/gconfd.c:375
#, c-format
msgid "Error loading some config sources: %s"

#: ../gconf/gconfd.c:387
msgid ""
"No config source addresses successfully resolved, can't load or store config "
"data"

#: ../gconf/gconfd.c:404
msgid ""
"No writable config sources successfully resolved, may not be able to save "
"some configuration changes"

#: ../gconf/gconftool.c:216
msgid ""
"Launch the config server (gconfd). (Normally happens automatically when "
"needed.)"

#: ../gconf/gconftool.c:333
msgid ""
"Access the config database directly, bypassing server. Requires that gconfd "
"is not running."

#: ../gconf/gconftool.c:342
msgid ""
"Properly installs schema files on the command line into the database. "
"GCONF_CONFIG_SOURCE environment variable should be set to a non-default "
"config source or set to the empty string to use the default."

#: ../gconf/gconftool.c:351
msgid ""
"Properly uninstalls schema files on the command line from the database. "
"GCONF_CONFIG_SOURCE environment variable should be set to a non-default "
"config source or set to the empty string to use the default."

#: ../gconf/gconftool.c:723
msgid ""
"You must specify a config source with --config-source when using --direct\n"

#: ../gconf/gconftool.c:1578
#, c-format
msgid "Failed to spawn the config server (gconfd): %s\n"

#: ../gconf/gconftool.c:3699 ../gconf/gconftool.c:3734
#, c-format
msgid "Error syncing config data: %s"


Please do *not* use slang terms such as "config". Please spell out
"configuration" instead. Doing so would also be a big boost for consistency, as
many messages already use the full term "configuration".
Comment 1 Adam Weinberger 2005-10-11 21:28:14 UTC
Using "config" isn't going to be confusing to English speakers, but abbreviations like that are slang and 
less professional-looking.

In my eyes, the real critical thing in those strings is to fix the comma splices. As a general rule: when 
you join two discrete sentences by simply inserting a comma between them, it is *ALWAYS* a grammar 
error. There are also a number of other grammar issues with the above strings.

#: ../gconf/gconfd.c:354
#, c-format
msgid ""
"No configuration files found, trying to use the default config source `%s'"

Should be "No configuration files found.  Attempting to use default configuration source `%s'"


#: ../gconf/gconfd.c:387
msgid ""
"No config source addresses successfully resolved, can't load or store config "
"data"

Should be maybe "No configuration source address was successfully resolved. Cannot load or store 
configuration data"


#: ../gconf/gconfd.c:404
msgid ""
"No writable config sources successfully resolved, may not be able to save "
"some configuration changes"

"No writable configuration source was successfully resolved. May be unable to save some configuration 
changes"


#: ../gconf/gconftool.c:333
msgid ""
"Access the config database directly, bypassing server. Requires that gconfd "
"is not running."

"Bypass server, and access the configuration database directly. Requires that gconfd not be running."


#: ../gconf/gconftool.c:342
msgid ""
"Properly installs schema files on the command line into the database. "
"GCONF_CONFIG_SOURCE environment variable should be set to a non-default "
"config source or set to the empty string to use the default."

#: ../gconf/gconftool.c:351
msgid ""
"Properly uninstalls schema files on the command line from the database. "
"GCONF_CONFIG_SOURCE environment variable should be set to a non-default "
"config source or set to the empty string to use the default."

For the last sentence of each of these, I'd recommend: "Specify a custom configuration source in the 
GCONF_CONFIG_SOURCE environment variable, or set the variable to an empty string to use the default 
configuration source."
Comment 2 Kjartan Maraas 2008-01-08 14:32:06 UTC
Fixed them all now finally.