[wp-trac] [WordPress Trac] #12081: $wp_default_secret_key can't be overridden, posing localization issues
WordPress Trac
wp-trac at lists.automattic.com
Fri Feb 12 08:31:12 UTC 2010
#12081: $wp_default_secret_key can't be overridden, posing localization issues
--------------------------+-------------------------------------------------
Reporter: nacin | Owner: nbachiyski
Type: defect (bug) | Status: new
Priority: normal | Milestone: 3.0
Component: i18n | Version:
Severity: normal | Keywords:
--------------------------+-------------------------------------------------
Comment(by nacin):
I didn't see that translator instruction, thanks.
I just looked through another dozen or so localizations and found maybe
half that translated the string but did not include the translated value
in their lang_code.php file.
There were three techniques employed that do work, but it shows that
implementation of this is all over the map:
- Many do it properly, by translating the string and include the
translated value in lang_code.php.
- Others leave it in English.
- At least one I found left it in English, and included a localized PHP
comment. Here's de_DE:
{{{
define('AUTH_KEY', 'put your unique phrase here'); // Trage hier eine
beliebige, möglichst zufällige Phrase ein.
}}}
I've seen this posing problems before. de_DE uses the same technique as
above for database defines, and thus do not translate those values in
setup-config.php either. But from #11812, one team did translate the
database defines, but did not translate the values in setup-config.php.
I think this is too widespread to mark this as invalid, but I'm not sure
what we can do besides more education.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/12081#comment:4>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list