[jira] [Closed] (OFBIZ-6869) Jgrowl enhancement i18n and centered

2016-02-03 Thread Gil Portenseigne (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gil Portenseigne closed OFBIZ-6869. --- Enhancement commited in trunk r1728351 > Jgrowl enhancement i18n and cente

[jira] [Updated] (OFBIZ-6869) Jgrowl enhancement i18n and centered

2016-02-03 Thread Gil Portenseigne (JIRA)
of JGrowl alert. > Jgrowl enhancement i18n and centered > > > Key: OFBIZ-6869 > URL: https://issues.apache.org/jira/browse/OFBIZ-6869 > Project: OFBiz > Issue Type: Improvement >

[jira] [Commented] (OFBIZ-6869) Jgrowl enhancement i18n and centered

2016-02-02 Thread Gil Portenseigne (JIRA)
Jgrowl enhancement i18n and centered > > > Key: OFBIZ-6869 > URL: https://issues.apache.org/jira/browse/OFBIZ-6869 > Project: OFBiz > Issue Type: Improvement > Components: fra

[jira] [Commented] (OFBIZ-6869) Jgrowl enhancement i18n and centered

2016-02-02 Thread Nicolas Malin (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127879#comment-15127879 ] Nicolas Malin commented on OFBIZ-6869: -- nice idea > Jgrowl enhancement i

[jira] [Commented] (OFBIZ-6869) Jgrowl enhancement i18n and centered

2016-02-02 Thread Jacques Le Roux (JIRA)
have parameters to optionally specify the position and size, like we did with lookups :) ? > Jgrowl enhancement i18n and centered > > > Key: OFBIZ-6869 > URL: https://issues.apache.org/jira/browse/OFBIZ-6869 >

[jira] [Updated] (OFBIZ-6869) Jgrowl enhancement i18n and centered

2016-02-01 Thread Gil Portenseigne (JIRA)
, use of labels, and speed up the display for a better UX > Jgrowl enhancement i18n and centered > > > Key: OFBIZ-6869 > URL: https://issues.apache.org/jira/browse/OFBIZ-6869 > Project: OFBiz >

[jira] [Created] (OFBIZ-6869) Jgrowl enhancement i18n and centered

2016-02-01 Thread Gil Portenseigne (JIRA)
Gil Portenseigne created OFBIZ-6869: --- Summary: Jgrowl enhancement i18n and centered Key: OFBIZ-6869 URL: https://issues.apache.org/jira/browse/OFBIZ-6869 Project: OFBiz Issue Type

[jira] [Updated] (OFBIZ-5362) Create a periodic service to use ICU4J for updating i18n data

2015-02-20 Thread Sharan Foga (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharan Foga updated OFBIZ-5362: --- Sprint: Bug Crush Event - 21/2/2015 > Create a periodic service to use ICU4J for updating i18n d

[jira] [Updated] (OFBIZ-3237) Add i18n capabilities to ProductFeature entity

2015-02-20 Thread Sharan Foga (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharan Foga updated OFBIZ-3237: --- Sprint: Bug Crush Event - 21/2/2015 > Add i18n capabilities to ProductFeature ent

[jira] [Updated] (OFBIZ-427) I18N Problem when pop field in an upload type form

2015-02-20 Thread Sharan Foga (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharan Foga updated OFBIZ-427: -- Sprint: Bug Crush Event - 21/2/2015 > I18N Problem when pop field in an upload type f

[jira] [Closed] (OFBIZ-1897) Product default image I18N (CONTRIBUTION)

2014-07-16 Thread Jacopo Cappellato (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacopo Cappellato closed OFBIZ-1897. Resolution: Incomplete > Product default image I18N (CONTRIBUT

[jira] [Closed] (OFBIZ-4288) Issue with i18n and Feature Tree display on productdetail

2014-03-26 Thread Jacopo Cappellato (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacopo Cappellato closed OFBIZ-4288. Resolution: Incomplete > Issue with i18n and Feature Tree display on productdet

[jira] [Assigned] (OFBIZ-5446) zh i18n for SERVICE_QUEUED and SERVICE_RUNNING is reversed.

2013-12-27 Thread Adrian Crum (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-5446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Crum reassigned OFBIZ-5446: -- Assignee: Adrian Crum > zh i18n for SERVICE_QUEUED and SERVICE_RUNNING is rever

[jira] [Closed] (OFBIZ-5446) zh i18n for SERVICE_QUEUED and SERVICE_RUNNING is reversed.

2013-12-27 Thread Adrian Crum (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-5446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Crum closed OFBIZ-5446. -- Resolution: Fixed Committed in revision: 1553663. Thanks Leon! > zh i18n for SERVICE_QUEUED

[jira] [Updated] (OFBIZ-5446) zh i18n for SERVICE_QUEUED and SERVICE_RUNNING is reversed.

2013-12-26 Thread Leon (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-5446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leon updated OFBIZ-5446: Attachment: OFBIZ-5446.patch > zh i18n for SERVICE_QUEUED and SERVICE_RUNNING is rever

[jira] [Updated] (OFBIZ-5446) zh i18n for SERVICE_QUEUED and SERVICE_RUNNING is reversed.

2013-12-26 Thread Leon (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-5446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leon updated OFBIZ-5446: Description: The zh and zh_TW i18n of "StatusItem.description.SERVICE_QUEUED" are meaning of "Ser

[jira] [Created] (OFBIZ-5446) zh i18n for SERVICE_QUEUED and SERVICE_RUNNING is reversed.

2013-12-26 Thread Leon (JIRA)
Leon created OFBIZ-5446: --- Summary: zh i18n for SERVICE_QUEUED and SERVICE_RUNNING is reversed. Key: OFBIZ-5446 URL: https://issues.apache.org/jira/browse/OFBIZ-5446 Project: OFBiz Issue Type: Bug

[jira] [Created] (OFBIZ-5362) Create a periodic service to use ICU4J for updating i18n data

2013-10-18 Thread Jacques Le Roux (JIRA)
Jacques Le Roux created OFBIZ-5362: -- Summary: Create a periodic service to use ICU4J for updating i18n data Key: OFBIZ-5362 URL: https://issues.apache.org/jira/browse/OFBIZ-5362 Project: OFBiz

Re: i18n

2013-09-28 Thread Jacques Le Roux
I did some work on this at revision: 1527171 More is needed on labels for this cases There are 99 Christian I correct a similary problem on calendrarForms.xml > (https://issues.apache.org/jira/browse/OFBIZ-4770) > On other thread "Why some invoice Type use hard code to retreive > associate inv

Re: i18n issue

2012-10-18 Thread Adrian Crum
This question should be asked on the users list. The properties file used for translating an entity's values is specified in the entity definition, not in the screen. -Adrian On 10/18/2012 4:39 PM, Martin Kaiser wrote: Hi all, I have a problem with i18n: I have extended the "Agr

i18n issue

2012-10-18 Thread Martin Kaiser
Hi all, I have a problem with i18n: I have extended the "AgreementType" Entity by simply adding some new Agreement Types: Now I want the descriptions to be translated by using the following code in freemarker: <#list agre

Re: i18n

2012-05-14 Thread Christian Geisert
Nicolas Malin schrieb: > Christian I correct a similary problem on calendrarForms.xml > (https://issues.apache.org/jira/browse/OFBIZ-4770) > On other thread "Why some invoice Type use hard code to retreive > associate invoice item type" I ask why we use a groovy to retreive list > invoice Type. If

Re: i18n

2012-05-07 Thread Nicolas Malin
Christian I correct a similary problem on calendrarForms.xml (https://issues.apache.org/jira/browse/OFBIZ-4770) On other thread "Why some invoice Type use hard code to retreive associate invoice item type" I ask why we use a groovy to retreive list invoice Type. If not needed, it's possible to u

Re: i18n

2012-05-07 Thread Jacques Le Roux
From: "Christian Geisert" I know (and the entity InvoiceItemTypes has default-resource-name="AccountingEntityLabels"), but this works only with and not with in a dropdown, right? AFAIK, with you may add your own specific options (can be on-fly, for instance) , so I think you are right Chr

Re: i18n

2012-05-07 Thread Christian Geisert
I know (and the entity InvoiceItemTypes has default-resource-name="AccountingEntityLabels"), but this works only with and not with in a dropdown, right? In this case the InvoiceItemTypes are filterd in GetInvoiceItemTypes.groovy. Christian Adrian Crum schrieb: > Use the "default-resource-name

Re: i18n

2012-05-04 Thread Adrian Crum
Use the "default-resource-name" attribute of the element. There are examples of this in the project. -Adrian On 5/4/2012 3:52 PM, Christian Geisert wrote: Hi, I just noticed that the InvoiceItemTypes are not localized on the Edit Invoice Items Screen (see https://demo-trunk.ofbiz.apache.org/

i18n

2012-05-04 Thread Christian Geisert
Hi, I just noticed that the InvoiceItemTypes are not localized on the Edit Invoice Items Screen (see https://demo-trunk.ofbiz.apache.org/accounting/control/listInvoiceItems?invoiceId=8010 ) I fixed this with the following code: - + Is this the recommended way do it? Christian

[jira] [Updated] (OFBIZ-3237) Add i18n capabilities to ProductFeature entity

2011-12-12 Thread Jacopo Cappellato (Updated) (JIRA)
: Release Branch 09.04) > Add i18n capabilities to ProductFeature entity > -- > > Key: OFBIZ-3237 > URL: https://issues.apache.org/jira/browse/OFBIZ-3237 > Project: OFBiz > Is

[jira] [Closed] (OFBIZ-4208) Product page meta-tag does not contain i18n content

2011-10-29 Thread Jacques Le Roux (Closed) (JIRA)
Thanks Carsten, Your patch is in trunk at r1194958 R11.04 at r1194965. > Product page meta-tag does not contain i18n content > --- > > Key: OFBIZ-4208 > URL: https://issues.apache.

[jira] [Closed] (OFBIZ-4349) commit r1077940 breaks the function to retrieve i18n translation from real entity underlying a view

2011-10-06 Thread Sascha Rodekamp (Closed) (JIRA)
fix it is committed in trunk @Rev1179943 > commit r1077940 breaks the function to retrieve i18n translation from real > entity underlying a view > --- > >

[jira] [Updated] (OFBIZ-4349) commit r1077940 breaks the function to retrieve i18n translation from real entity underlying a view

2011-10-06 Thread Leon (Updated) (JIRA)
view entity. and, correct some typos. > commit r1077940 breaks the function to retrieve i18n translation from real > entity underlying a view > --- > >

[jira] [Reopened] (OFBIZ-4349) commit r1077940 breaks the function to retrieve i18n translation from real entity underlying a view

2011-10-06 Thread Leon (Reopened) (JIRA)
r": if you select country as USA, then the state name in state combobox are all "United States". > commit r1077940 breaks the function to retrieve i18n translation from real

[jira] [Closed] (OFBIZ-4051) i18n for elrte editor

2011-10-02 Thread Jacques Le Roux (Closed) (JIRA)
Assignee: Jacques Le Roux (was: Erwan de FERRIERES) Fixed at trunk r1178175 R11.04 r1178181 > i18n for elrte editor > - > > Key: OFBIZ-4051 > URL: https://issues.apache.org/jira/browse/OFBIZ-4051 >

[jira] [Closed] (OFBIZ-4349) commit r1077940 breaks the function to retrieve i18n translation from real entity underlying a view

2011-09-22 Thread Erwan de FERRIERES (JIRA)
Leon > commit r1077940 breaks the function to retrieve i18n translation from real > entity underlying a view > --- > > Key: OFBIZ-4349 > URL: https://issu

[jira] [Assigned] (OFBIZ-4349) commit r1077940 breaks the function to retrieve i18n translation from real entity underlying a view

2011-09-22 Thread Erwan de FERRIERES (JIRA)
eve i18n translation from real > entity underlying a view > --- > > Key: OFBIZ-4349 > URL: https://issues.apache.org/jira/browse/OFBIZ-4349 >

[jira] [Commented] (OFBIZ-4349) commit r1077940 breaks the function to retrieve i18n translation from real entity underlying a view

2011-09-22 Thread Leon (JIRA)
real field name from alias. But in your patch, it's reversed to find the alias name for real field. Thanks for your explain and contribution. I think it's ok to apply your patch. > commit r1077940 breaks the function to retrieve i18n translation from real > enti

[jira] [Commented] (OFBIZ-4349) commit r1077940 breaks the function to retrieve i18n translation from real entity underlying a view

2011-09-22 Thread Olivier Heintz (JIRA)
name=workEffortName, but search in properties will fail because this.get("workEffortId") return a error "workEffortId is not a field for". I used this patch for 2 months and I can say that he solve really the problem. Cheers. > commit r1077940 breaks the function to retrieve

[jira] [Commented] (OFBIZ-4208) Product page meta-tag does not contain i18n content

2011-09-04 Thread Jacques Le Roux (JIRA)
ag does not contain i18n content > --- > > Key: OFBIZ-4208 > URL: https://issues.apache.org/jira/browse/OFBIZ-4208 > Project: OFBiz > Issue Type: Bug > Components:

[jira] [Commented] (OFBIZ-4349) commit r1077940 breaks the function to retrieve i18n translation from real entity underlying a view

2011-07-25 Thread Leon (JIRA)
ttle complex. The method get(ModelEntity modelEntity, ModelEntity modelEntityToUse, String name, String resource, Locale locale) is private and only invoked by method get(String name, String resource, Locale locale). In the latter one, it tries to get i18n value from entity firstly (no matter

[jira] [Updated] (OFBIZ-4349) commit r1077940 breaks the function to retrieve i18n translation from real entity underlying a view

2011-07-25 Thread Erwan de FERRIERES (JIRA)
when realEntity pkFieldName is different from viewEntity pkColName, but it's only working with simple view and it breaks retrieving i18n for view with multiple entity and pkColName == pkFieldName. So this new patch solves the two situations. Now the method : use pkField of realEntit

[jira] [Created] (OFBIZ-4349) commit r1077940 breaks the function to retrieve i18n translation from real entity underlying a view

2011-07-21 Thread Leon (JIRA)
commit r1077940 breaks the function to retrieve i18n translation from real entity underlying a view --- Key: OFBIZ-4349 URL: https://issues.apache.org/jira/browse

[jira] [Closed] (OFBIZ-4014) i18n from DateTime display fields

2011-06-28 Thread Sascha Rodekamp (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 fie

[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields

2011-06-28 Thread Sascha Rodekamp (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. > i1

[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields

2011-06-28 Thread Jonas Falberg (JIRA)
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: Improvem

[jira] [Reopened] (OFBIZ-4014) i18n from DateTime display fields

2011-06-06 Thread Sascha Rodekamp (JIRA)
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 >

[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields

2011-06-06 Thread Jonas Falberg (JIRA)
#x27;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

[jira] [Commented] (OFBIZ-4288) Issue with i18n and Feature Tree display on productdetail

2011-05-28 Thread Carsten Schinzer (JIRA)
this one and will provide a patch on Monday. Currently verifying the fix in my PROD already. Regards Carsten 2011/5/27 Marco Risaliti (JIRA) -- Best Carsten Schinzer Waisenhausstr. 53a 80637 München Germany > Issue with i18n and Feature Tree display on produc

[jira] [Assigned] (OFBIZ-4288) Issue with i18n and Feature Tree display on productdetail

2011-05-27 Thread Marco Risaliti (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Risaliti reassigned OFBIZ-4288: - Assignee: Marco Risaliti > Issue with i18n and Feature Tree display on productdet

[jira] [Created] (OFBIZ-4288) Issue with i18n and Feature Tree display on productdetail

2011-05-20 Thread Carsten Schinzer (JIRA)
Issue with i18n and Feature Tree display on productdetail - Key: OFBIZ-4288 URL: https://issues.apache.org/jira/browse/OFBIZ-4288 Project: OFBiz Issue Type: Bug Components

[jira] [Commented] (OFBIZ-4208) Product page meta-tag does not contain i18n content

2011-05-06 Thread Jacques Le Roux (JIRA)
e to update your trunk working copy? It's a pity it's corrected in releases and not in trunk... (BTW I will have to put it in R11.04 also) > Product page meta-tag does not contain i18n content > --- > > Key: OFBIZ-

[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields

2011-05-02 Thread Sascha Rodekamp (JIRA)
runk @Rev1098578 > i18n from DateTime display fields > -- > > Key: OFBIZ-4014 > URL: https://issues.apache.org/jira/browse/OFBIZ-4014 > Project: OFBiz > Issue Type: Improvement > Compon

[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields

2011-05-02 Thread Sascha Rodekamp (JIRA)
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

[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields

2011-05-02 Thread Jonas Falberg (JIRA)
; 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"); localeFile

[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields

2011-04-30 Thread Sascha Rodekamp (JIRA)
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

[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields

2011-04-29 Thread Erwan de FERRIERES (JIRA)
.?? 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:

[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields

2011-04-29 Thread Jonas Falberg (JIRA)
orks 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

[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields

2011-04-29 Thread Erwan de FERRIERES (JIRA)
k 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

[jira] [Commented] (OFBIZ-4014) i18n from DateTime display fields

2011-04-29 Thread Jonas Falberg (JIRA)
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 &

[jira] [Closed] (OFBIZ-4014) i18n from DateTime display fields

2011-04-08 Thread Sascha Rodekamp (JIRA)
.1090231 > i18n from DateTime display fields > -- > > Key: OFBIZ-4014 > URL: https://issues.apache.org/jira/browse/OFBIZ-4014 > Project: OFBiz > Issue Type: Improvement > Components

[jira] [Commented] (OFBIZ-4208) Product page meta-tag does not contain i18n content

2011-04-02 Thread Jacques Le Roux (JIRA)
0.04 and R9.04 are committed respectively at r1088035 and r1088034 At least your effort to build separate patches have been useful in this peculiar case ;) > Product page meta-tag does not contain i18n content > --- > >

[jira] [Updated] (OFBIZ-4014) i18n from DateTime display fields

2011-03-30 Thread Sascha Rodekamp (JIRA)
/framework/images/webapp/images/jquery/plugins/datejs > i18n from DateTime display fields > -- > > Key: OFBIZ-4014 > URL: https://issues.apache.org/jira/browse/OFBIZ-4014 > Project: OFBiz > Is

[jira] [Updated] (OFBIZ-4014) i18n from DateTime display fields

2011-03-30 Thread Sascha Rodekamp (JIRA)
. * extract the file * archive contains patch and a few files to copy in place No i use a static class with a language - file mapping should be better than a real time file checking. The Mapping file can be generated automatically. > i18n from DateTime display fie

[jira] [Commented] (OFBIZ-4208) Product page meta-tag does not contain i18n content

2011-03-27 Thread Jacques Le Roux (JIRA)
good work by the way! Just that someone has worked since on the same subject and I can't merge your work. Could you please handle it? Thanks > Product page meta-tag does not contain i18n content > --- > > Key: OFBIZ-

[jira] Updated: (OFBIZ-4014) i18n from DateTime display fields

2011-03-18 Thread Sascha Rodekamp (JIRA)
update > i18n from DateTime display fields > -- > > Key: OFBIZ-4014 > URL: https://issues.apache.org/jira/browse/OFBIZ-4014 > Project: OFBiz > Issue Type: Improvement > Components

[jira] Updated: (OFBIZ-4014) i18n from DateTime display fields

2011-03-17 Thread Sascha Rodekamp (JIRA)
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 >

[jira] Updated: (OFBIZ-4014) i18n from DateTime display fields

2011-03-17 Thread Sascha Rodekamp (JIRA)
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 fie

[jira] Commented: (OFBIZ-4208) Product page meta-tag does not contain i18n content

2011-03-16 Thread Carsten Schinzer (JIRA)
sted. Please let me know whether you think anything else would be outstanding. Regards Carsten > Product page meta-tag does not contain i18n content > --- > > Key: OFBIZ-4208 > URL: https://issues.apa

[jira] Updated: (OFBIZ-4014) i18n from DateTime display fields

2011-03-14 Thread Sascha Rodekamp (JIRA)
updated patch. Not sure why i removed the line but i changed the i18n js file loading a little bit. But as i said we need a common solution for all these i18n files. > i18n from DateTime display fields > -- > > Key: OFBIZ-4014 >

[jira] Commented: (OFBIZ-4014) i18n from DateTime display fields

2011-03-14 Thread Sascha Rodekamp (JIRA)
d. 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 ;) Chee

[jira] Commented: (OFBIZ-4014) i18n from DateTime display fields

2011-03-13 Thread Jacques Le Roux (JIRA)
atch please, I can't apply it patching file framework/example/widget/example/FormWidgetExampleForms.xml patching file framework/common/widget/CommonScreens.xml patch: malformed patch at line 32: Index: framework/widget/templates/htmlFormMacroLibrary.ftl > i18n from DateTime di

[jira] Commented: (OFBIZ-4014) i18n from DateTime display fields

2011-03-13 Thread Jacques Le Roux (JIRA)
why did you remove the line? > i18n from DateTime display fields > -- > > Key: OFBIZ-4014 > URL: https://issues.apache.org/jira/browse/OFBIZ-4014 > Project: OFBiz > Issue Type: Improvem

Re: i18n from date time fields and timepicker

2011-03-13 Thread Jacques Le Roux
I will have a look... hopefully soon... Jacques From: "Sascha Rodekamp" Hi *, i like to discuss the i18n from our date-time fields as well as the timepicker. I prepared a patch under: https://issues.apache.org/jira/browse/OFBIZ-4014which changes: 1.) The ModelFormField.java

[jira] Commented: (OFBIZ-4208) Product page meta-tag does not contain i18n content

2011-03-12 Thread Jacques Le Roux (JIRA)
e a patch for each version. Trunk is enough, we have tools to automatically backport in releases (sometimes with a little manual help) > Product page meta-tag does not contain i18n content > --- > > Key: OFBIZ-4208 >

[jira] Commented: (OFBIZ-4208) Product page meta-tag does not contain i18n content

2011-03-12 Thread Jacques Le Roux (JIRA)
work. See https://cwiki.apache.org/confluence/display/OFBIZ/How+to+localize+Product+and+Categories+descriptions and you should explain that in https://cwiki.apache.org/confluence/display/OFBIZ/Guide+to+OFBiz-i18n%2C++Internationalisation+of+OFBiz#GuidetoOFBiz-i18n,InternationalisationofO

[jira] Updated: (OFBIZ-4208) Product page meta-tag does not contain i18n content

2011-03-01 Thread Carsten Schinzer (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Schinzer updated OFBIZ-4208: Attachment: OFBIZ-4208_Product page meta-tag does not contain i18n content-SVNTRUNK.patch

[jira] Created: (OFBIZ-4208) Product page meta-tag does not contain i18n content

2011-03-01 Thread Carsten Schinzer (JIRA)
Product page meta-tag does not contain i18n content --- Key: OFBIZ-4208 URL: https://issues.apache.org/jira/browse/OFBIZ-4208 Project: OFBiz Issue Type: Bug Components: order

i18n from date time fields and timepicker

2011-02-19 Thread Sascha Rodekamp
Hi *, i like to discuss the i18n from our date-time fields as well as the timepicker. I prepared a patch under: https://issues.apache.org/jira/browse/OFBIZ-4014which changes: 1.) The ModelFormField.java for normal display-time fields in forms. 2.) Add an i18n modificator to the DateTimePicker. I

[jira] Updated: (OFBIZ-4014) i18n from DateTime display fields

2011-02-19 Thread Sascha Rodekamp (JIRA)
latest trunk version. And create one patch file for both patches. > i18n from DateTime display fields > -- > > Key: OFBIZ-4014 > URL: https://issues.apache.org/jira/browse/OFBIZ-4014 > Project: OFBiz >

[jira] Commented: (OFBIZ-4051) i18n for elrte editor

2011-02-01 Thread Jacques Le Roux (JIRA)
n't close... Thanks! > i18n for elrte editor > - > > Key: OFBIZ-4051 > URL: https://issues.apache.org/jira/browse/OFBIZ-4051 > Project: OFBiz > Issue Type: Sub-task > Components: ALL CO

[jira] Commented: (OFBIZ-4051) i18n for elrte editor

2011-01-31 Thread Sascha Rodekamp (JIRA)
Cheers Sascha > i18n for elrte editor > - > > Key: OFBIZ-4051 > URL: https://issues.apache.org/jira/browse/OFBIZ-4051 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONEN

[jira] Commented: (OFBIZ-4051) i18n for elrte editor

2011-01-30 Thread Jacques Le Roux (JIRA)
either in French... (I still see English) No errors in OFBiz log nor in js console. I tried seeing nodes at https://localhost:8443/content/control/WebSiteCms?webSiteId=CmsSite. What and where did you see it working? Thanks > i18n for elrte editor > -

[jira] Updated: (OFBIZ-4051) i18n for elrte editor

2011-01-28 Thread Sascha Rodekamp (JIRA)
seems that see zh_TW Bug is fixed, the language is loaded correctly. @dukian can you please doublecheck? To apply the patch: * extract the zip file * copy the files under the jquery/plugins/elrte folder Thanks Sascha > i18n for elrte editor > - > >

[jira] Closed: (OFBIZ-3892) L10N and I18N for BIRT reporting

2011-01-27 Thread Erwan de FERRIERES (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erwan de FERRIERES closed OFBIZ-3892. - Resolution: Fixed Fix Version/s: SVN trunk > L10N and I18N for BIRT report

[jira] Commented: (OFBIZ-3892) L10N and I18N for BIRT reporting

2011-01-27 Thread Erwan de FERRIERES (JIRA)
[ https://issues.apache.org/jira/browse/OFBIZ-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987646#action_12987646 ] Erwan de FERRIERES commented on OFBIZ-3892: --- Already done. > L10N and I

[jira] Commented: (OFBIZ-4014) i18n from DateTime display fields

2011-01-21 Thread Sascha Rodekamp (JIRA)
rry, just wanted to know if someone is interested or if it is worth to keep this issue open and up to date ;) Cheers > i18n from DateTime display fields > -- > > Key: OFBIZ-4014 > URL: https://issues.apache.or

[jira] Commented: (OFBIZ-4014) i18n from DateTime display fields

2011-01-21 Thread Jacques Le Roux (JIRA)
ently cleaning a lot of pending tasks in my todo list... > i18n from DateTime display fields > -- > > Key: OFBIZ-4014 > URL: https://issues.apache.org/jira/browse/OFBIZ-4014 > Project: OFBiz &g

[jira] Commented: (OFBIZ-4014) i18n from DateTime display fields

2011-01-21 Thread Sascha Rodekamp (JIRA)
lize date/time display fields and date/time picker? > i18n from DateTime display fields > -- > > Key: OFBIZ-4014 > URL: https://issues.apache.org/jira/browse/OFBIZ-4014 > Project: OFBiz >

[jira] Commented: (OFBIZ-4014) i18n from DateTime display fields

2011-01-14 Thread Sascha Rodekamp (JIRA)
are date fields in FTL files. Maybe we create a simple java method which can be called within FTL to format the Date / Time field?! > i18n from DateTime display fields > -- > > Key: OFBIZ-4014 > URL: https://issues.apa

[jira] Updated: (OFBIZ-4014) i18n from DateTime display fields

2011-01-14 Thread Sascha Rodekamp (JIRA)
latest trunk. > i18n from DateTime display fields > -- > > Key: OFBIZ-4014 > URL: https://issues.apache.org/jira/browse/OFBIZ-4014 > Project: OFBiz > Issue Type: Improvement >

[jira] Updated: (OFBIZ-4014) i18n from DateTime display fields

2011-01-10 Thread Sascha Rodekamp (JIRA)
, here is a POC to i18n the Timepicker results. I used the JS Lib Erwan suggested. We have still the problem to load the right language template file. I tested my implementation in the example screens, you can: * Change the Date via the Date / Timepicker * Change the Date manually The Script

[jira] Closed: (OFBIZ-4101) i18n problem in auto-completed dropdown box: display not correct characters but html entities

2011-01-09 Thread Jacques Le Roux (JIRA)
Leon, Dukian just tested your patch, so I'm now almost sure there are no issues. Your (slightly modified) patch is in trunk at r1056977 > i18n problem in auto-completed dropdown box: display not correct characters > but ht

[jira] Updated: (OFBIZ-4101) i18n problem in auto-completed dropdown box: display not correct characters but html entities

2011-01-09 Thread Jacques Le Roux (JIRA)
$ shortcut in OFBiz js code. Updated patch... > i18n problem in auto-completed dropdown box: display not correct characters > but html entities > - > > Key: OFBIZ-4101 >

[jira] Commented: (OFBIZ-4101) i18n problem in auto-completed dropdown box: display not correct characters but html entities

2011-01-09 Thread Jacques Le Roux (JIRA)
fore committing... > i18n problem in auto-completed dropdown box: display not correct characters > but html entities > - > > Key: OFBIZ-4101 > URL: https://

[jira] Updated: (OFBIZ-4101) i18n problem in auto-completed dropdown box: display not correct characters but html entities

2011-01-09 Thread Leon (JIRA)
, maybe it's only available to my case. > i18n problem in auto-completed dropdown box: display not correct characters > but html entities > - > > Key: OFBIZ-4101 >

[jira] Updated: (OFBIZ-4101) i18n problem in auto-completed dropdown box: display not correct characters but html entities

2011-01-09 Thread Leon (JIRA)
association form, this problem is exist in the places where the lookup+auto-completed text box used. > i18n problem in auto-completed dropdown box: display not correct characters > but html en

[jira] Created: (OFBIZ-4101) i18n problem in auto-completed dropdown box: display not correct characters but html entities

2011-01-09 Thread Leon (JIRA)
i18n problem in auto-completed dropdown box: display not correct characters but html entities - Key: OFBIZ-4101 URL: https://issues.apache.org/jira/browse/OFBIZ-4101

[jira] Commented: (OFBIZ-4014) i18n from DateTime display fields

2010-12-20 Thread Erwan de FERRIERES (JIRA)
rested in seeing what you can do with it... At the moment, I don't dive the time to deep dive into it. But I know that lot of people are waiting to see a correctly formatted date on screen ! Cheers > i18n from DateTime display fields > -- > >

[jira] Commented: (OFBIZ-4014) i18n from DateTime display fields

2010-12-20 Thread Sascha Rodekamp (JIRA)
etty interesting (i like the ninja logo :)). I'll have a closer look in the next day, but at a first glace i think that can solve a few issues. Nicoals what do u mean? So long Sascha > i18n from DateTime display fields > -- > >

[jira] Commented: (OFBIZ-4014) i18n from DateTime display fields

2010-12-17 Thread Erwan de FERRIERES (JIRA)
you take a look at this library which could resolve a lot of issues on displaying date : http://code.google.com/p/datejs/ Cheers, > i18n from DateTime display fields > -- > > Key: OFBIZ-4014 > URL: https://issues.apa

[jira] Commented: (OFBIZ-4051) i18n for elrte editor

2010-12-14 Thread Jacques Le Roux (JIRA)
gree > i18n for elrte editor > - > > Key: OFBIZ-4051 > URL: https://issues.apache.org/jira/browse/OFBIZ-4051 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS &

  1   2   3   >