@ Juan, we know this is a notation issue and i hope that this will be “fixed” very soon. Please be so kind and open a bug report on bugs.otrs.org or just update an bug that I found which seems to be related to this issue: http://bugs.otrs.org/show_bug.cgi?id=6441

@ Carlos, changing the xx_Custom.pm doesn’t solve the problem of the differences between "to lock” and "the lock”. If you e.g. translate “lock” to “take over”, you will have locked tickets displayed as “take over” tickets, which is also with no sense ;-))

On 09.11.2011, at 13:28, Carlos Andrés Gallego Arboleda wrote:

Did you try change the es_Custom.pm
that's work's for me
El nov 9, 2011 7:10 a.m., "Juan Manuel Clavero Almirón" <juanm.clavero@ibsalut.es> escribió:
Hi,
thanks for your reply

the problem is that, in my Language, there is a big difference between the translation of 'lock' and the translation of 'locked'. This difference makes that the people don't understand if they see a 'lock' where it should be 'locked' (that is, where it should be an adjective, not a noun or verb)

my first aproximation (changing values in otrs.ticket_lock_type) was wrong because the values 'lock' and 'unlock' are hardcoded in the Perl modules and I'd have to change ~100 lines of code in several modules.

Instead, I've modified Ticket.pm to add a custom field to tickets ($Ticket{Locked} = 'Yes'|'No') and ' Ticket Information' in AgentTicketZoom to show this field (now it looks like "Locked:Yes | No"). I don't like this solution, but it works

Juan Clavero Almirón

-- Cheers, Nils

http://webint.cryptonode.de / a Fractal project