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
