Jacques, you meant you agreed with Scott, right?
Scott, I got confused about how to handle this. Probably because I haven't implemented nor studied the customization of OfBiz for a customer yet. What did you mean by customizing the label for a particular deployment? How would I do that? I am not sure that´s how I want to handle. I do not have enough information yet. The other problem I have, it is not so much disabling the label during implementation. My bigger problem is to add the options necessary to operate in Brazil (in this particular case). In any case, I would like to have it OOTB. But there is something more. I am translating and adding the tag pt_BR. I am mind that means not only Portuguese but Brazilian Portuguese to be used in Brazil. So, this made me think what is the goal of the translation. My goal until now was to get OfBiz ready to be deployed in Brazil. So, I need not only the direct translations, but the local terms. After reading your email, at first I did not see any sense in direct translation, but after some thought, I came to the realization that direct translation serves to someone that wants to read Portuguese but lives in the US for example. In this case, it makes sense to have the direct translation. I also thought that direct translation should use the tag pt, and that's what in ofbiz right now. So, I do not know how to proceed. My goal is to prepare to deploy in Brazil. Should I change my plan of action? in this case how should I proceed? Please, advise. Regards, Raul On Fri, 23 Oct 2009 07:16:56 +0200 "Jacques Le Roux" <[email protected]> wrote: > I agree, else you lose label signification. Better to keep it as is > OOTB and remove it during local implementation if not used. > > Jacques > > From: "Scott Gray" <[email protected]> > > Hi Raul > > > > Personally I would just do a direct translation and leave it at > > that, if a particular method of deprecation isn't supported in a > > country that uses a certain language then it is up to the > > implementation team to make sure that it is disabled or otherwise > > unused. You can always customize the label for your particular > > deployment if that's how you want to handle the situation but I > > think labels in the project should always just be direct > > translations. > > > > Regards > > Scott > > > > HotWax Media > > http://www.hotwaxmedia.com > > > > > > On 23/10/2009, at 2:29 PM, Raul Sieberath wrote: > > > >> Hi, > >> > >> I am translating a label that it does not make sense in Portuguese. > >> > >> Here is the problem. > >> Double decline depreciatiion algorithm for fixed asset > >> > >> In Brazil, there is not a double depreciation. There is what is > >> called a accelerated depreciation with a difference. Depending on > >> how you setup your asset usage, there is a different coefficient. > >> They can be 1.0 (regular), 1.5 and 2.0 > >> Since it is an accounting expression, I do not know if I should > >> leave it in English. So, the person needs to look what it means > >> (very bad during a demo.) Or if I should translate to Portuguese > >> with an explanation. Maybe a tool tip where I could put a warning, > >> but then it would need to be implemented system wide. > >> > >> Is there away to suppress something to show if the system is setup > >> for a certain language? > >> > >> I am sure every translation comes to this problem. But I am not > >> aware the solution. > >> > >> Please advise. > >> > >> Raul > > > > >
