Re: Guideline translation definition and the application there of in service functions and widget element, o.a.

[Michael Brohl]

Pierre,

this will be my last response to this thread to clear some points and 
let the interested readers draw their own conclusions.


See my responses inline.

Regards,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 30.01.22 um 18:32 schrieb Pierre Smits:

Thanks Michael, for your opinion and suggestions,

Re: "namely the intention to reuse labels from other applications instead
of using context related specified labels in the application itself"

This is not the project's viewpoint. It is your viewpoint. All the


I consider a viewpoint the project's viewpoint if a majority of 
participating contributors have expressed a similar viewpoint. This is 
called lazy consensus.


There have been several voices who argumented for this viewpoint but to 
this day, I have seen noone else argumenting for your viewpoint. I have 
given some examples of discussions and rejected contributions in the 
past message. It's your problem that you cannot accept decisions against 
your own viewpoint.


That there have been contributions and/or commits in the past does not 
prove anything except that those cases might have been overseen or 
simply not thought about. We all make mistakes.


This has happened just recently, where Jacques merged some of those 
questioned PR's. Instead of correcting your own work, you refused to do 
so and Jacques did it for you afterwards to return to a reasonable use 
of specified labels.


Good for you that he was so kind to do what would have been your job.

[..]

Re: " in English, you often can use the same translation but in other
languages,
words are very different based on the context.

This argument is flawed.
As an example, the labels for 'productiId' in the various UILabel.xml files
in ofbiz-framework show for the German translation gives:


[...]

It makes perfect sense that the translations provided in OOTB OFBiz are 
constant throughout all applications.


And yet, it proves nothing.

As said several times before, context matters and the use case matters. 
OOTB OFBiz is neutral in it's terminology here. It would make no sense 
to translate those labels in different terminology.


A product in OFBiz can have a lot of characteristics and they have their 
own names in different businees domains. Just some examples from custom 
projects who use the following terms for a product ID / Produkt-Nr. in 
German:


Produkt-Nr., Artikel-Nr., Bauteil-Nr., Material-Nr., Achs-Artikel-Nr., 
Ersatzteil-Nr., ...


And those names are not necessarily equal in different applications for 
the same customer on the same OFBiz instance. Thats my experience.


Would it be reasonable to change "Produkt ID" to some of the examples 
above? No! Because it would only fit for some users, not for all users. 
Hence it's perfectly fine to keep it neutral and consistent throughout 
OOTB OFBiz.


And it's easy to translate "Produkt ID" to "Artikel-Nr." or something 
else throughout all applications, if you want to use exactly the same 
term in every application. Just a few seconds with search & replace and 
you are done. But if you cut that feature and start to have only one 
label for ALL occurences throughout ALL applications, you would have to 
re-introduce the specified labels to gain back this flexibility.


Not acceptable.

So, I think we will start an initiative to correct those cases who 
accidently introduced such a state. Thanks for the hint.




Michael continues to bring up this argument that 'users' are limited in
their choices, when changes are implemented in the OFBiz code by the
contributors.  This argument makes Michael 'complain' about a variety of
improvements brought forward, including (but not limited to) correcting
labels, removal of labels not applied by the project and removal of
commented out code.

This argument is flawed by design. Users are not limited in anyway, because
this project - as per ASF directives-  provides the source code in the form
of releases. Those users you keep bringing up are thus not limited in their
choices. That is - without limitation-  the promise of Open Source
solutions from the ASF.

If users are not content with what contributors incorporate into the
codebase, they have no grounds for complaints. Because of the following
statement of each file included:

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.


Your are throwing smoke candles here.  I did not say anything like that.

And I do not see what the ASF License has to do with the points I made. 
Those are far-fetched arguments so broad that they are always right. But 
they have nothing to do with the topic.


I said, in different contexts, that we should not cut down existing, 
valuable features and that we should always consider backwards 
compatibility and/or migration plans for users.


I am supporting OFBiz users for long time periods, my oldest 

Re: [jira] [Updated] (OFBIZ-6349) Replace ViewQuoteItems.ftl with form widgets

[Pierre Smits]

Hi Nicolas, Christian,

Are you both still collaborating to get this issue successfully resolved?
It seems to me that the both of you, being privileged contributors, should
easily get this in play.

Met vriendelijke groet,

Pierre Smits
*Proud* *contributor** of* Apache OFBiz  since
2008 (without privileges)
Proud contributor to the ASF since 2006
*Apache Directory , PMC Member*

Anyone could have been you, whereas I've always been anyone.


On Fri, Sep 18, 2015 at 4:20 PM Michael Brohl (JIRA) 
wrote:

>
>  [
> https://issues.apache.org/jira/browse/OFBIZ-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Michael Brohl updated OFBIZ-6349:
> -
> Sprint: Community Day 2 - 2015, Community Day 3 - 2015  (was:
> Community Day 2 - 2015)
>
> > Replace ViewQuoteItems.ftl with form widgets
> > 
> >
> > Key: OFBIZ-6349
> > URL: https://issues.apache.org/jira/browse/OFBIZ-6349
> > Project: OFBiz
> >  Issue Type: Improvement
> >  Components: order
> >Affects Versions: Trunk
> >Reporter: Christian Carlow
> >Assignee: Nicolas Malin
> > Attachments: OFBIZ-6349.patch
> >
> >
>
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>