[TYPO3-core] RFC: Bug 4666: Date formatting should use Typo3 default settings and be configurable

Michael Stucki michael at typo3.org
Sat Feb 3 12:54:06 CET 2007


Hi Martin & Dmitry,

> date() does not localize names (of months, etc). So date() can only but
> used where short dates (eg in lists) are possible. To be precise, for FE
> date() should never be used - use strftime() instead. And even for BE
> strftime() is the better choice.

As it seems (see Dmitrys reply) they are both not optimal. So we can either
add the consistency with the TYPO3_CONF_VARS settings wherever date() is
used, or we don't change anything until the API is in place.

Attached is a new version of the patch. It is almost the same like before,
but I have removed the new "hhmmss" property again because the whole
setting seems to become deprecated soon...

All that this patch does now is to respect the setting of
$TYPO3_CONF_VARS['SYS']['ddmmyy'] and $TYPO3_CONF_VARS['SYS']['hhmm'].

Branches: Still Trunk only.

- michael
-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bug_4666_v3.diff
Type: text/x-diff
Size: 10300 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20070203/b29b5e25/attachment.bin 


More information about the TYPO3-team-core mailing list