Red Hat Bugzilla – Bug 117672
Please avoid trailing newlines in authconfig messages
Last modified: 2007-11-30 17:10:37 EST
msgid "disable MD5 passwords by default\n"
msgid "default NIS server\n"
msgid "default LDAP base DN\n"
msgid "default kerberos realm\n"
msgid "disable use of DNS to find kerberos realms\n"
msgid "names of servers to authenticate against\n"
msgid "join the winbind domain or ads realm now as this administrator\n"
msgid "disable wins for hostname resolution\n"
msgid "default hesiod RHS\n"
msgid "disable caching of user information by default\n"
msgid "%s: bad argument %s: %s\n"
msgid "%s: attempting to continue\n"
msgid "%s: unexpected argument\n"
msgid "%s: can only be run as root\n"
msgid "dialog was cancelled\n"
Trailing newlines is a plague for translators (see
Also, it makes the messages in authconfig inconsistent with eachother
as most messages don't use trailing newlines.
Hello Christian, trailing newlines will be eliminated from l10n
strings starting from authconfig-4.6.5.
Why did you mark this as NOTABUG? This is sure a problem for translators.
I closed this bug as NOTABUG, because it is reported with "normal"
severity, where it is not a bug. I think that it is not a bug, because
it doesn't affect functionality of authconfig. (please use
"translation" severity for such reports)
D'oh -- you could just have marked it with "translation" severity
This won't be fixed. The messages are already translated, removing the
newlines would create even more mess.
If authconfig is deprecated software that will never have any new
releases or translations from now on, I'm bound to agree.
If not, then I don't think the answer "changing now would be more
problematic" is a given fact. That would imply that you don't expect
authconfig to receive new translations. It also leaves the question
unanswered if you intend to avoid newlines on new messages, and if not
why. If so, I see a consistency problem coming, where some messages
may be duplicated, one in an older version with trailing newline, and
No, it isn't deprecated. I'll try to avoid such trailing \n in new
messages but of course I won't create duplicate messages.
But I don't see it as too big problem for translators if there aren't