[jira] Created: (OFBIZ-4014) i18n from DateTime display fields
Locked
12
12
[jira] Updated: (OFBIZ-4014) i18n from DateTime display fields
 
|
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Rodekamp updated OFBIZ-4014: ----------------------------------- Attachment: OFBIZ-4014_lazyLoadJsLanguageFiles.patch OFBIZ-4014_dateJs.zip Here is a proposal for the javascript language loading problem. I decided to use a lazy loading mechanism and not to load the files directly in the Common Screens. We are more flexible this way. What do you thing? > 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_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
[jira] Updated: (OFBIZ-4014) i18n from DateTime display fields
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Rodekamp updated OFBIZ-4014: ----------------------------------- Attachment: OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch This is the Timepicker patch update corresponding to my previous submitted lazy loading patch. > 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_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
[jira] Updated: (OFBIZ-4014) i18n from DateTime display fields
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Rodekamp updated OFBIZ-4014: ----------------------------------- Attachment: OFBIZ-4014_lazyLoadJsLanguageFiles.patch New patch updated after jQuery 1.5.1 update > 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_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
[jira] [Closed] (OFBIZ-4014) i18n from DateTime display fields
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Rodekamp closed OFBIZ-4014. ---------------------------------- Resolution: Fixed Assignee: Sascha Rodekamp The patches are committed in trunk Rev.1090231 > 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 > Assignee: 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_dateJs.zip, OFBIZ-4014_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_languageFileLoading.zip, OFBIZ-4014_lazyLoadJsLanguageFiles.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026904#comment-13026904 ] Jonas Falberg commented on OFBIZ-4014: -------------------------------------- I've been following this thread for a while now, looking for a fix to dates (in my case, Danish) and was pretty pleased when I saw this got closed as fixed. But after looking at this for a while now, this fix just doesn't work. Works fine with en-US dates, but Danish dates are wonky (de-DE, and probably others, as well). If the dates are between the 1st and 12th of the month, the datepicker thinks you mean month and as such switches the date/month around. Typing 12-4-1990 should result in April 12th, 1990 but it returns December 4th, 1990. Using 13-4-1990 results in the correct date of April 13th, 1990. It seems to also work on jQuery's website, so I tried updating jQuery to 1.5.2, and ui to 1.8.16 to see if it was a general bug but that didn't fix it. Another thing is, the jsLanguageFilesMapping.java file uses en-US as standard for da locale and da-DK only for da_DK. The parser is wrong for most two-letter locales, and I couldn't find under what circumstances this file is rewritten to fix it properly. So something is still wrong somewhere, but I'm not well-versed enough in the inner workings of ofbiz to fix it... Tested on Revision 1097719 > 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 > Assignee: 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_dateJs.zip, OFBIZ-4014_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_languageFileLoading.zip, OFBIZ-4014_lazyLoadJsLanguageFiles.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026907#comment-13026907 ] Erwan de FERRIERES commented on OFBIZ-4014: ------------------------------------------- Hi Jonas, you may take a look to datejs which is the framework used for dates: http://www.datejs.com/ There is an input box on the main page where you can make your tests. I think the problem is more coming from datejs than OFBiz. Cheers, > 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 > Assignee: 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_dateJs.zip, OFBIZ-4014_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_languageFileLoading.zip, OFBIZ-4014_lazyLoadJsLanguageFiles.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026912#comment-13026912 ] Jonas Falberg commented on OFBIZ-4014: -------------------------------------- Hm. You're right. The datepicker works fine on http://jqueryui.com/demos/datepicker/#localization though. Aren't they using the same code? Am I just very confused? > 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 > Assignee: 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_dateJs.zip, OFBIZ-4014_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_languageFileLoading.zip, OFBIZ-4014_lazyLoadJsLanguageFiles.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026999#comment-13026999 ] Erwan de FERRIERES commented on OFBIZ-4014: ------------------------------------------- hi, I don't think this is the same basecode. From http://www.datejs.com/2007/11/27/getting-started-with-datejs/ ??Datejs has traveled to many lands and returns with knowledge of over 150 individual Cultures. Supporting your language of choice is simple, just swap out the date.js file for another culture-specific file.?? So I think your datejs localized file is not loaded, if it exists. > 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 > Assignee: 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_dateJs.zip, OFBIZ-4014_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_languageFileLoading.zip, OFBIZ-4014_lazyLoadJsLanguageFiles.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027331#comment-13027331 ] Sascha Rodekamp commented on OFBIZ-4014: ---------------------------------------- Hi Jonas, hi Erwan, sorry for my late response to this. We have a date/time conversion file for danish(date-da-DK.js) which is loaded properly when i choose da-DK language. Maybe something is wrong in the i18n file itself. The Idea was to support the country specific date/ time format and convert it on the fly in the ofbiz default one. I have neither problems with german (de-DE, de) nor english date/time formats. What's your default date/time format (pattern) you would support? The jsLanguageFilesMapping.java is generated automatically based on the languages ofbiz supports. There is also a Service which creates this java class if it is triggered. Have a good day 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 > Assignee: 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_dateJs.zip, OFBIZ-4014_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_languageFileLoading.zip, OFBIZ-4014_lazyLoadJsLanguageFiles.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027567#comment-13027567 ] Jonas Falberg commented on OFBIZ-4014: -------------------------------------- "So I think your datejs localized file is not loaded, if it exists." It does get loaded, checked that. It doesn't get loaded by default though. I had to edit the jsLanguageFilesMapping.java to get it to use the right file. Hi Sascha, When using da-DK it's fine. The problem (and I can see this happening loads of places in the file), is that it does not load the propper file if the locale is just "da". If you look at the file then any locale where the first two letters and the last two letters are not the same in the long locale (fx. da-DK, instead of da-DA), it will load the default en-US for the two-letter locale "da". More examples at the bottom. It does work with ofbiz, translating dates propperly that are already in the DB. The problem is that it seems to misinterpret some inputs. But as Erwan linked, it seems that problem - the switching dates - might lie in dateJS itself, as the problem also happens on their site. In which case, I don't think there's a whole lot to be done about it... --- // This works because nl-NL is present localeFiles.put("nl", "/images/jquery/plugins/datejs/date-nl-NL.js"); localeFiles.put("nl_BE", "/images/jquery/plugins/datejs/date-nl-BE.js"); localeFiles.put("nl_NL", "/images/jquery/plugins/datejs/date-nl-NL.js"); // This doesn't work because zh-ZH isn't present localeFiles.put("zh", "/images/jquery/plugins/datejs/date-en-US.js"); localeFiles.put("zh_CN", "/images/jquery/plugins/datejs/date-zh-CN.js"); localeFiles.put("zh_HK", "/images/jquery/plugins/datejs/date-zh-HK.js"); localeFiles.put("zh_SG", "/images/jquery/plugins/datejs/date-zh-SG.js"); localeFiles.put("zh_TW", "/images/jquery/plugins/datejs/date-zh-TW.js"); > 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 > Assignee: 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_dateJs.zip, OFBIZ-4014_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_languageFileLoading.zip, OFBIZ-4014_lazyLoadJsLanguageFiles.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027584#comment-13027584 ] Sascha Rodekamp commented on OFBIZ-4014: ---------------------------------------- Hi Jonas, yea i know, i wrote the mapping. The easiest way to fix this issue would be to create a da-DA locale file based on the da-DK (if da-DK is sufficient). If you want to klnow how the creation of the mapping file work, have a look at : JsLanguageFileMappingCreator.java, the corresponding ofbiz service is called: createJsLanguageFileMapping. For languages which are described with two letters the method try to guess the the last two once. In the case if the danish language we have no related file with the guessed name so the method take the default language file. To fix the misinterpret issues, i'll check in detail the code and see what i can do. If this is really a problem of the datejs maybe we can report to ther dev team and see if they can fix it. Have a good day 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 > Assignee: 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_dateJs.zip, OFBIZ-4014_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_languageFileLoading.zip, OFBIZ-4014_lazyLoadJsLanguageFiles.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028044#comment-13028044 ] Sascha Rodekamp commented on OFBIZ-4014: ---------------------------------------- Hi Jonas, the patch is in Trunk @Rev1098578 > 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 > Assignee: 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_dateJs.zip, OFBIZ-4014_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_languageFileLoading.zip, OFBIZ-4014_lazyLoadJsLanguageFiles.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044741#comment-13044741 ] Jonas Falberg commented on OFBIZ-4014: -------------------------------------- Hi Sascha, sorry for the late reply. Finally got a chance to look at your latest fix for this, but it still doesn't work properly. I see you changed the mapping, which is great, but it still misinteprets the dates. Dunno if you looked at that in your commit. I've had someone look at the original datejs and that works as it's supposed to, using dd-mm-yy consistently. So I think it must be somewhere in the ofbiz code... > 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 > Assignee: 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_dateJs.zip, OFBIZ-4014_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_languageFileLoading.zip, OFBIZ-4014_lazyLoadJsLanguageFiles.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
[jira] [Reopened] (OFBIZ-4014) i18n from DateTime display fields
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Rodekamp reopened OFBIZ-4014: ------------------------------------ Hi Jonas, ok i will investigate. I'm a little bit busy at the moment but hope to find time in the next days. > 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 > Assignee: 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_dateJs.zip, OFBIZ-4014_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_languageFileLoading.zip, OFBIZ-4014_lazyLoadJsLanguageFiles.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056434#comment-13056434 ] Jonas Falberg commented on OFBIZ-4014: -------------------------------------- Hi Sascha, Problem is fixed in OFBIZ-4306, so now it works correctly. > 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 > Assignee: 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_dateJs.zip, OFBIZ-4014_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_languageFileLoading.zip, OFBIZ-4014_lazyLoadJsLanguageFiles.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056436#comment-13056436 ] Sascha Rodekamp commented on OFBIZ-4014: ---------------------------------------- Hi Jonas, ok thanks. > 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 > Assignee: 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_dateJs.zip, OFBIZ-4014_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_languageFileLoading.zip, OFBIZ-4014_lazyLoadJsLanguageFiles.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
[jira] [Closed] (OFBIZ-4014) i18n from DateTime display fields
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Rodekamp closed OFBIZ-4014. ---------------------------------- Resolution: Fixed > 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 > Assignee: 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_dateJs.zip, OFBIZ-4014_dateJs.zip, OFBIZ-4014_i18nTimepicker.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_i18nTimepicker_And_DateTimeField.patch, OFBIZ-4014_languageFileLoading.zip, OFBIZ-4014_lazyLoadJsLanguageFiles.patch, OFBIZ-4014_lazyLoadJsLanguageFiles.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 |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |