[wp-hackers] Feed date format and locale not using blog settings. Bug or feature?

DD32 wordpress at dd32.id.au
Thu Feb 12 02:30:39 GMT 2009


You can manually change the 'rss_language' option in the database if
you'd like to output a different language value..
However, The language marker makes no impact what so ever upon any
machine-parsable fields, It mearly states that the contents of the
field are non-english.

I'm not sure if the rss_language value changes if you have defined a
language.. This would probably work in your themes functions.php:

add_filter('option_rss_language', 'theme_rss_lang');
function theme_rss_lang($lang) {
return defined('WPLANG') && !empty(WPLANG) ? WPLANG : $lang;
}

That uses your defined Language if its set, else the default thats set.

2009/2/12 Heiko Rabe <heiko.rabe at code-styling.de>:
> Please have a look at "RSS Specifications for Creation of Rhode Island
> Government Information Exchange Feeds"
>
> http://www.ri.gov/rex/downloads/RSSelements.pdf
>
> Several goverments take care about language field of RSS (use google an you
> will find a lot f) and also refere to W3C who states, that not only the
> "en-us" is valid but all languages also meet HTML lang fields.
> HTML is a subset of XML family and RSS too. so all of them have to publish
> their correct language they depend on even if no reader is interested!
>
> This leads to supporting at least a filter for WordPress RSS feed, so user
> can make the decision if the pass it back to WordPress or if they modify it
> depending on feeds content (in term of multi-ligual blogs).
>
> This force only "en-us" is not the way it should be.
>
> regards
>
> Heiko
>
>> FYI, I just added this to the Codex.
>>
>> See:
>>
>> http://codex.wordpress.org/index.php?title=WordPress_Feeds&action=edit&section=7
>>
>> grtz
>> BjornW
>>
>>
>>>
>>> Ok, before I add it to the Codex:
>>>
>>> The time/date format of feed should NOT be localized since the the
>>> current RSS
>>> specifications are referring to RFC822 which specifies English as a
>>> default.
>>> This implies that every RSS consumer should take care of translating
>>> time/date
>>> according to its locale.
>>>
>>> Any remarks hints or tips before I add it to the codex?
>>>
>>> Thanks for the feedback so far!
>>>
>>> All the best,
>>>
>>> grtz
>>> BjornW
>>>
>>>
>>>
>>>
>>>>
>>>> On 11 Feb 2009, at 11:39, DD32 wrote:
>>>>
>>>>
>>>>>
>>>>> Once again, No.
>>>>> Simply for the fact, That Feed readers do not understand different
>>>>> languages, The RSS spec (along with most other spec's and software) is
>>>>> written with English as the common format..
>>>>> If the spec makes no mention of it, Its not going to be supported by
>>>>> implementations of it, I do see that people would want it shown in
>>>>> their native tongue, IMO, Feed readers should be able to translate the
>>>>> time from a english-centric date/time into the users custom format (or
>>>>> language format).
>>>>>
>>>>> I somewhat think Internationalisation might be something that would be
>>>>> included in future spec's though.
>>>>>
>>>>> 2009/2/11 Bjorn Wijers <burobjorn at gmail.com>:
>>>>>
>>>>>>
>>>>>> Good point.
>>>>>>
>>>>>> I looked at the RSS spec[1] and it refers to RFC822[2] which states
>>>>>> (I glanced
>>>>>> over it) that the current time/date format as used by Wordpress is
>>>>>> the correct
>>>>>> one. I've added this to the Codex[3]. However as far as I know it
>>>>>> doesn't
>>>>>> mention anything on the localization of this? So my question on if
>>>>>> this
>>>>>> could/should be localized remains.
>>>>>>
>>>>>> LINKS
>>>>>> [1] http://cyber.law.harvard.edu/rss/rss.html
>>>>>>
>>>>>> [2] http://asg.web.cmu.edu/rfc/rfc822.html
>>>>>>
>>>>>> [3]
>>>>>>
>>>>>> http://codex.wordpress.org/index.php?title=WordPress_Feeds&action=edit&section=7
>>>>>>
>>>>>>
>>>>>> All the best,
>>>>>>
>>>>>>
>>>>
>>>> It must not be localised.
>>>>
>>>> It must conform to the RFC which is specific about the format of the
>>>> date/time string.
>>>>
>>>> The only change that RSS makes is it relaxed the rules on year to accept
>>>> 2 digit years (But they should be avoided anyway as they are ambigious)
>>>>
>>>> westi
>>>>
>>>
>>> _______________________________________________
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>
>>>
>>
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>>
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>


More information about the wp-hackers mailing list