[
https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006358#comment-13006358
]
Sascha Rodekamp commented on OFBIZ-4014:
----------------------------------------
Hi Jacques, yea the patch is outdated. I will have a look this evening.
I also search for a better alternative to organize the i18n file. It's rally a
pain to add another date lib with new i18n definitions.
Hard to maintain, a lot of overhead and we have also the problem with missing
files. A better concept is needed ;)
Cheers
Sascha
> i18n from DateTime display fields
> ----------------------------------
>
> Key: OFBIZ-4014
> URL: https://issues.apache.org/jira/browse/OFBIZ-4014
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Sascha Rodekamp
> Fix For: SVN trunk
>
> Attachments: OFBIZ-4014_ModelFormField_DateTimeField_i18n.patch,
> OFBIZ-4014_ModelFormField_DateTimeField_i18n.patch, OFBIZ-4014_dateJs.zip,
> OFBIZ-4014_i18nTimepicker.patch,
> OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch
>
>
> Hi everybody,
> i did a little improvement in the "display" form fields from type date and
> date-time.
> In the past the timestamps where read from the DB and the string was simply
> cut, that didn't match with (i.e.) German date pattern. I changed this
> substring stuff and used the locale and timezone with the dateFormatter to
> create a i18n date string.
> This patch works for: <display type="date" /> and <display type="date-time" />
> Hope that helps.
> Have a nice day
> Sascha
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
