[
https://issues.apache.org/jira/browse/OFBIZ-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891989#action_12891989
]
Adrian Crum commented on OFBIZ-3843:
------------------------------------
A few comments about this issue:
1. The current date-time format is not a US format, it is the JDBC escape
format supported by the Timestamp class. The date-time format was chosen as a
defacto "standard" format for consistency - so no matter what locale the user
has selected, date-time data entry will always be the same.
2. The date-time format issue has been brought up enough times that it is clear
we need to provide a means to override the JDBC escape format. Whatever method
is used to accomplish that, we still need to support those who prefer to use
the JDBC escape format.
3. I haven't applied this patch - I only looked through it, but I can see some
serious problems:
A. The format override is a setting in a properties file - the user-selected
locale is ignored.
B. The date-time popup calendar has not been updated to support the format
override.
4. The implementation is not a good design. I would suggest changing the
UtilDateTime methods that reference the static format fields so that a flag is
checked that indicates whether to use the user's locale or the JDBC escape
format, and then use the appropriate format.
> Localized date format for end user
> ----------------------------------
>
> Key: OFBIZ-3843
> URL: https://issues.apache.org/jira/browse/OFBIZ-3843
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Nicolas Malin
> Priority: Minor
> Attachments: date-localized.patch, With the patch.jpg, Without patch
> (in trunk demo).jpg
>
>
> Many French end users don't want to use this date format : yyyy-mm-dd.
> To make a better user friendly OFBiz interface, I've added the possibility to
> configure in general.properties a localized date format. OFBiz use localized
> format (as dd/mm/yyyy) for all interactions with users but keep universal
> format for its framework. It's then possible to set date with unniversal or
> localized format.
> What's working :
> * Dates in screen engine : display, date-find, date-time
> * performFind
> * Service call
> Know problem :
> * I don't find how to configure js calendar to support this functionality
> It's possible that my solution isn't the best one to do that. But I'm open to
> all comment
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
