1 fplanque Apr 15, 2004 17:36
Actually the spec says -
http://www.w3.org/TR/html4/struct/dirlang.html#h-8.1
So - it is going to be…
We may also add a ‘PHPcharset’ key to locales, in order to have a constant to use with functions like htmlentities (see example: http://www.php.net/manual/en/function.htmlentities.php)
Hi, I’m the new developer.. :)
Started the conversion to locale-only today, when I wanted to make the installation multilangual and asked FP a question about that. He said “don’t touch", because he planed to do the same.
So, I commited what I had done and will now stop with that.
Changing this, $locales should definitely go into DB, allowing to enable/disable them and setting the default one - from the Options.
Auto-detect by HTTP_ACCEPT_LANGUAGE is already implemented in the function locale_from_httpaccept(), don’t know if there is something to more locale-specific.
Using $locales[’xx-XX’] instead of ‘xx_XX’ is good, if it’s more standard. Adding the[’messages’] field is also useful, of course.
keep on hackin’ :o)
> The locale used should (ideally) obey to this order:
> - current post (I’ll take care of this)
> - current blog (partially implemented)
> - user profile pref (not implemented)
> - browser pref (your impl)
> - options screen global pref (not implemented)
> - last resort: config file (en-US) since it’s not on the global
> options yet.
My vote for: _